800G DAC

BWNFiber 800G OSFP112 to 2x 400G QSFP112 Passive DAC Cable

This assembly is most useful when the port map is fixed before the cable BOM is released. The BWNFiber 800G OSFP to 2x400G QSFP112 DAC, also specified as a 800G breakout DAC, is built for a OSFP112 uplink to 2x QSFP112 fan-out link for port consolidation, staged speed migration, and high-density server or accelerator attachment. It keeps the link passive and avoids an optical conversion stage. Standard and custom ordering options should be confirmed against the host port, requested length, and environmental requirements before the BOM is approved.

800G — Aggregate link OSFP112 to 2x QSFP112 — Endpoint mapping Up to 2 m listed — Datasheet guidance
Verified Specifications

800G OSFP112 to 2x 400G QSFP112 Passive DAC Cable Specifications

Link roleA OSFP112 uplink to 2x QSFP112 fan-out link for port consolidation, staged speed migration, and high-density server or accelerator attachment.
Endpoint form factorOSFP112 to 2x QSFP112; lane breakout must be enabled on the host port
Aggregate data rate800G
Lane / channel detailEight-lane electrical interface up to 112 Gbps
Length guidanceUp to 2 m listed
Power approachPassive cable assembly; no active optical engine
Standards / managementMeet SFF-8432 & OSFP MSA; Meet CMIS Rev 5.0; Meet IEEE 802.3cd & IEEE 802.3ck
Cable constructionVaries by length and assembly option; copper twinax assembly
Operating temperature0°C to 70°C (commercial)
Configuration statusStandard and custom options must be confirmed in the quotation and approved BOM

Search terminology for this configuration includes OSFP112 to QSFP112 DAC, 800G to 400G breakout copper, AI cluster breakout DAC. These phrases describe the same purchase task only when the endpoint form factor, breakout ratio and lane map, and ordered length match this page.

Standards context: IEEE 802 standards catalog · SNIA SFF technology affiliates · OSFP MSA specifications.

Selection

When to Use This 800G Passive DAC

  • Use it for fan-out links with OSFP112 to 2x QSFP112 endpoints when the routed path stays within up to 2 m listed.
  • Choose passive copper when low cable power and simple installation matter more than reach or cable diameter.
  • Confirm that the source port supports the required breakout mode and that each leg maps to the intended downstream port.
Choose an alternative when: Use an ACC when a copper route exceeds the practical passive budget but remains short. Use an AOC when the route needs more distance, a lighter cable body, or EMI immunity.
Deployment Control

Compatibility and Acceptance Checklist

  1. Confirm the connector at each end: OSFP112 to 2x QSFP112.
  2. Confirm the required aggregate rate and host lane mode: Eight-lane electrical interface up to 112 Gbps.
  3. Measure the routed path, not the straight-line rack distance; the current datasheet states up to 2 m listed.
  4. Send switch/NIC part numbers and firmware versions for coding review; no platform-specific compatibility is assumed without validation.
  5. Provide the lane-to-leg map, leg labels, and branch length before production approval.
  6. Enable and validate host breakout mode before acceptance testing each downstream leg independently.
  7. Specify commercial or industrial temperature requirements and the requested jacket/label/packaging details.
  8. At receipt, verify labels and part numbers, inspect latches and cable jackets, then test the complete link at the intended data rate.
BOM Planning

Ordering Options

Part NumberDescriptionLengthAWGJacketLength Tolerance
BWN-DAC-OSFP-2QSFP112-800G-0.5M800G OSFP to 2x400G QSFP112 Passive DAC0.5 m30PVC / LSZH+/-15 mm
BWN-DAC-OSFP-2QSFP112-800G-01M800G OSFP to 2x400G QSFP112 Passive DAC1 m30PVC / LSZH+/-25 mm
BWN-DAC-OSFP-2QSFP112-800G-1.5M800G OSFP to 2x400G QSFP112 Passive DAC1.5 m28PVC / LSZH+/-30 mm
BWN-DAC-OSFP-2QSFP112-800G-02M800G OSFP to 2x400G QSFP112 Passive DAC2 m28PVC / LSZH+/-45 mm
BWN-DAC-OSFP-2QSFP112-800G-xxM800G OSFP to 2x400G QSFP112 Passive DACCustomCustom
Buyer Questions

Common Procurement Objections

Will it work in my switch or NIC?

Form factor and standards alignment are necessary but not sufficient. Send the exact host model, firmware, port mode, length, and coding requirement for a compatibility review.

Which length should I order?

The current datasheet lists up to 2 m listed. Measure the routed path, include a controlled service loop, and avoid ordering unnecessary slack.

Should I use AOC instead?

Use an ACC when a copper route exceeds the practical passive budget but remains short. Use an AOC when the route needs more distance, a lighter cable body, or EMI immunity.

Can BWNFiber customize the assembly?

Datasheet ordering tables include standard and/or custom entries. Submit the endpoint, length, label, jacket, coding, temperature, packaging, and quantity requirements for feasibility confirmation.

Related Choices

Related High-Speed Cable Options

Engineering RFQ

Request a Configuration Review

Send endpoint models, firmware, port mode, length, quantity, temperature, labeling, packaging, and acceptance requirements. BWNFiber can return a proposed cable code and BOM for review.

Send Your Requirements

FAQ

800G OSFP112 to 2x 400G QSFP112 Passive DAC Cable FAQ

What is the BWNFiber 800G OSFP112 to 2x 400G QSFP112 Passive DAC Cable?

BWNFiber 800G OSFP to 2x400G QSFP112 Passive Direct Attach Copper Twinax Cable is designed for use in 800GBASE Ethernet. OSFP112 targets 112 Gb/s per lane in an 8-lane OSFP system, enabling the OSFP 800G interconnect ecosystem. The 400G QSFP112 passive cable assembly is based on a 4x100G or 4x112G structure and fully meets next-generation 400G switch, server and router application needs with excellent signal integrity. The page uses the supplied datasheet as the claim source; final host compatibility remains configuration-specific.

What link length is available for this DAC?

The current datasheet indicates up to 2 m listed. The usable length for a particular deployment still depends on the ordered part number, host electrical budget, route, and acceptance criteria.

Which interfaces does this cable connect?

This product is defined as OSFP112 to 2x QSFP112. Match the complete connector, lane mode, and endpoint role rather than relying on aggregate speed alone.

Does the host need breakout mode enabled?

Yes. The source port must support the specified fan-out mode, and each leg must be mapped and tested at its downstream rate.

How do I check OSFP112 to 2x QSFP112 compatibility?

Provide the two host model numbers, firmware versions, port type, port mode, required cable code, and planned length. A standards match does not by itself prove a host will accept every third-party cable code.

When should I choose DAC for this link?

Use it for fan-out links with OSFP112 to 2x QSFP112 endpoints when the routed path stays within up to 2 m listed. Choose passive copper when low cable power and simple installation matter more than reach or cable diameter. Confirm that the source port supports the required breakout mode and that each leg maps to the intended downstream port.

What should be included in an RFQ?

Include endpoint A and B, host models, firmware, port mode, length and service-loop allowance, quantity, temperature, jacket, label, packaging, destination, and required acceptance tests.

How should the cable be accepted on arrival?

Verify the label and ordered part number, inspect the cable and latches, connect to the intended hosts, confirm link state and lane mode, then run the site-defined traffic or BER acceptance procedure.

Related Products

Related Products

Explore additional fiber optic products related to this item and suitable for similar network deployment needs.