research(stp): a modelled Catalyst runs Rapid PVST+, so the word is rstp not ieee #2008

Merged
jaylouisw merged 1 commit from rev/1118-1701 into main 2026-11-18 17:45:04 +00:00
Owner

One narrow question: is ieee the mode a modelled Catalyst is in before any configuration, and what does a real box print on show spanning-tree's first line?

Finding. Cisco documents the default mode per platform and release: the 2960-X is PVST+ at 15.2(2)E but Rapid PVST+ from 15.2(4)E, and the 9200 ships in Rapid PVST+. A box in Rapid PVST+ prints Spanning tree enabled protocol rstp; ieee is the PVST+ word. PacketForge prints ieee for all 19 Catalyst 9000 / 2960-X entries and times every port at 2x forward delay (30 s), so both halves of the answer describe a mode Cisco stopped defaulting to.

The trap is that RSTP re-uses the same hello/max-age/forward-delay numbers (the 9200 default table prints 2 s / 20 s / 15 s), so neither a timer test nor the convergence figure can tell the modes apart - only the protocol word can, and nothing pins it (test/l2.test.js:205 only checks that the command runs).

No engine change. The remedy is a second protocol mode - RSTP transition rules, per-VLAN instances and a spanning-tree mode command - which is a feature. Swapping the word alone would make the console claim rstp while converging like 802.1D. The note records what is known, what a boot capture would settle (timing on a 9200 edge port; whether spanning-tree mode pvst flips the word), and why the catalogue cannot answer it per device: a device entry carries no software release.

Also recorded, not acted on: the same 9200 table shows the long path-cost method as its default (1 Gb = 20000), while engine/stp.js implements the short table - a separate question.

Docs only: research/stp-mode-default.md (117 lines, 11 sources).

Gates: check-control-bytes clean; syntax-check 419 files OK; full npm test 345 suites, 11982 assertions, 0 failed.

One narrow question: is `ieee` the mode a modelled Catalyst is in before any configuration, and what does a real box print on `show spanning-tree`'s first line? **Finding.** Cisco documents the default mode per platform and release: the 2960-X is PVST+ at 15.2(2)E but **Rapid PVST+ from 15.2(4)E**, and the 9200 ships in Rapid PVST+. A box in Rapid PVST+ prints `Spanning tree enabled protocol rstp`; `ieee` is the *PVST+* word. PacketForge prints `ieee` for all 19 Catalyst 9000 / 2960-X entries **and** times every port at 2x forward delay (30 s), so both halves of the answer describe a mode Cisco stopped defaulting to. The trap is that RSTP re-uses the same hello/max-age/forward-delay numbers (the 9200 default table prints 2 s / 20 s / 15 s), so neither a timer test nor the convergence figure can tell the modes apart - only the protocol word can, and nothing pins it (`test/l2.test.js:205` only checks that the command runs). **No engine change.** The remedy is a second protocol mode - RSTP transition rules, per-VLAN instances and a `spanning-tree mode` command - which is a feature. Swapping the word alone would make the console claim rstp while converging like 802.1D. The note records what is known, what a boot capture would settle (timing on a 9200 edge port; whether `spanning-tree mode pvst` flips the word), and why the catalogue cannot answer it per device: a device entry carries no software release. Also recorded, not acted on: the same 9200 table shows the **long** path-cost method as its default (1 Gb = 20000), while `engine/stp.js` implements the short table - a separate question. Docs only: `research/stp-mode-default.md` (117 lines, 11 sources). **Gates:** `check-control-bytes` clean; `syntax-check` 419 files OK; full `npm test` **345 suites, 11982 assertions, 0 failed**.
research(stp): a modelled Catalyst runs Rapid PVST+, so the word is rstp not ieee
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 7s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 22s
4f1eaba7ea
The default spanning-tree mode is documented per platform: the 2960-X is PVST+ at 15.2(2)E but Rapid PVST+ from 15.2(4)E, and the 9200 ships in Rapid PVST+. A box in Rapid PVST+ prints 'Spanning tree enabled protocol rstp'; 'ieee' is the PVST+ word, and PacketForge prints ieee for all 19 Catalyst 9000/2960-X entries.

Both halves of the answer describe one mode: the word (engine/cli.js) and the 2x forward-delay timing (engine/convergence.js). RSTP re-uses the same hello/max-age/forward-delay numbers, so no timer test can tell the modes apart.

Not adopted: the remedy is a second protocol mode - transition rules, per-VLAN instances, a spanning-tree mode command - which is a feature, and swapping the word alone would make the console claim rstp while converging like 802.1D. The note records what is known, what a boot capture would settle, and why the catalogue cannot answer it per device (no software release on a device entry).
forgejo-actions force-pushed rev/1118-1701 from 4f1eaba7ea
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 7s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 22s
to 5fe86b1db9 2026-11-18 17:20:23 +00:00
Compare
forgejo-actions force-pushed rev/1118-1701 from 5fe86b1db9 to 984a23f53c
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 3s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 31s
2026-11-18 17:24:53 +00:00
Compare
jaylouisw deleted branch rev/1118-1701 2026-11-18 17:45:06 +00:00
Author
Owner

Dispatch gap solved — close/reopen re-emits the event and CI runs. Merged as f9b18c28.

The missing checks were not event loss on the branch: run 6481 shows this PR's first SHA 4f1eaba7 did get 8 checks, then pr-rebase.yml rebased onto the new main and force-pushed 984a23f5, and the synchronize event for that workflow push never produced a run. A same-token no-op push reproduces the silence; a close + reopen (PATCH state=closed -> open) does not — it re-emits pull_request opened, and run 6491 built and passed 8/8 on 984a23f5 within 90 s.

Workaround for the sibling loops: if a rebased PR sits with zero checks, close and reopen it rather than force-pushing again.

**Dispatch gap solved — close/reopen re-emits the event and CI runs.** Merged as `f9b18c28`. The missing checks were not event loss on the branch: run 6481 shows this PR's *first* SHA `4f1eaba7` did get 8 checks, then `pr-rebase.yml` rebased onto the new main and force-pushed `984a23f5`, and the synchronize event for that workflow push never produced a run. A same-token no-op push reproduces the silence; a **close + reopen (PATCH state=closed -> open)** does not — it re-emits `pull_request opened`, and run 6491 built and passed 8/8 on `984a23f5` within 90 s. Workaround for the sibling loops: if a rebased PR sits with zero checks, close and reopen it rather than force-pushing again.
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!2008
No description provided.