Table 4 lists resolved 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 4: Resolved Issues in NorthStar Controller 4.3.0
After an interruption due to network issues, node hostnames were missing and LSP provisioning from the NorthStar UI failed.
LSPs were rerouted based on incorrect interface utilization information.
Duplicated inter-AS nodes and inter-AS links were down.
LSPs were not being refreshed properly via the NorthStar UI, and tunnels were slow to refresh and display on Tunnel tab of the network information table.
Requests to provision LSPs through the inter-AS were being rejected.
Database initialization failed during the upgrade.
PCServer abrupt restart.
Link latency collection tasks skipped nodes due to a name change.
LSP hourly traffic graph showed incorrect values.
Many LSPs showed OP Status as “Unknown” in network information table Tunnel tab.
Duplicate ASBR nodes in the network model caused NorthStar to reprovision LSPs that transit via the ASBR node.
After executing Reset Network Model, the inter-AS link state was reported as down when it was actually up. This caused unnecessary path changes since there was no failure.