a two-member LAG drops all traffic when one member's link goes down #1515
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1515
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
_forwardL2builds its usable-member list and filters out STP-blocked ports, wrong-VLAN ports and the ingress port - but not ports whose link is down. The hash then picks among all members, may pick the dead one, and_deliverdrops the frame with reasonlink down.Measured: a two-member
channel-group 1between two switches, with member 1's cable pulled, loses the ping entirely. Reproduced isolated.Expected: a LAG with one live member carries traffic. Losing one member of a bundle is the case bundles exist for.
Why it matters beyond the lab: "no single cable failure kills HA" is one of the intent checks a plan is supposed to be scored against, and the most common HA implementation in a homelab is a two-member LAG. As it stands the simulator fails that check for a simulator reason, which makes the check worthless the first time it is used.
Where:
engine/simulator.js_forwardL2usable-port list;_deliverrejection path.Suggested fix: exclude
ifaceStatus-down members from the hash, and if the bundle has no usable member, fail with a code that names the bundle rather than dropping the frame silently.Found by the w7 intent-check study, probe6.js.