Step 5: 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 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

    5 Oct 21 15:52:07 Selected as active path

    4 Oct 21 15:52:07 Record Route:  10.1.13.2 10.1.36.2

    3 Oct 21 15:52:07 Up

    2 Oct 21 15:52:07 Originate Call

    1 Oct 21 15:52:07 CSPF: computation result accepted

  Created: Thu Oct 21 15:52:06 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:  142, Since: Thu Oct 21 15:41:59 2004

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

  Port number: sender 2 receiver 39082 protocol 0

  PATH rcvfrom: 10.1.13.2 (so-0/0/2.0) 17 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

user@R3> show mpls lsp extensive

Ingress LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

Egress LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

Transit LSP: 2 sessions

10.0.0.1

  From: 10.0.0.6, LSPstate: Up, ActiveRoute: 1

  LSPname: R6-to-R1, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 3

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

  Time left:  125, Since: Thu Oct 21 15:29:26 2004

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

  Port number: sender 2 receiver 39082 protocol 0

  PATH rcvfrom: 10.1.36.2 (so-0/0/3.0) 17 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.1.13.1 (so-0/0/2.0) 17 pkts

  RESV rcvfrom: 10.1.13.1 (so-0/0/2.0) 17 pkts

  Explct route: 10.1.13.1 

  Record route: 10.1.36.2 <self> 10.1.13.1  

10.0.0.6

  From: 10.0.0.1, LSPstate: Up, ActiveRoute: 1

  LSPname: R1-to-R6, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 3

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

  Time left:  147, Since: Thu Oct 21 15:39:33 2004

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

  Port number: sender 1 receiver 47963 protocol 0

  PATH rcvfrom: 10.1.13.1 (so-0/0/2.0) 4 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.1.36.2 (so-0/0/3.0) 4 pkts

  RESV rcvfrom: 10.1.36.2 (so-0/0/3.0) 4 pkts

  Explct route: 10.1.36.2 

  Record route: 10.1.13.1 <self> 10.1.36.2  

Total 2 displayed, Up 2, Down 0

Sample Output 3

user@R6> show mpls lsp extensive

Ingress LSP: 1 sessions

10.0.0.1

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

  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.36.1 S 10.1.13.1 S 

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

          10.1.36.1 10.1.13.1

   18 Oct 21 15:34:18 Selected as active path

   17 Oct 21 15:34:17 Record Route:  10.1.36.1 10.1.13.1

   16 Oct 21 15:34:17 Up

   15 Oct 21 15:34:17 Originate Call

   14 Oct 21 15:34:17 CSPF: computation result accepted

   [...Output truncated...]

  Created: Tue Oct 19 22:28:30 2004

Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions

10.0.0.6

  From: 10.0.0.1, LSPstate: Up, ActiveRoute: 0

  LSPname: R1-to-R6, 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:  126, Since: Thu Oct 21 15:44:25 2004

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

  Port number: sender 1 receiver 47963 protocol 0

  PATH rcvfrom: 10.1.36.1 (so-0/0/3.0) 4 pkts

  Adspec: received MTU 1500 

  PATH sentto: localclient

  RESV rcvfrom: localclient 

  Record route: 10.1.13.1 10.1.36.1 <self>  

Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

What It Means

Sample Outputs 1 and 3 from ingress router R1 and egress router R6 show 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. In addition, Sample Output 2 from transit router R3 shows that there are two transit LSP sessions, one from R1 to R6, and the other from R6 to R1.