catalogue: Huawei NetEngine 8000 M8 — 34 ports from the vendor’s own AC build (#797) #1802

Merged
jaylouisw merged 1 commit from catalogue/1117-0625 into main 2026-11-17 06:48:03 +00:00
Owner

Fixes #797

NetEngine 8000 M8 — modelled as the build Huawei states, not the chassis maximum

The M8 is a card chassis with no fixed-interface slot (Hardware Description V800R024C10SPC500 Table 1-14: PIC DC: 1-8, AC: 2, 4-8 | IPU 9,10 | PIU | FAN 13), so the bare model has no cableable port. The datasheet does print a card complement, though — in the row it uses to state power and heat — and on the AC chassis that build fills every PIC slot:

[IPU-2T4-A/IPU-2T4-E-B]2*CR8DE1KB00M1(1*400GE)+1*CR8DE4NB00M1(4*100GE)+1*CR8DE8YF0025(8*25GE)+2*CR5D00LAXF91(10*10GE)=774.3 W

Six cards against six AC service slots (datasheet: Number of slots 11, Number of service board slots 6), so nothing is left to choose and no slot is silently empty.

devices/huawei/netengine-8000-m8.json — 34 ports: 2x 400GE QSFP-DD, 4x 100GE/50GE QSFP28, 8x 25GE/10GE SFP28, 20x 10GE/GE SFP+. Every count comes out of a card's own vendor name, not out of a maximum:

card vendor name ports
CR8DE1KB00M1 1-Port 400GBase-QSFP-DD Single-layer Physical Interface Card(PIC) 1 x 400GE
CR8DE4NB00M1 4-Port 100GBase/50GBase-QSFP28 Physical Interface Card(PIC) 4 x 100GE/50GE
CR8DE8YF0025 8-Port 25GE(SFP28)/10GE(SFP+) MACsec Physical Interface Card (PIC) 8 x 25GE/10GE
CR5D00LAXF91 10-Port 10GE/GE LAN/WAN-SFP+ MACsec Physical Interface Card(PIC) 10 x 10GE/GE

Sources read (2026-11-17)

  • https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/e9dd06e260b64df683f6221fc8442cbf/M3T1A590N1140253824460255266/NetEngine%208000%20M8%20Universal%20Service%20Router%20Datasheet.pdf — HTTP 200, application/pdf, 514,517 B. AC and DC specification tables, the stated configurations, per-rate maxima, weights and power.
  • https://support.huawei.com/enterprise/en/doc/EDOC1100465701/e4ccf4a0/netengine-8000-m8 — HTTP 200, 637,383 B with a crawler user-agent (a browser user-agent gets HTTP 403). Slot table 1-14, Tables 1-19/1-20 for the DC chassis.
  • https://support.huawei.com/enterprise/en/doc/EDOC1100465701/af1a855b/interface-card — every card part number with its port count and socket in the name.
  • https://e.huawei.com/en/products/routers/ne8000 — per-model switching, forwarding, line-card-slot and power table.

Deliberately absent

  • The DC chassis has its own stated build and it is a different population — seven cards against eight service slots (…+1*CR5D00EAGF95(10*GE)=739.1 W). It is recorded in notes, not folded into this port list; an M8 DC entry would quote that row as its own build.
  • Slot-numbered port names. NetEngine 8000 names ports slot/subcard/port, but the vendor does not print which card sits in which PIC slot, so the port names are flat (400ge0 … 10ge33) rather than asserting an order that is not published.
  • Management/OAM, console and alarm ports (listed, but with no cableable count on either page read), PoE (none), and the AC maxima (120 ports, 3x 400GE, 18x 100GE, 48x 25GE, 60x 10GE, 60x GE) — maxima over six fitted cards, not this build.

Note on the plan

docs/plans/stated-configurations.md (step 4) proposed 8x CR5D00LAXF90, 80x 10GE on the DC chassis. That card is supported, but Huawei never states it as a build, so this PR uses the vendor's own configured row instead and puts it on the chassis where it fills every slot. research/huawei-netengine-8000-m-series-slots.md records the finding.

Gates

  • node scripts/syntax-check.js — 377 files, all OK
  • node scripts/audit-port-types.js — 2,347 models, 29,183 ports, 0 offending devices, 0 offending ports
  • node scripts/check-control-bytes.js — no control bytes
  • node scripts/import-devices.js (dry run) — no new rejections, capability tripwire silent
  • node test/spec-vs-description.test.js — 3/3; node test/hardware-invariants.test.js — 26/26
  • npm test — 306 suites, 10,698 assertions, 0 failed (885 s)
  • npm run regen:registry-doc — registry regenerated, 2,346 → 2,347 models
Fixes #797 ## NetEngine 8000 M8 — modelled as the build Huawei states, not the chassis maximum The M8 is a card chassis with **no fixed-interface slot** (Hardware Description V800R024C10SPC500 Table 1-14: `PIC DC: 1-8, AC: 2, 4-8 | IPU 9,10 | PIU | FAN 13`), so the bare model has no cableable port. The datasheet does print a card complement, though — in the row it uses to state power and heat — and on the AC chassis that build fills **every** PIC slot: > `[IPU-2T4-A/IPU-2T4-E-B]2*CR8DE1KB00M1(1*400GE)+1*CR8DE4NB00M1(4*100GE)+1*CR8DE8YF0025(8*25GE)+2*CR5D00LAXF91(10*10GE)=774.3 W` Six cards against six AC service slots (datasheet: `Number of slots 11`, `Number of service board slots 6`), so nothing is left to choose and no slot is silently empty. `devices/huawei/netengine-8000-m8.json` — **34 ports**: 2x 400GE QSFP-DD, 4x 100GE/50GE QSFP28, 8x 25GE/10GE SFP28, 20x 10GE/GE SFP+. Every count comes out of a card's own vendor name, not out of a maximum: | card | vendor name | ports | |---|---|---| | `CR8DE1KB00M1` | 1-Port 400GBase-QSFP-DD Single-layer Physical Interface Card(PIC) | 1 x 400GE | | `CR8DE4NB00M1` | 4-Port 100GBase/50GBase-QSFP28 Physical Interface Card(PIC) | 4 x 100GE/50GE | | `CR8DE8YF0025` | 8-Port 25GE(SFP28)/10GE(SFP+) MACsec Physical Interface Card (PIC) | 8 x 25GE/10GE | | `CR5D00LAXF91` | 10-Port 10GE/GE LAN/WAN-SFP+ MACsec Physical Interface Card(PIC) | 10 x 10GE/GE | ### Sources read (2026-11-17) - `https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/e9dd06e260b64df683f6221fc8442cbf/M3T1A590N1140253824460255266/NetEngine%208000%20M8%20Universal%20Service%20Router%20Datasheet.pdf` — HTTP 200, `application/pdf`, 514,517 B. AC and DC specification tables, the stated configurations, per-rate maxima, weights and power. - `https://support.huawei.com/enterprise/en/doc/EDOC1100465701/e4ccf4a0/netengine-8000-m8` — HTTP 200, 637,383 B with a crawler user-agent (a browser user-agent gets HTTP 403). Slot table 1-14, Tables 1-19/1-20 for the DC chassis. - `https://support.huawei.com/enterprise/en/doc/EDOC1100465701/af1a855b/interface-card` — every card part number with its port count and socket in the name. - `https://e.huawei.com/en/products/routers/ne8000` — per-model switching, forwarding, line-card-slot and power table. ### Deliberately absent - **The DC chassis** has its own stated build and it is a different population — seven cards against eight service slots (`…+1*CR5D00EAGF95(10*GE)=739.1 W`). It is recorded in `notes`, not folded into this port list; an M8 DC entry would quote that row as its own build. - **Slot-numbered port names.** NetEngine 8000 names ports `slot/subcard/port`, but the vendor does not print which card sits in which PIC slot, so the port names are flat (`400ge0` … `10ge33`) rather than asserting an order that is not published. - Management/OAM, console and alarm ports (listed, but with no cableable count on either page read), PoE (none), and the AC maxima (120 ports, 3x 400GE, 18x 100GE, 48x 25GE, 60x 10GE, 60x GE) — maxima over six fitted cards, not this build. ### Note on the plan `docs/plans/stated-configurations.md` (step 4) proposed `8x CR5D00LAXF90, 80x 10GE` on the DC chassis. That card is supported, but Huawei never states it as a build, so this PR uses the vendor's own configured row instead and puts it on the chassis where it fills every slot. `research/huawei-netengine-8000-m-series-slots.md` records the finding. ### Gates - `node scripts/syntax-check.js` — 377 files, all OK - `node scripts/audit-port-types.js` — 2,347 models, 29,183 ports, 0 offending devices, 0 offending ports - `node scripts/check-control-bytes.js` — no control bytes - `node scripts/import-devices.js` (dry run) — no new rejections, capability tripwire silent - `node test/spec-vs-description.test.js` — 3/3; `node test/hardware-invariants.test.js` — 26/26 - `npm test` — **306 suites, 10,698 assertions, 0 failed** (885 s) - `npm run regen:registry-doc` — registry regenerated, 2,346 → 2,347 models
catalogue: Huawei NetEngine 8000 M8 — 34 ports from the vendor's own AC build (#797)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m9s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 8s
6e4873e77c
The M8 is a card chassis with no fixed-interface slot, so the bare model has no
cableable port. Its datasheet states a card complement in the row it uses for
power and heat, and on the AC chassis that build fills all six PIC slots:
2*CR8DE1KB00M1(1*400GE)+1*CR8DE4NB00M1(4*100GE)+1*CR8DE8YF0025(8*25GE)
+2*CR5D00LAXF91(10*10GE) = 774.3 W - 34 ports, every count in a card name.

Co-authored-by: Hermes Agent <jay@jayw.uk>
jaylouisw force-pushed catalogue/1117-0625 from 6e4873e77c
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m9s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 8s
to cb3de0a2bb
All checks were successful
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 27s
2026-11-17 06:45:30 +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!1802
No description provided.