Table 3 lists known issues that are newly identified in NorthStar Release 6.0.1. If an identifier is reported, it is the assigned identifier in the GNATS problem report tracking system.
Table 3: Known Issues in NorthStar Controller Release 6.0.1.
Dashboard LSP Hop Count chart shows incorrect information.
Fresh install for analytics has connection refused error.
Elastic Search cleanup task should remove LSP events more frequently.
Core regression link update - unable to delete old link.
P2MP: NorthStar cannot process simultaneous different operations that modify a single device/LSP (POST and PATCH, POST and DELETE, PATCH and DELETE). To work around this issue, complete the first request and verify success in the NorthStar UI or on the device before submitting the next request.
Need to add Cassandra cluster port check in net_setup.
NorthStar cannot discover overload bit set properly in ISIS network by NTAD.
You cannot create an SR LSP with loose hops when the routing method is routeByDevice.
There is a BMP OSPF link migration merging link issue.
Table 4 lists known issues in NorthStar Controller Release 6.0.0. If an identifier is reported, it is the assigned identifier in the GNATS problem report tracking system.
Table 4: Known Issues in NorthStar Controller Release 6.0.0.
Before performing a fresh install of NorthStar, you must
Toposerver and mladapter restarted intermittently.
PRPD does not remove prefixes (prefixes that have mapping) that were withdrawn by PCCs.
Elasticsearch cluster health was Red.
No NorthStar LSP traffic or interface traffic statistics were displaying in the UI.
NorthStar cRPD does not forward adjacency-SID data to the topology server. As a consequence, cRPD cannot be used for applications that use segment routing (including EPE steering). This is due to Junos OS behavior.
In NorthStar 6.0, this is fixed, but awaiting Junos OS 19.3R3 release to support it.
NorthStar Planner Hardware Inventory had missing and incorrect fields.
Return Delegation to PCC does not work.
Routes were missing when trying to import IGP topology into BGP-LS table.
Node report showed incorrect count of LSPs per node.
Cassandra password got reset to default for user cassandra.
NorthStar pushed incomplete SRLG configuration to devices.
Migrating IP addresses between links causes the links to be marked as failed.
NorthStar Planner ingress and egress traffic had some interfaces shown with Terabyte information.
NorthStar Planner showed incomplete device name in traffic file.
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.
NorthStar Planner Desktop: There is no validation on the NorthStar Planner Destop when a license upload is attempted.
The routing method is CSPF for P2MP groups which are configured from devices (as opposed to from within NorthStar), when the expected routing method is routeByDevice.
If you change the cMGD password using net_setup.py (Option D > Option 8: Change cMGD Root Password), you must restart the following processes:
Creating a loop in the path of an SR LSP causes the operational status to be Down for the LSP.
Modifying a sub-LSP ERO for a scheduled P2MP tree causes the sub-LSP to be provisioned immediately because the provision order does not contain the schedule.
Bulk modification for Setup and Hold priority is not working.