Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Issues

 

Table 3 lists known issues in NorthStar Controller Release 6.1.0. 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.1.0.

Identifier

Description

1449676

Toposerver and mladapter restarted intermittently.

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.

In NorthStar 6.0, this is fixed, but awaiting Junos OS 19.3R3 release to support it.

1497630

NorthStar pushes incomplete SRLG configuration to devices.

1502238

NorthStar Planner ingress and egress traffic has some interfaces shown with Terabyte information.

1534627

COS stats are missing for some Cisco devices.

NA

NorthStar Planner Desktop: There is no validation on the NorthStar Planner Desktop when a license upload is attempted.

NA

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

NA

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.

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

NorthStar web UI allows the user to create primary and secondary or standby LSPs that have different provisioning methods (PCEP and NETCONF). Using different provisioning methods can result in unintended setup due to the precedence of NETCONF over PCEP ephemeral state. While unlikely to be deliberate, NorthStar does not restrict the user input in those cases. This can result in unintentional mismatches.

NA

Elastic Search cleanup task should remove LSP events more frequently.

NA

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.

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

Interface name was copied over to persisted state when user add delay to a link.

NA

TopoServer fails to remove LSP config state.

NA

Provisioning NETCONF SR LSP with binding-sid label failed for version 18.3R2.4.

NA

For BMP topology acquisition, SR enabled-node might be displayed as not SR-enabled when the node has multiple IP addresses configured on the loopback interface.

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

Maintenance might lose its elements (nodes, links, SRLGs) during a TopoServer restart event such as HA switchover, sync network model, or reset network model.

NA

When a user specifies an SR traversing binding-sid with routing-method “default”, the status would be down with controller status “No path found”.

NA

When a user specifies an SR over binding-sid pair, the provisioned configlet has a remote ip-address 0.0.0.0, e.g. segment2 label 1048049 ip-address 0.0.0.0.

NA

Issue in provisioning SR-TE LSP via NETCONF with routeByDevice routing method on Junos version older than 19.1R1.1 when "Allow any SID at first hop" is enabled on the ingress node.

NA

Live network Tunnel specifications should not include explicit required path PR in most cases.

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

NETCONF color SR towards remote ASBR for Junos OS Release 19.1R1.1 and above is not working due to NETCONF template issue. The SR LSP Op status is showing as Up in NorthStar while the router shows the Op status as Down.

NA

NETCONF 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

Topology filter might not work properly for all nodes after performing process restart (on bmpMonitor, topoServer and topoFilter).

As a workaround, you can delete the impacted topology filter and add it back in again.

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.