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.2.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.2.1.

Identifier

Description

1449676

Toposerver and mladapter restart intermittently.

1502238

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

1534627

CoS statistics missing when performing SNMP task collection.

1563326

PCEP sessions unable to upgrade to some versions of Junos EVO and newer versions of third-party IOS-XR.

1624975

P2MP tunnels originating from Cisco IOS XR devices are duplicated.

As a workaround, enable PCEP on Cisco IOS XR devices before running device collection.

NA

SR-LSP is not supported in BGP confederation topology.

NA

TE-Tunnel should use SIGNAME, if available, to prevent creation of duplicate or deactivated tunnels in NorthStar Planner.

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

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

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 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

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

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

Some TE++ tunnel specifications for NorthStar Planner Live Network Archive do not include the explicit required path PR.

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

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.

N/A

Advanced filter cannot filter LSP coloring for tunnels.

N/A

Tunnel coloring does not work for partial match. For example, if you filter an LSP for both red and blue, you must specify the exact wording (i.e. red | blue) in the filter.

NA

NorthStar is unable to delegate or remove ODN SR LSPs.

As a workaround, add or remove the lsp-external-controller pccd statement in your router configuration.

NA

After issuing a service northstar restart command, logstash might show an unexpected error message.

As a workaround, restart the logstash process.

NA

Scheduling for P2MP LSP is lost after a Path Computation Server (PCS) restart. This can cause an inactive P2MP LSP to be reactivated.

The PCS restarts when you sync or reset the topology, during an HA switchover, when you upgrade NorthStar or install a patch.

NA

When the NorthStar Controller is in High Availability (HA) mode, a timeout error might occur when deleting a dummy node.

NA

NorthStar does not support provisioning of Netconf inter-AS SR LSP that has ECMP paths towards its destination with routeByDevice as routing method.

NA

SR enabled mode shows “SR disabled” if NorthStar does not identify a node with the correct primary loopback address. This can cause some of the node attributes (i.e. SR enabled flag) to be incorrect.

NA

When you change the time zone and date/time user preferences in NorthStar, the changes do not take effect.

NA

When a P2MP group is scheduled and its sub-LSP is activated, the sub-LSP expires and is reactivated after the P2MP group scheduled end time.

NA

Stale demands cannot be deleted after NS image is upgraded

The workaround is to reload the demands and then remove stale duplicated demands from the database.

NA

Bandwidth values specified in the EPE Settings page (Kb/s, b/s, kb/s, Mb/s) only show in b/s in the EPE Properties tab.

The workaround is to enter the bandwidth values in bits per second when adding or modifying a link. For example, enter 10000000 if you want 10 Mbs, regardless of the bandwidth unit setting in the EPE Settings.