A LAG keeps hashing traffic onto a member whose link is down #1263
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1263
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?
What happens
Two switches joined by a two-member port-channel. With both cables in, a ping crosses. Take one cable
out and every ping fails:
lagLib.selectMember()filtered onenabledand nothing else, and the forwarding path's candidate listfiltered spanning tree and VLAN membership and nothing else. So the hash kept landing on the unplugged member
— and
Fa0/2, which was up and idle, carried nothing.show etherchannel summaryreported both members(P)throughout:(P)meaning "this port is carrying traffic", printed for a port whose link was down.Why it matters
A bundle is supposed to survive losing a member — that is the entire reason to build one. Here, losing a
member cost roughly half the flows (whatever hashed to it) while the surviving member sat idle, and the only
clue was a drop count on a port that looked bundled.
Expected
shut, it is administratively down, or spanning tree blocks it;
with nothing wrong, the selection is byte-for-byte what it was, so flows do not re-balance on an unrelated
change;
reason, so the loss stays countable (#1258) rather than disappearing into a bundle that looks healthy;
show etherchannel summarymarks(P)only for members that can carry,(D)otherwise, says why in thesame sentence
show interfacesuses, and reports how many members the bundle is running on;lagtimeline event records the eligible members, so a viewer can see why one was not chosen.Scope
The existing LAG selection rule, the existing forwarding candidate list, and the existing
show etherchanneloutput. No new commands.