Replying to my own question.
I received direct reply from one of juniper-nsp subscribers with link
to article explaining this behavior:
This is FAD to ensure new backup synchronizes correctly.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB32221
Kind regards,
Andrey
Andrey Kostin писал 30.07.2018 10:39:
Hello juniper-nsp,
Installed new 17.3R3.9 for testing on the router acting as L2TP LNS
and encountered strange behavior right off the bat. When mastership
is
switched between REs, the former master RE reloads right after it
releases it's mastership. Switchover itself goes smoothly, all
protocols survive, subscriber sessions stay online etc. So overall
it's not harmful but suspicious. Opened JTAC case but wondering if
anybody already seen this in any release or may be it's normal in
17.x
train? Before that JTAC told me that 17.3R3 is going to be a "golden
release", so I didn't expect to face a problem that's so obvious.
Kind regards,
Andrey
_______________________________________________
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
