Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Issues

 

Table 2 lists known issues in NorthStar Controller Release 4.3.0. The identifier associated with each entry is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

Table 2: Known Issues in NorthStar Controller 4.3.0

Identifier

Description

NA

NorthStar web UI Planner: Network spec files will be overwritten if an existing network name exists when using Save or Save As. A warning dialog appears if an existing name is found using Save As.

NA

NorthStar web UI Planner: If a user leaves the browser open without activity for a period of time, the session may get disconnected and not be able to fully resume later. As a result, some UI operations may not response properly. The workaround is to use the close network menu option and reopen the network.

NA

The binding SID SR LSP name specified in NorthStar 4.3.0 release 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. This issue will be fixed in a future release.

NA

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 10.11.11.1 and 10.11.11.2, and the user modifies the device interface IP addresses to 10.11.11.5 and 10.11.11.6. In NorthStar, there might be three links displayed, each representing the ISIS adjacency:

  • The original adjacency of 10.11.11.1 and 10.11.11.2 in DOWN state

  • The transient adjacency of 10.11.11.5 and 10.11.11.2 in DOWN state

  • The new adjacency of 10.11.11.5 and 10.11.11.6 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.

NA

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.

1421093

Junos OS: A user can configure template in the router and map that template with an external controller. Router inherits the required configuration from the template and then provisions the external controller initiated LSP. Unbinding the template from the external controller or changing template configuration might trigger deletetion of the PCE initiated LSPs (only LSPs which are using that particular template). Later, the LSPs are re-provisioned by external controller.

1419356

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

1420702

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.

1421106

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.