research(cli): deleting a VLAN under a restricted trunk - no refusal shown, no rewrite shown #2056
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!2056
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1119-0012"
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?
One narrow question: with
switchport trunk allowed vlan 10-30on a port, what doesno vlan 22do - refuse, or delete and leave the list as typed?Verdict: no source shows a refusal; what the list does afterwards is unresolved, so nothing in the engine changed. Six configuration guides (2960 12.2(55)SE, 3560 12.2(50)SE, 9200 16.11, plus the trunk chapters of 9300 17.17, 9500 17.13 and ESS3300) describe deletion unconditionally and warn only that access ports go inactive. The trunk chapters define membership as enabled AND known to VTP AND in the allowed list, so a deleted VLAN stops being carried with no edit to the list - and the same paragraph says VTP adding a VLAN does not add it to the list either.
What is missing is any transcript of
show running-config interface/show interfaces trunkafter the deletion, so whether the list survives verbatim or is rewritten (asswitchport trunk allowed vlan remove 22would rewrite it) is recorded as unresolved.engine/cli.jschanges in comments only: the guard's stated reason ("deleting a VLAN does rewrite a trunk's allowed list") was unsourced, and now points atresearch/trunk-allowed-vlan-on-vlan-delete.md, which lists the four-reference family (live trunk, native VLAN, staged list, voice VLAN), the evidence, and the single paste that would settle it.Gates:
node scripts/syntax-check.js430 files OK; fullnpm test354 suites / 12,234 assertions, 0 failed;node scripts/check-doc-citations.jsclean.The 'no vlan' guard still refuses when a trunk carries the VLAN ("% VLAN 22 is still carried by 1 port(s): Fa0/3 - move them off it first") and explains itself with a claim no source in hand supports: that deleting a VLAN rewrites that trunk's allowed list. Six configuration guides across four Catalyst product lines describe the deletion unconditionally and warn only that access ports go inactive; the trunk guides define membership as enabled AND known to VTP AND in the allowed list, so a deleted VLAN stops being carried without any list edit, and VTP adding a VLAN does not edit the list either. What the running-config line does afterwards is still not witnessed by any transcript, so the refusal stays and the note records the one paste that would settle it. engine/cli.js changes in comments only; no behaviour.