Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Verify the LSP Again

    Purpose

    After taking the appropriate action to correct the error, the LSP needs to be checked again to confirm that the problem in the IS-IS protocol has been resolved.

    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

    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
        Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
              10.1.13.2 10.1.36.2
        4 Oct 19 21:22:54 Selected as active path
        3 Oct 19 21:22:53 Record Route:  10.1.13.2 10.1.36.2
        2 Oct 19 21:22:53 Up
        1 Oct 19 21:22:53 Originate Call
      Created: Tue Oct 19 21:22:53 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:  117, Since: Tue Oct 19 21:17:42 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 2 receiver 39064 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
    
    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: 100416, Label out: 3
      Time left:  139, Since: Tue Oct 19 21:05:11 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 2 receiver 39064 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: 100448, Label out: 3
      Time left:  135, Since: Tue Oct 19 21:10:22 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 47951 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
      Record route: 10.1.13.1 <self> 10.1.36.2  
    Total 2 displayed,  Up 2 , Down 0
    
    user@R6>  run 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: 2)
     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
       19 Oct 19 21:09:52 Selected as active path
       18 Oct 19 21:09:52 Record Route:  10.1.36.1 10.1.13.1
       17 Oct 19 21:09:52 Up
       16 Oct 19 21:09:52 Originate Call
       15 Oct 19 21:09:52 CSPF: computation result accepted
      Created: Tue Oct 19 18:30:09 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:  120, Since: Tue Oct 19 21:15:03 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 47951 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
    

    Meaning

    The sample output from ingress router R1 and egress router R6 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. In addition, the sample output from transit router R3 shows that there are two transit LSP sessions, one from R1 to R6, and the other from R6 to R1.

    Published: 2013-07-25