docs(CLI): the eight-link example is typed at a port that is already in the bundle #2112

Merged
jaylouisw merged 1 commit from fix/1119-0702 into main 2026-11-19 07:13:20 +00:00
Owner

The EtherChannel transcript printed a join refusal over channel-group 1 mode on typed at Gi1/0/9 — the socket that joined the group as hot-standby in the line above. _channelGroup() answers that line on the mode-change path (alreadyIn + retuning + held > cap), so the console prints % Channel group 1 not moved to mode on: it holds 10 members, …; the refusal on the page is one the console gives a port the group does not hold.

The example now follows the session it is a transcript of:

  • both standby receipts (Gi1/0/9 and Gi1/0/10 — the summary table below already showed both as (H));
  • the mode-change refusal where the console really gives it, with the group's own count of ten;
  • the join refusal at Gi1/0/11, outside the ten-member bundle, which is the case the page was trying to show.

test/docs-cli-transcript.test.js now replays the section's three fences against a C2960X-48FPS-L, prompt for prompt and line for line (the DHCP section's replay is the same helper now), so the answers and the port they are typed at cannot drift from the code again. Written failing first: before the page change it reported the page's join refusal against the console's mode-change one.

Supersedes the transcript half of #2033, whose engine half landed in #2069 — that PR's branch also no longer applies to main.

Gates: scripts/syntax-check.js 443 files OK; check-control-bytes clean; check-doc-citations 356 citations, none judged stale; npm test 364 suites, 12,425 assertions, 0 failed.

The EtherChannel transcript printed a join refusal over `channel-group 1 mode on` typed at **Gi1/0/9** — the socket that joined the group as hot-standby in the line above. `_channelGroup()` answers that line on the mode-change path (`alreadyIn` + `retuning` + `held > cap`), so the console prints `% Channel group 1 not moved to mode on: it holds 10 members, …`; the refusal on the page is one the console gives a port the group does not hold. The example now follows the session it is a transcript of: * both standby receipts (Gi1/0/9 and Gi1/0/10 — the summary table below already showed both as `(H)`); * the mode-change refusal where the console really gives it, with the group's own count of ten; * the join refusal at **Gi1/0/11**, outside the ten-member bundle, which is the case the page was trying to show. `test/docs-cli-transcript.test.js` now replays the section's three fences against a C2960X-48FPS-L, prompt for prompt and line for line (the DHCP section's replay is the same helper now), so the answers and the port they are typed at cannot drift from the code again. Written failing first: before the page change it reported the page's join refusal against the console's mode-change one. Supersedes the transcript half of #2033, whose engine half landed in #2069 — that PR's branch also no longer applies to `main`. Gates: `scripts/syntax-check.js` 443 files OK; `check-control-bytes` clean; `check-doc-citations` 356 citations, none judged stale; `npm test` 364 suites, 12,425 assertions, 0 failed.
docs(CLI): the eight-link example is typed at a port that is already in the bundle
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 18) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 3s
f164922091
The transcript in "A bundle carries eight links" printed a join refusal over `channel-group 1 mode on` typed at
Gi1/0/9 — the socket that joined the group as hot-standby in the line above. `_channelGroup()` answers that line
on the mode-change path, not the join path, so the console prints
`% Channel group 1 not moved to mode on: it holds 10 members, ...` there; the refusal on the page is one the
console gives a port the group does not hold.

The example now follows the session it is a transcript of: both standby receipts (Gi1/0/9 and Gi1/0/10, which
the summary table already showed as `(H)`), the mode-change refusal where the console really gives it, and the
join refusal at Gi1/0/11, outside the ten-member bundle. The running count is the group's own ten rather than
nine, which is what the console answers.

`test/docs-cli-transcript.test.js` replays the section's three fences against a 2960X, prompt for prompt, so the
answers and the port they are typed at cannot drift from the code again (the DHCP section's replay is the same
helper now).

Supersedes the transcript half of #2033, whose engine half landed in #2069.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 07:10:11 +00:00
jaylouisw deleted branch fix/1119-0702 2026-11-19 07:13:21 +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!2112
No description provided.