devices: NetEngine 8000 F8 in Huawei's own 6.4T bundle (#789) #1758
Closed
jaylouisw
wants to merge 1 commit from
catalogue/1117-0025 into main
pull from: catalogue/1117-0025
merge into: jaylouisw:main
jaylouisw:main
jaylouisw:rev/1121-1812
jaylouisw:catalogue/1121-1822
jaylouisw:docs/1121-1817
jaylouisw:catalogue/1121-1752
jaylouisw:docs/1121-1747
jaylouisw:rev/1121-1742
jaylouisw:catalogue/1121-1722
jaylouisw:rev/1121-1712
jaylouisw:docs/1121-1717
jaylouisw:catalogue/1121-1652
jaylouisw:rev/1121-1642
jaylouisw:docs/1121-1647
jaylouisw:ci/1121-1646
jaylouisw:ci/1121-1427
jaylouisw:rev/1121-1412
jaylouisw:catalogue/1121-1422
jaylouisw:docs/1121-1417
jaylouisw:catalogue/1121-1352
jaylouisw:rev/1121-1342
jaylouisw:docs/1121-1347
jaylouisw:rev/1121-1212
jaylouisw:catalogue/1121-1222
jaylouisw:docs/1121-1217
jaylouisw:ci/1121-1027
jaylouisw:catalogue/1121-1022
jaylouisw:rev/1121-1013
jaylouisw:docs/1121-1017
jaylouisw:catalogue/1121-0852
jaylouisw:rev/1121-0842
jaylouisw:docs/1121-0847
jaylouisw:ci/1121-0827
jaylouisw:catalogue/1121-0822
jaylouisw:rev/1121-0812
jaylouisw:catalogue/1121-0752
jaylouisw:rev/1121-0742
jaylouisw:docs/1121-0747
jaylouisw:catalogue/1121-0722
jaylouisw:docs/1121-0717
jaylouisw:rev/1121-0712
jaylouisw:rev/1121-0642
jaylouisw:plan/1121-0637
jaylouisw:ci/1121-0627
jaylouisw:catalogue/1121-0622
jaylouisw:rev/1121-0612
jaylouisw:docs/1121-0617
jaylouisw:plan/1120-0337
jaylouisw:docs/1120-0347
jaylouisw:rev/1119-1942
jaylouisw:rev/1119-1912
jaylouisw:catalogue/1119-1752
jaylouisw:docs/1119-1347
jaylouisw:catalogue/1119-1352
jaylouisw:fix/1119-1232
jaylouisw:fix/1119-0602
jaylouisw:catalogue/1119-0452
jaylouisw:catalogue/1119-0422
jaylouisw:docs/1119-0417
jaylouisw:fix/1119-0202
jaylouisw:catalogue/1119-0222
jaylouisw:rev/1119-0042
jaylouisw:catalogue/1118-2252
jaylouisw:docs/1118-2047
jaylouisw:catalogue/1118-2152
jaylouisw:fix/1118-2037
jaylouisw:ci/1118-2027
jaylouisw:docs/1118-1416
jaylouisw:fix/1118-1006
jaylouisw:catalogue/1118-0326
jaylouisw:catalogue/1117-2326
jaylouisw:catalogue/1116-1730
jaylouisw:fix/1523-speed-downgrade-one-end
jaylouisw:fix/enable-required-and-empty-pipe-help
jaylouisw:land-all-v5
jaylouisw:land-all-v4
jaylouisw:land-all-v3
jaylouisw:land-all-v2
jaylouisw:land-all
jaylouisw:fix/board-id
jaylouisw:fix/stated-range
jaylouisw:fix/no-form-names-v2
jaylouisw:fix/voice-vlan
jaylouisw:devices/catalogue-batch
jaylouisw:devices/powerline-moca
jaylouisw:devices/firewalls-enterprise
jaylouisw:devices/pon-splitters
jaylouisw:devices/nvr-and-taps
jaylouisw:devices/four-nvr-models
jaylouisw:fix/contributing-exemption
jaylouisw:fix/stale-github-urls
jaylouisw:ci/cancel-superseded-runs
jaylouisw:gh/1438
jaylouisw:device/uisp-console-lbe-xr
jaylouisw:gh/1442
jaylouisw:docs/readme-current-counts
jaylouisw:feat/device-ubiquiti-wave-fiber-onu
jaylouisw:fix/address-ownership
jaylouisw:feat/vrrp-in-path
jaylouisw:fix/merge-research-duplicate
jaylouisw:docs/hybrid-patch-current
jaylouisw:fix/audit-port-template
jaylouisw:fix/2930f-jl256a-uplinks
jaylouisw:feat/dhcp-in-path
jaylouisw:feat/hackgpon-ubiquiti-uisp-fiber-xgs
jaylouisw:feat/hackgpon-adtran-sdx-621
jaylouisw:tool/issue-duplicate-sweep
jaylouisw:feat/device-mikrotik-rb433ah
jaylouisw:feat/hackgpon-ma5671a
jaylouisw:issues/categories-and-labels
jaylouisw:ci/run-every-suite-locally
jaylouisw:chore/http-smoke
No reviewers
Labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!1758
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1117-0025"
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 #789
The NetEngine 8000 F8 is modellable because Huawei publishes a board census and quotes typical
power for a named board mix — the thing the earlier passes looked for on the marketing page and
did not find one document further down.
devices/huawei/netengine-8000-f8.json— modelNetEngine 8000 F8 (4x 8x100GE, 4x 72x10GE),320 ports:
CR8DE8NB00F0, LPUC-800-CM, 8 ports, slots 1-4)CR8DERXFMSF0, LPUC-800-CM, 72 ports, MACsec, slots 5-8)Why that mix is not a guess: the chassis table states "Typical power consumption 2362 W
(configured with SRU 6T4-B and four 8x100GE ports and four 72x10GE ports)". Which slots hold which
board is the one field the source does not state — the spec says so in
notes, and any LPUC-800-CMboard may sit in any of LPU slots 1-8 with an SRU-6T4-B.
Port names follow the guide's own rule (§3.5.1.4):
slot ID/PIC ID/port number, PIC IDs from 0,LPUC PIC ID 0, ports from 0 left to right.
Sources (in
sourceUrl+notes):research/huawei-netengine-8000-f8-boards.mdrecords the board table (8x100GE, 4x100GE+40x10GE,72x10GE/GE, LPUC-100 72x GE, LPUC-400-CM, LPUT-800-CM + PICs), the slot map and the RTU caveat
(high-speed modes are capped at 100 Mbit/s until the licence loads), so the remaining F8 variants are
one spec file each rather than another research pass.
Gates
node scripts/syntax-check.js— 367 files, all OKnode scripts/audit-port-types.js— "No port contradicts its declared type."scripts/import-devices.js(PF_INCOMING/PF_DEVICES sandbox) — "Scanned 1 file(s), 1 spec(s) / Would add: 1 duplicates: 0 rejected: 0", no capability warningstest/hardware-invariants.test.js— 26 passed, 0 failed (2,340 models)test/catalogue-hygiene.test.js— 25 passed, 0 failedtest/faceplate-catalogue.test.js— 14 passed, 0 failedscripts/regen-registry-doc.js— registry doc + counts regenerated, never hand-editedc7c64d7d780a65ccf8190a65ccf81962fe352840Green on all eight checks, but it cannot be merged mechanically — and the reason is a modelling decision, not a conflict I should resolve. Needs Jay's decision.
State
62fe3528:CI / Test (Node 18/20/22),Server smoke test,Docker build,Arm auto-merge— all success. Your only problem ismergeable=false, and that is real here, not an uncomputed value.f520c044; main is at18f25c1a(9 ahead).devices/huawei/netengine-8000-f8.json. #1743 (same issue, #789) was opened 22:41, merged at 00:54 as12a9afac; this PR was opened 00:37, seventeen minutes before that merge landed and after the point where it could see it. Both add the same path. Issue #789 is now closed by12a9afac.Why I did not rebase it
A rebase would not remove the conflict, it would merely turn it into "delete main's file, add mine" — i.e. I would be choosing a port census. That is yours.
12a9afac(#1743)netengine-8000-f8NetEngine 8000 F8 (4x 8x100GE, 4x 72x10GE)100GE1/0/0…100GE8/3/1)100GE1/0/0…10GE8/0/71)NE8000 F8,NetEngine 8000E F8CR8PBKPF8DC0,LPUC-800-CMresearch/huawei-netengine-8000-f8-boards.md(77 lines),docs/CONNECTORS.md, README,docs/wiki/Home.md,scripts/build-wiki.jsBoth cite the same document family (datasheet
V800R026C00); the difference is which sentence is the model of record — #1743 took the maximum interface configuration (every slot with a 100GE PIC), this PR took the 6.4T bundle board mix (CR8DE8NB00F0x4 +CR8DERXFMSF0x4). Neither is invented; they are two populations of one chassis.Decision needed
netengine-8000-m1d.jsonvs-m1d-b.json,ar8140-12g10xgvs-12g10xg-variant,f1avsf1a-c), so this PR could land as e.g.netengine-8000-f8-6.4t.json. I would need you to name the suffix rule; inventing it is how the alias tests start failing.12a9afacand this is the same request twice.Secondary, for whoever wins:
LPUC-800-CMis a line-card part number, not a device alias; on main it lives innotes. Alias lists are asserted unique across the catalogue, so shipping it as an alias is a trap for the next device that uses that PIC.Verified: both JSONs parsed; port counts summed from
interfaces[](64 vs 320);git merge-base --is-ancestor 12a9afac origin/main→ true;GET /pulls/1758/files→ 7 files,devices/huawei/netengine-8000-f8.jsonadded at +3260. I have not pushed to or rebased this branch.— surgery watchdog
Follow-up from the surgery watchdog — the conflict is narrower than "two F8s", and here is the exact shape of it.
I diffed the two versions of
devices/huawei/netengine-8000-f8.jsonas they exist today:59769c3f, 16,970 Bf991e67a, 60,366 Bnetengine-8000-f8NetEngine 8000 F8 (4x 8x100GE, 4x 72x10GE)So this is not a duplicated chassis, it is a collision on
model/ slug: both versions are the same physical 13U box with the same 28.86 Tbit/s fabric, and each encodes one legitimate line-card mix. Only one can ownnetengine-8000-f8.The decision I cannot make for you is a catalogue rule, not a merge:
netengine-8000-f8and land this as e.g.netengine-8000-f8-6.4t-bundle. Both survive, main stays green, but it sets a precedent that per-order line-card mixes each get their own slug — which then applies to every modular chassis we carry, not just this one.interfacesto cover both slot mixes. Cheapest for the registry, but the entry then describes a box that does not ship as configured, andinterfacesis what the reachability/socket counts are derived from.Verified before posting: head
62fe3528is green on all eight checks; the PR is 15 commits behind main and the only conflicting path is this one JSON file (add/add) — regenerated docs and the registry surfaces are not in conflict.Closing as superseded — main already answers #789, and this entry can only land by replacing the one that is already there.
Verified this run on
64fb915d:[Device]: NetEngine 8000 F8wentclosedat 2026-11-17T00:54:11Z, fixed by #1743 /12a9afac(huawei: NetEngine 8000 F8, 64x 100GE from the vendor's own maximum configuration). That commit createddevices/huawei/netengine-8000-f8.jsonon main.git merge-treeagainst64fb915dgives three stages fordevices/huawei/netengine-8000-f8.json— main59769c3f(16,970 B) vs this branchf991e67a— plus regenerated-doc conflicts inREADME.md,docs/CONNECTORS.md,docs/DEVICE_REGISTRY.md,docs/wiki/Home.mdand one line inscripts/build-wiki.js. Only one commit on main has ever touched that device file, so there is nothing to rebase onto: the two entries are competing descriptions of one 13U chassis.netengine-8000-f8, matching the file path). This branch models a mixed 6.4T bundle (4× 8×100GE + 4× 72×10GE, 32 QSFP28 + 288 SFP+), withmodelset toNetEngine 8000 F8 (4x 8x100GE, 4x 72x10GE)— a display label in a field that is a slug everywhere else in the registry. Landing both would give the catalogue two spellings and two port counts for one box, which is exactly the failure #60 was raised about.62fe3528(Test18/20/22, server smoke, docker build, rebase, auto-merge) — the branch itself is sound. Nothing is being thrown away: the commit is still reachable atrefs/pull/1758/head.If the bundle build is worth having, it needs its own identity — e.g.
devices/huawei/netengine-8000-f8-6t4.jsonwithmodel: "netengine-8000-f8-6t4"and alabelcarrying the 4×100GE + 4×72×10GE description — and that is a catalogue-shape decision for Jay, not something I will bake in. Reopen or re-cut against that path and it will merge cleanly.Closed by the surgery watchdog (cron) under the superseded-PR rule: branch's issue already fixed on main, cite the commit, close.
Pull request closed