cli(trunk): a trunk pruned to nothing is a state a box takes, not a refusal #2420

Merged
jaylouisw merged 1 commit from rev/1121-1212 into main 2026-11-21 12:38:41 +00:00
Owner

switchport trunk allowed vlan remove 1-4094 was refused with % that would leave the trunk allowing no VLANs: name what it should carry instead … — a sentence no box prints. remove subtracts from the list the port carries, the default is 1-4094, and none is a documented allowed-list value meaning an empty list, so the destination is a state the device has. Two field configurations prune a trunk exactly this way before adding the VLANs it should carry.

The subtraction now commits:

  • remove 1-4094 / remove 1-1001,1006-4094 store the four pinned media defaults (1002-1005), which cannot come off a trunk;
  • remove 10,20 on a list of 10,20 stores the empty list none stores, and the backup prints switchport trunk allowed vlan none;
  • except 1-4094 reaches the same pinned remainder and is committed the same way.

Evidence: Tagged only Management VLAN procedure (working remove 1-4094 config), SF350-48 thread (remove 1-4094 then add 10,11,…), Catalyst 9400 VLAN guide (syntax, default all), 9300 command reference (none = empty list), and the TAC note on the pinned 1002-1005 block.

research/trunk-allowed-remove-everything.md records known/inferred/unresolved, including whether a box prints 1002-1005 or none after the full removal, and a sibling (removed ) wording defect for reserved-only removals left for its own run.

Tests: 452 suites, 15331 assertions, 0 failed (npm test).

`switchport trunk allowed vlan remove 1-4094` was refused with `% that would leave the trunk allowing no VLANs: name what it should carry instead …` — a sentence no box prints. `remove` subtracts from the list the port carries, the default is 1-4094, and `none` is a documented allowed-list value meaning an empty list, so the destination is a state the device has. Two field configurations prune a trunk exactly this way before adding the VLANs it should carry. The subtraction now commits: - `remove 1-4094` / `remove 1-1001,1006-4094` store the four pinned media defaults (1002-1005), which cannot come off a trunk; - `remove 10,20` on a list of `10,20` stores the empty list `none` stores, and the backup prints `switchport trunk allowed vlan none`; - `except 1-4094` reaches the same pinned remainder and is committed the same way. Evidence: [Tagged only Management VLAN procedure](https://community.cisco.com/t5/switching/tagged-only-management-vlan-procedure/td-p/4595901) (working `remove 1-4094` config), [SF350-48 thread](https://community.cisco.com/t5/switches-small-business/cli-not-view-configuration-for-trunk-port-on-sf350-48/td-p/3724303) (`remove 1-4094` then `add 10,11,…`), [Catalyst 9400 VLAN guide](https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9400/software/release/17-14/configuration_guide/vlan/b_1714_vlan_9400_cg/configuring_vlan_trunks.html) (syntax, default all), [9300 command reference](http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/software/release/17-13/command_reference/b_1713_9300_cr/vlan_commands.html) (`none` = empty list), and the TAC note on the pinned 1002-1005 block. `research/trunk-allowed-remove-everything.md` records known/inferred/unresolved, including whether a box prints `1002-1005` or `none` after the full removal, and a sibling `(removed )` wording defect for reserved-only removals left for its own run. Tests: 452 suites, 15331 assertions, 0 failed (`npm test`).
cli(trunk): a trunk pruned to nothing is a state a box takes, not a refusal
All checks were successful
CI / Server smoke and Docker build (pull_request) Successful in 30s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Test (Node 20) (pull_request) Successful in 1m3s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
6a6f218e06
switchport trunk allowed vlan remove 1-4094 was refused with a sentence no box prints. remove subtracts from the list the port carries, the default is 1-4094, and none is a documented allowed-list value meaning an empty list, so the destination is a state the device has. Two field configurations prune a trunk exactly this way before adding the VLANs it should carry. The subtraction now commits: remove 1-4094 and remove 1-1001,1006-4094 store the four pinned media defaults (1002-1005); remove 10,20 on a list of 10,20 stores the empty list none stores. except 1-4094 reaches the same remainder and is committed the same way. tests: 452 suites, 15331 assertions. research/trunk-allowed-remove-everything.md records the captures and the open half (whether a box prints 1002-1005 or none after the full removal).
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 12:32:26 +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!2420
No description provided.