[j-nsp] one-way lsp

[Thomas Salmen]

ibgp between the two routers is up (local address is configured). 

E-series interface config seems valid (e.g mpls and rsvp seem to be
enabled):

interface gigabitEthernet 4/0
 mtu 1522
 duplex full
 speed 1000
 link failover timeout 5000
 encapsulation vlan
! 
interface gigabitEthernet 4/0.100
 vlan id 100
 ip address 172.27.32.130 255.255.255.0
 ip ospf authentication-key <removed>
 mpls
 mpls rsvp profile default


In fact, according to the ERX, there is an RSVP session established between
itself and the J:

ERX-a0-3a-53#show mpls rsvp sessions  
Destination 172.28.32.253 TunnelId 1 Extended Tunnel Id xx.xxx.8.14
Internal Index 0x0000011B
  PSB: Sender xx.xxx.8.14 LSPId 1 timeout -- InLabel --
       Internal Index 0x0000011B
       Associated Minor Interface: Tunnel pe2
       PHopIntf 
       IncomingIntf 
       OutgoingIntf GigabitEthernet4/0.100
       PHopAddr 0.0.0.0 NextHopAddr 172.27.32.120
       NextHop 172.27.32.120/255.255.255.255 (strict)
       LabelRange --
       SenderTSpec CType IntServ Controlled Load
                   Token Bucket Rate 0
                   Token Bucket Size 0
                   Peak Data Rate 0
                   Min Policed Unit 0
                   Max Packet Size 0
       RRO --
       ADSPEC --
       IN ERO IPv4 hop 172.27.32.120 (strict)
       OUT ERO IPv4 hop 172.27.32.120 (strict)
       SES ATTR Setup Pri 4, Hold Pri 4, name --
                Flags : SharedExplicitStyle
       TTC --
       Policy Object --
       Unknown Objects --
       Flags : RouteChangeNotify
               RroRequired
               PathRefreshSent
  RSB: Timeout 157500 label 3
       Internal Index 0x00000002
       Associated Minor Interface: Tunnel pe2
       FlowSpec CType IntServ Controlled Load
                Token Bucket Rate 0
                Token Bucket Size 0
                Peak Data Rate 0
                Min Policed Unit 1
                Max Packet Size 1
       RRO IPv4 hop 172.27.32.120 
       Bypassed Links --
       Policy Object --
       Unknown Objects --
       Flags : StyleConverted

But on the J:

lab at orcontest# run show rsvp session extensive 
Ingress RSVP: 1 sessions

xx.xxx.8.14
  From: 172.28.32.253, LSPstate: Dn, ActiveRoute: 0
  LSPname: pe1, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: -
  Resv style: 0 -, Label in: -, Label out: -
  Time left:    -, Since: Wed Dec 28 10:46:51 2005
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 60051 protocol 0
  PATH rcvfrom: localclient 
  Adspec: sent MTU 1500
  Path MTU: received 0
  PATH sentto: 172.27.32.130 (fe-0/0/0.100) 486 pkts
  Explct route: 172.27.32.130 
  Record route: <self> ...incomplete
Total 1 displayed, Up 0, Down 1

Egress RSVP: 1 sessions

172.28.32.253
  From: xx.xxx.8.14, LSPstate: Up, ActiveRoute: 0
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: -
  Resv style: 1 SE, Label in: 3, Label out: -
  Time left:  136, Since: Sun Dec 25 10:59:17 2005
  Tspec: rate 0bps size 0bps peak 0bps m 0 M 0
  Port number: sender 1 receiver 1 protocol 0
  PATH rcvfrom: 172.27.32.130 (fe-0/0/0.100) 8944 pkts
  PATH sentto: localclient
  RESV rcvfrom: localclient 
  Record route: 172.27.32.130 <self>  
Total 1 displayed, Up 1, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0


I'm mildly stumped. 

/t


> 
> I might have been to quick here :-/
> The J-series config is probably OK (is your iBGP session up? You might
> need to use "local-address")
> I'm even more losy on the E-series config but is RSVP and MPLS enable
> properly on all valid interfaces?
> //Jan
> 
> -----Original Message-----
> From: Thomas Salmen [mailto:tsalmen at orcon.net.nz]
> Sent: den 28 december 2005 00:00
> To: Jan Andersson H (AL/EAB); 'jnsp list'
> Subject: RE: [j-nsp] one-way lsp
> 
> 
> 
> Is this required under the label-switched-path config? (is it even
> configurable?) Surely this is configured for a named path only? I was
> under the impression that configuring a named path was not required at
> all, and the IGP could simply be relied on.
> 
> /t
> 
> >
> >  Hi,
> > Use a loose path since you are using loopbacks
> >
> > mpls {
> >     label-switched-path pe1 {
> >         to xx.xxx.8.14 LOOSE;
> >     }
> >     interface fe-0/0/0.100;
> > }
> >
> > HTH
> >