Optical Module PN/BOM RFQ Checklist
Normalize exact part numbers, quantities, platform context, substitution policy and delivery requirements.
Technical Center
Selection guidance for 400G / 800G / 1.6T optical interconnect, AOC / DAC, Ethernet and InfiniBand projects.
Form Factor · Optical Architecture · Fabric · Fiber · RFQ Inputs
OSFP vs QSFP-DDMechanical and platform context
DR4 / DR8 / FR4Fiber and reach architecture
Ethernet / InfiniBandFabric-specific link context
RFQ ReadinessInputs required before selection
Guide 01 / Form Factor
OSFP vs QSFP-DD: confirm the host cage first
OSFP and QSFP-DD are different physical form factors. They are not mechanically interchangeable. The first selection step is to confirm the exact switch, NIC / DPU or server port before choosing an 800G-class module.
01Identify platformSwitch / NIC / DPU model
02Confirm cageOSFP or QSFP-DD
03Confirm port modeNative or breakout
04Then select opticsArchitecture + reach
Guide 02 / Optical Architecture
DR4, DR8 and FR4 change the physical link
Parallel optics and wavelength-multiplexed optics use different fiber and connector paths. The correct choice depends on rate, reach, fiber plant, breakout requirement and host support—not on bandwidth alone.
DR4Parallel SMFCommon 400G short-reach path
DR8Parallel SMFCommon 800G short-reach architecture
FR4Duplex SMFWDM path for longer reach
CHECKConnector / topologyMPO or duplex implementation
Guide 03 / Network Fabric
Ethernet and InfiniBand require platform context
The optical module or cable sits inside a larger fabric. Confirm the exact switch, adapter / DPU, port mechanics, protocol, lane mode and platform validation requirements before production deployment.
ETHERNETAI scale-out fabricNIC → leaf → spine
INFINIBANDAI / HPC fabricHCA / DPU → IB switch
COMMONForm factor mattersOSFP / QSFP-DD / cable shell
VALIDATEFull linkPort + media + firmware context
Guide 04 / Fiber & Connector
MPO vs LC is an architecture decision
Connector choice follows the optical architecture and fiber plant. Parallel optics commonly use MPO implementations, while duplex wavelength-multiplexed links commonly use LC-class paths. Exact connector details remain PN and platform dependent.
01Confirm fiber typeSMF / MMF / integrated cable
02Confirm connectorMPO / LC / project specific
03Confirm polarityEspecially for parallel optics
04Confirm loss budgetReach + patch path
Guide 05 / RFQ Readiness
What to send before an 800G RFQ
If an exact manufacturer PN is available, send it. If not, send the platform, port form factor, protocol, target rate, reach, connector / fiber, quantity and required date. This is enough to structure the next technical and commercial step.
PLATFORMSwitch / NIC / DPUExact model preferred
LINKRate + reachNative or breakout
MEDIAFiber + connectorIf already known
COMMERCIALQty + required dateSample or volume
Guide 06 / 1.6T Deployment & Selection
How to select 1.6T optics for current AI data-center deployments
1.6T selection should start from the actual platform and deployment requirement. Form factor, electrical lane mapping, optical architecture, connector, thermal envelope, firmware / FEC, interoperability, quantity and delivery timing should be matched to the project.
Deployment principle: Exact PN, compatibility, quantity and lead time are confirmed per project.
Procurement & Validation Guides
Turn technical uncertainty into RFQ-ready inputs
Use these guides before procurement or sample validation to reduce ambiguity and keep platform-specific assumptions visible.
800G OSFP vs QSFP-DD
Choose from the actual host cage, port mode and optical architecture—not from the 800G rate alone.
800G Optical Module RFQ Checklist
Platform, port, topology, reach, fiber, connector, quantity and delivery inputs for a cleaner 800G RFQ.
FEC, Firmware & Interoperability Checklist
Validate host platform, port mode, firmware, FEC context, optics and cabling before volume ordering.
800G DR8 vs 2×FR4
Compare parallel DR8 and dual-FR4 paths by reach, fiber plant, connector architecture, breakout and platform support.
AI Cluster Optical Interconnect Validation Checklist
Freeze platform, port mode, exact optic, fiber, firmware/FEC, diagnostics and test evidence before scale.
Media & Fiber Guides
Choose the physical link from architecture, reach and operations
These guides connect optical architecture to cable medium, connector choice and the installed fiber plant.
400G DR4 vs FR4
Compare parallel SMF and duplex WDM paths by reach, connector, fiber count, breakout and platform support.
AOC vs DAC
Choose integrated optical or passive copper by exact endpoints, route length, power, airflow and service model.
MPO vs LC
Map parallel DR and duplex FR architectures to fiber count, polarity, patching and migration requirements.
Architecture & Platform Guides
Move from generic optics to platform-aware network design
These guides connect optical selection to the actual AI Ethernet architecture and platform evidence.
Server → Leaf → Spine Optical Interconnect
Structure the BOM by link role, endpoints, port mode, reach, media and validation requirement.
Spectrum-X Optical Interconnect Selection
Use NVIDIA official platform documentation and validated solution-stack evidence before proposing an optic.
ConnectX Optics & Cable Compatibility
Plan from the exact adapter model, port implementation, protocol, peer switch and NVIDIA validated interconnect evidence.
NDR: Optics vs AOC vs DAC
Choose the media path by exact endpoints, reach, topology and current NVIDIA LinkX support—not by distance alone.
1.6T Selection & RFQ Guide
Structure current 1.6T requirements by host platform, lane rate, topology, optical path, validation and delivery inputs.
400G → 800G → 1.6T Fabric Migration
Plan a staged upgrade around endpoint generations, breakout, fiber reuse, validation and rollback boundaries.
400G Router Compatibility Review
A 400G label alone cannot qualify a transceiver
For Juniper PTX10001-36MR and other high-speed routers, start with the real host port, network operating system and physical link before choosing an exact optic.
| Check | What the buyer should confirm | Engineering outcome |
|---|---|---|
| Host port and software | Exact router SKU, PIC and port number, Junos OS Evolved release, line-card and current optics policy | PTX10001-36MR has QSFP56-DD-class 400GbE network ports; exact third-party PN still requires validation |
| End-to-end optical path | Peer-end host and optical interface, SMF or MMF, LC or MPO, actual reach and full channel loss | FR4, DR4, LR4 and VR4 are different optical families and cannot be substituted by speed alone |
| Module and qualification | Exact manufacturer PN and revision, FEC, CMIS, firmware coding, power and thermal budget | Request controlled datasheet and OEM compatibility evidence or a target-device sample test |
| Commercial RFQ | Quantity, sample plan, delivery destination, desired date and acceptance criteria | Only a confirmed specification and written supplier terms can support a formal quotation |
Manufacturer information is a technical reference, not proof of tested compatibility on the buyer's host. Juniper also documents thermal restrictions for certain adjacent QDD-400G-FR4/LR8 placements. Confirm the exact port layout and environmental conditions before deployment.
Juniper PTX10001-36MR port documentation · Juniper optics planning guidance
Deployment readiness checklist
Six facts that help avoid costly link surprises
Send what you know; unknown facts can be marked for engineering review. This is a preparation guide, not an automatic compatibility certification.
Host and endpoint
Record the exact switch or NIC/DPU model, port/cage, peer-end model and software release. A form factor alone is not a compatibility approval.
Rate, protocol and breakout
Confirm Ethernet or InfiniBand, native link speed, electrical lane mode, breakout mapping and whether both endpoints support the intended mode.
Fiber and connectors
Check SMF versus MMF, cable length, LC or MPO/MTP pinout, polarity, patch-panel insertion loss and any existing cabling constraints.
Optical budget and reach
Compare transmit/receive levels and required optical budget with total expected channel loss; include margins and the actual environment.
FEC, management and firmware
Check port FEC mode, CMIS or other management interface, module coding requirements, network OS/firmware policy and diagnostic support.
Power, airflow and validation
Confirm cage thermal envelope, max module power, airflow, link-up/BER tests, DOM telemetry, acceptance criteria and approved sample plan.
Technical FAQ
Questions that should be answered before deployment
Can an OSFP module be inserted into a QSFP-DD port?
No. OSFP and QSFP-DD are different mechanical form factors. Confirm the host cage before selecting the module.
Is 800G enough information to choose the optic?
No. You still need the host platform, form factor, optical architecture, reach, connector / fiber, topology and compatibility context.
When should AOC or DAC be considered?
For short-reach links where an integrated cable assembly is appropriate. Endpoint form factor, rate, length, bend/routing and platform support still need confirmation.
Can QIANWU confirm compatibility without the target platform?
Not responsibly. Compatibility should be tied to the exact switch, NIC / DPU, firmware context and deployment requirement.
Do identical link speeds guarantee interoperability?
No. Host-port type, lane mode, FEC, optical architecture, connector, firmware and approved validation evidence still have to match across both link endpoints.
Which software and hardware versions should be supplied?
Provide both host part numbers, port identifiers, network operating system release, adapter firmware and any known OEM optic policy. Do not assume compatibility across revisions.
What do we need for native 800G versus 2×400G breakout?
Confirm the physical port mode and electrical lane allocation at both endpoints, supported FEC, optical PMD and correct breakout cable or transceiver design.
When do we use single-mode instead of multimode fiber?
Choose the fiber type from the actual PMD specification and deployed cable plant. SMF/MMF, connector type and nominal reach are not interchangeable by default.
How should link loss and optical power budget be assessed?
Include fiber attenuation, connector and splice losses, patch panels, relevant margins and the precise module transmit/receive specification; do not choose by nominal distance alone.
Does the connector label confirm MPO polarity?
No. Confirm the exact MPO/MTP fiber count, gender, keying, polarity, optical lane mapping and patching on both ends before installation.
Which FEC and CMIS values matter?
Confirm the host's supported FEC mode and module management standard/revision using current platform documentation and device diagnostics. Unknown combinations need engineering review.
How is temperature and module power validated?
Check the module power class, host power budget, cage/heat-sink arrangement, airflow direction, inlet temperature and environmental limits for the exact module revision.
How do we verify a module before mass deployment?
Use approved samples in the target device with the intended OS/firmware. Record link-up, negotiated rate, error counters/BER, optical diagnostics and test duration.
Can an optics type be declared NVIDIA or Juniper compatible without tests?
Not from the speed or label alone. Compatibility claims need an exact host/port/firmware context and approved manufacturer documentation or reproducible test evidence.
What if the customer only has an OEM part number or a BOM?
Submit the original PN/BOM and quantities. We can clarify the target host, physical link, alternatives and the facts required for a valid technical and commercial quote.
Is 1.6T a supply option today?
QIANWU can review 1.6T project requirements today. Exact form factor, lane mode, manufacturer PN, quantity, sample schedule and lead time require a project-specific confirmation.
Need selection help for an active project?
Send the platform, PN/BOM, quantity and required date.