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

[adamv0025 at netconsultings.com]

> 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. 

> 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).

adam