catalogue(huawei): NetEngine 8000 M6 AC - 16 ports from the vendor's own AC build (#796) #1911
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1911
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-2225"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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):
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):CR8D00E1VBC0OUT0 IN0CR8D00L4XFC0OUT0 IN0 to OUT3 IN3CR8D00EAGFC0OUT0 IN0 to OUT9 IN92 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
50ge0 .. ge15) rather than NetEngine'sslot/subcard/port.CR8D25E2XFC0, 2x10GECR8D00E2XFC0, 8xRJ45CR8D00E8GEC1, 20-port CSFPCR8D00EEGFC0, 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 OKnode scripts/audit-port-types.js- "No port contradicts its declared type"node scripts/import-devices.js(dry run) - nothing refused for this specnode test/hardware-invariants.test.js- 26 passed, 0 failednode test/device-aliases.test.js- 13 passed, 0 failednode test/doc-catalog-counts.test.js- 43 passed, 0 failednode scripts/run-tests.js --concurrency=4- 326 suites, 11,364 assertions, 0 failednode scripts/regen-registry-doc.js- registry regenerated: 2,351 models, Huawei 96 -> 97, router 381 -> 382f29c0e4c45a11839a327