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

    Purpose

    Confirm that interfaces are configured for OSPF, the OSPF protocol is configured correctly and that neighbors are established.

    Action

    To verify the LSP, 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: Dn, ActiveRoute: 0,  LSPname: R1-to-R6
      ActivePath: (none)
      LoadBalance: Random
      Encoding type: Packet, Switching type: Packet, GPID: IPv4
      Primary                    State: Dn
       11 Oct 19 18:06:04 No Route toward dest[78 times]
       10 Oct 19 17:08:09 Deselected as active
      Created: Mon Oct 18 21:48:42 2004
    Total 1 displayed, Up 0,  Down 1
    
    Egress LSP: 0 sessions
    Total 0 displayed, Up 0, 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: 0 sessions
    Total 0 displayed, Up 0, Down 0
    

    Sample Output 3

    user@R6> show mpls lsp extensive
    Ingress LSP: 1 sessions
    To              From            State Rt ActivePath       P     LSPname
    10.0.0.1        10.0.0.6        Dn     0 -                      R6-to-R1
    Total 1 displayed, Up 0,  Down 1
    
    Egress LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0
    
    Transit LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0
    

    Sample Output 4

    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
        5 Oct 19 10:37:55 Selected as active path
        4 Oct 19 10:37:55 Record Route:  10.1.13.2 10.1.36.2
        3 Oct 19 10:37:55 Up
        2 Oct 19 10:37:10 No Route toward dest[1029 times]
        1 Oct 18 21:48:42 Originate Call
      Created: Mon Oct 18 21:48:42 2004
    Total 1 displayed,  Up 1 , Down 0
    
    Egress LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0
    
    Transit LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0
    

    Sample Output 5

    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: 1 sessions
    
    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: 100368, Label out: 3
      Time left:  154, Since: Tue Oct 19 10:25:24 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 47933 protocol 0
      PATH rcvfrom: 10.1.13.1 (so-0/0/2.0) 209 pkts
      Adspec: received MTU 1500 sent MTU 1500
      PATH sentto: 10.1.36.2 (so-0/0/3.0) 209 pkts
      RESV rcvfrom: 10.1.36.2 (so-0/0/3.0) 209 pkts
      Record route: 10.1.13.1 <self> 10.1.36.2  
    Total 1 displayed, Up 1, Down 0
    

    Sample Output 6

    user@R6> show mpls lsp extensive
    Ingress LSP: 1 sessions
    
    10.0.0.1
      From: 10.0.0.6, State: Dn, ActiveRoute: 0,  LSPname: R6-to-R1
       ActivePath: (none)
      LoadBalance: Random
      Encoding type: Packet, Switching type: Packet, GPID: IPv4
      Primary                    State: Dn
        2 Oct 19 13:01:54 10.1.56.2:  MPLS label allocation failure [9 times]
        1 Oct 19 12:57:51 Originate Call
      Created: Tue Oct 19 12:57:51 2004
    Total 1 displayed, Up 0,  Down 1
    
    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:  148, Since: Tue Oct 19 10:30:03 2004
      Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
      Port number: sender 1 receiver 47933 protocol 0
      PATH rcvfrom: 10.1.36.1 (so-0/0/3.0) 206 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

    Sample Outputs 1, 2, and 3 show that the LSP and the reverse LSP are down:

    • Sample Output 1 from ingress router R1 shows that LSP R1-to-R6 does not have a route towards the destination (R6).
    • Sample Output 2 from transit router R3 shows that there are no LSP sessions.
    • Sample Output 3 from egress router R6 also shows that reverse LSP R6-to-R1 is down.

    Sample Outputs 4, 5, and 6 show that the LSP is up and the reverse LSP is down:

    • Sample Output 4 from ingress router R1 shows that LSP R1-to-R6 is up and there are no egress LSP sessions.
    • Sample Output 5 from transit router R3 shows that there is one ingress LSP session (R1-to-R6) and no egress LSP sessions.
    • Sample Output 6 from egress router R6 shows that LSP R6-to-R1 is down due to an MPLS label allocation failure.

    Published: 2013-07-25