Step 6: Verify the LSP Again
Action
To verify that the LSP is up and traversing the network as expected, enter the following command from the ingress, egress, and transit routers:
user@host>show mpls lsp extensiveSample Output
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.24 Oct 19 21:22:54 Selected as active path3 Oct 19 21:22:53 Record Route: 10.1.13.2 10.1.36.22 Oct 19 21:22:53 Up1 Oct 19 21:22:53 Originate CallCreated: Tue Oct 19 21:22:53 2004Total 1 displayed,Up 1, Down 0Egress LSP: 1 sessions10.0.0.1From: 10.0.0.6,LSPstate: Up, ActiveRoute: 0LSPname: R6-to-R1, LSPpath: PrimarySuggested label received: -, Suggested label sent: -Recovery label received: -, Recovery label sent: -Resv style: 1 FF, Label in: 3, Label out: -Time left: 117, Since: Tue Oct 19 21:17:42 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 2 receiver 39064 protocol 0PATH rcvfrom: 10.1.13.2 (so-0/0/2.0) 10 pktsAdspec: received MTU 1500PATH sentto: localclientRESV rcvfrom: localclientRecord route: 10.1.36.2 10.1.13.2 <self>Total 1 displayed,Up 1, Down 0Transit LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0user@R3>show mpls lsp extensiveIngress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Egress LSP: 0 sessionsTotal 0 displayed, Up 0, Down 0Transit LSP:2 sessions10.0.0.1From: 10.0.0.6, LSPstate: Up, ActiveRoute: 1LSPname: R6-to-R1, LSPpath: PrimarySuggested label received: -, Suggested label sent: -Recovery label received: -, Recovery label sent: 3Resv style: 1 FF, Label in: 100416, Label out: 3Time left: 139, Since: Tue Oct 19 21:05:11 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 2 receiver 39064 protocol 0PATH rcvfrom: 10.1.36.2 (so-0/0/3.0) 11 pktsAdspec: received MTU 1500 sent MTU 1500PATH sentto: 10.1.13.1 (so-0/0/2.0) 11 pktsRESV rcvfrom: 10.1.13.1 (so-0/0/2.0) 11 pktsExplct route: 10.1.13.1Record route: 10.1.36.2 <self> 10.1.13.110.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: 100448, Label out: 3Time left: 135, Since: Tue Oct 19 21:10:22 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 1 receiver 47951 protocol 0PATH rcvfrom: 10.1.13.1 (so-0/0/2.0) 4 pktsAdspec: received MTU 1500 sent MTU 1500PATH sentto: 10.1.36.2 (so-0/0/3.0) 4 pktsRESV rcvfrom: 10.1.36.2 (so-0/0/3.0) 4 pktsRecord route: 10.1.13.1 <self> 10.1.36.2Total 2 displayed,Up 2, Down 0user@R6>run show mpls lsp extensiveIngress LSP: 1 sessions10.0.0.1From: 10.0.0.6, State: Up, ActiveRoute: 1, LSPname: R6-to-R1ActivePath: (primary)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4*Primary State: UpComputed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)10.1.36.1 S 10.1.13.1 SReceived RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.1.36.1 10.1.13.119 Oct 19 21:09:52 Selected as active path18 Oct 19 21:09:52 Record Route: 10.1.36.1 10.1.13.117 Oct 19 21:09:52 Up16 Oct 19 21:09:52 Originate Call15 Oct 19 21:09:52 CSPF: computation result acceptedCreated: Tue Oct 19 18:30:09 2004Total 1 displayed,Up 1, Down 0Egress 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: 120, Since: Tue Oct 19 21:15:03 2004Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500Port number: sender 1 receiver 47951 protocol 0PATH rcvfrom: 10.1.36.1 (so-0/0/3.0) 4 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
The sample output from ingress router
R1and egress routerR6shows that the LSP is now traversing the network along the expected path, fromR1throughR3toR6, and the reverse LSP, fromR6throughR3toR1. In addition, the sample output from transit routerR3shows that there are two transit LSP sessions, one fromR1toR6, and the other fromR6toR1.