Description

This article provides information on how to identify the Ingress/Egress interface of a RSVP signaled LSP.

Symptoms

This is helpful for troubleshooting purposes. The ingress/egress interface can be determined by looking at the output of show rsvp session extensive or run show rsvp session detail .

Topology :

alt

Configuration : 

hongkong#show protocols mpls 
label-switched-path to-amsterdam {
    to 192.168.4.1;
    no-cspf;
}
interface ge-1/0/0.0;
interface ge-1/1/7.0;
interface all;
Outputs : 
hongkong#run show route 192.168.4.1 
< Two equal cost paths exist to reach the destination via two different interfaces 

inet.0: 21 destinations, 21 routes (21 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.4.1/32     *[OSPF/10] 00:16:27, metric 3
                    > to 10.222.12.2 via ge-1/0/0.0
                      to 10.222.15.2 via ge-1/1/7.0
Ingress router : 
hongkong#run show mpls lsp ingress           
Ingress LSP: 1 sessions
To              From            State Rt P     ActivePath       LSPname
192.168.4.1     192.168.1.1     Up     0 *                      to-amsterdam

Transit router : 
sanjose#run show mpls lsp transit 
Transit LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.4.1     192.168.1.1     Up       0  1 FF  299776   299776 to-amsterdam
Total 1 displayed, Up 1, Down 0

Egress router : 
amsterdam#run show mpls lsp egress           
Egress LSP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname 
192.168.4.1     192.168.1.1     Up       0  1 FF       3        - to-amsterdam
Total 1 displayed, Up 1, Down 0

Solution


The outputs of the show rsvp session extensive lsp name <name> detail and show rsvp session extensive lsp name <name> extensive commands display the ingress and egress interfaces of the specified ISP: 

Ingress router : hongkong 

hongkong#run show rsvp session detail ingress lsp name to-amsterdam 
Ingress RSVP: 1 sessions

192.168.4.1
  From: 192.168.1.1, LSPstate: Up, ActiveRoute: 0
  LSPname: to-amsterdam, LSPpath: Primary
  LSPtype: Static Configured
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299776
  Resv style: 1 FF, Label in: -, Label out: 299776
  Time left:    -, Since: Thu Jun 14 19:13:19 2012
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 227 protocol 0
  PATH rcvfrom: localclient < Ingress interface will be mentioned here,
  as this is the ingress router.   the ingress interface is local client. 
  Adspec: sent MTU 1500
  Path MTU: received 1500
  PATH sentto: 10.222.15.2 (ge-1/1/7.0) 31 pkts < The Egress interface will be mentioned here  
  RESV rcvfrom: 10.222.15.2 (ge-1/1/7.0) 32 pkts < The Egress interface will be mentioned here  
  Record route: <self> 10.222.15.2 10.222.56.2 10.222.46.1  
Total 1 displayed, Up 1, Down 0

Transit router : sanjose 

sanjose#run show rsvp session detail lsp name to-amsterdam transit 
Transit RSVP: 1 sessions

192.168.4.1
  From: 192.168.1.1, LSPstate: Up, ActiveRoute: 0
  LSPname: to-amsterdam, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299776
  Resv style: 1 FF, Label in: 299776, Label out: 299776
  Time left:  130, Since: Thu Jun 14 19:17:58 2012
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 227 protocol 0
  PATH rcvfrom: 10.222.15.1 (ge-1/1/6.0) 36 pkts < Ingress interface will be mentioned here
  Adspec: received MTU 1500 sent MTU 1500
  PATH sentto: 10.222.56.2 (ge-1/1/0.0) 37 pkts < The Egress interface will be mentioned here
  RESV rcvfrom: 10.222.56.2 (ge-1/1/0.0) 37 pkts < The Egress interface will be mentioned here
  Record route: 10.222.15.1 <self> 10.222.56.2 10.222.46.1  
Total 1 displayed, Up 1, Down 0

Egress router : amsterdam 

amsterdam#run show rsvp session detail lsp name to-amsterdam egress 
Egress RSVP: 1 sessions

192.168.4.1
  From: 192.168.1.1, LSPstate: Up, ActiveRoute: 0
  LSPname: to-amsterdam, 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:  131, Since: Thu Jun 14 19:17:58 2012
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 227 protocol 0
  PATH rcvfrom: 10.222.46.2 (ge-1/0/6.0) 40 pkts < Ingress interface will be mentioned here,
  as this is the egress router. There is no Ingress physical interface.  
  Adspec: received MTU 1500 
  PATH sentto: localclient < The Egress interface will be mentioned here
  RESV rcvfrom: localclient < The Egress interface will be mentioned here
  Record route: 10.222.15.1 10.222.56.1 10.222.46.2 <self>  
Total 1 displayed, Up 1, Down 0