huawei: NetEngine 8000 X4, X8 and X16 at 32/64/128 x 400GE from the vendor's port density table #1762

Merged
jaylouisw merged 1 commit from catalogue/1117-0055 into main 2026-11-17 01:11:41 +00:00
Owner

Fixes #800
Fixes #801
Fixes #802

What was blocked, and what unblocked it

The earlier pass on all three issues read the family landing page (https://e.huawei.com/en/products/routers/ne8000), found capacity, line-card counts and power but no port census, and correctly refused to invent one. The vendor does publish a census - in the X Series datasheet's Port Density table, which gives a per-board port count and a per-model maximum for every port rate.

The census, and why it is not a guess

  • Datasheet 'NetEngine 8000 X Series Router', Port Density table, quoted verbatim: 400G | 8 | 128 (14.4T SRU) | 64 (4T SRU) | 32 (4T SRU) - i.e. 8 x 400GE cages per board, and 128 / 64 / 32 for X16 / X8 / X4. The neighbouring rows are 400G (14.4T SRU) | 36 | 576 | 288 | 144, 100G | 40 | 640 | 320 | 160 and 25GE/10G/GE | 72 | 1152 | 576 | 288.
  • The same datasheet's board table names the 8-cage card exactly: LPUI-4T/LPUI-4T-E/LPUI-4T-L: 8*400GE QSFP-DD + 8*100GE QSFP28.
  • Service slots 4 / 8 / 16 (X Series brochure, 'Product Specifications'), and the product page's Line Card row 16 / 8 / 4.
  • 8 x 4 = 32, 8 x 8 = 64, 8 x 16 = 128: the per-board count times the line-card slots lands on the datasheet's own 400G maximum for every one of the three models. Slot capability is 1T/2T/4T/14.4T/19.2T per slot on the X4 and X8 and 1T/2T/9.6T/14.4T on the X16, so a 4T card is valid in every slot of every member.

Each chassis is therefore modelled as the 4T card in every line-card slot - devices/huawei/netengine-8000-x4.json (32 ports), -x8.json (64), -x16.json (128) - with port names 400GE<slot>/0/<0-7>, following the hardware guide's rule that NetEngine 8000 X ports are slot ID/subcard ID/port number and a fixed card's subcard ID is 0. LPU slots are 1-4, 1-8 and 1-16 on the three chassis (hardware guide slot tables).

Deliberately not claimed

  • The 8 x 100GE QSFP28 cages each LPUI-4T also carries. The datasheet prints no port numbering inside that mixed-rate card, and the hardware guide's one worked mixed example (25GE 0-35 then 100GE 36-45) is not enough to place 400GE and 100GE on this card. Declaring the 400GE census and saying so is the question; numbering the 100GE half would be the guess.
  • The larger builds. 400G (14.4T SRU) (576 / 288 / 144), the 40-cage 100GE build (640 / 320 / 160) and the 19.2T 800GE card are different populations, named in the notes rather than folded in.
  • MPLS/SRv6/EVPN/FlexE/BNG/CGN/IPsec/1588v2 are in the datasheet's Product Features but are not engine capability tokens, so they are in notes. nat is declared because the feature table lists CGN; no firewall capability is claimed because the vendor's table lists none.
  • No PoE and no console port: neither is published for these chassis.

Sources

  1. https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/f274014bf341427ba955064d5919b2fe/M2T1A669N992206662674575488/NetEngine%208000%20X%20Series%20Universal%20Service%20Router%20Datasheet.pdf (canonical; Port Density + board tables). Huawei's host answers 404 to a non-browser fetch, so the identical PDF was read at its mirror https://www.ycict.net/wp-content/uploads/2023/09/NetEngine-8000-X-Series-Universal-Service-Router-Datasheet.pdf
  2. https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/02d9fbd0807243b5b37d66759665d25a/M3T1A590N1069280707103375400/NetEngine%208000%20X%20Series%20Brochure.pdf - service slots 4/8/16, LPUI-4T and LPUI-14T4 rows, product features.
  3. https://e.huawei.com/en/products/routers/ne8000 - per-model switching capacity, forwarding, MPU 2 1:1, SFU 8 7+1, power modules, dimensions, typical power.
  4. https://support.huawei.com/enterprise/doc/EDOC1100465699/67e2f8f8/board - port numbering (slot/subcard/port, subcard 0 on a fixed card; mixed-rate LPU convention).

Gates

  • node scripts/syntax-check.js - 368 files, all OK.
  • node scripts/audit-port-types.js - no port contradicts its declared type (QSFP-DD cages at 400GE).
  • node scripts/audit-devices.js - no hard defects.
  • test/hardware-invariants.test.js - 26 passed, 0 failed (2,343 models).
  • test/catalogue-hygiene.test.js, test/device-aliases.test.js, test/missing-devices.test.js, test/import-devices-capabilities.test.js, test/doc-catalog-counts.test.js - all pass.
  • node scripts/regen-registry-doc.js regenerated docs/DEVICE_REGISTRY.md, README, docs/CONNECTORS.md, docs/wiki/Home.md and the scripts/build-wiki.js headline (2,343 models, 29,052 sockets).
Fixes #800 Fixes #801 Fixes #802 ## What was blocked, and what unblocked it The earlier pass on all three issues read the family landing page (`https://e.huawei.com/en/products/routers/ne8000`), found capacity, line-card counts and power but no port census, and correctly refused to invent one. The vendor does publish a census - in the X Series datasheet's **Port Density** table, which gives a per-board port count *and* a per-model maximum for every port rate. ## The census, and why it is not a guess - Datasheet 'NetEngine 8000 X Series Router', Port Density table, quoted verbatim: `400G | 8 | 128 (14.4T SRU) | 64 (4T SRU) | 32 (4T SRU)` - i.e. 8 x 400GE cages per board, and 128 / 64 / 32 for X16 / X8 / X4. The neighbouring rows are `400G (14.4T SRU) | 36 | 576 | 288 | 144`, `100G | 40 | 640 | 320 | 160` and `25GE/10G/GE | 72 | 1152 | 576 | 288`. - The same datasheet's board table names the 8-cage card exactly: `LPUI-4T/LPUI-4T-E/LPUI-4T-L: 8*400GE QSFP-DD + 8*100GE QSFP28`. - Service slots 4 / 8 / 16 (X Series brochure, 'Product Specifications'), and the product page's Line Card row 16 / 8 / 4. - 8 x 4 = 32, 8 x 8 = 64, 8 x 16 = 128: the per-board count times the line-card slots lands on the datasheet's own 400G maximum for every one of the three models. Slot capability is 1T/2T/4T/14.4T/19.2T per slot on the X4 and X8 and 1T/2T/9.6T/14.4T on the X16, so a 4T card is valid in every slot of every member. Each chassis is therefore modelled as the 4T card in every line-card slot - `devices/huawei/netengine-8000-x4.json` (32 ports), `-x8.json` (64), `-x16.json` (128) - with port names `400GE<slot>/0/<0-7>`, following the hardware guide's rule that NetEngine 8000 X ports are `slot ID/subcard ID/port number` and a fixed card's subcard ID is 0. LPU slots are 1-4, 1-8 and 1-16 on the three chassis (hardware guide slot tables). ## Deliberately not claimed - **The 8 x 100GE QSFP28 cages each LPUI-4T also carries.** The datasheet prints no port numbering inside that mixed-rate card, and the hardware guide's one worked mixed example (`25GE 0-35 then 100GE 36-45`) is not enough to place 400GE and 100GE on this card. Declaring the 400GE census and saying so is the question; numbering the 100GE half would be the guess. - **The larger builds.** `400G (14.4T SRU)` (576 / 288 / 144), the 40-cage 100GE build (640 / 320 / 160) and the 19.2T 800GE card are different populations, named in the notes rather than folded in. - **MPLS/SRv6/EVPN/FlexE/BNG/CGN/IPsec/1588v2** are in the datasheet's Product Features but are not engine capability tokens, so they are in `notes`. `nat` is declared because the feature table lists CGN; no firewall capability is claimed because the vendor's table lists none. - No PoE and no console port: neither is published for these chassis. ## Sources 1. https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/f274014bf341427ba955064d5919b2fe/M2T1A669N992206662674575488/NetEngine%208000%20X%20Series%20Universal%20Service%20Router%20Datasheet.pdf (canonical; Port Density + board tables). Huawei's host answers 404 to a non-browser fetch, so the identical PDF was read at its mirror https://www.ycict.net/wp-content/uploads/2023/09/NetEngine-8000-X-Series-Universal-Service-Router-Datasheet.pdf 2. https://e-file.huawei.com/marketingcloud/pep/asset/20000001/Material/02d9fbd0807243b5b37d66759665d25a/M3T1A590N1069280707103375400/NetEngine%208000%20X%20Series%20Brochure.pdf - service slots 4/8/16, LPUI-4T and LPUI-14T4 rows, product features. 3. https://e.huawei.com/en/products/routers/ne8000 - per-model switching capacity, forwarding, MPU 2 1:1, SFU 8 7+1, power modules, dimensions, typical power. 4. https://support.huawei.com/enterprise/doc/EDOC1100465699/67e2f8f8/board - port numbering (slot/subcard/port, subcard 0 on a fixed card; mixed-rate LPU convention). ## Gates - `node scripts/syntax-check.js` - 368 files, all OK. - `node scripts/audit-port-types.js` - no port contradicts its declared type (QSFP-DD cages at 400GE). - `node scripts/audit-devices.js` - no hard defects. - `test/hardware-invariants.test.js` - 26 passed, 0 failed (2,343 models). - `test/catalogue-hygiene.test.js`, `test/device-aliases.test.js`, `test/missing-devices.test.js`, `test/import-devices-capabilities.test.js`, `test/doc-catalog-counts.test.js` - all pass. - `node scripts/regen-registry-doc.js` regenerated docs/DEVICE_REGISTRY.md, README, docs/CONNECTORS.md, docs/wiki/Home.md and the scripts/build-wiki.js headline (2,343 models, 29,052 sockets).
huawei: NetEngine 8000 X4, X8 and X16 at 32/64/128 x 400GE from the vendor's port density table
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m13s
CI / Test (Node 22) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 2s
58dcc54d5f
The whole X family was blocked on 'Huawei publishes no port census'. It does:
the X Series datasheet's Port Density table gives 400G at 8 ports per board for
X16/X8/X4 (128 / 64 / 32) and the board table names the card that carries them,
LPUI-4T (8*400GE QSFP-DD + 8*100GE QSFP28). Eight cages x 4/8/16 line-card slots
lands on the stated maximum for every model, so each chassis is modelled with a
4T card in every line-card slot and no invented mix.

Fixes #800, #801, #802
jaylouisw force-pushed catalogue/1117-0055 from 58dcc54d5f
Some checks failed
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Failing after 1m2s
CI / Test (Node 18) (pull_request) Successful in 1m13s
CI / Test (Node 22) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 2s
to 949e44ecf2
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Successful in 8s
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 1m3s
CI / Arm auto-merge (pull_request) Successful in 17s
2026-11-17 01:05:16 +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!1762
No description provided.