Step 1: Verify the LSP
Action
To verify the LSP, enter the following command on the ingress, transit, and egress routers:
user@host>show mpls lsp extensiveSample Output 1
user@R1>show mpls lsp extensiveIngress LSP: 1 sessions10.0.0.6From: 10.0.0.1, State: Dn, ActiveRoute: 0,LSPname: R1-to-R6ActivePath: (none)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4Primary State: Dn11 Oct 19 18:06:04 No Route toward dest[78 times]10 Oct 19 17:08:09 Deselected as activeCreated: Mon Oct 18 21:48:42 2004Total 1 displayed, Up 0,Down 1Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Sample Output 2
user@R3>show mpls lsp extensiveIngress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Sample Output 3
user@R6>show mpls lsp extensiveIngress LSP: 1 sessionsTo From State Rt ActivePath P LSPname10.0.0.1 10.0.0.6 Dn 0 - R6-to-R1Total 1 displayed, Up 0,Down 1Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Sample Output 4
user@R1>show mpls lsp extensiveIngress LSP: 1 sessions10.0.0.6From: 10.0.0.1, State: Up, ActiveRoute: 1,LSPname: R1-to-R6ActivePath: (primary)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4*Primary State: UpReceived RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.1.13.2 10.1.36.25 Oct 19 10:37:55 Selected as active path4 Oct 19 10:37:55 Record Route: 10.1.13.2 10.1.36.23 Oct 19 10:37:55 Up2 Oct 19 10:37:10 No Route toward dest[1029 times]1 Oct 18 21:48:42 Originate CallCreated: Mon Oct 18 21:48:42 2004Total 1 displayed,Up 1, Down 0Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Sample Output 5
user@R3>show mpls lsp extensiveIngress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP: 1 sessions10.0.0.6From: 10.0.0.1, LSPstate: Up, ActiveRoute: 1LSPname: R1-to-R6, LSPpath: PrimarySuggested label received: -, Suggested label sent: -Recovery label received: -, Recovery label sent: 3Resv style: 1 FF, Label in: 100368, Label out: 3Time left: 154, Since: Tue Oct 19 10:25:24 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 1 receiver 47933 protocol 0PATH rcvfrom: 10.1.13.1 (so-0/0/2.0) 209 pktsAdspec: received MTU 1500 sent MTU 1500PATH sentto: 10.1.36.2 (so-0/0/3.0) 209 pktsRESV rcvfrom: 10.1.36.2 (so-0/0/3.0) 209 pktsRecord route: 10.1.13.1 <self> 10.1.36.2Total 1 displayed, Up 1, Down 0Sample Output 6
user@R6>show mpls lsp extensiveIngress LSP: 1 sessions10.0.0.1From: 10.0.0.6, State: Dn, ActiveRoute: 0,LSPname: R6-to-R1ActivePath: (none)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4Primary State: Dn2 Oct 19 13:01:54 10.1.56.2:MPLS label allocation failure[9 times]1 Oct 19 12:57:51 Originate CallCreated: Tue Oct 19 12:57:51 2004Total 1 displayed, Up 0,Down 1Egress LSP: 1 sessions10.0.0.6From: 10.0.0.1, LSPstate: Up, ActiveRoute: 0LSPname: R1-to-R6, LSPpath: PrimarySuggested label received: -, Suggested label sent: -Recovery label received: -, Recovery label sent: -Resv style: 1 FF, Label in: 3, Label out: -Time left: 148, Since: Tue Oct 19 10:30:03 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 1 receiver 47933 protocol 0PATH rcvfrom: 10.1.36.1 (so-0/0/3.0) 206 pktsAdspec: received MTU 1500PATH sentto: localclientRESV rcvfrom: localclientRecord route: 10.1.13.1 10.1.36.1 <self>Total 1 displayed, Up 1, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0What It Means
Sample Outputs 1, 2, and 3 show that the LSP and the reverse LSP are down:
- Sample Output 1 from ingress router
R1shows that LSPR1-to-R6does not have a route towards the destination (R6).- Sample Output 2 from transit router
R3shows that there are no LSP sessions.- Sample Output 3 from egress router
R6also shows that reverse LSPR6-to-R1is down.Sample Outputs 4, 5, and 6 show that the LSP is up and the reverse LSP is down:
- Sample Output 4 from ingress router
R1shows that LSPR1-to-R6is up and there are no egress LSP sessions.- Sample Output 5 from transit router R3 shows that there is one ingress LSP session (
R1-to-R6)and no egress LSP sessions.- Sample Output 6 from egress router
R6shows that LSPR6-to-R1is down due to an MPLS label allocation failure.