Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Resolved Issues


Table 4 lists resolved issues in NorthStar Controller Release 5.0.0. If an identifier is reported, it is the assigned identifier in the GNATS problem report tracking system.

Table 4: Resolved Issues in NorthStar Controller 5.0.0




Junos OS: An RPD core is observed when a user deactivates a template configuration.


Junos OS: PCE-initiated P2MP LSP goes through a make-before-break when the user modifies the template configuration in the router–even if that template is not mapped to an external controller.


Junos OS: When a PCE initiated P2MP LSP is created, the LSP is not created with the template bandwidth. The user has to deactivate and activate the template bandwidth, causing the LSP to be recreated with the configured template bandwidth.


When a user modifies device interface IP addresses resulting in ISIS adjacency or OSPF neighbor migration, there could be additional links created in NorthStar due to transient states being advertised into NorthStar.

For example, suppose an ISIS adjacency is formed between interface IP address of and, and the user modifies the device interface IP addresses to and In NorthStar, there might be three links displayed, each representing the ISIS adjacency:

  • The original adjacency of and in DOWN state

  • The transient adjacency of and in DOWN state

  • The new adjacency of and in UP state

The original and transient adjacencies are harmless to NorthStar path computation, as they are in DOWN state. The user can manually delete them to clean up the topology view.


When deleting a NETCONF-provisioned P2MP sub-LSP using the Modify P2MP Group window, the following error is displayed: “Invalid Request : Cannot read property '_TYPE' of null”. The sub-LSP is successfully deleted, regardless of this error. You reach the Modify P2MP Group window by selecting a group on the P2MP Group tab of the network information table and clicking the Modify button at the bottom of the table. You delete a sub-LSP by removing a Node Z from the Node Z list.


The binding SID SR LSP name must not contain the “-” character. For example, “bsid-between-P3-ASBR12” would be an invalid name where as “bsid_between_P3_ASBR12” would be valid.