LSP Controller Statuses Overview

A label-switched path (LSP) passes through various provisioning states before it is successfully provisioned in the network. You can view these provisioning states in the Controller Status column on the Tunnel tab of the network information table (Network > Topology).

Table 1 lists the various LSP controller statuses and their meanings.

Table 1: LSP Controller Statuses
This Controller Status	Indicates That
FAILED	The controller has failed to provision the LSP.
PENDING	The Path Computation Server (PCS) has sent a provisioning order for the LSP to the Path Computation Element (PCE) server. The PCS is awaiting a response from the PCE server.
PCC_PENDING	The PCE server has sent an LSP provisioning order to the Path Computation Client (PCC). The PCS is awaiting a response from the PCC.
NETCONF_PENDING	The PCS has sent an LSP provisioning order to the netconfd process. The PCS is awaiting a response from the netconfd process.
PRPD_PENDING	The PCS has sent an LSP provisioning order to the programmable routing protocol process (daemon) [PRPD] client to provision a BGP route. The PCS is awaiting a response from the PRPD client.
SCHEDULED_DELETE	The PCS has scheduled the LSP to be deleted; the PCS will send the deletion provisioning order to the PCC.
SCHEDULED_DISCONNECT	The PCS has scheduled the LSP to be disconnected. The LSP will be moved to Shutdown status. Therefore, the LSP is retained in the Pathfinder database and the Persist state is associated with it. The LSP is not used in Constrained Shortest Path First (CSPF) calculations.
NoRoute_Rescheduled	The PCS hasn’t found a path for the LSP. The PCS will scan the LSPs periodically and will try to find a path for the LSP that is not routed. The PCS will then schedule the reprovisioning of the LSP.
FRR_DETOUR_Rescheduled	The PCS has detoured the LSP and rescheduled the LSP’s re-provisioning.
Provision_Rescheduled	The PCS has scheduled the LSP to be provisioned.
Maint_NotHandled	The LSP is not a part of the ongoing maintenance event, because Pathfinder does not control the LSP.
Maint_Rerouted	The PCS has rerouted the LSP due to maintenance.
Callsetup_Scheduled	The PCS must provision the LSP when an event that triggers LSP provisioning starts.
Disconnect_Scheduled	The PCS must disconnect the LSP when the event that triggers LSP provisioning ends.
No path found	The PCS was unable to find a path for the LSP.
Path found on down LSP	The PCS has found a path for the LSP, but the PCE server has reported that the LSP is down.
Path include loops	The segment routing-LSP has one or more loops.
Maint_NotReroute_DivPathUp	The PCS doesn't reroute the LSP due to a maintenance event, because a standby path is already up and running.
Maint_NotReroute_NodeDown	The PCE doesn't reroute the LSP because the maintenance event is for the endpoints of the LSP.
PLANNED_LSP	The LSP must be provisioned but is not in the provisioning queue yet.
PLANNED_DISCONNECT	The LSP must be disconnected but is not in the provisioning queue yet.
PLANNED_DELETE	The LSP must be deleted but is not in the provisioning queue yet.
Candidate_ReOptimization	The PCS has selected the LSP as a candidate for reoptimization.
Activated (used_by_primary)	The secondary path for the LSP is activated.
Time_Expired	The scheduled window for the LSP has expired.
PCEP_Capability_not_supported	The device may not support PCEP. If the device supports PCEP, it may not be configured, may be disabled, or may be misconfigured on the device.
De-activated	The controller has deactivated the secondary LSP.
NS_ERR_NCC_NOT_FOUND	The controller is unable to use the NETCONF Connection Client (NCC) to establish a NETCONF connection with the device to create a NETCONF-based LSP. Workaround: Log in to the NETCONF pod and view the logs to troubleshoot the issue. See View Logs for the procedure to view logs: To solve a synchronization issue, you can re-synchronize the network model from the Pathfinder page (Configuration > Network Settings > Pathfinder Settings > Advanced Settings) in the GUI. See Synchronize the Network Model for details. If the NETCONF log doesn't print a message, restart the NETCONF pod on the Kubernetes server by using one of the following commands: kubectl delete pod netconf-pod-name -n northstar kubectl rollout restart deployment ns-netconfd -n northstar
SR LSP provisioning requires LSP stateful SR capability	The Junos OS device is not configured with the segment routing capability. Configure the following command on the Junos OS device through the CLI to provision the segment routing LSP: set protocols pcep pce name spring-capability

To decide the corrective actions that you must perform to solve problems related to the provisioning of LSPs, refer to the log files. You can view the log files either from the Logs page (Monitoring > Logs) in the GUI or by manually logging in to the respective pods by using the CLI. To find the procedure for viewing logs from the CLI, see General Troubleshooting Techniques.