research(e6616x): a deployed subrack names its boards - TM65 is the chassis prefix, not the board one #1995

Merged
jaylouisw merged 1 commit from catalogue/1118-1456 into main 2026-11-18 15:09:25 +00:00
Owner

Refs #803 - does not close it.

A deployment record names the X's boards, and corrects the prefix the thread has been chasing.

Ningbo Rail Transit Line 4 maintenance tender (appendix 4, bill of maintained equipment) - 135 pp, 736,057 B, 91,554 characters of text layer, read end to end:

item label model qty
32 总装机箱 (OptiXtrans E6616X) TM65K32AFB 1
33 通用交叉及主控时钟处理板 65UXCL 1
34 2M 处理板 B2PD1 1
35 2M 业务板 B2DMS 1
36 32xE1/T1 电接口倒换出线板 (75Ω) SSN1D75S 1

Fleet line: 延伸段传输系统设备(E6616X)2 套 车站通信设备室.

What it settles. TM65* is the chassis and cross-connect prefix (TM65K31AFB/TM65K32AFB, TM65UXCL), not the service-board namespace - the inference two passes drew from the R026 brochure's single TM65UXCL part number. The X's 2M pair is the B2 generation, i.e. the assembly the price list calls TMB2TPS (1DMS+2PD1, 32xE1/T1). The X is deployed as a 2M/PDH aggregation node, which is what #803 asks for.

What it does not settle, and this is the whole blocker now. Every row is qty 1 - a spares list, not a built subrack - so four cards cannot become fourteen slots; and B2DMS's own port count and slot cost (the TPS assembly is three boards) are unstated.

Unblock, narrower: the per-slot complement of one real subrack, or a Huawei board chapter whose Valid Slots table names E6616X - candidates now TMB2PD1 / TMB2DMS / TMB2TPS, plus the GDC / EX10 / EG10 Ethernet set the same document maintains (TMK1* by inference, flagged).

Evidence: research/optixtrans-e6616x-deployment-board-inventory.md. Tanatel price catalogue would have corroborated the codes but still refuses TCP 443 from this host. Gates: syntax-check 417 files OK; audit-port-types clean; hardware-invariants 26/26; catalogue-hygiene 25/25; closed-issues-audit 36/36; close-merged-issues 81/81.

Refs #803 - does not close it. **A deployment record names the X's boards, and corrects the prefix the thread has been chasing.** Ningbo Rail Transit Line 4 maintenance tender (appendix 4, bill of maintained equipment) - 135 pp, 736,057 B, 91,554 characters of text layer, read end to end: | item | label | model | qty | |--|--|--|--| | 32 | 总装机箱 (OptiXtrans E6616X) | **TM65K32AFB** | 1 | | 33 | 通用交叉及主控时钟处理板 | **65UXCL** | 1 | | 34 | 2M 处理板 | **B2PD1** | 1 | | 35 | 2M 业务板 | **B2DMS** | 1 | | 36 | 32xE1/T1 电接口倒换出线板 (75Ω) | SSN1D75S | 1 | Fleet line: `延伸段传输系统设备(E6616X)2 套 车站通信设备室`. **What it settles.** `TM65*` is the chassis and cross-connect prefix (`TM65K31AFB`/`TM65K32AFB`, `TM65UXCL`), not the service-board namespace - the inference two passes drew from the R026 brochure's single `TM65UXCL` part number. The X's 2M pair is the `B2` generation, i.e. the assembly the price list calls `TMB2TPS` (1*DMS+2*PD1, 32xE1/T1). The X is deployed as a 2M/PDH aggregation node, which is what #803 asks for. **What it does not settle, and this is the whole blocker now.** Every row is qty 1 - a spares list, not a built subrack - so four cards cannot become fourteen slots; and `B2DMS`'s own port count and slot cost (the TPS assembly is three boards) are unstated. **Unblock, narrower:** the per-slot complement of one real subrack, or a Huawei board chapter whose Valid Slots table names E6616X - candidates now TMB2PD1 / TMB2DMS / TMB2TPS, plus the GDC / EX10 / EG10 Ethernet set the same document maintains (TMK1* by inference, flagged). Evidence: `research/optixtrans-e6616x-deployment-board-inventory.md`. Tanatel price catalogue would have corroborated the codes but still refuses TCP 443 from this host. Gates: syntax-check 417 files OK; audit-port-types clean; hardware-invariants 26/26; catalogue-hygiene 25/25; closed-issues-audit 36/36; close-merged-issues 81/81.
research(e6616x): a deployed subrack names its boards, and TM65 is the chassis prefix not the board one
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 3s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 23s
404d4359bf
A Ningbo Rail Transit Line 4 maintenance tender (135 pp, 91,554-char text layer) lists two OptiXtrans E6616X in station equipment rooms: chassis TM65K32AFB, 65UXCL, B2PD1, B2DMS. Every previous pass inferred the X's service boards were TM65* from the brochure's single TM65UXCL part number; that is a cross-connect code. The 2M pair is B2 (TMB2TPS = 1*DMS+2*PD1). Per-slot complement still unpublished; #803 stays open.
jaylouisw deleted branch catalogue/1118-1456 2026-11-18 15:09:26 +00:00
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!1995
No description provided.