brief: an EtherChannel is an interface, and it has a row #2035

Merged
jaylouisw merged 1 commit from rev/1118-2042 into main 2026-11-18 22:45:44 +00:00
Owner

show ip interface brief listed only the member ports of an EtherChannel. A bundle is an interface and a box prints its row:

  • Port-channel2 unassigned YES unset up up on a 3850 — Cisco doc 221664
  • Port-channel1 ... down down while its members were suspended — Cisco doc 225790
  • a 3750X table ending Port-channel1 ... up up / Port-channel20 ... down down after Te1/1/2 — community capture
  • one capture showing both spellings: 4 Po4(SU) LACP Gi4/31(P) in the summary, Port-channel4 ... up up in the brief table — community capture

The row is spelled out (Port-channel<n>, not the Po1 the summary and MAC table print), carries unassigned YES unset because this model builds no Layer 3 bundle, and is up up only when at least one member is really in the bundle — a bundle of stand-alone members reads down down while each member reads up up, the same predicate the summary prints as Po1(SD) with (I) members.

The per-member rule moved out of show etherchannel summary into _lagMemberStates(), so the letters and the bundle row cannot disagree; engine/lag.js now names the bundle in both spellings.

Tests: test/brief-port-channel-row.test.js (19 checks); full suite 350 suites / 12,121 assertions / 0 failed.

Open (recorded in research/port-channel-in-interface-brief.md): one 9300-class table prints Port-channel1 first, so row order is a stated choice; show interfaces Port-channel1 and show mac address-table interface Po1 still cannot resolve the bundle (a port-identity change, next increment); and the box's Creating a port-channel interface Port-channel 1 receipt is not printed here.

`show ip interface brief` listed only the member ports of an EtherChannel. A bundle is an interface and a box prints its row: - `Port-channel2 unassigned YES unset up up` on a 3850 — [Cisco doc 221664](https://www.cisco.com/c/en/us/support/docs/security/secure-firewall-management-center/221664-integrate-redundant-solution-for-secure.html) - `Port-channel1 ... down down` while its members were suspended — [Cisco doc 225790](https://www.cisco.com/c/en/us/support/docs/security/secure-firewall-threat-defense/225790-troubleshoot-lacp-port-channel-failure.html) - a 3750X table ending `Port-channel1 ... up up` / `Port-channel20 ... down down` after `Te1/1/2` — [community capture](https://community.cisco.com/t5/switching/port-not-working-for-access-to-vlan/td-p/4084339) - one capture showing both spellings: `4 Po4(SU) LACP Gi4/31(P)` in the summary, `Port-channel4 ... up up` in the brief table — [community capture](https://community.cisco.com/t5/switching/help-understanding-etherchannel-output/m-p/4015412) The row is spelled out (`Port-channel<n>`, not the `Po1` the summary and MAC table print), carries `unassigned YES unset` because this model builds no Layer 3 bundle, and is `up up` only when at least one member is really in the bundle — a bundle of stand-alone members reads `down down` while each member reads `up up`, the same predicate the summary prints as `Po1(SD)` with `(I)` members. The per-member rule moved out of `show etherchannel summary` into `_lagMemberStates()`, so the letters and the bundle row cannot disagree; `engine/lag.js` now names the bundle in both spellings. **Tests:** `test/brief-port-channel-row.test.js` (19 checks); full suite 350 suites / 12,121 assertions / 0 failed. **Open** (recorded in `research/port-channel-in-interface-brief.md`): one 9300-class table prints `Port-channel1` first, so row order is a stated choice; `show interfaces Port-channel1` and `show mac address-table interface Po1` still cannot resolve the bundle (a port-identity change, next increment); and the box's `Creating a port-channel interface Port-channel 1` receipt is not printed here.
brief: an EtherChannel is an interface, and it has a row
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 53s
d6460efe15
`show ip interface brief` listed only the member ports of a bundle. An EtherChannel is an
interface and a box prints its row: `Port-channel2 unassigned YES unset up up` on a 3850
(Cisco doc 221664), `Port-channel1 ... down down` on an FTD whose members were suspended
(doc 225790), and a 3750X table ending `Port-channel1 ... up up` / `Port-channel20 ...
down down` after `Te1/1/2` (community capture).

The row is spelled out - `Port-channel<n>`, not the `Po1` the summary and the MAC table
print - carries `unassigned YES unset` (no Layer 3 bundle in this model), and is `up up`
only when at least one member is really in the bundle; a bundle of stand-alone members
reads `down down` while each member reads `up up`, the same predicate the summary prints
as `Po1(SD)` with `(I)` members.

The per-member rule moved out of `show etherchannel summary` into `_lagMemberStates()`,
so the summary's `(P)`/`(I)`/`(D)`/`(H)` letters and the bundle's own row cannot disagree.
`engine/lag.js` names the bundle in both spellings (`Po1`, `Port-channel1`).

test/brief-port-channel-row.test.js: 19 checks. Full suite: 350 suites, 12121
assertions, 0 failed. research/port-channel-in-interface-brief.md carries the captures,
the row-order contradiction one 9300-class table shows, and what is still open
(`show interfaces Port-channel1` cannot resolve the bundle).
forgejo-actions force-pushed rev/1118-2042 from d6460efe15
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Arm auto-merge (pull_request) Successful in 53s
to dd65008047 2026-11-18 21:04:54 +00:00
Compare
forgejo-actions force-pushed rev/1118-2042 from f7989ebe58 to be800d3cf8
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-18 21:20:15 +00:00
Compare
forgejo-actions force-pushed rev/1118-2042 from be800d3cf8
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 4s
to 7290295e62 2026-11-18 21:24:22 +00:00
Compare
jaylouisw force-pushed rev/1118-2042 from 6320501efd to 6d01313db3
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 6s
CI / Server smoke test (pull_request) Successful in 13s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 53s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-18 22:41:45 +00:00
Compare
jaylouisw deleted branch rev/1118-2042 2026-11-18 22:45:45 +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!2035
No description provided.