catalogue(huawei): NetEngine 8000 M6 AC - 16 ports from the vendor's own AC build (#796) #1911

Merged
jaylouisw merged 1 commit from catalogue/1117-2225 into main 2026-11-17 22:44:37 +00:00
Owner

Fixes #796

Device: Huawei NetEngine 8000 M6 AC, modelled as the build Huawei states in its own AC typical-configuration row.
Spec: devices/huawei/netengine-8000-m6.json - 16 ports: 2x 50GE QSFP28, 4x 10GE/GE SFP+, 10x GE/FE SFP.

1. The bare chassis has no cableable port (vendor-sourced)

Hardware Description V800R023C10SPC500 Table 1-29, "Slots on the NetEngine 8000 M6"
(https://support.huawei.com/enterprise/en/doc/EDOC1100382052/374d9a7/netengine-8000-m6, HTTP 200, 526,382 B, crawler user-agent): PIC DC 1-6 / AC 2, 4-6, CXP 7, 8, PIU DC 9, 10 / AC 1, 3, FAN 11 - no fixed-interface row.

2. But the AC table does state a build, and it fills the chassis

Same document, Table 1-31 (technical specifications of the CR8BM6BKPAC1):

[CXP-160/CXP-160-B]AC Typical configuration 2: 2*CXP+1*FAN+2*AC power+2*CR8D00E1VBC0+1*CR8D00L4XFC0 + 1*CR8D00EAGFC0 =220.07 W

Four PICs (2 + 1 + 1) against the AC chassis' 9 slots, 4 service board slots (Table 1-31; the datasheet's own spec table reads "Service Slots 6 (DC) / 4 (AC)"). Every service slot is occupied, so nothing is left silently empty and no card-to-slot choice is made on the vendor's behalf - the same property that made the M8's power row a usable build in #1802.

The DC row (205.8 W) carries the same four cards against six DC service slots, so two would be empty there; it is deliberately not folded in, which is why this entry is the AC variant.

An earlier datasheet revision prints 222.07 W for this AC row; the current vendor datasheet (340,235 B, 6 pp., read the same day) dropped its ordering/configuration sections entirely, so the hardware description in force is the source quoted. The card set is identical either way.

3. Card port counts, from each card's own vendor chapter

Vendor Hardware Guide https://support.huawei.com/enterprise/en/doc/EDOC1100264779 (Issue 05, 2023-03-31):

card chapter description / silkscreen ports connector
CR8D00E1VBC0 3.4.5.42, p.903 1-port 50G Base (QSFP28) PIC / 1x50GE-QSFP28 - "Provides one 50GE interface", breakout not supported OUT0 IN0 QSFP28
CR8D00L4XFC0 3.4.5.52, p.963 4-Port 10GE(SFP+)/GE(SFP) MACsec PIC / 4x10GE-SFP+ OUT0 IN0 to OUT3 IN3 SFP+
CR8D00EAGFC0 3.4.5.56, p.965 10-port 100/1000Base-X-SFP MACsec PIC / 10xFE/GE-SFP OUT0 IN0 to OUT9 IN9 SFP

2 x 50GE + 4 x 10GE/GE + 10 x GE/FE = 16 ports. The AC chassis' per-rate maxima (50GE 2, 10GE 14, GE 70, physical 70) are used only as a bound to check the build against, never as counts.

Chassis figures from Table 1-31: 88.9 x 442 x 220 mm (2U), 11.35 kg fully configured, 320 Gbit/s switching capacity, MTBF 116.61 y, MTTR 0.5 h, 2 power modules 1+1, redundant CXPs 1:1, 1500 W rated output, standard C13.

Not asserted, deliberately

  • Card-to-slot assignment - the vendor prints the complement, not an order, so port names are flat (50ge0 .. ge15) rather than NetEngine's slot/subcard/port.
  • ETH management port count - the CXP is listed with a console but no management-port count is published for this chassis (same call as the M8).
  • The other PICs the M6 can take (25GE CR8D25E2XFC0, 2x10GE CR8D00E2XFC0, 8xRJ45 CR8D00E8GEC1, 20-port CSFP CR8D00EEGFC0, E1/cPOS/voice) - a spec states one build.

Research trail: research/huawei-netengine-8000-m-series-slots.md, new final section.

Gates

  • node scripts/syntax-check.js - 399 files, all OK
  • node scripts/audit-port-types.js - "No port contradicts its declared type"
  • node scripts/import-devices.js (dry run) - nothing refused for this spec
  • node test/hardware-invariants.test.js - 26 passed, 0 failed
  • node test/device-aliases.test.js - 13 passed, 0 failed
  • node test/doc-catalog-counts.test.js - 43 passed, 0 failed
  • node scripts/run-tests.js --concurrency=4 - 326 suites, 11,364 assertions, 0 failed
  • node scripts/regen-registry-doc.js - registry regenerated: 2,351 models, Huawei 96 -> 97, router 381 -> 382
Fixes #796 **Device:** Huawei NetEngine 8000 M6 **AC**, modelled as the build Huawei states in its own AC typical-configuration row. **Spec:** `devices/huawei/netengine-8000-m6.json` - 16 ports: 2x 50GE QSFP28, 4x 10GE/GE SFP+, 10x GE/FE SFP. ### 1. The bare chassis has no cableable port (vendor-sourced) Hardware Description V800R023C10SPC500 Table 1-29, "Slots on the NetEngine 8000 M6" (`https://support.huawei.com/enterprise/en/doc/EDOC1100382052/374d9a7/netengine-8000-m6`, HTTP 200, 526,382 B, crawler user-agent): PIC **DC 1-6 / AC 2, 4-6**, CXP 7, 8, PIU DC 9, 10 / AC 1, 3, FAN 11 - **no fixed-interface row**. ### 2. But the AC table does state a build, and it fills the chassis Same document, Table 1-31 (technical specifications of the CR8BM6BKPAC1): > [CXP-160/CXP-160-B]AC Typical configuration 2: 2\*CXP+1\*FAN+2\*AC power+2\*`CR8D00E1VBC0`+1\*`CR8D00L4XFC0` + 1\*`CR8D00EAGFC0` =220.07 W Four PICs (2 + 1 + 1) against the AC chassis' **9 slots, 4 service board slots** (Table 1-31; the datasheet's own spec table reads "Service Slots 6 (DC) / 4 (AC)"). Every service slot is occupied, so nothing is left silently empty and no card-to-slot choice is made on the vendor's behalf - the same property that made the M8's power row a usable build in #1802. The **DC** row (205.8 W) carries the same four cards against six DC service slots, so two would be empty there; it is deliberately not folded in, which is why this entry is the AC variant. An earlier datasheet revision prints 222.07 W for this AC row; the current vendor datasheet (340,235 B, 6 pp., read the same day) dropped its ordering/configuration sections entirely, so the hardware description in force is the source quoted. The card set is identical either way. ### 3. Card port counts, from each card's own vendor chapter Vendor Hardware Guide `https://support.huawei.com/enterprise/en/doc/EDOC1100264779` (Issue 05, 2023-03-31): | card | chapter | description / silkscreen | ports | connector | |---|---|---|---|---| | `CR8D00E1VBC0` | 3.4.5.42, p.903 | 1-port 50G Base (QSFP28) PIC / 1x50GE-QSFP28 - "Provides one 50GE interface", breakout not supported | `OUT0 IN0` | QSFP28 | | `CR8D00L4XFC0` | 3.4.5.52, p.963 | 4-Port 10GE(SFP+)/GE(SFP) MACsec PIC / 4x10GE-SFP+ | `OUT0 IN0 to OUT3 IN3` | SFP+ | | `CR8D00EAGFC0` | 3.4.5.56, p.965 | 10-port 100/1000Base-X-SFP MACsec PIC / 10xFE/GE-SFP | `OUT0 IN0 to OUT9 IN9` | SFP | 2 x 50GE + 4 x 10GE/GE + 10 x GE/FE = **16 ports**. The AC chassis' per-rate maxima (50GE 2, 10GE 14, GE 70, physical 70) are used only as a bound to check the build against, never as counts. Chassis figures from Table 1-31: 88.9 x 442 x 220 mm (2U), 11.35 kg fully configured, 320 Gbit/s switching capacity, MTBF 116.61 y, MTTR 0.5 h, 2 power modules 1+1, redundant CXPs 1:1, 1500 W rated output, standard C13. ### Not asserted, deliberately - **Card-to-slot assignment** - the vendor prints the complement, not an order, so port names are flat (`50ge0 .. ge15`) rather than NetEngine's `slot/subcard/port`. - **ETH management port count** - the CXP is listed with a console but no management-port count is published for this chassis (same call as the M8). - **The other PICs the M6 can take** (25GE `CR8D25E2XFC0`, 2x10GE `CR8D00E2XFC0`, 8xRJ45 `CR8D00E8GEC1`, 20-port CSFP `CR8D00EEGFC0`, E1/cPOS/voice) - a spec states one build. Research trail: `research/huawei-netengine-8000-m-series-slots.md`, new final section. ### Gates - `node scripts/syntax-check.js` - 399 files, all OK - `node scripts/audit-port-types.js` - "No port contradicts its declared type" - `node scripts/import-devices.js` (dry run) - nothing refused for this spec - `node test/hardware-invariants.test.js` - 26 passed, 0 failed - `node test/device-aliases.test.js` - 13 passed, 0 failed - `node test/doc-catalog-counts.test.js` - 43 passed, 0 failed - `node scripts/run-tests.js --concurrency=4` - 326 suites, 11,364 assertions, 0 failed - `node scripts/regen-registry-doc.js` - registry regenerated: 2,351 models, Huawei 96 -> 97, router 381 -> 382
catalogue(huawei): NetEngine 8000 M6 AC - 16 ports from the vendor's own AC build (#796)
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 15s
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 51s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 7s
f29c0e4c45
The M6's AC specification table states its measurement configuration as 2x CR8D00E1VBC0 + 1x CR8D00L4XFC0 + 1x CR8D00EAGFC0 (220.07 W) - four PICs against the AC chassis' four service slots, so the build fills the chassis exactly, the same property that made the M8's power row usable. Card port counts come from each card's own chapter in the vendor Hardware Guide (3.4.5.42, 3.4.5.52, 3.4.5.56): 1x 50GE QSFP28, 4x 10GE/GE SFP+, 10x GE/FE SFP = 16 ports.
jaylouisw force-pushed catalogue/1117-2225 from f29c0e4c45
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 15s
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 51s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 7s
to a11839a327
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 21s
2026-11-17 22:42:29 +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!1911
No description provided.