Huawei NetEngine 8000 M4: 36 fixed ports, and two Huawei figures for its capacity (#795) #1545
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!1545
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1115-2055"
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?
Adds the Huawei NetEngine 8000 M4 chassis (issue #795) — a 2U model in the NetEngine 8000 M family, and the only one of M4/M6/M8/M14 with a fixed service panel.
What is modelled. 36 fixed cages in the datasheet's default combination ("Type 1"):
The four DC PIC slots are empty in this entry, so the entry is the fixed panel — not the chassis maximum of 116 ports / 12x100GE / 12x50GE. The panel's five other combination modes (Type 2-6) and the port-group mapping are in
notes; the mode switches per group, not per port.Discrepancy, stated rather than resolved. Huawei's M4 datasheet and brochure give 1.2 Tbit/s system capacity; the current NetEngine 8000 series specification table gives the M4 2.4 Tbit/s / 405 Mpps. Both are Huawei documents and they disagree by 2x, so no
fabricis declared — a fabric block would have to pick one.Sources
Unverifiable. support.huawei.com answers 403 to a direct fetch from this host, so the hardware-description figures were read through the search index of that page rather than the rendered page; the port table, the management-port list and the 116-port chassis maximum are the figures that come only from that document.
Validation.
syntax-check323 files OK ·audit-port-types"No port contradicts its declared type" ·spec-vs-description3/3 ·duplicate-models21/21 ·device-aliases+iface-alias30/30 ·premerge-checkclean · importer applied 1 spec, 0 rejected, 0 warnings.This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
Rebased onto main (
00204b30) � the only conflict was the generateddocs/DEVICE_REGISTRY.md, resolved by runningnpm run regen:registry-docrather than by hand: 2,057 -> 2,058 models, router 371 -> 372, Huawei 84 -> 85. Verified:audit:ports(no port contradicts its declared type),hardware-invariants26/26,apply-research10/10,validation22/22,check:citationsexit 0, and the regen is idempotent (clean tree afterwards). New head123c849e.d4cee2d8b1123c849e91This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
Rebased onto
origin/main(2f61af67) and pushed as91a82aae;mergeable=trueagain.The only conflict was
docs/DEVICE_REGISTRY.md— a generated file, so no side was hand-picked. I ranscripts/regen-registry-doc.jsagainst the merged catalogue: headline 2,067 models across 252 vendors, router 372, Huawei 85 (your NE8000 M4 adds one model and one Huawei row; main's #1550 added the router).regen-registry-doc.js --checkreports the doc is current.Verified: full
node scripts/run-tests.js— 254 suites, 9,267 assertions, 0 failed;missing-devices.jsCI gate passed. The catalogue JSONs themselves merged without conflict.91a82aae1157de12822dThis branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
Rebased onto main (
d013e7c2), dropping the earlier merge commit. Conflict was docs/DEVICE_REGISTRY.md only; regenerated withnode scripts/regen-registry-doc.js: 2,074 -> 2,075 models, router 371 -> 372, Huawei 84 -> 85. Nothing hand-edited. Verified: fullnpm teston the rebased head — 255 suites, 9,297 assertions, 0 failed — plus doc-catalog-counts 24, catalogue-hygiene 25, faceplate-catalogue 14, missing-devices 66, apply-research 10, import-devices-capabilities 29. Head is now57de1282, mergeable. No CI run dispatched yet.This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
57de12822daa9ee52024aa9ee52024d320721d62