Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Known Issues

This section lists the known issues in NorthStar Controller Release 6.2.4. If an identifier is reported, it is the assigned identifier in the GNATS problem report tracking system.

  • SR-LSP is not supported in BGP confederation topology.

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

  • Audit logs are not generated for REST API calls made for reset topology, sync topology, and optimize now operations.

    Workaround: There is no known workaround.

  • Filter is not working properly for audit log path, description, and status.

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

  • Elastic Search cleanup task should remove LSP events more frequently.

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

  • TopoServer fails to remove LSP config state.

    Workaround: There is no known workaround.

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

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

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

    Workaround: You can delete the impacted topology filter and add it back in again.

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

    Workaround: Restart the logstash process.

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

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

    Workaround: There is no known workaround.

  • If there is area multiple paths with equal cost existing towards a destination, you cannot provision an inter-AS SR LSP with routing method routebydevice by using the NETCONF provisioning method.

  • The RSVP Utilization of links carrying Container sub-LSP could be incorrectly computed.

    Workaround: There is no known workaround.

  • The RSVP Utilization of links carrying Container sub-LSPs is incorrectly computed when you sync the network model (by clicking the Sync option under the Sync Network Model in Advanced Settings).

    Workaround: There is no known workaround.

  • NorthStar is creating P2MP diverse tree designs without a calculated explicit route object (ERO) under planned properties.

    Workaround: There is no known workaround.

  • Bandwidth reservation for PCC-controlled RSVP TE-LSPs with non-routeByDevice routing method is not accounted.

    Workaround: There is no workaround for this issue. To prevent this issue, you should avoid reserving bandwidth for PCC-controlled RSVP TE-LSPs that have non-routeByDevice routing method.

  • You cannot modify an LSP originating from a Cisco IOS-XR device through NorthStar Controller after running device collection as follows:

    1. LSP is discovered through PCEP.

    2. LSP is modified from the controller.

    3. Device collection is run on the ingress router.

    This issue is occurring because, in the API call to modify the LSP, path_name for the LSP is null.

    To avoid this issue, ensure to run device collection for retrieving the path_name from the router’s configuration once on the ingress router (step 3) before modifying the LSP from the controller (step 2).

    Workaround: To recover from this issue:

    1. Force delete LSP user information:

    2. Modify the LSP from the controller.

  • Path computation server (PCS) is not updating demand parameters in the database correctly leading to incorrect mapping of LSP to demands.

    Workaround: There is no known workaround.

  • Rest handler is not updating destination IP address for LSP correctly in the database.

    Workaround: There is no known workaround.