[j-nsp] RSVP-TE broken between pre and post 16.1 code?

[Nathan Ward]

> On 16/08/2019, at 10:01 PM, <adamv0025 at netconsultings.com> <adamv0025 at netconsultings.com> wrote:
> 
> 
> 
>> From: Nathan Ward <nward at daork.net>
>> Sent: Friday, August 16, 2019 8:39 AM
>> 
>>> On 1/07/2019, at 9:59 PM, adamv0025 at netconsultings.com wrote:
>>> 
>>>> From: Michael Hare <michael.hare at wisc.edu>
>>>> Sent: Friday, June 28, 2019 7:02 PM
>>>> 
>>>> Adam-
>>>> 
>>>> Have you accounted for this behavioral change?
>>>> 
>>>> 
>> https://kb.juniper.net/InfoCenter/index?page=content&id=KB32883&pmv=
>>>> print&actp=LIST&searchid=&type=currentpaging
>>>> 
>>> Thank you, yes please we're aware of that, but even with this the
>>> issue is still present if the refresh timer is not <1200 or CSPF is enabled.
>> 
>> I’m confused by this one - what’s the refresh timer and CSPF got to do with
>> it?
>> 
> Not much it's a bug, it appears form the logs that the path message has "something different" in the ERO when CSPF is enabled triggering the bug ... 
> 
>> LSPs on 16.1 will do self-ping after they come up before they put traffic on
>> them. The lo0 filter has to permit that, or you’ve got to disable self-ping.
>> 
> LSPs will do self ping when switching onto a new/optimized path, not when the LSP is first brought up -which in this case doesn’t happen. 

I am fairly certain they’ll do self ping on new LSPs as well. It’s, in theory, whenever the ingress LSR gets a RESV message - for either a new path, or a whole new LSP it doesn’t matter.

>> Or am I parsing this weird, and you’re saying this is still an issue even with the
>> self ping disabled (or permitted in filters), under those conditions?
>> 
> Yes that is correct, this problem appears even before the self-ping is engaged (the LSP is not even signalled -the RESV msg is never sent as a response to PATH msg in this case).

Yeah got it, that’s certainly Not Right.

Weird that the refresh timer <1200 triggers it. Do you mean the refresh timer in the time values object is 1200 - i.e. 1.2s? JunOS default is 30,000 (30s), 1200 seems very short, or very long? Certainly it sounds like a bug, but, I’m curious why you’d have timers like that..

--
Nathan Ward