Step 4: Verify the LSP Again

Action

From the ingress, egress, and transit routers, verify that the LSP is up and traversing the network as expected:

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

   145 Sep 30 12:25:01 Selected as active path

   144 Sep 30 12:25:01 Record Route:  10.1.13.2 10.1.36.2

   143 Sep 30 12:25:01 Up

   142 Sep 30 12:25:01 Originate Call

   141 Sep 30 12:25:01 CSPF: computation result accepted

   140 Sep 30 12:24:32 CSPF failed: no route toward 10.0.0.6[74 times]

   139 Sep 30 11:48:57 Deselected as active

   138 Sep 30 11:48:56 CSPF failed: no route toward 10.0.0.6

   137 Sep 30 11:48:56 Clear Call

   136 Sep 30 11:48:56 CSPF: link down/deleted 
10.1.36.1(R3.00/10.0.0.3)->10.1.36.2(R6.00/10.0.0.6)

   [...Output truncated...]

  Created: Sat Jul 10 18:18:43 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:  134, Since: Thu Sep 30 12:24:56 2004

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

  Port number: sender 6 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

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

   50 Sep 30 12:24:12 Selected as active path

   49 Sep 30 12:24:12 Record Route:  10.1.36.1 10.1.13.1

   48 Sep 30 12:24:12 Up

   47 Sep 30 12:24:12 Originate Call

   46 Sep 30 12:24:12 CSPF: computation result accepted

   45 Sep 30 12:23:43 CSPF failed: no route toward 10.0.0.1[73 times]

   44 Sep 30 11:48:12 Deselected as active

   43 Sep 30 11:48:12 CSPF failed: no route toward 10.0.0.1

   42 Sep 30 11:48:12 CSPF: link down/deleted 
10.1.36.2(R6.00/10.0.0.6)->10.1.36.1(R3.00/10.0.0.3)

   [...Output truncated...]

  Created: Tue Aug 17 12:18:34 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:  159, Since: Thu Sep 30 12:24:16 2004

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

  Port number: sender 19 receiver 44251 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

Sample Output 3

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: 100176, Label out: 3

  Time left:  143, Since: Thu Sep 30 12:21:25 2004

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

  Port number: sender 6 receiver 39024 protocol 0

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

  Adspec: received MTU 1500 sent MTU 1500

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

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

  Time left:  148, Since: Thu Sep 30 12:21:30 2004

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

  Port number: sender 19 receiver 44251 protocol 0

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

  Adspec: received MTU 1500 sent MTU 1500

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

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

user@R1> show configuration protocols mpls 

label-switched-path R1-to-R6 {

    to 10.0.0.6;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

interface so-0/0/2.0;

user@R6> show configuration protocols mpls 

label-switched-path R6-to-R1 {

    to 10.0.0.1;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

inactive: interface so-0/0/2.0;

interface so-0/0/3.0;

user@R3> show configuration protocols mpls 

interface fxp0.0 {

    disable;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

interface so-0/0/2.0;

interface so-0/0/3.0;

What It Means

Sample Outputs 1 and 2 from ingress router R1 and egress router R6, respectively, 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.

Sample Output 3 from transit router R3 shows that there are two transit LSP sessions, one from R1 to R6 and the other from R6 to R1.

Sample Output 4 shows the interfaces that were deactivated on the ingress, egress, and transit routers, forcing the LSP to take the intended path. If these interfaces were not deactivated, even though the configuration is now correct, the LSP would still traverse the network through the alternate path.