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 6.2.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 Release 6.2.0.

Identifier

Description

1473362

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.

1497630

NorthStar pushes incomplete SRLG configuration to devices.

1547560

Planner archive considered IOS-XR multicast static route as unicast causing incorrect static path loop message.

NA

Inter-domain link discovery between two different IGP (ISIS and OSPF) inot working correctly.

NA

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.

NA

When upgrading from NorthStar Release 6.0, the default value of es_log_rollups_retention_days and es_log_retention_days might not be updated correctly in northstar.cfg, requiring the user to manually update those parameters (to 180d, 14d) after the upgrade .

NA

When a link is migrated from one endpoint to another (for example, link between between node A IP 10.0.0.1 and node B IP 10.0.0.2 is moved to between node A IP 10.0.01 and node C IP 10.0.0.2), the topology might show two operationally Down links.

NA

P2MP group creation currently only supports default routing method (TE metric). Changing the field to other routing method won't have effect.

NA

SR-TE LSP discovered from device collection will have Down operational status.

NA

User cannot modify P2MP LSPs discovered from device collection.

NA

Network archives with TE++ might not open in Planner.

NA

When using the Multipath SR routing engine, the corresponding LSP state is not updated quickly when a provisioning timeout occurs, and can be misleading. For example the "initialProvisioning (COMPLETE)" or "provisioning (COMPLETE)" state indicates that NorthStar is waiting for a reply from the router. This corresponds to the PCC_PENDING state in the default routing engine. This state will not be updated when reprovisioning is attempted. It will be updated when the timeout (up to 3 minutes) expires.

NA

Seen in JUNOS 19.2R1.8. The PCC may silently ignore some SR LSPs when several are provisioned in one PCInitiate message. In this case, NorthStar provisioning will timeout and the LSP will be reprovisioned. During that time the LSP will be down.

NA

NETCONFf non-color SR LSP with routing method = routebyDevice, LSP Op status will change to Down after running device collection. This is applicable for Junos OS Release 19.1R1.1 and above.

NA

When using the Device Configuration feature together with the Run Device Collection option, there is a possibility the latest configuration will not be picked up due to a timing issue. The workaround is to manually run device collection.

NA

If the "clear bgp session" command is used in cRPD, JunosVM, or any router sending BMP events to NorthStar when topology filter feature is used, you might see incorrect operational Down status labeled on links over topology. To clear and correct the status, you can perform Admin > System Settings > Advanced > Sync network model.

NA

Planner demand route optimization route cost was including additional cost due to MPLS tunnels traversing non shortest path.