plans: a VRRP master keeps a gateway it can no longer serve #2253
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2253
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1120-0337"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One page of forward plan, no code. Measured on
8b94f987.Finding. A VRRP master whose only uplink dies keeps priority 150 and the VIP: the election's only input for liveness is the group's own interface (
engine/simulator.js:1080), so a healthy backup at 100 is never asked to take over. Probe lab (generic devices): PC pings a server through R1 (master, 150); cut R1's Gi0/1 and the ping returnslink down (dropped by d1)0/2 while R2 sits atBackupwith a connected route.show vrrpon R1 still printsMaster 150.Second finding.
setLinkState()(engine/simulator.js:498-556) rebuilds STP, flushes MAC tables and re-bases the schedule but never re-runscomputeVrrp(); evenshutdownon the master leavesdevice.vrrpClaimswith it until the next ping orshow.Steps. (1) re-elect from the one choke point
markTopologyChange(); (2)vrrp <vrid> track <iface> [decrement N]; (3)show vrrpnames the track and the priority in force; (4) running-config round-trip and thenoform; (5)preempt delay minimum; (6) docs. Sizes S/M/S/S/M/S. Closes no open issue (queue is #130 and #1980).Left out on purpose: advertisement-loss detection, which needs held per-group state the module deliberately does not keep — flagged as a decision for Jay.