show vlan prints VLAN 1 twice and puts every trunk in VLAN 1 #1261
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1261
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
show vlanprints two tables under one header:VLAN 1 twice, with different names and different port lists. The cause is a pseudo-key
all: a trunk whoseallowed list is
allwas pushed into VLAN 1 under the keyall, and that key was then rendered as VLAN 1.So a trunk carrying every VLAN is reported as a member of VLAN 1 and of nothing else.
The rest of the table disagrees with the data plane too: a trunk appears in VLAN 1 whether or not its allowed
list includes VLAN 1, and the
(n)/(t)/(trunk)decorations describe an intent rather than whatclassifyEgress()would actually forward.show spanning-treealso answers the wrong question: with no simulation run it saysNo bridged ports: this device is not part of any L2 loop.— a claim about the lab, printed when the truthis that nothing has computed the tree yet. Same defect class as
show interfacescounters (#1252).Expected
classifyEgress()— the rule the data plane forwards by — so an access port appearsin its access VLAN only, a trunk in exactly the VLANs its allowed list carries (not VLAN 1 merely for
being a trunk), and an
alltrunk in every row;show vlan briefis the same table;show spanning-treesaysNot measured (no simulation run)when nothing has run, and "no ports arebridging" only when something has.
Scope
The existing
show vlanandshow spanning-treeoutput. No new commands.show vlanprinted VLAN 1 twice, and put every trunk in VLAN 1 (#1261) #1262