Step 5: Verify the LSP Again

Action

To verify the LSP again, enter the following command on the ingress, transit, and egress 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

   54 Oct 15 21:28:16 Selected as active path

   53 Oct 15 21:28:16 Record Route:  10.1.13.2 10.1.36.2

   52 Oct 15 21:28:16 Up

   51 Oct 15 21:28:16 10.1.15.1: MPLS label allocation failure[2 times]

   50 Oct 15 21:28:11 CSPF: computation result accepted

   49 Oct 15 21:27:42 10.1.15.1: MPLS label allocation failure

   48 Oct 15 21:27:42 CSPF: computation result accepted

   47 Oct 15 21:27:31 10.1.15.1: MPLS label allocation failure[4 times]

   46 Oct 15 21:27:13 Originate Call

   45 Oct 15 21:27:13 CSPF: computation result accepted

   [...Output truncated...]

  Created: Thu Oct 14 16:04:34 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: Fri Oct 15 21:28:13 2004

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

  Port number: sender 13 receiver 39024 protocol 0

  PATH rcvfrom: 10.1.13.2 (so-0/0/2.0) 10 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: 100336, Label out: 3

  Time left:  156, Since: Fri Oct 15 21:15:47 2004

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

  Port number: sender 13 receiver 39024 protocol 0

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

  Adspec: received MTU 1500 sent MTU 1500

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

  RESV rcvfrom: 10.1.13.1 (so-0/0/2.0) 11 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: 100352, Label out: 3

  Time left:  159, Since: Fri Oct 15 21:15:50 2004

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

  Port number: sender 5 receiver 47901 protocol 0

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

  Adspec: received MTU 1500 sent MTU 1500

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

  RESV rcvfrom: 10.1.36.2 (so-0/0/3.0) 11 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

   187 Oct 15 21:20:05 Selected as active path

   186 Oct 15 21:20:05 Record Route:  10.1.36.1 10.1.13.1

   185 Oct 15 21:20:05 Up

   184 Oct 15 21:20:05 Clear Call

   183 Oct 15 21:20:05 CSPF: computation result accepted

   182 Oct 15 21:20:05 CSPF: link down/deleted 
10.1.13.2(R3.00/10.0.0.3)->10.1.13.2(R1.00/10.0.0.1)

   [...Output truncated...]

  Created: Tue Aug 17 12:18:33 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:  144, Since: Fri Oct 15 21:20:08 2004

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

  Port number: sender 5 receiver 47901 protocol 0

  PATH rcvfrom: 10.1.36.1 (so-0/0/3.0) 11 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 Output 1 from ingress router R1 shows that LSP R1-to-R6 has an active route to R6 and the state is up. The output shows that the egress LSP session R6-to-R1 received and sent a recovery label.

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. Both LSPs are up.

Sample Output 3 from egress router R6 shows that the LSP is up and the active route is the primary route. 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.