research(svi): a factory switch has a Vlan1, and this console has no SVI #2075

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

Question

Does an IOS-like switch have a VLAN 1 interface before anybody configures anything - and what do show running-config, show ip interface brief and show interfaces print for it?

Evidence (8 sources, in research/svi-vlan1-default-state.md)

  • Catalyst 9300 16.12 CR, show running-config capture: interface Vlan1 / no ip address / the shutdown line, in a box nobody configured VLAN 1 on.
  • Catalyst 9200 CR, five releases (16.10, 17.7, 17.12, 17.13, 26.x): Vlan1 unassigned YES NVRAM administratively down down.
  • Catalyst 6500 guide: Vlan1 unassigned YES NVRAM down down; a 1905 ISR paste: Vlan1 unassigned YES unset down down.
  • 2960-X 15.2(2)E guide: the three autostate conditions for an SVI line state.
  • 2960 12.2(58)SE guide: interface vlan <id> is the documented way to address a switch, show interfaces vlan <id> the verify step.

Verdict

The interface exists on the box and does not exist here: PacketForge refuses interface vlan 1 as an unknown name and prints no Vlan1 row. The row cells disagree across platforms (administratively down vs down, NVRAM vs unset), so no wording was adopted, and an honest Vlan1 row needs an interface object with autostate - a feature this run may not add. No engine code, no test; the note records the measurement, the inferred explanation (shutdown by default) and the transcript that would settle the rest.

Checks

node scripts/syntax-check.js 435 files OK; check-control-bytes clean; check-doc-citations 356 citations, 2 allowed pre-existing suspects; full npm test: 358 suites, 12318 assertions passed, 0 failed (no engine change).

## Question Does an IOS-like switch have a VLAN 1 interface before anybody configures anything - and what do `show running-config`, `show ip interface brief` and `show interfaces` print for it? ## Evidence (8 sources, in `research/svi-vlan1-default-state.md`) * Catalyst 9300 16.12 CR, `show running-config` capture: `interface Vlan1` / `no ip address` / the shutdown line, in a box nobody configured VLAN 1 on. * Catalyst 9200 CR, five releases (16.10, 17.7, 17.12, 17.13, 26.x): `Vlan1 unassigned YES NVRAM administratively down down`. * Catalyst 6500 guide: `Vlan1 unassigned YES NVRAM down down`; a 1905 ISR paste: `Vlan1 unassigned YES unset down down`. * 2960-X 15.2(2)E guide: the three autostate conditions for an SVI line state. * 2960 12.2(58)SE guide: `interface vlan <id>` is the documented way to address a switch, `show interfaces vlan <id>` the verify step. ## Verdict The interface exists on the box and does not exist here: PacketForge refuses `interface vlan 1` as an unknown name and prints no `Vlan1` row. The row cells disagree across platforms (`administratively down` vs `down`, `NVRAM` vs `unset`), so no wording was adopted, and an honest `Vlan1` row needs an interface object with autostate - a feature this run may not add. No engine code, no test; the note records the measurement, the inferred explanation (shutdown by default) and the transcript that would settle the rest. ## Checks `node scripts/syntax-check.js` 435 files OK; `check-control-bytes` clean; `check-doc-citations` 356 citations, 2 allowed pre-existing suspects; full `npm test`: **358 suites, 12318 assertions passed, 0 failed** (no engine change).
research(svi): a factory switch has a Vlan1, and this console has no SVI
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 13s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
7291d34984
Asks one question: does an IOS-like switch have a VLAN 1 interface before anybody configures it, and how do show running-config, show ip interface brief and show interfaces print it? Eight sources: a 9300 running-config capture with the shut Vlan1 stanza, five releases of the 9200 reference printing 'Vlan1 unassigned YES NVRAM administratively down down', a 6500 and a 1905 capture printing 'down down' / 'unset', the SVI autostate rule from the 2960-X guide, and the 2960 guide's interface vlan / show interfaces vlan steps.

Verdict: the interface exists; PacketForge has no SVI object at all (interface vlan 1 is refused as an unknown name, and no Vlan1 row is printed). The row's cells are contradictory across platforms, and an honest row needs an interface with autostate - new capability, so no engine change and no test. The note records what would settle the wording.
forgejo-actions force-pushed rev/1119-0242 from 7291d34984
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Server smoke test (pull_request) Successful in 13s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 3s
to 3050a50a54 2026-11-19 02:56:37 +00:00
Compare
jaylouisw force-pushed rev/1119-0242 from 3050a50a54 to d0db1f7fc6
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-19 03:13:08 +00:00
Compare
forgejo-actions force-pushed rev/1119-0242 from d0db1f7fc6
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 3s
to 740a4235b6 2026-11-19 03:13:29 +00:00
Compare
jaylouisw force-pushed rev/1119-0242 from 740a4235b6 to 18838f9938
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-19 03:47:11 +00:00
Compare
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 03:50:24 +00:00
jaylouisw deleted branch rev/1119-0242 2026-11-19 03:51:50 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!2075
No description provided.