show vlan brief: a trunk port is in no row, and a trunk's allowed list creates no VLAN #1638
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!1638
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1116-0830"
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?
Question
On a Cisco-style access switch, does
show vlan brieflist a trunk port in the VLANs it carries?Verdict
No. The Ports column is access membership, and the row set is the VLAN database.
show vlan: "When displaying multiple VLANs only non-trunk ports are displayed";show vlan all-portsexists to add trunks.PacketForge listed a trunk in every VLAN it carried, because membership was decided by
classifyEgress()- the data plane rule (#1261), right about forwarding and wrong about this table. It also invented rows for VLANs that only a trunk'sallowed vlanlist named.Changed
engine/cli.js:show vlan/show vlan briefbuilds rows from the VLAN database only, and skips trunk-mode ports in the Ports cell.test/show-vlan.test.js: membership section asserts the vendor rule (listed iff access port belonging to the VLAN), plus a lab where a trunk allows two VLANs nobody created.test/trunk-allowed-add-remove.test.js: theshow vlan briefcheck now expects no rows for non-existent VLANs and no trunk in any row.docs/CLI.md: theshow vlanrow says access ports.research/vlan-brief-trunk-ports.md: evidence, the unconnected-trunk contradiction, and the EtherChannel /show vlan iditems left open.classifyEgress()is untouched: the data plane still forwards every VLAN a trunk allows.Tests
node scripts/syntax-check.js- 345 files OK;npm test- 275 suites, 9851 assertions, 0 failed.cba17987e5c466bb56ec