research: NetEngine 8000 M8/M14 have no fixed panel � slot tables and the 60-card census (#797) #1747

Merged
jaylouisw merged 1 commit from catalogue/1116-2255 into main 2026-11-16 23:06:10 +00:00
Owner

Refs #797, #796, #799, #800, #801, #802, #789 � documentary, does NOT close any of them.

Every one of those requests was parked on the same sentence: Huawei publishes slots, not a port census. That is true, but the passes stopped at the marketing page. The primary hardware description says something sharper, and it turns out to be readable.

Source: NetEngine 8000 M14, M8, M4 and 8000E M14, M8, M4 V800R024C10SPC500 Hardware Description, EDOC1100465701 (2025-04-29) � /chassis, /boards, /af1a855b/interface-card, /ed7ab88b/netengine-8000-m4, /e4ccf4a0/netengine-8000-m8, /f446cf6d/netengine-8000-m14.

Fetch: a desktop UA gets 403 and web_extract gets the JS shell, but a crawler UA gets 200 and the full server-rendered page (620 kB for the M4 page). docs/MAINTAINING.md recorded this vendor as a login wall; that entry is corrected here.

What the slot tables say (quoted in the research file):

  • M4 Table 1-7 has a Fixed interface row for slot 5 � which is the 36-cage panel devices/huawei/netengine-8000-m4.json already models, and why #795 could close.
  • M8 Table 1-14: PIC DC 1-8 / AC 2,4-8, IPU 9-10, PIU DC 11-12 / AC 1,3, FAN 13. No fixed-interface slot.
  • M14 Table 1-25: PIC DC 1-14, IPU 15-16, PIU DC 17-18, FAN 19. No fixed-interface slot.

So an M8 or M14 with no cards has no cableable port, and the maximum is 8 or 14 cards worth � neither is "the device". Same test on the neighbours: the M6 datasheet accounts for 11 DC slots as 6 PIC + 2 IPU + 2 PIU + FAN, and X4/X8/X16 are line-card chassis.

What this PR adds: research/huawei-netengine-8000-m-series-slots.md with the reachable URLs, the fetch recipe, the three slot tables and the 60-part-number interface-card census (74 order codes) that a stated order gets built from � so "M8, slots 1-2 = CR8D00EAXFC1" converts to a spec with no inference.

Blocked, precisely: the field the issues need is which cards are fitted. Huawei does not state it for a bare model, and the catalogue has no way to express "N slots, card-dependent" � a slot list plus a card list is the catalogue change that would let these be modelled as chassis instead of parked.

Gates: node scripts/syntax-check.js (366 files OK), node scripts/audit-port-types.js (no port contradicts its declared type), node test/hardware-invariants.test.js (26 passed, 0 failed), node scripts/check-control-bytes.js (clean). No spec files touched, so no importer run and no registry regeneration.

Refs #797, #796, #799, #800, #801, #802, #789 � documentary, does NOT close any of them. Every one of those requests was parked on the same sentence: Huawei publishes slots, not a port census. That is true, but the passes stopped at the marketing page. The primary hardware description says something sharper, and it turns out to be readable. **Source:** NetEngine 8000 M14, M8, M4 and 8000E M14, M8, M4 V800R024C10SPC500 Hardware Description, EDOC1100465701 (2025-04-29) � /chassis, /boards, /af1a855b/interface-card, /ed7ab88b/netengine-8000-m4, /e4ccf4a0/netengine-8000-m8, /f446cf6d/netengine-8000-m14. **Fetch:** a desktop UA gets 403 and web_extract gets the JS shell, but a crawler UA gets 200 and the full server-rendered page (620 kB for the M4 page). docs/MAINTAINING.md recorded this vendor as a login wall; that entry is corrected here. **What the slot tables say** (quoted in the research file): - M4 Table 1-7 has a *Fixed interface* row for slot 5 � which is the 36-cage panel devices/huawei/netengine-8000-m4.json already models, and why #795 could close. - M8 Table 1-14: PIC DC 1-8 / AC 2,4-8, IPU 9-10, PIU DC 11-12 / AC 1,3, FAN 13. No fixed-interface slot. - M14 Table 1-25: PIC DC 1-14, IPU 15-16, PIU DC 17-18, FAN 19. No fixed-interface slot. So an M8 or M14 with no cards has no cableable port, and the maximum is 8 or 14 cards worth � neither is "the device". Same test on the neighbours: the M6 datasheet accounts for 11 DC slots as 6 PIC + 2 IPU + 2 PIU + FAN, and X4/X8/X16 are line-card chassis. **What this PR adds:** research/huawei-netengine-8000-m-series-slots.md with the reachable URLs, the fetch recipe, the three slot tables and the 60-part-number interface-card census (74 order codes) that a stated order gets built from � so "M8, slots 1-2 = CR8D00EAXFC1" converts to a spec with no inference. **Blocked, precisely:** the field the issues need is *which cards are fitted*. Huawei does not state it for a bare model, and the catalogue has no way to express "N slots, card-dependent" � a slot list plus a card list is the catalogue change that would let these be modelled as chassis instead of parked. **Gates:** node scripts/syntax-check.js (366 files OK), node scripts/audit-port-types.js (no port contradicts its declared type), node test/hardware-invariants.test.js (26 passed, 0 failed), node scripts/check-control-bytes.js (clean). No spec files touched, so no importer run and no registry regeneration.
research: NetEngine 8000 M8/M14 have no fixed panel, and support.huawei.com is readable to a crawler UA (#797)
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 17s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 5s
a9c3ece1ed
jaylouisw force-pushed catalogue/1116-2255 from a9c3ece1ed
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 17s
CI / Server smoke test (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Docker build (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Arm auto-merge (pull_request) Successful in 5s
to 4d61991a10
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 18s
CI / Server smoke test (pull_request) Successful in 23s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 20) (pull_request) Successful in 1m1s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Arm auto-merge (pull_request) Successful in 13s
2026-11-16 23:02:54 +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!1747
No description provided.