Known Issues | Juniper Networks

The path computed by NorthStar for a standby LSP with maximum hop constraint could violate the configured constraint.

Workaround: There is no known workaround.

If bandwidth sizing is enabled for a container LSP, and the minimum variation threshold configured is 0, the bandwidth sizing feature is shown as disabled for the provisioned sub LSPs in the Web UI.

Workaround: Configure a value greater than 0 as the minimum variation threshold.

BMPMonitor does not close inactive TCP sessions. As a result, multiple sessions might appear between the BMPMonitor and the BMP client while using netstat.

Workaround: There is no known workaround.

There is a possibility that the PCS is unable to find LSP with link diversity in a topology that has multiple parallel links between nodes.

Workaround: There is no known workaround.

In a Diverse P2MP tree design, links utils displayed on the Links tab are prefixed with a minus sign.

Workaround: Save the network, and reopen it.

Some NETCONF P2MP sub-LSPs with virtual nodes as leaf nodes cannot be deleted from the controller.

Workaround: Manually delete NETCONF P2MP sub-LSPs from the router.

NorthStar does not support the changing or updating of interface details (under HA settings) after a cluster is deployed.

Workaround: Reset the VMs with new interfaces, and deploy the cluster afresh with updated interface details.

After running device collection, the Node OS version is not displayed under the Node tab.

Workaround: Specify the device OS version in the Device Profile.

The following logs are missing from the node: anycastGrouper.log, configServer.log, and prpdclient.log

Workaround: There is no known workaround.

After you restart the netconf:netconfd_00 process by running the supervisorctl restart netconf:netconfd_00 command, the Node OS version is not displayed under the Node tab.

Workaround: Specify the device OS version in the Device Profile.

You cannot create a NETCONF-provisioned SR LSP on an ACX Series router (running Junos Evolved OS 22.4 and later) with a name that was previously used for an SR LSP on the same router, and that was deleted earlier. If you do, you will see an error stating that the SR LSP already exists.

Workaround: Use a different name for the SR LSP.

If the NetFlow collector configuration option (aggregate-by-prefix) is set in cMGD, a restart of the netflowd will result in netflowd considering the aggregate-by-prefix option as disabled. In this scenario, the demands will not be aggregated as expected.

Workaround: Follow these steps to reconfigure the aggregate-by-prefix option:

Access the NorthStar server by using SSH, and execute the cmgd_cli tool to connect with cMGD CLI.
After you log in to the cMGD CLI, run the following command to check for existing configurations.
Do any one of the following.
1. If there is no existing configuration or if the feature is set to 'disable', exit the cMGD CLI by typing exit.
2. If the output of step 2 is always or unknown-destination, remove the existing configuration by entering the config mode.
  You must then reconfigure with the already existing settings and then commit changes.

There is no need to restart netflowd after this change. However, you must ensure the following:

Perform these steps after NorthStar (analytics) is upgraded to Release 6.2.7 since netflowd is restarted during the upgrade.
Perform these steps everytime netflowd restarts.

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.

In an Interactive Scenario, the path through the fail link is shown when you try to view paths for multiple tunnels at the same time.

From Junos OS Release 22.4R1 onwards, the multipath feature for PCEP segment routing-traffic engineering (SR-TE) is enabled, by default. NorthStar is not multipath capable and hence PCEP sessions are not established. To ensure that PCEP sessions are established when a PCC is running Junos OS Release 22.4R1 and above, disable the PCEP multipath feature using the following command: set protocols pcep disable-multipath-capability

Secondary path is not supported.

During bandwidth sizing, an active secondary LSP that has bandwidth sizing enabled might not get resized. When this issue occurs, the RSVP utilization of the links in secondary path could be incorrectly updated.

Workaround: There is no known workaround.

Topology filter using host name may occasionally be cleared if bmpMonitor process is restarted.

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.