Known Issues

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

• When an interface's description is updated on the router and the device collection is run, the updated description is not visible on the UI and in the REST API output.

  Workaround: Restart web processes on the application server. In case of a cluster setup, restart web processes on the active server.

• When the control of a NETCONF-provisioned LSP that has been provisioned by using the LSP Scheduling feature is delegated to NorthStar, it fails to remove that LSP on expiry of the scheduled period.

  Workaround: Manually delete the LSP.

• A standby LSP (PCE-initiated or PCC-delegated) is not resized to a lower bandwidth when the primary LSP becomes active again, leading to excess bandwidth being reserved for the standby LSP.

• Container LSP loses sub LSP information when PCServer restarts.

• Junos OS Release 22.4R1 and later have a limitation with SR-TE LSPs. For PCEP sessions to be established, you must disable the multipath feature using the following command:

  Secondary path is not supported.

• Topology filter using hostname may occasionally be cleared if bmpMonitor process is restarted.

• The bandwidth in Demand Path and Diversity in Report Manager (NorthStar Planner) does not match the Demand tab.

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

  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 is uploaded.

  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 different operations that modify a single device/LSP (POST and PATCH, POST and DELETE, PATCH and DELETE) simultaneously. 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 is copied over to a persisted state when you add delay to a link.

  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.

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

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

  Workaround: There is no known workaround.

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

• Top N demand prefixes are not working in NorthStar Controller.

  Workaround: There is no known workaround.

• The demand aging task is not completing execution.

  Workaround: There is no known workaround.