catalogue: Huawei NetEngine 8000 M14 - 52 ports from the vendor's own DC build (#799) #1805

Merged
jaylouisw merged 2 commits from catalogue/1117-0655 into main 2026-11-17 07:18:16 +00:00
Owner

Fixes #799

NetEngine 8000 M14 - the request's "14 service slots" is a slot count, and the build fills seven of them

The M14 has no fixed-interface slot (PIC DC: 1-14 | IPU 15,16 | PIU DC 17,18 | FAN 19, Hardware Description V800R024C10SPC500 Table 1-25), so an empty chassis has no cableable port. The datasheet confirms the request's figure and what it means: Service Slots 14 (DC) / 10 (4AC) / 12 (2AC), 442 mm x 220 mm x 222 mm (5U).

Huawei states a build in the DC chassis power row:

[IPU-2T/IPU-2T-B]DC: 1*fan+2*DC power+2*IPU+2*CR5DE2NE4X14+1*CR5D00E8XM25+3*CR5D00LAXF91+1*CR5D00EAGF95=905.6 W

Seven PICs in fourteen slots. This is where the M14 differs from the M8 that closed #797 an hour ago: on the M8 the stated build happened to fill all six AC service slots, so no judgement call was needed. No published M14 build fills the chassis - the same seven cards are stated for the 10-slot 4AC chassis (CR8B0BKPACC2, 02353ABK, 968.36 W) and a seven-card variant for the 12-slot 2AC chassis (935.81 W). The choice is therefore "which chassis is the build measured on", and the DC chassis wins because it is the chassis #799 names (14 service slots) and the one this row belongs to.

devices/huawei/netengine-8000-m14.json - 52 ports: 4x 100GE/50GE QSFP28, 8x 25GE/10GE SFP28, 30x 10GE/GE SFP+, 10x 100/1000Base-X SFP. Every count is a card's own vendor name, not a maximum:

card vendor name ports
CR5DE2NE4X14 x2 03033GDS: 2-Port 100GBase/50GBase-QSFP28 FlexE MACsec Interface Card(PIC) 4 x 100GE/50GE
CR5D00E8XM25 x1 03033BLM: 8-Port 25GE(SFP28)/10GE(SFP+) MACsec Physical Interface Card (PIC) 8 x 25GE/10GE
CR5D00LAXF91 x3 03033BLN: 10-Port 10GE/GE LAN/WAN-SFP+ MACsec Physical Interface Card(PIC) 30 x 10GE/GE
CR5D00EAGF95 x1 03033FXE: 10-port 100/1000Base-X-SFP MACsec Physical Interface Card(PIC) 10 x 100/1000Base-X

Sources read (2026-11-17)

  • https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/f4f1a7b9424a44ff9770b75a19eb5d2e/M3T1A590N1267221252983996547/NetEngine%208000%20M14%20Universal%20Service%20Router%20Datasheet.pdf - HTTP 200, application/pdf, 446,839 B. Service slots 14/10/12, 5U, typical power 486/968/931 W, feature table (DHCP Server, NAT/CGN).
  • https://support.huawei.com/enterprise/en/doc/EDOC1100465701/f446cf6d/netengine-8000-m14 - HTTP 200 (crawler user-agent; a browser user-agent gets HTTP 403), 609,790 B. Table 1-24 chassis codes, Table 1-25 slot layout, DC specification table (222 x 442 x 220 mm 5U, 10.1 kg bare / 28.5 kg configured, 19 slots of which 14 service, 4 Tbit/s with IPU-2T, MTBF 147.1 y).
  • https://support.huawei.com/enterprise/en/doc/EDOC1100465701/af1a855b/interface-card - HTTP 200, 2,022,238 B: 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 seven empty PIC slots. They are empty in Huawei's own measured configuration; filling them would mean inventing an order. The description and notes say 7 of 14 explicitly.
  • The AC chassis codes (CR8B0BKPACC2 4AC; ACC1/ACC6 2AC) and the newer IPU-3T6 eight-card build 2*CR8DE1KB00M1+2*CR8DE4NB00M1+2*CR5D00LAXF91+2*CR5D00EAGF95 = 931.67 W (50 ports, 7.2 Tbit/s) - separate populations, recorded in notes and research/huawei-netengine-8000-m-series-slots.md, not folded in.
  • Slot-numbered port names - flat 100ge0 .. ge51, because the vendor does not print which PIC sits in which slot.
  • Management/OAM, console, TOD and alarm ports (no cableable count published), PoE (none), and the per-rate maxima (280 physical ports, 20x 100GE, 28x 50GE, 80x 25GE, 140x 10GE) - maxima across fourteen cards, not this build.
  • Capability tokens the engine lacks: MPLS, SRv6, EVPN/VXLAN, FlexE, IPsec/MACsec are recorded in notes. nat and dhcp-server are declared because the datasheet feature table states NAT/CGN and DHCP Server.

Gates

  • node scripts/syntax-check.js - 377 files, all OK
  • node scripts/audit-port-types.js - no port contradicts its declared type
  • node scripts/import-devices.js (dry run) - no rejection or capability-tripwire hit for this spec (the two refusals it prints are pre-existing duplicate spellings in the incoming batches)
  • node test/hardware-invariants.test.js - 26/26; node test/spec-vs-description.test.js - 3/3; node test/cage-resolution.test.js - 16/16; node test/cage-media-resolves.test.js - 27/27; node test/canonical-urls.test.js - 52/52
  • npm run regen:registry-doc - regenerated, 2,347 -> 2,348 models (Huawei 93 -> 94, router 380 -> 381)
Fixes #799 ## NetEngine 8000 M14 - the request's "14 service slots" is a slot count, and the build fills seven of them The M14 has no fixed-interface slot (`PIC DC: 1-14 | IPU 15,16 | PIU DC 17,18 | FAN 19`, Hardware Description V800R024C10SPC500 Table 1-25), so an empty chassis has no cableable port. The datasheet confirms the request's figure and what it means: `Service Slots 14 (DC) / 10 (4AC) / 12 (2AC)`, `442 mm x 220 mm x 222 mm (5U)`. Huawei states a build in the DC chassis power row: > `[IPU-2T/IPU-2T-B]DC: 1*fan+2*DC power+2*IPU+2*CR5DE2NE4X14+1*CR5D00E8XM25+3*CR5D00LAXF91+1*CR5D00EAGF95=905.6 W` Seven PICs in fourteen slots. This is where the M14 differs from the M8 that closed #797 an hour ago: on the M8 the stated build happened to fill all six AC service slots, so no judgement call was needed. **No published M14 build fills the chassis** - the same seven cards are stated for the 10-slot 4*AC chassis (`CR8B0BKPACC2`, 02353ABK, 968.36 W) and a seven-card variant for the 12-slot 2*AC chassis (935.81 W). The choice is therefore "which chassis is the build measured on", and the DC chassis wins because it is the chassis #799 names (14 service slots) and the one this row belongs to. `devices/huawei/netengine-8000-m14.json` - **52 ports**: 4x 100GE/50GE QSFP28, 8x 25GE/10GE SFP28, 30x 10GE/GE SFP+, 10x 100/1000Base-X SFP. Every count is a card's own vendor name, not a maximum: | card | vendor name | ports | |---|---|---| | `CR5DE2NE4X14` x2 | 03033GDS: 2-Port 100GBase/50GBase-QSFP28 FlexE MACsec Interface Card(PIC) | 4 x 100GE/50GE | | `CR5D00E8XM25` x1 | 03033BLM: 8-Port 25GE(SFP28)/10GE(SFP+) MACsec Physical Interface Card (PIC) | 8 x 25GE/10GE | | `CR5D00LAXF91` x3 | 03033BLN: 10-Port 10GE/GE LAN/WAN-SFP+ MACsec Physical Interface Card(PIC) | 30 x 10GE/GE | | `CR5D00EAGF95` x1 | 03033FXE: 10-port 100/1000Base-X-SFP MACsec Physical Interface Card(PIC) | 10 x 100/1000Base-X | ### Sources read (2026-11-17) - `https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/f4f1a7b9424a44ff9770b75a19eb5d2e/M3T1A590N1267221252983996547/NetEngine%208000%20M14%20Universal%20Service%20Router%20Datasheet.pdf` - HTTP 200, `application/pdf`, 446,839 B. Service slots 14/10/12, 5U, typical power 486/968/931 W, feature table (`DHCP Server`, `NAT/CGN`). - `https://support.huawei.com/enterprise/en/doc/EDOC1100465701/f446cf6d/netengine-8000-m14` - HTTP 200 (crawler user-agent; a browser user-agent gets HTTP 403), 609,790 B. Table 1-24 chassis codes, Table 1-25 slot layout, DC specification table (222 x 442 x 220 mm 5U, 10.1 kg bare / 28.5 kg configured, 19 slots of which 14 service, 4 Tbit/s with IPU-2T, MTBF 147.1 y). - `https://support.huawei.com/enterprise/en/doc/EDOC1100465701/af1a855b/interface-card` - HTTP 200, 2,022,238 B: 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 seven empty PIC slots.** They are empty in Huawei's own measured configuration; filling them would mean inventing an order. The description and `notes` say 7 of 14 explicitly. - **The AC chassis codes** (`CR8B0BKPACC2` 4*AC; `ACC1`/`ACC6` 2*AC) and the newer IPU-3T6 eight-card build `2*CR8DE1KB00M1+2*CR8DE4NB00M1+2*CR5D00LAXF91+2*CR5D00EAGF95 = 931.67 W` (50 ports, 7.2 Tbit/s) - separate populations, recorded in `notes` and `research/huawei-netengine-8000-m-series-slots.md`, not folded in. - **Slot-numbered port names** - flat `100ge0 .. ge51`, because the vendor does not print which PIC sits in which slot. - Management/OAM, console, TOD and alarm ports (no cableable count published), PoE (none), and the per-rate maxima (280 physical ports, 20x 100GE, 28x 50GE, 80x 25GE, 140x 10GE) - maxima across fourteen cards, not this build. - Capability tokens the engine lacks: MPLS, SRv6, EVPN/VXLAN, FlexE, IPsec/MACsec are recorded in `notes`. `nat` and `dhcp-server` are declared because the datasheet feature table states `NAT/CGN` and `DHCP Server`. ### Gates - `node scripts/syntax-check.js` - 377 files, all OK - `node scripts/audit-port-types.js` - no port contradicts its declared type - `node scripts/import-devices.js` (dry run) - no rejection or capability-tripwire hit for this spec (the two refusals it prints are pre-existing duplicate spellings in the incoming batches) - `node test/hardware-invariants.test.js` - 26/26; `node test/spec-vs-description.test.js` - 3/3; `node test/cage-resolution.test.js` - 16/16; `node test/cage-media-resolves.test.js` - 27/27; `node test/canonical-urls.test.js` - 52/52 - `npm run regen:registry-doc` - regenerated, 2,347 -> 2,348 models (Huawei 93 -> 94, router 380 -> 381)
catalogue: Huawei NetEngine 8000 M14 - 52 ports from the vendor's own DC build (#799)
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 43s
CI / Test (Node 18) (pull_request) Failing after 49s
CI / Test (Node 22) (pull_request) Failing after 48s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 2s
3c08da08a3
jaylouisw force-pushed catalogue/1117-0655 from 3c08da08a3
Some checks failed
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 9s
CI / Test (Node 20) (pull_request) Failing after 43s
CI / Test (Node 18) (pull_request) Failing after 49s
CI / Test (Node 22) (pull_request) Failing after 48s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 2s
to 80d022ad19
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
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 24s
CI / Test (Node 20) (pull_request) Failing after 44s
CI / Test (Node 18) (pull_request) Failing after 51s
CI / Test (Node 22) (pull_request) Failing after 48s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 07:01:07 +00:00
Compare
jaylouisw force-pushed catalogue/1117-0655 from 80d022ad19
Some checks failed
CI / Classify the change (pull_request) Successful in 9s
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 24s
CI / Test (Node 20) (pull_request) Failing after 44s
CI / Test (Node 18) (pull_request) Failing after 51s
CI / Test (Node 22) (pull_request) Failing after 48s
CI / Arm auto-merge (pull_request) Successful in 4s
to 9317e1c4ba
Some checks failed
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 5s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Failing after 46s
CI / Test (Node 18) (pull_request) Failing after 52s
CI / Test (Node 22) (pull_request) Failing after 47s
CI / Arm auto-merge (pull_request) Successful in 3s
2026-11-17 07:02:15 +00:00
Compare
catalogue: the M14 alias list repeated its own model name, which device-aliases forbids
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 7s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 44s
CI / Test (Node 22) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 16s
d618240342
The aliases were NE8000 M14 / NetEngine 8000 M14 / NetEngine 8000 M14 DC.
The middle one normalises to the model string netengine-8000-m14, so it is a
self-referential alias and test/device-aliases.test.js fails the catalogue on it
(alias is its own model name). Search already matches the model name, so the
entry adds nothing; the AC/DC distinct aliases stay.
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!1805
No description provided.