engine(vlan): no vlan 22 is accepted while a trunk's list names it #2427
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!2427
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1121-1312"
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
no vlan 22while a trunk'sswitchport trunk allowed vlanlist names 22: does a Cisco IOS-style switch refuse the command, and does the list change afterwards?Verdict
Settled, and the console was wrong. Deleting a VLAN is a VLAN-database operation; the interface line is configuration and survives it, and the port stops carrying the VLAN because a trunk port is a member of a VLAN only while that VLAN exists.
Sources:
Vlans allowed on trunk(configuration) vsVlans allowed and active in management domain(database/STP).What changed
engine/cli.js-no vlan <id>no longer refuses for a live trunk. It deletes the VLAN, printsFa0/3 stops carrying VLAN 22: the switchport configuration is unchanged (vlan 22 brings it back)(native VLANs marked(native)), and leaves theswitchport trunk ...lines exactly as typed. Ports that only reference the VLAN (native/allowed stored on a non-trunk port, voice VLAN) still refuse - unsettled.engine/device.js-Device.knowsVlan(id): built-ins always exist, others only while inconfig.vlans;nullon a box with no VLAN database.engine/simulator.js- frames in a VLAN the database does not hold are dropped at ingress (so nothing is learned in a VLANshow vlanno longer prints) and at egress; L2-only, and LLDP exempt as it already was from the allowed list.test/vlan-delete-leaves-port-inactive.test.js(39 checks) andtest/show-interfaces-port.test.js(47) pin the receipt, the untouched backup, the drop counter and the MAC table; two mismatch fixtures that used a nonexistent native VLAN now create it.docs/CLI.md,docs/plans/interfaces-trunk-view.md,research/trunk-allowed-vlan-on-vlan-delete.mdupdated; CHANGELOG entry added.Gates
node scripts/syntax-check.js- 534 files, all OKnpm test- 454 suites, 15434 assertions, 0 failedStill open
The native-VLAN variant has no direct transcript (treated the same way, recorded in the research note);
show interfaces trunk(where the deleted VLAN would drop out of the "active" list) is still a plan step; references that are stored but not in force still refuse.Deleting a VLAN is a VLAN-database operation, and a trunk's `switchport trunk allowed vlan ...` line is configuration: the list is not rewritten and the port stops carrying the VLAN because a trunk port is a member of a VLAN only while that VLAN exists. Two operators answer the exact question on Cisco Community ("No, you need to remove it manually from the trunk interface"; "only deleting it ('no vlan 30') won't make it disappear from the interface's config"), and the Catalyst 9300 trunk guide states the three-part membership test. The console answered with a sentence no box prints ("% VLAN 22 is still carried by 1 port(s) ...") and kept the VLAN. It now commits the deletion, names the trunks that stop carrying it, and leaves their lines exactly as typed; the data path drops frames for a VLAN the database does not hold, on ingress and on egress, while LLDP stays exempt as it was from the allowed list. Ports that only reference a VLAN without carrying it still refuse, because no source says what a box does with a reference that is not in force. research/trunk-allowed-vlan-on-vlan-delete.md carries the sources and the native-VLAN paste that is still open.