show etherchannel summary: the device's key, counts and Po1(SU) cell, and a Protocol column that names a protocol #1619

Merged
jaylouisw merged 1 commit from rev/1116-0630 into main 2026-11-16 06:47:06 +00:00
Owner

show etherchannel summary printed a table this console invented: Group Protocol Ports, no flag
legend, no counts, no port-channel column - and a Protocol cell holding the negotiation mode as LACP (active)
or Static, which no box prints.

A Catalyst prints a fixed nine-line flag key, then Number of channel-groups in use / Number of aggregators,
then Group Port-channel Protocol Ports over a drawn rule, and each row carries the bundle's own flags in
a Po1(SU) cell (S = Layer2, U = in use, D when no member can carry).

  • the key, both counts, the header and the rule verbatim, including the header's two-column drift from its own
    rows (that drift is the device's);
  • Po1(SU) / Po1(SD), following whether any member can carry a frame;
  • Protocol = LACP for active/passive, - for mode on - Cisco's own lab transcript prints -, because on
    negotiates nothing. The mode is still readable in show running-config, where a box keeps it.

Evidence: Catalyst SD-WAN 26.x interface guide, Catalyst 9500 (17.10) and 2960-X (15.2(4)E) command
references, two Cisco-authored EtherChannel labs, and a Cisco Community transcript showing Po26(SD) beside a
static -. What is inferred, and what is unresolved (a box with zero groups; show etherchannel <n> summary
refuses its argument), is written up in research/etherchannel-summary-layout.md.

Tests: new test/etherchannel-summary-layout.test.js (28 assertions); lag-mode (54), show-view-phrase (48)
and no-command-touches-only-what-it-names updated because they pinned the old header cells. Full suite: 270
suites, 9735 assertions, 1 failure - property-validator.test.js (E_PROTOCOL_MISMATCH on seed 36), which
fails identically on origin/main with this change stashed.

`show etherchannel summary` printed a table this console invented: `Group Protocol Ports`, no flag legend, no counts, no port-channel column - and a Protocol cell holding the negotiation mode as `LACP (active)` or `Static`, which no box prints. A Catalyst prints a fixed nine-line flag key, then `Number of channel-groups in use` / `Number of aggregators`, then `Group Port-channel Protocol Ports` over a drawn rule, and each row carries the bundle's own flags in a `Po1(SU)` cell (S = Layer2, U = in use, D when no member can carry). - the key, both counts, the header and the rule verbatim, including the header's two-column drift from its own rows (that drift is the device's); - `Po1(SU)` / `Po1(SD)`, following whether any member can carry a frame; - Protocol = `LACP` for active/passive, `-` for `mode on` - Cisco's own lab transcript prints `-`, because `on` negotiates nothing. The mode is still readable in `show running-config`, where a box keeps it. Evidence: Catalyst SD-WAN 26.x interface guide, Catalyst 9500 (17.10) and 2960-X (15.2(4)E) command references, two Cisco-authored EtherChannel labs, and a Cisco Community transcript showing `Po26(SD)` beside a static `-`. What is inferred, and what is unresolved (a box with zero groups; `show etherchannel <n> summary` refuses its argument), is written up in `research/etherchannel-summary-layout.md`. Tests: new `test/etherchannel-summary-layout.test.js` (28 assertions); `lag-mode` (54), `show-view-phrase` (48) and `no-command-touches-only-what-it-names` updated because they pinned the old header cells. Full suite: 270 suites, 9735 assertions, 1 failure - `property-validator.test.js` (`E_PROTOCOL_MISMATCH` on seed 36), which fails identically on origin/main with this change stashed.
show etherchannel summary: the device's key, counts and Po1(SU) cell, and a Protocol column that names a protocol
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 48s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 1m32s
CI / Test (Node 18) (pull_request) Failing after 1m40s
CI / Test (Node 22) (pull_request) Failing after 1m49s
c2f865c9f4
The table started at a header this console invented - `Group  Protocol  Ports` - with no legend, no
counts and no port-channel column, and its Protocol cell carried the negotiation mode as `LACP
(active)` or `Static`, strings no box produces (Cisco's own lab transcript reads `-` for `mode on`).

A Catalyst prints a fixed nine-line flag key, `Number of channel-groups in use` and `Number of
aggregators`, then `Group  Port-channel  Protocol    Ports` over a drawn rule, and each row carries the
bundle's flags in a `Po1(SU)` cell - S for Layer2, U in use, D when no member can carry. Evidence and
the points that are inferred rather than read: research/etherchannel-summary-layout.md.

The header's two-column drift from its own rows is the device's and is reproduced; the mode is still
readable in show running-config, where a box keeps it.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 06:46:56 +00:00
jaylouisw force-pushed rev/1116-0630 from c2f865c9f4
Some checks failed
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Server smoke test (pull_request) Successful in 48s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Failing after 1m32s
CI / Test (Node 18) (pull_request) Failing after 1m40s
CI / Test (Node 22) (pull_request) Failing after 1m49s
to fbb9d5a881
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
2026-11-16 06:46:59 +00:00
Compare
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!1619
No description provided.