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

2019-08-19 Thread adamv0025
> From: Nathan Ward > Sent: Friday, August 16, 2019 11:20 AM > > 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,

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

2019-08-16 Thread Andrey Kostin
Could it be: Number PR1443811 Title RSVP refresh-timer interoperability between 15.1 and 16.1+ Release Note Path message with long refresh interval (equal to or more than 20 minutes) from a node that does not support Refresh-interval Independent RSVP (RI-RSVP) is dropped by the receiver with

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

2019-08-16 Thread Nathan Ward
> On 16/08/2019, at 10:01 PM, > wrote: > > > >> From: Nathan Ward >> Sent: Friday, August 16, 2019 8:39 AM >> >>> On 1/07/2019, at 9:59 PM, adamv0...@netconsultings.com wrote: >>> From: Michael Hare Sent: Friday, June 28, 2019 7:02 PM Adam- Have you accoun

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

2019-08-16 Thread adamv0025
> From: Nathan Ward > Sent: Friday, August 16, 2019 8:39 AM > > > On 1/07/2019, at 9:59 PM, adamv0...@netconsultings.com wrote: > > > >> From: Michael Hare > >> Sent: Friday, June 28, 2019 7:02 PM > >> > >> Adam- > >> > >> Have you accounted for this behavioral change? > >> > >> > https://kb.j

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

2019-08-15 Thread Olivier Benghozi
Looks like the PR about this is now available: PR1443811 «RSVP refresh-timer interoperability between 15.1 and 16.1+». «Path message with long refresh interval (equal to or more than 20 minutes) from a node that does not support Refresh-interval Independent RSVP (RI-RSVP) is dropped by the rece

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

2019-07-02 Thread Simon Dixon
I had that issue between QFX5110's and MX's.Some feature at the time forced me to run 17.4 on the QFX's and they wouldn't establish LSP's with older MX80's in our fleet that were still running 14.2. I had to either downgrade the QFX's to 15.1 or upgrade the MX's to 16.1 or greater. I ended up

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

2019-07-01 Thread Jared Mauch
We have seen similar issues with single hop LSPs and the stats being wrong unless we explicitly configure the single hop LSPs differently with UHP. Sent from my iCar On Jul 1, 2019, at 5:59 AM, wrote: >> From: Michael Hare >> Sent: Friday, June 28, 2019 7:02 PM >> >> Adam- >> >> Have you

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

2019-07-01 Thread adamv0025
> From: Michael Hare > 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

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

2019-06-28 Thread Michael Hare via juniper-nsp
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 -Michael > -Original Message- > From: juniper-nsp On Behalf Of > adamv0...@netconsultings.com > Sent: Friday, June 28, 2

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

2019-06-28 Thread Ryan Gasik
I have MXs and ACXs all running RSVP, ranging in versions from 13 to 18. I haven't had any issues. What platform are you using? On Fri, Jun 28, 2019 at 7:15 AM wrote: > > Hi gents, > > Just wondering if anyone experienced RSVP-TE incompatibility issues when > moving from pre 16.1 code to post 16