Five decisions to retain:
- A supported cross-generation system path does not automatically approve the installed cable.
- Generation, aggregate rate, and host form factor do not define the complete optical interface.
- A shared
MPO/APClabel does not prove that the active positions, map, route, reach, and junctions match. - Historical inspection, OTDR, or insertion-loss records describe the installed path; they do not qualify a different target application by themselves.
- Compare price and delivery only after suppliers receive the same technically approved transition scope.
Use the detailed sections as an InfiniBand cable reuse guide for two bounded decisions: HDR-to-NDR transition paths and NDR to XDR cabling. The vendor-supported product list, full channel map, and project acceptance plan remain separate records.
Technical disclaimer: These examples are for reference only and are not a compatibility guarantee. Each example applies only to the cited part and configuration. Recheck the current documents for both endpoints before ordering or reusing an interconnect.
Planning an upgrade? Record the current endpoints, target endpoints, port modes, and exact interconnect or optic part numbers before preparing a transition review request.
Can an HDR cable be reused for NDR or XDR?
Not from the generation names alone. Separate three decisions that are often collapsed into one:
| Decision | Question | Evidence that closes it | What a "yes" does not prove |
|---|---|---|---|
| Protocol or system interoperability | Can the current and target devices operate in a supported cross-generation mode? | Current vendor system and supported-configuration documentation | That the old cable, transceiver, or passive fiber remains usable |
| Active interconnect support | Is an exact DAC, ACC, AOC, or transceiver pair qualified for the two endpoints and selected port mode? | Exact cable/module part number in a current supported-products source | That a neighboring SKU, different length, or third-party assembly is approved |
| Passive optical-path compatibility | Do the two selected optics accept the installed connector, polish, fiber, active positions, lane map, reach, and connector-junction architecture? | Both optic specifications plus the controlled route and project budget | That every path described only as "MPO" or "OS2" is interchangeable |
All applicable rows must describe the same supported path. A supported endpoint pairing may still need a new transition cable, and a usable pathway may still terminate in the wrong optical interface.
Treat an InfiniBand cable backward compatibility claim as incomplete unless it names the endpoint pair, port mode, and interconnect part.
How should you evaluate HDR vs NDR cable reuse?
- Confirm that the two exact endpoints and selected port modes form a currently supported cross-generation system path.
- Match the exact DAC, ACC, AOC, or transceiver pair to both endpoints and the selected mode.
- If any passive fiber remains, compare connector, polish, fiber, active positions, mapping, route, reach, and junction assumptions.
- Record the result as
reuse candidate,replace, orunresolved. A reuse candidate still needs the target application budget and technical approval.
BWNFiber's data-center connectivity portfolio provides the broader commercial context. A portfolio page is not compatibility evidence.
Why the generation name does not define the interface
Official examples show that generation, aggregate rate, host form factor, and optical interface are different fields.
| Documented example | Lane and host context | Optical interface in that example | Upgrade implication |
|---|---|---|---|
| HDR SR4: NVIDIA MMA1T00-HS | HDR 200 Gb/s, four optical channels, QSFP56 | Parallel multimode over OM3 or OM4, MPO-12/UPC; the documented mating patch is unpinned and crossed | This is a valid part-specific HDR MPO path, not an all-HDR rule. MMA1T00-HS specification |
| HDR FR4: NVIDIA MMS1W50-HM | HDR 200 Gb/s, QSFP56 | Single-mode, duplex LC/UPC | HDR optical connectivity can be LC rather than MPO. MMS1W50-HM specification |
| NDR / NDR200 architecture | Full NDR is four lanes at the NDR lane rate; NDR200 uses two. NVIDIA documents twin-port OSFP at Quantum-2 switches and single-port OSFP or QSFP112 at supported endpoints | Documented NDR passive optical families include single-mode and multimode MPO/APC options | Record the logical port, endpoint form factor, module pair, fiber type, and supported split. NDR overview |
| XDR DR4: NVIDIA MMS4A20 | XDR 800 Gb/s, four 200G-PAM4 optical lanes, single-port OSFP | Single-mode MPO-12/APC with four transmit and four receive fibers active | An XDR 800G label does not establish MPO-16 or eight optical lanes. MMS4A20 overview |
The InfiniBand Trade Association XDR announcement describes XDR at 200 Gb/s per lane, with 800 Gb/s endpoint ports and higher aggregate switch-to-switch capacity. Current NVIDIA validated-configuration material lists Quantum-X800 and ConnectX-8 XDR systems, so XDR should not be treated merely as a future placeholder. The exact interconnect still comes from the named device and product documentation.
The 200G label also hides a critical difference. Full HDR 200G uses four lanes at 50 Gb/s, while NDR200 uses two lanes at 100 Gb/s. An NDR200 vs HDR200 cabling review cannot stop at aggregate rate; it must verify the cage, cable construction, port mode, and endpoint support.
Check four compatibility layers before you compare cables
Create one current-to-target comparison for every link class affected by the migration.
| Compatibility layer | Current-state record | Target-state record | Hold condition |
|---|---|---|---|
| Endpoint and port mode | Device part number, cage/port, enabled rate and split | Target device part number, cage/port, enabled rate and split | Either endpoint or logical port mode is inferred from a family name |
| Qualified active interconnect | Installed DAC/ACC/AOC or transceiver part numbers and support source | Exact transition cable or transceiver pair and current support source | Only form-factor or speed labels are available |
| Optical interface | Connector, polish, pin state, fiber, active positions, and lane map at both current ends | The same fields for both target optics | MPO, OSFP, QSFP56, or QSFP112 is being used as a complete interface definition |
| Passive path | Every retained adapter, panel, cassette, trunk, transition, and known baseline | Target reach, junction, loss, and mapping assumptions | A retained component has no controlled part/drawing or target-application evidence |
This table is an upgrade delta, not a replacement for the full lane map. When a passive MPO channel is a reuse candidate, move the detailed component and position trace to the full MPO channel-map and polarity workflow.
If one of the four layers is still open, send the missing field and its owner with the review request. A generic cable quote cannot close an endpoint, port-mode, or passive-route uncertainty.
HDR to NDR: backward compatibility does not mean passive-fiber reuse
For an HDR to NDR cable compatibility review, start with the exact documented transition path. NVIDIA documents backward-compatible NDR connections to previous HDR and EDR equipment using specific transition cable families. In the cited design guide, the NDR switch end uses an OSFP twin connection and the older-generation legs use the appropriate QSFP variant. The guide describes DAC options up to 2 m and AOC options up to 30 m for those documented configurations. These are source-specific supported paths, not universal distance thresholds. See NDR connections to HDR and EDR.
The same source says there is no easy passive-fiber path for these cross-generation connections because previous InfiniBand optics and fiber cables do not support the NDR MPO/APC interface. This is the practical boundary in an MPO UPC vs APC InfiniBand migration check, not a rule that every product in either generation has the same interface.
A currently supported OSFP-to-QSFP transition assembly is conditional on the documented endpoints, port mode, cable part, length, and release. An HDR SR4 MPO-12/UPC path proposed for NDR MPO/APC optics is a replacement case. An HDR FR4 duplex-LC path remains unresolved until the target modules and retained path are documented. An NDR200 target also needs a new port and interconnect decision because NDR200 and HDR use different lane structures.
"NDR is backward compatible" describes a supported system configuration. It does not approve the installed HDR cable.
NDR to XDR: MPO/APC still does not prove reuse
NDR and a current XDR example can both expose MPO-12/APC, but that shared label is only one compatibility field. NVIDIA's NDR architecture uses a 100 Gb/s lane rate; the cited MMS4A20 XDR DR4 example uses four 200G-PAM4 optical lanes. The target modules, active positions, link mode, supported reach, and allowed connector-junction architecture must still be reconciled.
NVIDIA's current structured-cabling requirements for XDR/NDR illustrate single-mode and multimode architectures within specific transceiver and connector-junction assumptions. A retained passive route can become a reuse candidate only within those assumptions.
If the installed record says only MPO/APC, the decision is unresolved. A controlled drawing that confirms MPO-12/APC, fiber type, pinning, and the end-to-end map can move the path to reuse-candidate status when the target optics accept the same route and junctions. An undocumented cassette keeps the path unresolved. Treat a fixed NDR active cable as a replacement unless current support documentation names that exact part for the XDR endpoints.
If the route becomes a reuse candidate, complete the application-specific channel calculation in the MPO trunk and loss-budget design guide. A passing NDR baseline is useful evidence, but it does not substitute for the XDR application limit.
Use a migration decision matrix
Assign a preliminary status before the quote is released:
| Current path | Target path | Initial decision | Evidence needed to close it |
|---|---|---|---|
| HDR SR4 MPO/UPC | NDR passive MPO/APC | Replace | Select the exact target optics and new passive path supported for them |
| HDR endpoint retained behind a new NDR switch | Vendor-documented OSFP-to-QSFP transition cable | Supported conditionally | Exact endpoints, port split, transition part, length, firmware/support source |
| HDR FR4 duplex-LC passive path | NDR or XDR LC-based target optics | Reuse candidate or unresolved | Both target module specifications plus fiber, route, junction, wavelength/reach, and budget evidence |
| NDR MPO/APC structured path | XDR MPO/APC optics | Reuse candidate or unresolved | Exact target modules, active positions, pinning, mapping, fiber, junction count, reach, and budget |
| NDR fixed active cable | XDR endpoints | Replace unless explicitly requalified | Current supported-products evidence naming the same exact cable and target endpoints |
| Any installed path with unknown connector polish or internal cassette map | Any new generation | Unresolved | Inspection alone is insufficient; obtain the controlled product/drawing and target source |
Reuse candidate authorizes the next engineering check. It does not authorize purchase or installation. Unresolved keeps an unsupported assumption out of the purchase order.
Create an upgrade delta record
Do not copy the full old BOM and change only the speed column. Create a delta record for each link class that changes or is proposed for reuse.
| Field | Current evidence | Target evidence | Decision entry |
|---|---|---|---|
| Endpoint A and B | Installed device/port part numbers and enabled mode | New device/port part numbers and intended mode | Match, mismatch, or missing |
| Active interconnect | Installed cable or module pair and support record | Target qualified cable or module pair | Retain, replace, or unresolved |
| Physical interfaces | Host form, optical connector, polish, pin state | Target fields from exact product documents | List every changed field |
| Optical path | Fiber, active positions, lane map, retained components | Target interface and supported route assumptions | Reuse candidate, replace, or unresolved |
| Application limits | Existing approved design and baseline records | Target reach, junction, loss, and test requirements | Name the owner who must close the comparison |
| Source control | Document title, URL/revision, review date | Current target source and supported-products record | Record expiry/recheck trigger |
Historical test results can establish the state of the installed plant; they cannot prove a different target application by themselves. Use each record for its defined purpose. IEC 61300-3-35 covers visual inspection of fiber-optic connector and transceiver end faces and states that inspection does not replace attenuation or return-loss measurement. IEC 61280-4-5 covers attenuation measurement and polarity and length determination for installed MPO-terminated multimode and single-mode cabling. An inspection result, OTDR record, or passing insertion-loss record does not qualify a retained path for a new HDR, NDR, or XDR application by itself. Set the acceptance limits and methods from the exact target module, system, and project documents. Keep the detailed procedure in the fiber-cabling test workflow rather than duplicating it here.
Illustrative review scenario, not a customer case: An inventory calls the retained path only MPO, while the target schedule calls the new port only NDR. The result is unresolved, not reuse candidate. The reviewer first identifies the current HDR optic, the target endpoint and port mode, and the documented transition assembly or target optic. The hold applies to that link class until connector polish, fiber, active-position map, and route evidence are complete; it does not turn the scenario into proof of a BWNFiber deployment.
What should procurement require in the supplier response?
Do not accept a line item described only as "NDR-compatible MPO cable." Ask the supplier to return the proposed cable or transceiver part number, the endpoint and port mode it supports, and the source revision used for that decision. The response should also identify every retained component that depends on customer-supplied records.
Put exceptions in writing. If the supplier cannot confirm a target module, port split, connector polish, lane map, or route assumption, keep that field unresolved and assign an owner before the purchase order is released.
Resolve source conflicts before approving cable reuse
When two sources appear to disagree, use the most specific current source that governs the exact endpoint pair, enabled port mode, and interconnect part. Do not combine a length from one SKU, a connector from another, and a support statement from an older release into a configuration that no source actually approves.
| Decision field | Controlling evidence | Approval owner | Keep unresolved when |
|---|---|---|---|
| Endpoint and port mode | Current system or support document naming both exact devices and the enabled mode | Network architect and equipment vendor | A device, port split, or operating mode is absent, inferred, or contradicted |
| Active interconnect | Exact cable or module part number in the current supported-products source plus its product specification | Project technical authority and equipment vendor | Only a family name, form factor, or neighboring SKU is available |
| Passive optical path | Both exact optic specifications plus controlled component records and the end-to-end route | Optical design owner | Connector, polish, fiber, active positions, map, junction, or retained component is unknown |
| Acceptance evidence | Target-application limit and the approved measurement method | Named technical reviewer and project authority | Only a historical pass, generic web threshold, or unrelated application limit is available |
| Purchase-order release | Resolved fields, source title or revision, named owner, and written exceptions | Procurement and technical approver | Supplier shorthand replaces an unresolved technical field |
Reopen a completed review when an endpoint or port mode changes, the exact interconnect part or length changes, a retained passive component or route changes, or the governing support source is revised. A previously approved decision is not transferable to a materially different configuration.
Move from technical approval to a comparable supplier offer
Compare price and delivery only after every supplier receives the same cross-generation path definition. If one proposal assumes a new active cable while another assumes reuse of an undocumented passive route, the offers are not commercially comparable.
For an international order, add the destination country, site authority or owner specification, adopted standard and edition, indoor pathway and fire/smoke/material requirement, document language, labels, packing and import documents, ship-to point, and requested delivery basis. Country alone does not select the cable or prove a compliance requirement. If any retained route leaves the controlled data-center space or enters an outdoor or access-network path, split it into a separate design owned by the appropriate outside-plant or access-network engineer; this article does not approve ADSS, drop, duct, direct-burial, jacket, flame, UV, water-blocking, temperature, or rodent-resistance performance.
| Commercial handoff | Buyer provides | Supplier response must identify | Hold before moving forward when |
|---|---|---|---|
| Release the transition scope | Link-class ID, exact current and target endpoints, port modes, and reuse candidate / replace / unresolved status | Exact proposed interconnect or optic pair and every dependency on the retained path | The proposal changes an endpoint, mode, or reuse assumption without a new technical review |
| Normalize the quotation | Quantity by exact part and length, destination, requested delivery basis, target date, packaging or labeling scope, and quotation-validity requirement | Unit and total price basis, quoted lead-time basis, delivery assumptions, validity, and exclusions | Price or lead time is based on a different technical or logistics scope |
| Request controlled documents | Current product datasheet, configuration drawing, supported-path reference, and list of stated exceptions | Document title or number, revision, applicability, and any customer-supplied dependency | A catalog image or product-family page is offered as the exact item record |
| Define any sample or test review | Sample purpose, exact sample part and revision, physical checks, measurement scope, acceptance criteria, and approver | What the sample can validate, applicable report format, and whether production must match the approved sample | The sample has no controlled identity or is expected to prove vendor interoperability by itself |
| Release the order or project action | Approved drawing and document list, quotation revision, written deviations, required labels/packaging, test deliverables, and change owner | Order acknowledgement or action list preserving those references | A substitution, design change, or revised support source has not reopened the affected decision |
A sample may help approve construction, labeling, fit, or a defined measurement record for the exact proposed item. It cannot convert an unsupported endpoint pairing into a vendor-qualified configuration. Availability, sample terms, MOQ, price, and lead time must be confirmed for the exact item in the written quotation; this article supplies none of those values.
BWNFiber describes its project workflow as project input, engineering review, sample and quotation, followed by production and test for approved items. For this transition, ask BWNFiber to organize the submitted passive-cabling requirement, identify evidence gaps, and state which exact drawing, datasheet, test-record format, sample step, and commercial terms are available for the proposed item. If OEM/ODM labeling, packaging, or another project-specific change is requested, keep it in the same controlled drawing and quotation revision. See how BWNFiber handles project inputs and evidence. The equipment vendor and project authority still own interoperability and final technical approval.
Common cross-generation cabling mistakes
| Shortcut | Why it fails | Correct decision record |
|---|---|---|
| "The protocol is backward compatible." | Says nothing about whether the old active cable or passive interface is supported | Name the exact supported cross-generation path |
| "Both links are 200G." | HDR 200G and NDR200 use different lane structures | Record the port mode, lane structure, and exact interconnect |
| "Both ends are OSFP." | OSFP is the host form factor, not the complete optical interface or support decision | Record cable/module part numbers and optical interfaces |
| "Both paths use MPO/APC." | Connector family and polish do not establish active positions, mapping, fiber, reach, or junction support | Compare the exact target modules and retained route |
| "The installed trunk is OS2 and low-loss." | Fiber category and a grade label do not prove target optical-interface compatibility | Close connector, polish, map, route, and target budget evidence |
| "XDR is 800G, so it needs MPO-16." | A current XDR DR4 example uses four optical lanes and MPO-12/APC | Use the exact XDR transceiver specification |
| "A nearby SKU uses the same shell." | Neighboring products can differ in port role, firmware support, pinning, fiber, or reach | Cite the exact SKU and current support source |
HDR, NDR and XDR cabling FAQ
Are HDR and NDR InfiniBand cables backward compatible?
There is no universal yes. NVIDIA documents specific NDR-to-HDR/EDR transition DAC and AOC assemblies, while also stating that previous HDR/EDR MPO/UPC fiber is not the passive NDR MPO/APC path. Check the exact endpoints and supported cable part.
Can an NDR switch connect to an HDR adapter?
Yes, in documented configurations using the appropriate OSFP-twin-to-QSFP transition assembly. Endpoint type, port split, cable variant, length, and current support restrictions still apply.
Is NDR200 the same as HDR 200G?
No. NDR200 uses two lanes at the NDR lane rate, while full HDR 200G uses four 50 Gb/s lanes. Equal aggregate rate does not make their ports or cables interchangeable.
Can an HDR MPO fiber plant be reused for NDR?
Do not assume so. The documented NVIDIA HDR SR4 example uses MPO-12/UPC, while NDR passive optical families use MPO/APC and are described as non-interoperable with previous InfiniBand MPO/UPC fiber. Inventory every retained component against the target optics.
Does XDR InfiniBand require MPO-16?
No universal rule supports that conclusion. The current NVIDIA MMS4A20 XDR DR4 example uses one MPO-12/APC interface with four transmit and four receive fibers active.
Can an NDR MPO/APC trunk be reused for XDR?
It can become a reuse candidate only when the exact XDR modules, fiber, pinning, active positions, lane map, supported route, reach, and budget all accept the installed path. MPO/APC alone is not approval.
Does the same MPO shell mean two cables are compatible?
No. Shell appearance does not establish polish, pin state, keying, fiber type, active positions, mapping, application reach, or supported endpoint pairing.
What should be documented before an InfiniBand upgrade quote?
Provide the current and target endpoint part numbers, port modes, installed and proposed cable/transceiver parts, current support sources, retained passive-route records, and a list of paths proposed for reuse. Mark missing fields unresolved.
Does NDR use MPO/UPC or MPO/APC?
Do not assign one polish to every NDR product. The passive NDR optical families cited in this guide use MPO/APC, but the exact module specification controls. Confirm the module part number, mating interface, fiber type, and supported route before selecting a jumper or trunk.
Can an HDR FR4 duplex-LC path be reused for NDR or XDR?
It is only a reuse candidate when the exact target modules accept the installed fiber, connector and polish, wavelength/reach design, junction count, and budget. A shared duplex-LC label is not enough.
Does InfiniBand backward compatibility always require a splitter cable?
No. The required path depends on the exact switch port, endpoint, enabled mode, and documented interconnect. Some cross-generation configurations use a specific split transition assembly; that does not create a universal splitter rule.
When should an InfiniBand migration decision remain unresolved?
Keep it unresolved whenever an endpoint part number, port mode, active interconnect part, optical-interface field, retained component map, route limit, or current support source is missing. Do not convert missing evidence into a supplier default.
Request an HDR vs NDR cabling transition review
Send one current-to-target record for each affected link class. Include any NDR-to-XDR scope in the same record:
- current switch and adapter/HCA/DPU part numbers, ports, rates, and split modes;
- target switch and endpoint part numbers, ports, rates, and split modes;
- installed cable or transceiver part numbers and the current support source;
- proposed transition cable or target transceiver pair and its support source;
- retained panels, cassettes, trunks, adapters, fiber type, route, and known interface records;
- the paths you expect to reuse and every unresolved field.
If the request should proceed to a commercial offer after technical review, also provide quantity by exact part and length, destination, requested delivery basis and target date, required documents, labeling or packaging scope, and whether a controlled sample is needed. Availability, sample terms, MOQ, pricing, and lead time must be returned for the exact proposed item in writing.
BWNFiber can review the requested passive-cabling definition and identify specification or evidence gaps that still require the equipment vendor, project engineer, or product owner. This is not a vendor-qualification or interoperability guarantee. Request an HDR vs NDR cabling transition review.
