Step 5: Verify the LSP Again

Action

To verify that the LSP is up and traversing the network as expected, enter the following command:

user@host> show mpls lsp extensive

Sample Output 1

user@R1> show mpls lsp extensive

Ingress LSP: 1 sessions

10.0.0.6

  From: 10.0.0.1, State: Up, ActiveRoute: 1, LSPname: R1-to-R6

  ActivePath:  (primary)

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

 *Primary                    State: Up

    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)

 10.1.13.2 S 10.1.36.2 S 

    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 
10=SoftPreempt):

          10.1.13.2 10.1.36.2

   112 Sep 21 16:27:33 Record Route:  10.1.13.2 10.1.36.2

   111 Sep 21 16:27:33 Up

   110 Sep 21 16:27:33 CSPF: computation result accepted

   109 Sep 21 16:27:33 CSPF: link down/deleted 
10.1.12.1(R1.00/10.0.0.1)->10.1.12.2(R2.00/10.0.0.2)

   108 Sep 21 16:27:33 CSPF: link down/deleted 
10.1.15.1(R1.00/10.0.0.1)->10.1.15.2(R5.00/10.0.0.5)

   [Output truncated...]

  Created: Sat Jul 10 18:18:44 2004

Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions

10.0.0.1

  From: 10.0.0.6, LSPstate: Up, ActiveRoute: 0

  LSPname: R6-to-R1, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: -

  Resv style: 1 FF, Label in: 3, Label out: -

  Time left:  149, Since: Tue Sep 21 16:29:43 2004

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 2 receiver 39024 protocol 0

  PATH rcvfrom: 10.1.13.2 (so-0/0/2.0) 7 pkts

  Adspec: received MTU 1500 

  PATH sentto: localclient

  RESV rcvfrom: localclient 

  Record route: 10.1.36.2 10.1.13.2 <self>  

Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

Sample Output 2

[edit protocols mpls]

user@R1# show 

label-switched-path R1-to-R6 {

    to 10.0.0.6;

}

interface fxp0.0 {

    disable;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

interface so-0/0/2.0;

What It Means

Sample Output 1 from ingress router R1 shows that the LSP is now traversing the network along the expected path, from R1 through R3 to R6, and the reverse LSP, from R6 through R3 to R1.

Sample Output 2 from ingress router R1 shows that the LSP is forced to take the intended path because MPLS is deactivated on R1 interfaces so-0/0/0.0 and so-0/0/1.0. If these interfaces were not deactivated, even though the configuration is now correct, the LSP would still traverse the network through the alternate path.