Re: [j-nsp] Strange Behavior after ISSU from 13.3R8 to 17.4R1.16

Hi Jeffrey, I'm under impression that (quote from https://www.juniper.net/documentation/en_US/junos/topics/topic-map/junos-kernel-freebsd-upgraded.html ) "ISSU is not supported from an older version of FreeBSD to an upgraded FreeBSD" On 28-May-18 04:01, Jeffrey Nikoletich wrote: Hello

[j-nsp] Strange Behavior after ISSU from 13.3R8 to 17.4R1.16

You're a brave soul, trying ISSU at all and what-not... Mark. On 28/May/18 04:49, Jeffrey Nikoletich wrote: > Scratch that. Problem still exist. ☹ > > > > > > > > *From:* Jeffrey Nikoletich > *Sent:* May 27, 2018 07:43 PM > *To:* juniper-nsp@puck.nether.net > *Subject:* RE: Strange Behavior

Re: [j-nsp] Strange Behavior after ISSU from 13.3R8 to 17.4R1.16

Scratch that. Problem still exist. ☹ *From:* Jeffrey Nikoletich *Sent:* May 27, 2018 07:43 PM *To:* juniper-nsp@puck.nether.net *Subject:* RE: Strange Behavior after ISSU from 13.3R8 to 17.4R1.16 All, So after I sent this email I noticed a had a rogue rib-group in

Re: [j-nsp] Strange Behavior after ISSU from 13.3R8 to 17.4R1.16

All, So after I sent this email I noticed a had a rogue rib-group in place. I removed that and it seems traffic is fine now. I am testing and will let you know. Apparently it helps me to email the whole group just to “hopefully” find the answer 5 seconds late. Thanks, Jeffrey

[j-nsp] Strange Behavior after ISSU from 13.3R8 to 17.4R1.16

Hello all, So I have been scratching my head at a weird issue I am seeing on only 1 of our devices after a ISSU rollout to 17.4. It seems that all peering session links are not passing traffic. Here is what I know so far: 1. Peering sessions (via exchanges) connect just fine. 2. If the