Huawei NetEngine 8000 M4: 36 fixed ports, and two Huawei figures for its capacity (#795) #1545

Merged
jaylouisw merged 1 commit from catalogue/1115-2055 into main 2026-11-16 01:00:11 +00:00
Owner

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"):

  • 0-3: QSFP28, 100GE/50GE/40GE — the only ports that break out (4x25GE or 4x10GE each)
  • 4-19: SFP28 at GE in the default mode (cages accept 25GE/10GE/GE)
  • 20-35: SFP28 at 25GE/10GE (no 1GE mode on this group)

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 fabric is 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-check 323 files OK · audit-port-types "No port contradicts its declared type" · spec-vs-description 3/3 · duplicate-models 21/21 · device-aliases + iface-alias 30/30 · premerge-check clean · importer applied 1 spec, 0 rejected, 0 warnings.

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"): - 0-3: QSFP28, 100GE/50GE/40GE — the only ports that break out (4x25GE or 4x10GE each) - 4-19: SFP28 at GE in the default mode (cages accept 25GE/10GE/GE) - 20-35: SFP28 at 25GE/10GE (no 1GE mode on this group) 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 `fabric` is declared — a fabric block would have to pick one. **Sources** - Hardware description V800R024C10SPC500, "NetEngine 8000 M4" (port table, slot layout, 116-port maximum, management ports, V800R022C00SPC600 first supported version): https://support.huawei.com/enterprise/en/doc/EDOC1100465701/ed7ab88b/netengine-8000-m4 - Huawei NetEngine 8000 series specification table (2.4 Tbit/s, 405 Mpps, 2U 88.4 mm, 283.4 W, 10.4 kg): https://e.huawei.com/en/products/routers/ne8000 - M4 datasheet (six fixed-port modes, 4 DC / 2 AC service slots, BNG/CGNAT/IPSec, PIC list): https://www.sicetelecom.it/wp-content/MU/datasheet/Huawei-Router-HuaweiNetEngine-8000-M4-2x100G-CR8PM4BASDC0-SICE-Distributore-Italiano.pdf **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-check` 323 files OK · `audit-port-types` "No port contradicts its declared type" · `spec-vs-description` 3/3 · `duplicate-models` 21/21 · `device-aliases` + `iface-alias` 30/30 · `premerge-check` clean · importer applied 1 spec, 0 rejected, 0 warnings.
Huawei NetEngine 8000 M4: 36 fixed ports, and two Huawei figures for its capacity (#795)
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Test (Node 18) (pull_request) Successful in 3m21s
CI / Test (Node 20) (pull_request) Successful in 3m7s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 3m4s
d4cee2d8b1
Author
Owner

This branch conflicts with main, so it was not rebased:

devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json 

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.

This branch conflicts with `main`, so it was not rebased: ``` devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json ``` 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.
Author
Owner

Rebased onto main (00204b30) � the only conflict was the generated docs/DEVICE_REGISTRY.md, resolved by running npm run regen:registry-doc rather than by hand: 2,057 -> 2,058 models, router 371 -> 372, Huawei 84 -> 85. Verified: audit:ports (no port contradicts its declared type), hardware-invariants 26/26, apply-research 10/10, validation 22/22, check:citations exit 0, and the regen is idempotent (clean tree afterwards). New head 123c849e.

Rebased onto main (00204b30) � the only conflict was the generated `docs/DEVICE_REGISTRY.md`, resolved by running `npm run regen:registry-doc` rather than by hand: 2,057 -> **2,058 models**, router 371 -> **372**, Huawei 84 -> **85**. Verified: `audit:ports` (no port contradicts its declared type), `hardware-invariants` 26/26, `apply-research` 10/10, `validation` 22/22, `check:citations` exit 0, and the regen is idempotent (clean tree afterwards). New head 123c849e.
jaylouisw force-pushed catalogue/1115-2055 from d4cee2d8b1
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Test (Node 18) (pull_request) Successful in 3m21s
CI / Test (Node 20) (pull_request) Successful in 3m7s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 3m4s
to 123c849e91
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 40s
CI / Test (Node 18) (pull_request) Successful in 3m26s
CI / Test (Node 20) (pull_request) Successful in 3m9s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 2m59s
2026-11-15 21:13:00 +00:00
Compare
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-15 21:51:39 +00:00
Author
Owner

This branch conflicts with main, so it was not rebased:

devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json 

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.

This branch conflicts with `main`, so it was not rebased: ``` devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json ``` 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.
Merge origin/main; regenerate DEVICE_REGISTRY.md counts
All checks were successful
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 3m31s
CI / Test (Node 20) (pull_request) Successful in 3m16s
CI / Server smoke test (pull_request) Successful in 31s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 3m16s
91a82aae11
Conflicts in docs/DEVICE_REGISTRY.md were generated counts (headline,
router, Huawei row). Resolved by running scripts/regen-registry-doc.js
against the merged catalogue — 2,067 models across 252 vendors, router
372, Huawei 85 — never by hand-picking a side.
Author
Owner

Rebased onto origin/main (2f61af67) and pushed as 91a82aae; mergeable=true again.

The only conflict was docs/DEVICE_REGISTRY.md — a generated file, so no side was hand-picked. I ran scripts/regen-registry-doc.js against 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 --check reports the doc is current.

Verified: full node scripts/run-tests.js — 254 suites, 9,267 assertions, 0 failed; missing-devices.js CI gate passed. The catalogue JSONs themselves merged without conflict.

Rebased onto `origin/main` (`2f61af67`) and pushed as `91a82aae`; `mergeable=true` again. The only conflict was `docs/DEVICE_REGISTRY.md` — a generated file, so no side was hand-picked. I ran `scripts/regen-registry-doc.js` against 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 --check` reports the doc is current. Verified: full `node scripts/run-tests.js` — 254 suites, 9,267 assertions, 0 failed; `missing-devices.js` CI gate passed. The catalogue JSONs themselves merged without conflict.
jaylouisw force-pushed catalogue/1115-2055 from 91a82aae11
All checks were successful
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 20s
CI / Test (Node 18) (pull_request) Successful in 3m31s
CI / Test (Node 20) (pull_request) Successful in 3m16s
CI / Server smoke test (pull_request) Successful in 31s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 3m16s
to 57de12822d
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 3m35s
CI / Test (Node 18) (pull_request) Successful in 3m47s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 3m11s
2026-11-15 22:58:08 +00:00
Compare
Author
Owner

This branch conflicts with main, so it was not rebased:

devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json 

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.

This branch conflicts with `main`, so it was not rebased: ``` devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json ``` 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.
Author
Owner

Rebased onto main (d013e7c2), dropping the earlier merge commit. Conflict was docs/DEVICE_REGISTRY.md only; regenerated with node scripts/regen-registry-doc.js: 2,074 -> 2,075 models, router 371 -> 372, Huawei 84 -> 85. Nothing hand-edited. Verified: full npm test on 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 now 57de1282, mergeable. No CI run dispatched yet.

Rebased onto main (d013e7c2), dropping the earlier merge commit. Conflict was docs/DEVICE_REGISTRY.md only; regenerated with `node scripts/regen-registry-doc.js`: 2,074 -> 2,075 models, router 371 -> 372, Huawei 84 -> 85. Nothing hand-edited. Verified: full `npm test` on 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 now 57de1282, mergeable. No CI run dispatched yet.
Author
Owner

This branch conflicts with main, so it was not rebased:

devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json 

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.

This branch conflicts with `main`, so it was not rebased: ``` devices/huawei/netengine-8000-m4.json docs/DEVICE_REGISTRY.md research/incoming/devices-huawei-ne8000-m4.json ``` 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.
jaylouisw force-pushed catalogue/1115-2055 from 57de12822d
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 3m35s
CI / Test (Node 18) (pull_request) Successful in 3m47s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 3m11s
to aa9ee52024
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 3m24s
CI / Test (Node 20) (pull_request) Failing after 3m12s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Failing after 3m4s
2026-11-15 23:25:36 +00:00
Compare
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 01:00:00 +00:00
jaylouisw force-pushed catalogue/1115-2055 from aa9ee52024
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 23s
CI / Test (Node 18) (pull_request) Failing after 3m24s
CI / Test (Node 20) (pull_request) Failing after 3m12s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Failing after 3m4s
to d320721d62
Some checks failed
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Failing after 3m16s
CI / Test (Node 18) (pull_request) Failing after 3m34s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Failing after 3m11s
2026-11-16 01:00:01 +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!1545
No description provided.