A QSFP28 DAC is a fixed-assembly copper cable with QSFP28 connectors on each end. The connectors plug directly into 100G QSFP28 ports, and the cable carries four 25G electrical lanes that together deliver 100G aggregate throughput. Because no optical conversion happens inside the cable, DACs consume less power and cost less than optical modules for the same short-distance link.
The QSFP28 form factor follows the SFF-8665 specification. It shares the same physical cage as QSFP+ but is electrically distinct, running at 25G per lane rather than 10G. Most modern 100G switches accept QSFP28 DACs without any firmware configuration, though some vendors require a specific compatibility flag.
DAC cables are governed by SFF Committee MSA specifications, which define the electrical signaling, connector dimensions, and the I2C EEPROM management interface that lets the host switch identify cable type, vendor, and length.
The most important call when buying a QSFP28 DAC is whether you need passive or active. They look nearly identical from the outside, but the internal design and the right use cases are quite different.
A passive DAC contains only copper conductors and connectors — no signal amplification or equalization circuitry inside the assembly. The host switch's SerDes handles all signal conditioning at both ends.
Passive cables are available from 0.5 meters up to about 3 meters. Beyond that, signal attenuation on passive copper typically exceeds what a switch port's receiver can reliably compensate for, and that's where active cables take over.
Passive DACs are the default choice for:
Because there's no active circuitry, passive cables draw no power from the host port beyond what the EEPROM requires for identification — effectively zero watts from the cable itself.
An active DAC (sometimes called an ACC or active copper cable) embeds signal conditioning chips inside one or both connector housings. These chips re-drive and equalize the signal, compensating for the higher attenuation of longer copper runs.
Active QSFP28 DAC cables are available from 5 meters up to about 10 meters, with some vendors offering 7-meter variants as a midpoint. The tradeoff is power: active cables typically draw 0.5W to 1.5W per end from the host port, which adds up across a dense deployment.
Active cables make sense when:
One thing worth clarifying: active DAC cables are not the same as active optical cables (AOCs). An AOC uses optical fiber with laser and photodetector assemblies inside the housing; an active DAC still uses copper. AOCs extend reach further — up to 100 meters for 100G — but at higher cost and power.
| Feature | Passive DAC | Active DAC |
|---|---|---|
| Typical length range | 0.5m to 3m | 5m to 10m |
| Signal conditioning | Host switch only | Embedded chips in connector |
| Power draw (cable) | ~0W | 0.5W to 1.5W per end |
| Cost | Lower | Moderate |
| Latency | Sub-nanosecond | Sub-nanosecond |
| Best use case | Same-rack links | Cross-rack or longer runs |
QSFP28 DAC cables aren't limited to 100G-to-100G connections. Breakout variants split the four 25G lanes into separate connectors — useful when connecting a 100G uplink port to four 25G server NICs or four 25G switch ports.
The most common configuration is 100G QSFP28 to 4x25G SFP28, available as a passive cable at 1–3 meters or an active cable at 5 meters. This is the standard cable for spine-leaf architectures where a 100G spine port fans out to four leaf-layer 25G connections.
Other breakout options you may encounter:
Breakout DAC cables require the switch to support breakout mode on the relevant port. On Cisco Nexus, that's configured with interface breakout module X port Y map 25g-4x. On Arista EOS, the speed forced 25gfull command and the relevant breakout interface configuration apply. Always confirm your switch model and software version support the specific breakout ratio before ordering.
Switch compatibility is where most DAC cable procurement problems start. Every major switch vendor encodes a compatibility check into the port initialization sequence. When a DAC cable's EEPROM data doesn't match the expected vendor ID or checksum, the switch may log a warning, disable the port, or both.
Cisco NX-OS and IOS-XE check the EEPROM vendor name and part number against an internal compatibility list. If the cable isn't on it, you may see:
%SFF8472-5-THRESHOLD_VIOLATION: module...
or a port that comes up but generates unsupported transceiver warnings in show interface output. The service unsupported-transceiver command in global configuration allows non-Cisco optics and cables to operate on most Nexus platforms, though Cisco's official position is that using it may affect TAC support eligibility.
Arista's approach is similar. Third-party DAC cables may trigger:
%XCVR-6-UNSUPPORTED_XCVR
The service unsupported-transceiver global command — or its per-interface equivalent in newer EOS versions — allows the port to come up. In practice, Arista is generally more permissive than Cisco when it comes to third-party optics.
Juniper uses a different mechanism. On QFX and EX platforms, no-auto-negotiation or an explicit speed configuration may need to be set for some third-party DAC cables. Juniper doesn't block non-Juniper cables by default on most QFX platforms, but signal integrity validation still runs at link-up.
Every QSFP28 DAC carries an I2C-accessible EEPROM that stores:
A third-party cable programmed with the correct vendor string for your switch platform will typically initialize without warnings. This is what "custom programmer" solutions refer to: the EEPROM is coded to match the expected vendor ID for a specific platform, so the switch treats the cable as a native component. HYTOPTODEVICE offers custom programmer solutions for exactly this use case — where the cable needs to identify itself correctly to a specific vendor's switch OS.
The table below summarizes typical QSFP28 DAC support across common switch families. Always verify against your specific software release notes, since support can change between minor versions.
| Switch Platform | Passive DAC Support | Active DAC Support | Breakout Support |
|---|---|---|---|
| Cisco Nexus 9300/9500 | Yes (with service cmd) | Yes | Yes (port-dependent) |
| Cisco Catalyst 9500 | Yes (with service cmd) | Yes | Limited |
| Arista 7050X3/7060X | Yes | Yes | Yes |
| Arista 7280R | Yes | Yes | Yes |
| Juniper QFX5120 | Yes | Yes | Yes |
| Juniper EX4650 | Yes | Yes | Limited |
| Mellanox/NVIDIA SN2700 | Yes | Yes | Yes |
This is a general reference. Specific software versions, line card types, and port groups within a chassis can all affect whether a particular cable length or type is supported. Test before deploying at scale.
Order passive for runs under 3 meters and active for 5 meters and above. Buying a passive cable for a 5-meter run to save a few dollars is a common mistake — one that tends to surface as link instability, CRC errors, and hours of troubleshooting.
Ask the supplier whether the cable is coded for your specific switch vendor. A cable coded for Arista carries a different vendor string in its EEPROM than one coded for Cisco. Some suppliers offer platform-specific coding; others ship generic MSA-compliant EEPROM and rely on the service unsupported-transceiver workaround. Both approaches work, but knowing which one you're buying avoids surprises during deployment.
Data center deployments typically require CM or CMR-rated jackets. If your cables route through plenum spaces, you need CMP-rated assemblies. This is a fire code requirement, not a performance one — but it matters for compliance and insurance purposes.
If you need a breakout cable, confirm that your switch supports the specific ratio (4x25G, 2x50G, etc.) on the port group you plan to use. Not all ports on a given switch support all breakout modes, and some require a specific license or software feature set.
The biggest risk with third-party DAC cables is deploying them in production without prior compatibility validation. Look for suppliers that provide test reports, compatibility matrices, or product documentation showing the cable has been validated against your switch platform. Actual test data is far more useful than a generic "compatible with Cisco/Arista/Juniper" claim on a product page.
DAC cables cost less per unit than optical transceivers, but think through the total deployment: cable management, bend radius constraints (active DAC cables have stiffer housings due to the embedded chips), and the operational overhead of managing two cable types across your inventory. For large deployments, standardizing on a single length and type reduces complexity even if it means slightly over-specifying some links.
QSFP28 DAC cables aren't the right answer for every 100G link. Here's a straightforward decision framework:
Use a DAC cable when:
Use an optical transceiver when:
For most server-to-ToR and ToR-to-spine links inside a single data center, passive QSFP28 DAC cables at 1–3 meters are the right tool. Optical transceivers take over for everything beyond that, and for any link where physical routing makes copper impractical.
If you're evaluating both DAC cables and optical transceivers for a 100G or 400G project, HYTOPTODEVICE covers the full range — from QSFP28 DAC assemblies to QSFP28 and QSFP-DD optical modules across all major vendor-compatible configurations.
Q1:What is the maximum length for a QSFP28 passive DAC cable?
A:Most passive QSFP28 DAC cables top out at 5 meters. Beyond that, signal attenuation on passive copper typically exceeds what a switch port's receiver can reliably handle, and you'll need an active DAC or optical solution.
Q2:Can I use a QSFP28 DAC cable in a QSFP+ port?
A:No. QSFP28 and QSFP+ share the same physical connector dimensions, but QSFP+ runs at 10G per lane while QSFP28 runs at 25G per lane — a QSFP28 DAC won't negotiate correctly in a QSFP+ port. Some switches support auto-negotiation between the two, but this is platform-specific and should be confirmed in the switch's release notes before you try it.
Q3:Do QSFP28 DAC cables work with Cisco's "service unsupported-transceiver" command?
A:Yes, on most Cisco Nexus and Catalyst platforms. The service unsupported-transceiver global command allows non-Cisco optics and cables to initialize. That said, Cisco's official position is that enabling this command may affect TAC support eligibility for the affected interface — review your support contract terms before enabling it in production.
Q4:What is the difference between an active DAC and an active optical cable (AOC)?
A:An active DAC uses copper conductors with signal conditioning chips embedded in the connector housing. An AOC uses optical fiber with laser and photodetector assemblies inside the housing. AOCs support longer distances — up to 100 meters for 100G — but consume more power and cost more than active DAC cables. Both plug into QSFP28 ports.
Q5:How do I know if a QSFP28 DAC cable is coded for my switch vendor?
A:Ask the supplier for the EEPROM vendor string programmed into the cable. For Cisco-compatible cables, the vendor name field matches Cisco's expected value; for Arista-compatible cables, it matches Arista's. A supplier that can't answer this question, or only says "MSA compliant," is shipping generic EEPROM coding that may trigger unsupported transceiver warnings on strict platforms.
Q6:What is a QSFP28 breakout DAC cable used for?
A:A breakout DAC splits the four 25G lanes of a single QSFP28 port into four separate SFP28 connectors, each carrying one 25G lane. This lets you connect one 100G switch port to four 25G server NICs or four 25G downstream switch ports — a standard configuration in spine-leaf data center architectures.
Q7:Is a QSFP28 DAC cable the same as a twinax cable?
A:Twinax is the copper conductor type used inside most DAC cables, so the terms are often used interchangeably. Technically, "twinax" refers to the cable construction (two conductors with a shared shield), while "DAC" refers to the complete assembly including the QSFP28 connectors and EEPROM. When a vendor says "twinax cable," they almost always mean a passive DAC.
Choosing the right QSFP28 DAC cable comes down to three decisions: passive or active based on cable length, standard or vendor-coded EEPROM based on your switch platform, and breakout or straight-through based on your port architecture. Get those three right and QSFP28 DAC cables are among the most reliable, cost-effective interconnects available for short-reach 100G links in 2026.
If you're sourcing QSFP28 DAC cables alongside optical transceivers for a broader 100G or 400G deployment, HYTOPTODEVICE carries both passive and active DAC variants with vendor-compatible EEPROM options across Cisco, Arista, Juniper, and other major platforms.