vrrp: the Pri column quotes the priority the group runs at, 255 for an address owner #1923
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!1923
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1118-vrrp-pri"
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?
VRRP reserves priority 255 for the address owner - the router whose own interface address is one of the group's virtual addresses - and the election in
engine/vrrp.jshas voted that way since VRRP was modelled.show vrrpprinted the configured value instead, so a router that owns the virtual gateway showed100in the very table explaining why it had just outranked a254, and the timeline event carried the same number.Sources: Cisco IOS FHRP Configuration Guide ("If a VRRP group is the IP address owner, its priority is fixed at 255"), Nexus 5600 Unicast Routing Configuration Guide ("255 for a master that has an interface IP address equal to the virtual IP address"), RFC 5798 5.2.2, and the ASR 900 VRRPv3 sample ("Priority is 255 (owner mode)").
electMaster()now reports both numbers per candidate (priority in force, configured);show vrrpprints the one in force and adds a note naming the address it holds, the owner mode, and the fact thatvrrp <vrid> prioritycannot set 255.show running-configkeeps the configured value, so nothing an operator typed is rewritten.test/show-vrrp-owner-priority.test.js: 28 checks (owner at 255 above a 254, configured value untouched in the running-config, the note, the timeline event).research/show-vrrp-owner-priority.md: the sources and the one question they do not settle.docs/CLI.md,CHANGELOG.md.Gates:
node scripts/syntax-check.js(403 files),test/show-vrrp-owner-priority.test.js28/28,test/vrrp.test.js94/94, fullnpm test330 suites / 11455 assertions / 0 failed (after merging main, which brought #1921 and #1922).VRRP reserves 255 for the router whose own interface address is one of the group's virtual addresses, and the election here has voted that way since VRRP was modelled. The Pri column printed the configured value instead, so a router that owned the virtual gateway showed 100 in the table explaining why it had just outranked a 254 - and the timeline event carried the same number. electMaster() now reports both numbers per candidate (priority, configured); show vrrp prints the one in force and adds a note naming the address it holds, the owner mode, and the fact that `vrrp <vrid> priority` cannot set 255. show running-config keeps the configured value. Sources: Cisco IOS FHRP Configuration Guide ('its priority is fixed at 255'), Nexus 5600 Unicast Routing Guide ('255 for a master that has an interface IP address equal to the virtual IP address'), RFC 5798 5.2.2, and the ASR 900 VRRPv3 'Priority is 255 (owner mode)' sample. research/show-vrrp-owner-priority.md records them and the one question left open. test/show-vrrp-owner-priority.test.js (28 checks).This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
2b23446f75f4e07ee512