Cisco Catalyst 1000: nine PoE+ access switches, and a Cisco guide that gives one model 12 PoE ports #1608

Merged
jaylouisw merged 1 commit from catalogue/1116-0455 into main 2026-11-16 06:26:49 +00:00
Owner

What this adds

Cisco Catalyst 1000 Gigabit PoE+ access switches. The catalogue had Catalyst 9200L/9300/9800 and the 2960, but nothing from the 1000 series - the box Cisco sells for the out-of-wiring-closet SMB edge.

Nine specs, one vendor family:

model copper uplinks PoE budget switching fan
C1000-8P-2G-L 8x 1G PoE+ 2 combo (1G SFP or 1G RJ-45) 67 W 20 Gbps fanless
C1000-8FP-2G-L 8x 1G PoE+ 2 combo 120 W 20 Gbps fanless
C1000-16P-2G-L 16x 1G PoE+ 2x 1G SFP 120 W 36 Gbps fanless
C1000-16FP-2G-L 16x 1G PoE+ 2x 1G SFP 240 W 36 Gbps fanless
C1000-24P-4G-L 24x 1G PoE+ 4x 1G SFP 195 W 56 Gbps fanless
C1000-24FP-4G-L 24x 1G PoE+ 4x 1G SFP 370 W 56 Gbps fan, 34.8 dB
C1000-48P-4G-L 48x 1G PoE+ 4x 1G SFP 370 W 104 Gbps fan, 36.1 dB
C1000-48FP-4G-L 48x 1G PoE+ 4x 1G SFP 740 W 104 Gbps fan, 47.6 dB
C1000-24FP-4X-L 24x 1G PoE+ 4x 10G SFP+ 370 W 128 Gbps fan, 34.8 dB

Sources, all Cisco:

Every spec carries the data sheet URL as sourceUrl and again on its poe block.

The budget, not the port count

The family is a ladder from 67 W to 740 W, and in every case the watts bind before the ports do:

  • 8P: 67 W over 8 ports = four Class-3 PDs, or two at 30 W.
  • 8FP: 120 W = four 30 W PDs; eight Class-3 PDs want 123.2 W and do not fit.
  • 16P: 120 W over 16 ports = seven Class-3 PDs; sixteen want 246.4 W.
  • 16FP: 240 W = fifteen Class-3, or eight 30 W.
  • 24P: 195 W = twelve Class-3, or six 30 W.
  • 24FP: 370 W = all 24 at Class 3 (369.6 W), or twelve 30 W.
  • 48P: 370 W = 24 of 48 ports at Class 3, or twelve 30 W.
  • 48FP: 740 W = all 48 at Class 3 (739.2 W), or 24 at 30 W.
  • 24FP-4X: 370 W, as the 24FP-4G.

No 802.3bt anywhere in the series: 30 W a port is the hardware ceiling, and Perpetual PoE holds power across a reload.

Where the sources disagree (data sheet wins)

  1. C1000-48P-4G-L port count. The 24/48-port HIG model table says 48 ports with 12 PoE+ ports (370 W budget) and 36 Ethernet ports. The data sheet configuration table and ordering table both say 48 PoE+ ports at 370 W, and the 15.2(7)E release notes repeat the data sheet. Modelled as 48 PoE+ ports; the HIG line looks like the 48PP-4G-L (12 PoE+, 180 W), a different SKU.
  2. -4X cage naming. Cisco renames an SFP+ cage with the module in it: the HIG port-mapping table maps Gi1/0/25-28 to Ten1/0/1-4 (Gi1/0/49-52 on the 48-port models) and says a module swap needs default-interface on the mapped port. The spec keeps the documented Gi1/0/25 name and records the Ten alias in notes rather than inventing a second port.
  3. Layer 2 or Layer 3. Cisco's prose calls the series Layer 2, but Table 2 budgets 542 IPv4 direct / 256 indirect routes (414/128 IPv6) and 600 security ACEs, so inter-VLAN routing is real at the static-table level. l3-forward is declared and the notes say what that does and does not mean.

Unverifiable / not modelled

  • The per-model power draw table in the data sheet is grouped by port class, not by SKU, so watts-at-the-wall is not recorded per model.
  • The 8/16-port HIG never prints interface names for its two SFP uplinks; the specs use Gi1/0/17-18 (Gi1/0/9-10 for the combo pairs on the 8-port models) as the positional next slots, and the notes say so.
  • The -E (external PSU) variants and the Fast Ethernet C1000FE models are not modelled here.

Validation

  • node scripts/syntax-check.js - 336 files, all OK
  • node scripts/audit-port-types.js - 2123 models / 252 vendors, 23019 ports, 0 offending devices, 0 offending ports
  • node scripts/import-devices.js --apply - Added: 9, no rejections; only the expected 802.3af/802.3at capability warnings (kept as declared, the engine does not implement them)
  • node --test test/spec-vs-description.test.js test/catalogue-hygiene.test.js test/spec-survives-load.test.js test/importer-roundtrip.test.js test/import-devices-capabilities.test.js test/faceplate-catalogue.test.js test/inspector-port-count.test.js test/device-aliases.test.js test/hardware-invariants.test.js test/combo.test.js - all suites pass
  • node scripts/regen-registry-doc.js - README and docs/DEVICE_REGISTRY.md counts moved to 2,123 models
## What this adds Cisco Catalyst 1000 Gigabit PoE+ access switches. The catalogue had Catalyst 9200L/9300/9800 and the 2960, but nothing from the 1000 series - the box Cisco sells for the out-of-wiring-closet SMB edge. Nine specs, one vendor family: | model | copper | uplinks | PoE budget | switching | fan | |---|---|---|---|---|---| | C1000-8P-2G-L | 8x 1G PoE+ | 2 combo (1G SFP or 1G RJ-45) | 67 W | 20 Gbps | fanless | | C1000-8FP-2G-L | 8x 1G PoE+ | 2 combo | 120 W | 20 Gbps | fanless | | C1000-16P-2G-L | 16x 1G PoE+ | 2x 1G SFP | 120 W | 36 Gbps | fanless | | C1000-16FP-2G-L | 16x 1G PoE+ | 2x 1G SFP | 240 W | 36 Gbps | fanless | | C1000-24P-4G-L | 24x 1G PoE+ | 4x 1G SFP | 195 W | 56 Gbps | fanless | | C1000-24FP-4G-L | 24x 1G PoE+ | 4x 1G SFP | 370 W | 56 Gbps | fan, 34.8 dB | | C1000-48P-4G-L | 48x 1G PoE+ | 4x 1G SFP | 370 W | 104 Gbps | fan, 36.1 dB | | C1000-48FP-4G-L | 48x 1G PoE+ | 4x 1G SFP | 740 W | 104 Gbps | fan, 47.6 dB | | C1000-24FP-4X-L | 24x 1G PoE+ | 4x 10G SFP+ | 370 W | 128 Gbps | fan, 34.8 dB | Sources, all Cisco: - data sheet Tables 1 and 2: https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-1000-series-switches/nb-06-cat1k-ser-switch-ds-cte-en.html - 8/16-port Hardware Installation Guide: 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 - 24/48-port Hardware Installation Guide: 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 - console defaults 9600 8-N-1, no flow control: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst1000/hardware/installation/24_48_port_hig/b_c1000_24_48_hig/configuring_the_switch.html Every spec carries the data sheet URL as `sourceUrl` and again on its `poe` block. ## The budget, not the port count The family is a ladder from 67 W to 740 W, and in every case the watts bind before the ports do: - 8P: 67 W over 8 ports = four Class-3 PDs, or two at 30 W. - 8FP: 120 W = four 30 W PDs; eight Class-3 PDs want 123.2 W and do not fit. - 16P: 120 W over 16 ports = seven Class-3 PDs; sixteen want 246.4 W. - 16FP: 240 W = fifteen Class-3, or eight 30 W. - 24P: 195 W = twelve Class-3, or six 30 W. - 24FP: 370 W = all 24 at Class 3 (369.6 W), or twelve 30 W. - 48P: 370 W = 24 of 48 ports at Class 3, or twelve 30 W. - 48FP: 740 W = all 48 at Class 3 (739.2 W), or 24 at 30 W. - 24FP-4X: 370 W, as the 24FP-4G. No 802.3bt anywhere in the series: 30 W a port is the hardware ceiling, and Perpetual PoE holds power across a reload. ## Where the sources disagree (data sheet wins) 1. **C1000-48P-4G-L port count.** The 24/48-port HIG model table says 48 ports with 12 PoE+ ports (370 W budget) and 36 Ethernet ports. The data sheet configuration table and ordering table both say 48 PoE+ ports at 370 W, and the 15.2(7)E release notes repeat the data sheet. Modelled as 48 PoE+ ports; the HIG line looks like the 48PP-4G-L (12 PoE+, 180 W), a different SKU. 2. **-4X cage naming.** Cisco renames an SFP+ cage with the module in it: the HIG port-mapping table maps Gi1/0/25-28 to Ten1/0/1-4 (Gi1/0/49-52 on the 48-port models) and says a module swap needs `default-interface` on the mapped port. The spec keeps the documented Gi1/0/25 name and records the Ten alias in `notes` rather than inventing a second port. 3. **Layer 2 or Layer 3.** Cisco's prose calls the series Layer 2, but Table 2 budgets 542 IPv4 direct / 256 indirect routes (414/128 IPv6) and 600 security ACEs, so inter-VLAN routing is real at the static-table level. `l3-forward` is declared and the notes say what that does and does not mean. ## Unverifiable / not modelled - The per-model power draw table in the data sheet is grouped by port class, not by SKU, so watts-at-the-wall is not recorded per model. - The 8/16-port HIG never prints interface names for its two SFP uplinks; the specs use Gi1/0/17-18 (Gi1/0/9-10 for the combo pairs on the 8-port models) as the positional next slots, and the notes say so. - The -E (external PSU) variants and the Fast Ethernet C1000FE models are not modelled here. ## Validation - `node scripts/syntax-check.js` - 336 files, all OK - `node scripts/audit-port-types.js` - 2123 models / 252 vendors, 23019 ports, 0 offending devices, 0 offending ports - `node scripts/import-devices.js --apply` - Added: 9, no rejections; only the expected `802.3af`/`802.3at` capability warnings (kept as declared, the engine does not implement them) - `node --test test/spec-vs-description.test.js test/catalogue-hygiene.test.js test/spec-survives-load.test.js test/importer-roundtrip.test.js test/import-devices-capabilities.test.js test/faceplate-catalogue.test.js test/inspector-port-count.test.js test/device-aliases.test.js test/hardware-invariants.test.js test/combo.test.js` - all suites pass - `node scripts/regen-registry-doc.js` - README and docs/DEVICE_REGISTRY.md counts moved to 2,123 models
Cisco Catalyst 1000: nine PoE+ access switches, a 67 W to 740 W ladder, and a Cisco guide that gives one model 12 PoE ports
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Failing after 12m32s
CI / Classify the change (pull_request) Failing after 12m41s
CI / Test (Node 18) (pull_request) Has been cancelled
CI / Test (Node 20) (pull_request) Has been cancelled
CI / Test (Node 22) (pull_request) Has been cancelled
CI / Server smoke test (pull_request) Has been cancelled
CI / Docker build (pull_request) Has been cancelled
4990ed6c67
Adds the Cisco Catalyst 1000 Gigabit PoE+ access switches the catalogue did
not have: C1000-8P-2G-L, C1000-8FP-2G-L, C1000-16P-2G-L, C1000-16FP-2G-L,
C1000-24P-4G-L, C1000-24FP-4G-L, C1000-48P-4G-L, C1000-48FP-4G-L and
C1000-24FP-4X-L.

Every field comes from Cisco's Catalyst 1000 data sheet (Tables 1 and 2) or
the 8/16-port and 24/48-port Hardware Installation Guides. The 370 W and 740 W
budgets are the ceiling, not the port count: 48 PoE+ ports at 30 W is 1440 W,
and the specs say so.

Two things the sources disagree on:
- the 24/48-port HIG model table calls the 48P-4G-L "48 ports; 12x PoE+ (370 W)
  and 36x Ethernet", while the data sheet configuration and ordering tables and
  the 15.2(7)E release notes all give 48 PoE+ ports at 370 W. The data sheet
  wins; the HIG line reads like the 48PP-4G-L (12 PoE+, 180 W).
- the -4X models rename an SFP+ cage with the module fitted (Ten1/0/1-4 vs
  Gi1/0/25-28), which is recorded in the notes rather than modelled twice.
jaylouisw force-pushed catalogue/1116-0455 from 4990ed6c67
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Failing after 12m32s
CI / Classify the change (pull_request) Failing after 12m41s
CI / Test (Node 18) (pull_request) Has been cancelled
CI / Test (Node 20) (pull_request) Has been cancelled
CI / Test (Node 22) (pull_request) Has been cancelled
CI / Server smoke test (pull_request) Has been cancelled
CI / Docker build (pull_request) Has been cancelled
to c34d4f2cf8
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
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:26:10 +00:00
Compare
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 06:26:37 +00:00
jaylouisw force-pushed catalogue/1116-0455 from c34d4f2cf8
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
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
to b6ec63c016
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 15s
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:26:40 +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!1608
No description provided.