Step 2: Verify That the Secondary Path Is Established
When the secondary path is configured with the
standbystatement, the secondary path should be up but not active; it will become active if the primary path fails. A secondary path configured without thestandbystatement will not come up unless the primary path fails. To test that the secondary path is correctly configured and would come up if the primary path were to fail, you must deactivate a link or node critical to the primary path, then issue theshow mpls lsplsp-path-nameextensivecommand.Action
To verify that the secondary path is established, enter the following JUNOS CLI operational mode command:
user@R1>show mpls lsp extensiveSample Output
The following sample output shows a correctly configured secondary path before and after it comes up. In the example, interface
fe-0/1/0onR2is deactivated, which brings down the primary pathvia-r2. The ingress routerR1switches traffic to the secondary pathvia-r7.user@R1>show mpls lsp extensiveIngress 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: 3)10.0.12.14 S 10.0.24.2 S 10.0.45.2 SReceived RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.0.12.14 10.0.24.2 10.0.45.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 acceptedSecondary via-r7 State: DnSmartOptimizeTimer: 180No computed ERO.Created: Sat Apr 29 14:40:43 2006Total 1 displayed, Up 1, Down 0[edit interfaces]user@R2#deactivate fe-0/1/0[edit interfaces]user@R2#showinactive: fe-0/1/0 {unit 0 {family inet {address 10.0.12.14/30;}family iso;family mpls;}}user@R1>show mpls lsp name r1-to-r4 extensiveIngress LSP: 1 sessions192.168.4.1From: 192.168.1.1, State: Up, ActiveRoute: 0, LSPname: r1-to-r4ActivePath: via-r7 (secondary)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4Primary via-r2 State: DnPriorities: 6 6Bandwidth: 35MbpsSmartOptimizeTimer: 180Will be enqueued for recomputation in 14 second(s).10 Apr 29 14:52:33CSPF failed: no route toward 10.0.12.14[21 times]9 Apr 29 14:42:48 Clear Call8 Apr 29 14:42:48 Deselected as active7 Apr 29 14:42:48 Session preempted6 Apr 29 14:42:48 Down5 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 accepted*Standby via-r7 State: UpSmartOptimizeTimer: 180Computed ERO(S [L] denotes strict [loose] hops): (CSPF metric: 11)10.0.17.14 S 10.0.47.1 SReceived RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.0.17.14 10.0.47.15 Apr 29 14:42:48 Selected as active path4 Apr 29 14:41:12 Record Route: 10.0.17.14 10.0.47.13 Apr 29 14:41:12 Up2 Apr 29 14:41:12 Originate Call1 Apr 29 14:41:12 CSPF: computation result acceptedCreated: Sat Apr 29 14:40:43 2006Total 1 displayed, Up 1, Down 0What It Means
The sample output from egress router
R1shows a correctly configured standby secondary path in a down state because the primary path is still up. Upon deactivation of an interface (interface fe-0/1/0 on R2) critical to the primary path, the primary pathvia-r2goes down and the standby secondary pathvia-r7comes up, allowing R1 to switch traffic to the standby secondary path.