Chris,
There are two bugs I see:
#1 A cosmetic cisco bug where "show mpls traf tun" shows implicit-null
signalling, yet it's really signalling explicit-null. Seen in latest 12.2
and 12.0S.
#2 A severe Juniper bug where a Juniper egress doesn't parse an
explicit-null LABEL object properly. I see cisco signalling explicit-null,
but the juniper penultimate puts bad info in mpls.0:
root@r10> show route table mpls.0 label-switched-path r4_t0 extensive
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100044 (1 entry, 1 announced)
TSI:
KRT in-kernel 100044 /36 -> {192.168.105.5}
*RSVP Preference: 7
Nexthop: 192.168.105.5 via fe-0/0/1.0, selected
label-switched-path r4_t0
Swap 0, Push 15(top)<--------------Bad label operation.
State: <Active Int>
Age: 13:25 Metric: 1
Task: RSVP
Announcement bits (1): 0-KRT
AS path: I
...if the cisco egress is configured for implicit-null, the Juniper puts the
right info in mpls.0:
root@r10> show route table mpls.0 label-switched-path r4_t0 extensive
mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100046 (1 entry, 1 announced)
TSI:
KRT in-kernel 100046 /36 -> {192.168.105.5}
*RSVP Preference: 7
Nexthop: 192.168.105.5 via fe-0/0/1.0, selected
label-switched-path r4_t0
Pop
State: <Active Int>
Age: 6 Metric: 1
Task: RSVP
Announcement bits (1): 0-KRT
AS path: I
See if this is your problem when using explicit-null.
Sean
> -----Original Message-----
> From: Sean Crocker
> Sent: Wednesday, August 08, 2001 8:40 PM
> To: 'cisco-nsp@puck.nether.net'; 'cmartin@gnilink.net'
> Subject: Re: Pinging across an LSP from Cisco<--Juniper--->Cisco
>
> Hey Chris,
>
> The fact that cisco as egress says that it's signalling
> implicit-null but is really signalling explicit-null is at
> least a cosmetic bug (possibly worse). I see it too, and
> still exists in 18S. I'll ask someone to check into it.
>
> I've never gotten RSVP-TE LSPs to work with cisco as egress
> and juniper as penultimate hop. I've been wanting to figure
> out which side is the culprit. I'll look at it more this week.
>
> What I _can_ tell you is that I see pings and all traffic
> transit the LSP fine as long as the egress ciscos on both
> sides are configured with "mpls traf sig implicit", running
> 16S and 4.4R3.4. Lemme know if you've verified via
> debugs/traceoptions that you're really doing explicit-null,
> and still have problems.
>
> Sean
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:49 EDT