research(cli): deleting a VLAN under a restricted trunk - no refusal shown, no rewrite shown #2056

Merged
jaylouisw merged 1 commit from rev/1119-0012 into main 2026-11-19 00:39:03 +00:00
Owner

One narrow question: with switchport trunk allowed vlan 10-30 on a port, what does no vlan 22 do - 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 trunk after the deletion, so whether the list survives verbatim or is rewritten (as switchport trunk allowed vlan remove 22 would rewrite it) is recorded as unresolved. engine/cli.js changes in comments only: the guard's stated reason ("deleting a VLAN does rewrite a trunk's allowed list") was unsourced, and now points at research/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.js 430 files OK; full npm test 354 suites / 12,234 assertions, 0 failed; node scripts/check-doc-citations.js clean.

One narrow question: with `switchport trunk allowed vlan 10-30` on a port, what does `no vlan 22` do - 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 trunk` after the deletion, so whether the list survives verbatim or is rewritten (as `switchport trunk allowed vlan remove 22` would rewrite it) is recorded as unresolved. `engine/cli.js` changes in comments only: the guard's stated reason ("deleting a VLAN does rewrite a trunk's allowed list") was unsourced, and now points at `research/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.js` 430 files OK; full `npm test` 354 suites / 12,234 assertions, 0 failed; `node scripts/check-doc-citations.js` clean.
research(cli): deleting a VLAN under a restricted trunk - no source shows a refusal, and none shows the list rewritten
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Classify the change (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 11s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 3s
3905e78805
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.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 00:30:26 +00:00
jaylouisw deleted branch rev/1119-0012 2026-11-19 00:39:05 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2056
No description provided.