mac table: a bundled address is named on the port-channel, not the member that carried it #1951
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!1951
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1118-0701"
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?
A real IOS switch learns a source address against the port-channel, not the member the frame arrived on. PacketForge learned on the member, so one address moved between
Fa0/2andFa0/3as the hash varied.Evidence
show mac-address-table dynamic: "The output for an EtherChannel interface changes the port number designation (for example, 5/7) to a port group number (for example, Po80)" - the same sentence in five releases (12.2(20)EW, 12.2(25)EWA, 12.2(31)SGA, IOS XE 3.8/15.2(4)E).100 20bb.c05e.5318 DYNAMIC Po1besideDYNAMIC Gi1/0/1, same table furniture this model prints.DYNAMIC Po1rows in three VLANs.Change
macRows()namesPo<id>for a member that is in the bundle; the physical port stays on the row aslearnedOn, soshow mac address-table interface <member>still answers.Simulator._logicalPortNamegives the spanning tree.lag.portChannelName()shared withshow etherchannel summary.Unresolved (in
research/mac-table-port-channel-name.md):show mac address-table interface Po1does not resolve here (a bundle is not an interface object), andshow spanning-treestill printslag-1.Gates:
node scripts/syntax-check.js407 files OK; full suite 334 suites, 11,570 assertions, 0 failed; new suitetest/mac-table-port-channel-name.test.js12 assertions.54d6ef22de985af11b26