The Operational State of the LSP Is Down
Problem
The Path Computation Server (PCS) has sent a provisioning order for the label-switched path (LSP) to the Path Computation Element (PCE) server. The PCS has received an acknowledgment from the PCE server. In addition, the PCS clears the controller status. However, the LSP still is not up (is not operational).
Solution
Check whether the LSP's operational status in the Op Status column on the Tunnel tab of the network information table is marked as Down. The LSP's operational status can be Down if the live and planned utilizations are different from each other. If the operational status of the LSP is marked as Down, the Path Computation Client (PCC) cannot signal the LSP.
-
Live utilization—The routers in the network use this utilization to signal a path. This utilization value is learned from the traffic engineering database through the BGP Monitoring Protocol (BMP).
The following is a sample log entry of the Path Computation Server (PCS). In particular, note the reservable bandwidth (
reservable_bw) entries that advertise the RSVP live utilization on the link:Note:The logs that you view may differ from the logs in this document. The logs change based on the installed version of Paragon Automation.
Apr 25 10:10:11.475686 user-PCS PCServer [<-TopoServer] LINK UPDATE: ID=L10.105.107.1_10.105.107.2 status=UP nodeA=0110.0000.0105 nodeZ=0110.0000.0107 protocols=(260)ISIS2,MPLS Apr 25 10:10:11.475690 user-PCS PCServer [A->Z] ID=L10.105.107.1_10.105.107.2 IP address=10.105.107.1 bw=10000000000 max_rsvp_bw=10000000000 te_metric=10 color=0 reservable_bw={9599699968 8599699456 7599699456 7599699456 7599699456 7599699456 7599699456 7099599360 } Apr 25 10:10:11.475694 user-PCS PCServer [Z->A] ID=L10.105.107.1_10.105.107.2 IP address=10.105.107.2 bw=10000000000 max_rsvp_bw=10000000000 te_metric=10 color=0 reservable_bw={10000000000 10000000000 10000000000 8999999488 7899999232 7899999232 7899999232 7899999232 } -
Planned utilization—The controller uses this type of utilization for path computation. The controller computes this utilization value through the Path Computation Element Protocol (PCEP). The controller computes this value when the router advertises the LSP and communicates to the controller the bandwidth and path the LSP must use.
Following is a sample log entry that the PCS generates. In particular, note the bandwidth (
bw) and record route object (RRO) entries that advertise the RSVP planned utilization on the link:Apr 25 10:06:45.208021 ns-PCS PCServer [<-TopoServer] routing_key = ns_lsp_link_key Apr 25 10:06:45.208034 ns-PCS PCServer [<-TopoServer] JTAC@10.0.0.102, LSP event=(2)UPDATE request_id=0 tunnel_id=9513 lsp_id=1 report_type=STATE_CHANGE Apr 25 10:06:45.208039 ns-PCS PCServer JTAC@10.0.0.102, lsp add/update event lsp_state=ACTIVE admin_state=UP, delegated=true Apr 25 10:06:45.208042 ns-PCS PCServer from=10.0.0.102 to=10.0.0.104 Apr 25 10:06:45.208046 ns-PCS PCServer primary path Apr 25 10:06:45.208049 ns-PCS PCServer association.group_id=128 association_type=1 Apr 25 10:06:45.208052 ns-PCS PCServer priority=7/7 bw=100000 metric=30 Apr 25 10:06:45.208056 ns-PCS PCServer admin group bits exclude=0 include_any=0 include_all=0 Apr 25 10:06:45.208059 ns-PCS PCServer PCE initiated Apr 25 10:06:45.208062 ns-PCS PCServer ERO=0110.0000.0102--10.102.105.2--10.105.107.2--10.114.117.1 Apr 25 10:06:45.208065 ns-PCS PCServer RRO=0110.0000.0102--10.102.105.2--10.105.107.2--10.114.117.1 Apr 25 10:06:45.208068 ns-PCS PCServer samepath, state changed
The two utilization values can be different from each other. The difference might interfere with the successful computation or signaling of the path. For example:
-
If the planned utilization is higher than the live utilization, a path computation issue could arise. From the perspective of the PCS, it might seem like no bandwidth is available for the new path. Therefore, the PCS cannot compute the path. However, sufficient bandwidth might be available to compute the path.
-
If the planned utilization is lower than the live utilization, the PCC does not signal the path. This is because, from the perspective of the PCC, it might seem like no bandwidth is available to signal the new path.
To view utilization in the GUI, navigate to the Topology (Network > Topology) page. In the Link tab of the network information table, the RSVP Live Util AZ and RSVP Live Util ZA columns indicate the RSVP live utilization. The RSVP Util AZ and RSVP Util ZA columns indicate the RSVP planned utilization. The topology map reflects the live utilization from the PCC and the planned utilization that the Controller computes based on planned properties.
You can compare the entries in these columns to check whether any mismatch exists between the live and the planned utilizations. To solve any mismatch, you can try re-synchronizing the network model from the Pathfinder page (Configuration > Network Settings > Pathfinder Settings > Advanced Settings) in the GUI. See Synchronize the Network Model for more information about re-synchronizing the network model.