Step 2: Verify That the Primary Path Is Operational
Primary paths must always be used in the network if they are available, therefore an LSP always moves back to the primary path after a failure, unless the configuration is adjusted. For more information on adjusting the configuration to prevent a failed primary path from reestablishing, see Preventing Use of a Path That Previously Failed.
Action
To verify that the primary path is operational, enter the following JUNOS command-line interface (CLI) operational mode commands:
user@host>show mpls lsp extensive ingressuser@host>show rsvp interfaceSample Output 1
user@R1>show mpls lsp extensive ingressIngress LSP: 1 sessions192.168.5.1From: 192.168.1.1, State: Up, ActiveRoute: 0, LSPname: r1-to-r5ActivePath: via-r2 (primary)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4*Primary via-r2 State: UpPriorities: 6 6Bandwidth: 35MbpsSmartOptimizeTimer: 180Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 11)10.0.12.14 S 10.0.24.2 SReceived RRO(ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.0.12.14 10.0.24.25 Apr 29 14:40:43 Selected as active path4 Apr 29 14:40:43 Record Route: 10.0.12.14 10.0.24.23 Apr 29 14:40:43 Up2 Apr 29 14:40:43 Originate Call1 Apr 29 14:40:43 CSPF: computation result acceptedStandby via-r7 State: DnSmartOptimizeTimer: 180No computed ERO.Created: Sat Apr 29 14:40:43 2006Total 1 displayed, Up 1, Down 0Sample Output 2
user@R1>show rsvp interfaceRSVP interface: 3 activeActive Subscr- Static Available Reserved HighwaterInterface State resv iption BW BW BW markfe-0/1/0.0 Up 2 100%100Mbps100Mbps 0bps 0bpsfe-0/1/1.0 Up 1 100%100Mbps100Mbps 0bps 0bpsso-0/0/3.0 Up 1 100%155.52Mbps155.52Mbps 0bps 0bpsWhat It Means
Sample output 1 shows that the LSP is operational and is using the primary path (
via-r2) withR2(10.0.12.14) andR4(10.0.24.2) as transit routers. The priority values are the same for setup and hold,6 6. Priority 0 is the highest (best) priority and 7 is the lowest (worst) priority. The JUNOS software default for setup and hold priority is 7:0. Unless some LSPs are more important than others, preserving the default is a good practice. Configuring a setup priority that is better than the hold priority is not allowed, resulting in a failed commit in order to avoid preemption loops.