catalogue(c1000): a 10G model's cages are Te1/0/1-4, not Gi1/0/25-28 #2026

Merged
jaylouisw merged 1 commit from rev/1118-2012 into main 2026-11-18 20:37:27 +00:00
Owner

Question. On a Catalyst 1000 with four 10G SFP+ cages (-4X), what does the CLI call them - the 1G model's continued numbering (Gi1/0/25-28) or Te1/0/1-4?

Verdict: Te1/0/1-Te1/0/4 - module 0, restarting at 1. The 1G models keep the continued numbering (Gi1/0/9-10, 17-18, 25-28, 49-52).

Evidence:

What changed: devices/cisco/c1000-24fp-4x-l.json renames the four cages (still 28 ports, still sfp+/10G, still 1000/10000 caps); test/c1000-4x-uplink-naming.test.js (37 checks) pins the rule over all nine C1000 specs plus the console consequences and a link on the corrected name; research/c1000-4x-uplink-naming.md records evidence and open points. No engine code changed - the type-word lookup already resolved Te1/0/1.

Measured before: show interfaces Te1/0/1 -> % No interface Te1/0/1 on ... and show interfaces Gi1/0/25 -> Gi1/0/25 (ethernet, 10G).

Unresolved: the front-panel silkscreen for the four cages; whether a 4X box also answers to Gi1/0/25 (Cisco calls them "mapped ports"); show interfaces status Type column for a 10G cage; the 48-port 4X models (not in the catalogue); C1200/C1300 neighbours.

Tests: node scripts/syntax-check.js 423 files OK; audit-port-types no contradictions; new suite 37/37; full npm test 349 suites, 12102 assertions, 0 failed.

**Question.** On a Catalyst 1000 with four 10G SFP+ cages (`-4X`), what does the CLI call them - the 1G model's continued numbering (`Gi1/0/25`-`28`) or `Te1/0/1`-`4`? **Verdict:** `Te1/0/1`-`Te1/0/4` - module 0, restarting at 1. The 1G models keep the continued numbering (`Gi1/0/9-10`, `17-18`, `25-28`, `49-52`). **Evidence:** - Catalyst 1000 24/48-Port HIG, port-mapping Tables 3-4: each row pairs the same cage's 1G and 10G name (`GigabitEthernet1/0/25` with `TenGigabitEthernet1/0/1` ... `.../28` with `.../4`). https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst1000/hardware/installation/24_48_port_hig/b_c1000_24_48_hig/product_overview.html - Catalyst 1000 8/16-Port HIG Tables 2-3: `Gi1/0/9-10`, `Gi1/0/17-18`. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst1000/hardware/installation/8_16_port_hig/b_c1000_8_16_hig/product_overview.html - C1000 Single IP Management CG (15.2(7)Ex): `show switch hstack-ports` lists `Te1/0/1`-`Te1/0/4` on a 10-G device and speaks of the "10 Gigabit Ethernet 1/0/1 interface"; the 1-G example lists the four continued-numbering families. https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst1000/software/releases/15_2_7_e/configuration_guides/stacking/b_1527e_single_ip_management_c1000_cg.pdf - NetBox NDX C1000-24P-4X-L: `TenGigabitEthernet1/0/1`-`4` at 10gbase-x-sfpp. https://netboxlabs.com/ndx/cisco/cisco-c1000-24p-4x-l/ **What changed:** `devices/cisco/c1000-24fp-4x-l.json` renames the four cages (still 28 ports, still `sfp+`/10G, still 1000/10000 caps); `test/c1000-4x-uplink-naming.test.js` (37 checks) pins the rule over all nine C1000 specs plus the console consequences and a link on the corrected name; `research/c1000-4x-uplink-naming.md` records evidence and open points. No engine code changed - the type-word lookup already resolved `Te1/0/1`. **Measured before:** `show interfaces Te1/0/1` -> `% No interface Te1/0/1 on ...` and `show interfaces Gi1/0/25` -> `Gi1/0/25 (ethernet, 10G)`. **Unresolved:** the front-panel silkscreen for the four cages; whether a 4X box also answers to `Gi1/0/25` (Cisco calls them "mapped ports"); `show interfaces status` Type column for a 10G cage; the 48-port 4X models (not in the catalogue); C1200/C1300 neighbours. **Tests:** `node scripts/syntax-check.js` 423 files OK; `audit-port-types` no contradictions; new suite 37/37; full `npm test` 349 suites, 12102 assertions, 0 failed.
catalogue(c1000): a 10G model's cages are Te1/0/1-4, not Gi1/0/25-28
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 32s
bf940626c8
The one Catalyst 1000 10G spec declared its four SFP+ cages as Gi1/0/25-Gi1/0/28 - the 1G
model's names and numbering - so the console called a 10-gigabit cage GigabitEthernet and
refused Te1/0/1, the name Cisco's 10-G examples print. Cisco's port-mapping tables pair the
same cage's two names (Gi1/0/25 with TenGigabitEthernet1/0/1, .../28 with .../4) and the C1000
single-IP-management guide lists Te1/0/1-Te1/0/4 in show switch hstack-ports for a 10-G device.
The rename moves four names and keeps 28 ports, the sfp+ connectors and the 1000/10000 caps.
37 checks in test/c1000-4x-uplink-naming.test.js cover all nine C1000 specs and the console.
research/c1000-4x-uplink-naming.md records the evidence and what stays open.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-18 20:30:19 +00:00
jaylouisw deleted branch rev/1118-2012 2026-11-18 20:37:28 +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!2026
No description provided.