SD-WAN

Happy Friday everyone! I hope your Summer has been fun and relaxing. I hope you had a chance to recover, get some of your projects done, and spend some time with the family. Maybe you got a little travel in if you are into that. I know I ...

Here is the data model example: device-interface ge-0-0 vrrp enabled true vrid 10 priority 100 vlan 10 advertisement-interval 1000 use-uptime-tiebreaker ...

Thanks - This should reduce unnecessary failback after the original node returns, although it would not, by itself, prevent the boot-time unsolicited ARP/GARP issue described above. (The issue is a premature GARP during SSR boot . The returning node ...

@Hannu I got this from Juniper support " key point is that VRRP node failover and session resiliency are separate mechanisms. The "non-revertible failover" recommendation in the HA documentation should not be interpreted as a VRRP no-preempt. " ...

To change SSR VRRP behavior to non-revertive you should set identical priorities on both interfaces in the redundant pair. There is a caveat to this. If there is a fault in the broadcast domain which results in both interfaces being active, a split ...

Thanks, this sounds potentially very related. In our case, the symptom is different, but the timing is very similar: during recovery, the shared interface becomes active, and an unsolicited GARP for the shared VIP is sent before VRRP is fully ...

I have now done a deeper packet-level analysis with a 2-hour PCAP captured on the LAN side of the SSR, using a SPAN of the EX4000 uplink toward the SSR. The result changes my original interpretation. The TCP retransmissions are real, ...