Verifying the PCE-Initiated LSP Status When the LSP Is Externally Provisioned
Purpose Verify the status of the PCE-initiated LSP.
Action From operational mode, run the show mpls lsp externally-provisioned detail command.
user@PCC# show mpls lsp externally-provisioned detail
Ingress LSP: 1 sessions
10.0.101.10
From: 10.0.102.9, State: Up, ActiveRoute: 0, LSPname: lsp15
ActivePath: path1 (primary)
Link protection desired
LSPtype: Externally Provisioned, Penultimate hop popping
LSP Control Status: Externally controlled
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary path1 State: Up
Priorities: 7 0
Bandwidth: 8Mbps
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 3)
10.0.102.10 S 10.0.101.9 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node
10=SoftPreempt 20=Node-ID):
10.0.102.10 S 10.0.101.9 S
Meaning In the output, the LSPtype output field shows that the LSP is externally provisioned.
The PCEP session between PCC and PCE1 is up, and the PCC receives the following
PCE-initiated LSP parameters:
• ERO (path)—10.0.102.10 and 10.0.101.9
• Bandwidth—8 Mbps
• Priority—7 0 (setup and hold values)
Related
Documentation
Support of the Path Computation Element Protocol for RSVP-TE Overview on page 692•
• Example: Configuring the Path Computation Element Protocol for MPLS RSVP-TE on
page 707
• Configuring Path Computation Element Protocol for MPLS RSVP-TE with Support of
PCE-Initiated LSPs on page 732
731Copyright © 2017, Juniper Networks, Inc.
Chapter 23: Configuring Path Computation Element Protocol (PCEP)
To Next Page
Loading...
Need help?
General
