research(NE8000 M6): the ordering table, not the datasheet summary, is why #796 is blocked #1777

Merged
jaylouisw merged 1 commit from catalogue/1117-0255 into main 2026-11-17 03:13:30 +00:00
Owner

Refs #796 (does not close it - the missing field is a configuration, not a document).

What changed. research/huawei-netengine-8000-m-series-slots.md gains "The M6, checked against its own ordering table", and the note title now includes the M6 with the M8/M14.

Why the M6 is blocked, stated rather than inferred. Earlier passes said "Huawei publishes slots, not ports". For the M6 that can be made exact:

  • https://support.huawei.com/enterprise/en/doc/EDOC1100382052/374d9a7/netengine-8000-m6 (V800R023C10SPC500 Hardware Description, crawler UA, HTTP 200) - Table 1-29: PIC DC 1-6 / AC 2,4-6; CXP 7,8; PIU DC 9,10 / AC 1,3; FAN 11. No fixed-interface row.
  • Same page, Tables 1-30/1-31: DC 11 slots / 6 service board slots, AC 9 / 4; max physical ports on the entire device 100, 25GE 6, 10GE 16, 50GE 2, 100GE/40GE NA - a maximum over six fitted cards, not a panel.
  • https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/b50df453e4bf4ca4b99ef855437e8cc9/M3T1A590N1140254128116289674/NetEngine%208000%20M6%20Universal%20Service%20Router%20Datasheet.pdf - current datasheet, "up to 160G port capacity and 6 service slots", and it has dropped the Ordering Information section.
  • https://data.nag.wiki/Huawei/Datasheet/NE8000/8000M6.pdf (earlier revision, 12 pages) - "Basic Hardware Configurations": CR8PM6BASDC1 / CR8PM6BASAC1 / CR8PM6BASDC3 / CR8PM6BASAC3 are chassis + 2CXP + 2power, no PIC; every card is a separate BOM line.

So an M6 as ordered has no cableable port, and the base SKU is not a device a lab can cable.

What would close #796: one line naming the PICs in Huawei part numbers and their slots, e.g. "NetEngine 8000 M6 (DC), slots 1-2 = CR8D00L4XFC0, slots 3-4 = CR8D00EAGFC0". The HD separately quotes two "Typical configuration" power references (2CR8D00L4XFC0 + 2CR8D00EAGFC0 = 196.1 W, and the 2CR8D00E1VBC0 + 1CR8D00L4XFC0 + 1*CR8D00EAGFC0 variant); those are recorded in the note as evidence a future answer can quote, with the reason they are not an order (no slot assignment, config 2 leaves two of six PIC slots empty).

Gates: syntax-check 371 files OK; audit-port-types clean; faceplate-catalogue.test.js 14/14; regen-registry-doc reports pages already current (2,344 models / 258 vendors); check-control-bytes clean. No spec files touched, so no importer/tripwire surface.

Refs #796 (does not close it - the missing field is a configuration, not a document). **What changed.** `research/huawei-netengine-8000-m-series-slots.md` gains "The M6, checked against its own ordering table", and the note title now includes the M6 with the M8/M14. **Why the M6 is blocked, stated rather than inferred.** Earlier passes said "Huawei publishes slots, not ports". For the M6 that can be made exact: - `https://support.huawei.com/enterprise/en/doc/EDOC1100382052/374d9a7/netengine-8000-m6` (V800R023C10SPC500 Hardware Description, crawler UA, HTTP 200) - Table 1-29: PIC DC 1-6 / AC 2,4-6; CXP 7,8; PIU DC 9,10 / AC 1,3; FAN 11. **No fixed-interface row.** - Same page, Tables 1-30/1-31: DC 11 slots / **6 service board slots**, AC 9 / **4**; max physical ports on the entire device **100**, 25GE 6, 10GE 16, 50GE 2, 100GE/40GE **NA** - a maximum over six fitted cards, not a panel. - `https://e.huawei.com/marketingcloud/pep/asset/20000001/Material/b50df453e4bf4ca4b99ef855437e8cc9/M3T1A590N1140254128116289674/NetEngine%208000%20M6%20Universal%20Service%20Router%20Datasheet.pdf` - current datasheet, "up to 160G port capacity and 6 service slots", and it has dropped the Ordering Information section. - `https://data.nag.wiki/Huawei/Datasheet/NE8000/8000M6.pdf` (earlier revision, 12 pages) - "Basic Hardware Configurations": `CR8PM6BASDC1` / `CR8PM6BASAC1` / `CR8PM6BASDC3` / `CR8PM6BASAC3` are **chassis + 2*CXP + 2*power, no PIC**; every card is a separate BOM line. So an M6 as ordered has no cableable port, and the base SKU is not a device a lab can cable. **What would close #796:** one line naming the PICs in Huawei part numbers and their slots, e.g. "NetEngine 8000 M6 (DC), slots 1-2 = CR8D00L4XFC0, slots 3-4 = CR8D00EAGFC0". The HD separately quotes two "Typical configuration" power references (2*CR8D00L4XFC0 + 2*CR8D00EAGFC0 = 196.1 W, and the 2*CR8D00E1VBC0 + 1*CR8D00L4XFC0 + 1*CR8D00EAGFC0 variant); those are recorded in the note as evidence a future answer can quote, with the reason they are not an order (no slot assignment, config 2 leaves two of six PIC slots empty). **Gates:** `syntax-check` 371 files OK; `audit-port-types` clean; `faceplate-catalogue.test.js` 14/14; `regen-registry-doc` reports pages already current (2,344 models / 258 vendors); `check-control-bytes` clean. No spec files touched, so no importer/tripwire surface.
research(NE8000): the M6's own ordering table, not its datasheet summary, is why #796 is blocked
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 20) (pull_request) Failing after 53s
CI / Test (Node 18) (pull_request) Successful in 1m7s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
7bca2f10df
The M6 was the one NetEngine 8000 member whose "no fixed panel" claim rested on a
datasheet summary. Checked against the primary hardware description and the datasheet's
Ordering Information section:

- V800R023C10SPC500 HD, Table 1-29: PIC DC 1-6 / AC 2,4-6, CXP 7,8, PIU DC 9,10 / AC 1,3,
  FAN 11 - no fixed-interface row. Tables 1-30/1-31: DC 11 slots / 6 service slots,
  AC 9 / 4, and a maximum-port block (100 physical, 16x10GE, 6x25GE, 2x50GE, 100GE NA)
  that is a maximum over six fitted cards, not a panel.
- Current datasheet dropped the Ordering Information section; the earlier revision's
  basic-configuration BOMs (CR8PM6BASDC1 / CR8PM6BASAC1 / CR8PM6BASDC3 / CR8PM6BASAC3)
  contain chassis + 2*CXP + 2*power and no PIC at all, with every card a separate line.

So an M6 as ordered has no cableable port: #796 needs a stated card set, not more research.
The HD's "Typical configuration" power references are recorded as evidence, with the
reason they are not an order.

Gates: syntax-check 371 OK, audit-port-types OK, faceplate-catalogue 14/14,
regen-registry-doc no change, check-control-bytes OK.
jaylouisw force-pushed catalogue/1117-0255 from 7bca2f10df
Some checks failed
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 8s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 30s
CI / Test (Node 20) (pull_request) Failing after 53s
CI / Test (Node 18) (pull_request) Successful in 1m7s
CI / Test (Node 22) (pull_request) Successful in 1m4s
CI / Arm auto-merge (pull_request) Successful in 3s
to a1dd5de59f
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 20s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 11s
2026-11-17 03:03:37 +00:00
Compare
jaylouisw force-pushed catalogue/1117-0255 from a1dd5de59f
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 20s
CI / Server smoke test (pull_request) Successful in 11s
CI / Test (Node 20) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 18) (pull_request) Successful in 1m4s
CI / Test (Node 22) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 11s
to e0ae66d7f0
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Classify the change (pull_request) Successful in 19s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Arm auto-merge (pull_request) Successful in 12s
2026-11-17 03:06:17 +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!1777
No description provided.