Also experienced these issues with most versions above 14.1X53. FWIW I've had no problems with 17.3R2-S1.2, but we did have issues with 17.4R1
We're working with our account team to try and sort this stuff out On Tue, Apr 24, 2018 at 8:21 AM Sebastian Wiesinger <sebast...@karotte.org> wrote: > * Chris via juniper-nsp <juniper-nsp@puck.nether.net> [2018-04-24 09:58]: > > I can't keep switching firmware around to try and resolve this/isolate > to a > > specific revision, but it is interesting that you also note you have not > > experienced any issues with 16.1, the same as us. If you get a proper > answer > > to what this issue is I would really like to know, but it looks like I > will > > probably have to downgrade to 16.1 due to these issues as they are > impacting > > services. > > Interesting stuff, I'm fishing around but I'm suspecting perhaps this > is some sort of timing issue. Just be aware that 16.1R6 is also a > "bad" version from our point of view. 16.1R5-S2 is fine. > > Sebastian > > -- > GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) > 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE > SCYTHE. > -- Terry Pratchett, The Fifth Elephant > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp