> 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,
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
> 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
> 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?
> >>
> >>
>
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
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
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
> 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=KB32883=
> print=LIST==currentpaging
>
Thank you, yes please we're aware of that, but even with this the issue is
gt; To: juniper-nsp@puck.nether.net
> Subject: [j-nsp] RSVP-TE broken between pre and post 16.1 code?
>
> Hi gents,
>
> Just wondering if anyone experienced RSVP-TE incompatibility issues when
> moving from pre 16.1 code to post 16.1 code.
> Didn't get much out of Juniper
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
Hi gents,
Just wondering if anyone experienced RSVP-TE incompatibility issues when
moving from pre 16.1 code to post 16.1 code.
Didn't get much out of Juniper folks thus far so I figured I'll ask here as
well.
The problem we're facing is that in case 17 code is LSP head-end and 15 code
is
11 matches
Mail list logo
