---
title: "DAC, AOC and AEC Cables: What Changes at the Physical Interface"
description: "Leviathan Systems — Technical content Published 2026-07-04; updated 2026-10-20."
canonical: "https://www.leviathansystems.co/articles/dac-vs-aoc-vs-aec-cabling"
last-updated: "2026-10-20"
---

# DAC, AOC and AEC Cables: What Changes at the Physical Interface

Leviathan Systems — Technical content
Published 2026-07-04; updated 2026-10-20.

Direct attach copper (DAC), active optical cable (AOC) and active electrical cable (AEC) describe different assembly approaches. Passive DAC carries electrical signals over copper; AOC integrates optical conversion and fiber; a retimer-based AEC adds clock/data recovery and regenerated transmission timing to copper. Compare the exact supported implementation and its replaceable parts, rather than choosing from the family name alone.

## Distinguish the assembly you will actually handle

Direct attach copper (DAC), active optical cable (AOC) and active electrical cable (AEC) describe what lies between the host connectors. A passive DAC carries the electrical signal through copper without cable-resident signal conditioning. An AOC converts between electrical host signals and an internal optical path. Amphenol's retimer-based AEC architecture keeps copper as the medium and adds signal-regeneration electronics.

Within active copper, gain changes signal amplitude; equalization or pre-emphasis reshapes the waveform to compensate for frequency-dependent attenuation. Linear conditioning alone does not recover a clock and regenerate transmission timing. A retimer additionally uses clock and data recovery (CDR) to recover the data and launch a regenerated signal using recovered timing. Texas Instruments explains this distinction in its December 2021 PCIe application brief; its PCIe design limits and recommendations do not become Ethernet or InfiniBand cable-selection rules.

Timing recovery is not, by itself, forward error correction (FEC) decoding or packet retransmission. FEC uses added redundancy to correct errors within the code's capability. Retiming does not guarantee recovery of every wrong bit, eliminate every impairment or establish zero bit-error rate (BER).

Keep vendor naming with the implementation: Amphenol distinguishes redriver-based active copper cables (ACCs) from retimer-based AECs; NVIDIA calls its cited pre-emphasis implementation linear active copper cable (LACC). An active label alone therefore leaves the timing-recovery function unresolved. Record the full manufacturer part number, medium, connector ends and length option.

References: [N1](https://docs.nvidia.com/networking/display/400g100gpam4ovdev/Copper-DAC-and-LACC-Cables-Overview), [N2](https://docs.nvidia.com/networking-ethernet-software/knowledge-base/Setup-and-Getting-Started/layer-1-Data-Center-Cheat-Sheet/), [A1](https://www.amphenol-cs.com/cables/active-electrical-cables.html), [T1](https://www.ti.com/document-viewer/lit/html/SNLA401/GUID-2999360A-C3BC-4361-9D1E-D056ADB93188), [C1](https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/implementation-optics-wp.html)

## Compare service boundaries as well as media

The electronic difference changes the evidence a buyer needs. For a linear implementation, waveform conditioning is the claimed function; for a retimer-based implementation, timing regeneration is an additional function to identify in the exact product. Neither description supplies the supported host/mode, power and thermal requirements or latency for the proposed combination. Those remain product-and-system questions, so one family is not a universal winner.

Serviceability is a separate comparison. An integrated assembly is tracked as a complete part, while a separable optical channel can contain individually identified modules and fiber components. Compare both the signal implementation and the unit a later replacement request would cover.

References: [N1](https://docs.nvidia.com/networking/display/400g100gpam4ovdev/Copper-DAC-and-LACC-Cables-Overview), [A1](https://www.amphenol-cs.com/cables/active-electrical-cables.html), [T1](https://www.ti.com/document-viewer/lit/html/SNLA401/GUID-2999360A-C3BC-4361-9D1E-D056ADB93188)

Cable assembly distinctions
| Type | What the assembly includes | Record or handling question | Source |
| --- | --- | --- | --- |
| Passive DAC | Copper conductors with electrical host interfaces | Which exact hosts and port mode qualify this complete part? | N1 |
| Active linear copper | Copper assembly with linear gain, equalization or pre-emphasis to condition the waveform | What conditioning implementation and supported host/mode does the exact product specify? | N1, A1, T1 |
| Retimer-based AEC | Copper assembly with clock/data recovery and regenerated transmission timing | Which product power, thermal and configuration requirements apply? | A1, T1 |
| AOC | Optical conversion and internal fiber in an integrated assembly | How is the complete assembly identified and routed? | N2 |
| Separate optics and fiber | Replaceable optical modules plus external fiber channel components | Which module pair, fiber, connectors and mapping form the channel? | N2 |
Assembly structures from the cited vendors; the complete product and supported system supply the actual operating and handling requirements.

## Read the actual active-cable description

Two Amphenol product records make the distinction concrete. NEUUSH-0103 is described as an OSFP-XD AEC for PCIe Gen5 with a Broadcom retimer. NJMMNK-0303 is described as an OSFP AEC with a Marvell retimer and a stated per-lane rate. Both identify a three-meter assembly. The shared AEC label and length do not make them interchangeable products.

Use the exact description and specification fields rather than a broad category heading or an abbreviated purchasing line. These two records identify retimers, but their protocol, form factor and application descriptions still differ. A per-lane rate alone leaves the approved system application unresolved.

For a proposed replacement, obtain the exact two host models, intended operating mode and applicable support evidence for the full assembly. A listing can identify the item while leaving that combination unqualified. Keep stock, a published lifecycle label and compatibility as separate questions: a public product record is not a supplier commitment to deliver or approval to use it on the project.

References: [A2](https://www.amphenol-cs.com/product/neuush0103.html), [A3](https://www.amphenol-cs.com/product/njmmnk0303.html)

Two specific AEC records: the family name leaves important differences
| Exact Amphenol part | Published description fields | What remains a project question | Source |
| --- | --- | --- | --- |
| NEUUSH-0103 | OSFP-XD; PCIe Gen5; 3m; Broadcom retimer | Supported hosts, actual application, supplied configuration and physical requirements. This is not generic Ethernet or InfiniBand approval. | A2 |
| NJMMNK-0303 | OSFP; 112G/lane; 3m; Marvell retimer | Applicable supported hosts and operating mode. Do not infer a full link application from the per-lane field. | A3 |
Public description fields checked October 15, 2026. These are identification examples, not parts recommendations; the 3m field is neither a family reach rule nor an approved route.

## Do not apply patch-cord maintenance to an AOC by name

An AOC's integrated optical path is not a pair of exposed fiber patch connectors simply because the name contains optical. Its bonded internal fiber is non-detachable. Determine which interfaces the actual assembly exposes and which maintenance the OEM permits; MPO cleaning or an OTDR test for a detachable trunk cannot automatically be applied to that internal path.

An optical transceiver with an external fiber channel instead has separately identifiable components and exposed interfaces with their own applicable procedures. Keep that service boundary explicit in the work package; it does not authorize opening an integrated assembly or improvising maintenance.

References: [N1](https://docs.nvidia.com/networking/display/400g100gpam4ovdev/Copper-DAC-and-LACC-Cables-Overview), [N2](https://docs.nvidia.com/networking-ethernet-software/knowledge-base/Setup-and-Getting-Started/layer-1-Data-Center-Cheat-Sheet/)

## Build the selection record around both hosts

Ask the responsible network owner for the approved part, host models, port modes, software/firmware applicability and any published restrictions. Then reconcile the chosen length and mechanical requirements with the released route. Power and thermal suitability belong to the exact supported endpoint combination, not a generic assumption that one family is always lower power.

Include connector clearance, branch junctions where present, service access and the applicable assembly handling instructions. Do not assume active copper shares a passive cable's bend requirement or that an optical assembly always occupies less space. Raise a mismatch before purchasing or installing an alternative.

## Read a cable benchmark with its test boundary

Amphenol's July 6, 2026 Z800 Freya evaluation examines DAC, ACC and AEC assemblies. It uses pseudorandom bit-sequence (PRBS) streams for BER analysis and separate Layer 2 packet streams for packet-loss testing. Pre-FEC BER concerns erroneous bits relative to the relevant observed bit population before correction; packet loss concerns missing frames in its own traffic stream and boundary. Zero observed packet loss therefore does not establish zero pre-FEC errors.

Its latency result uses stated last-bit-out and first-bit-in markers at a PHY-to-PHY datapath boundary. That is neither an application response-time result nor a universal latency definition.

Host behavior, assembly implementation and equalization affect applicability. Ask whether the proposed setup is covered; these vendor observations are not independent replication or results for the two catalogue examples. No benchmark number becomes a deployment threshold here. The related FEC-counter guide develops correction, counts and ratios.

References: [A4](https://www.amphenol-cs.com/connect/evaluating-dac-acc-aec-cables-800g-data-center-z800-freya.html), [C1](https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/implementation-optics-wp.html)

## Report a substitution as a design decision

Illustrative example: the schedule specifies a qualified passive copper part, but the supplied carton contains an active optical assembly of the same connector form. Record both exact identifiers and the affected links. The design/procurement owner must resolve compatibility, route and acceptance implications before release. Same connector and same advertised data rate are insufficient approval.

Leviathan installs approved customer-furnished assemblies and records the installed connections. Identify the appointed equipment/material supplier and delivery responsibilities. This article explains a buying decision; actual configuration, measurement and live-link work require their own approved scope and responsible performers.

References: [L1](https://www.leviathansystems.co/services/structured-cabling)

## Check the product generation before treating media as alternatives

NVIDIA's 100G-PAM4 overview, updated November 18, 2025, distinguishes passive DAC from pre-emphasis LACC. It excludes AOCs for the documented 100G-PAM4 Ethernet and InfiniBand series, while a separate passage describes backwards-compatible AOCs operating at 50G-PAM4 in an older-200G context. Those passages describe different operating contexts, not interchangeable media choices.

Use that dated generation example to order the decision: establish the exact supported alternatives first, then compare their physical and service boundaries. A retimer-based AEC catalogue record does not establish membership in NVIDIA's linear-active category or support for the intended InfiniBand system.

References: [N1](https://docs.nvidia.com/networking/display/400g100gpam4ovdev/Copper-DAC-and-LACC-Cables-Overview), [A1](https://www.amphenol-cs.com/cables/active-electrical-cables.html)

## Compare the replacement unit without changing the link count

Integrated and separable optical arrangements can represent the same number of planned links with different component populations. An AOC combines optical conversion and fiber in one assembly; separate modules and an external patch cord define a different replacement unit.

Fictional example EX-MD115 compares two separately stipulated three-link planning records. Plan I identifies three complete AOC assemblies. Plan S identifies six separate optical modules and three patch cords, with each module and cord associated to a particular link. Both plans describe three intended links; Plan S contains nine component identities rather than nine links. The example assumes that the design owner has supplied these different plans. It neither qualifies them as alternatives on one real system nor identifies an actual installed population.

This distinction matters when a quotation or later return says replace the cable. For Plan I, the question concerns the exact integrated assembly. For Plan S, it must identify a particular module, cord or the whole channel. Ask for the affected item and the responsible technical decision instead of silently substituting a different component scope.

References: [N2](https://docs.nvidia.com/networking-ethernet-software/knowledge-base/Setup-and-Getting-Started/layer-1-Data-Center-Cheat-Sheet/)

EX-MD115: three planned links are not three identical service populations
| Stipulated record | Component identities for three planned links | What a replacement request must identify | Source |
| --- | --- | --- | --- |
| Plan I: integrated assemblies | Three complete AOC identities, one associated to each intended link | The affected assembly identity and the actual authorized scope. | Planning analysis |
| Plan S: separable optical channels | Six module identities plus three patch-cord identities: nine components associated to three links | The particular module or cord, or the separately defined complete-channel scope. | Planning analysis |
| Comparison boundary | Three links in each plan; component records and link records are different units | Keep the affected component and the intended link separately identified. | Planning analysis |
Original fictional planning comparison. Counts follow the stipulated populations, not a universal bill of materials, fault diagnosis or replacement instruction.

## Primary sources

- [N1 — NVIDIA LinkX copper DAC and LACC overview](https://docs.nvidia.com/networking/display/400g100gpam4ovdev/Copper-DAC-and-LACC-Cables-Overview). Checked 2026-10-15. November 18, 2025 overview: passive/linear mechanisms and distinct 100G-PAM4 versus older 50G-PAM4 contexts. Exact part and supported endpoints remain necessary.
- [N2 — NVIDIA: Layer 1 data center cheat sheet](https://docs.nvidia.com/networking-ethernet-software/knowledge-base/Setup-and-Getting-Started/layer-1-Data-Center-Cheat-Sheet/). Checked 2026-10-15. Used for the integrated AOC assembly distinction, not as a current compatibility matrix or a universal installation procedure.
- [A1 — Amphenol: active electrical cable assemblies](https://www.amphenol-cs.com/cables/active-electrical-cables.html). Checked 2026-10-15. Vendor explanation of retimer-based AEC assemblies; other vendors may use different product naming. Exact part specifications control.
- [L1 — Leviathan structured cabling scope](https://www.leviathansystems.co/services/structured-cabling). Checked 2026-10-15. Physical cabling service boundaries; exact design, materials, authorization and verification are project-specific.
- [A2 — Amphenol NEUUSH-0103 product description](https://www.amphenol-cs.com/product/neuush0103.html). Checked 2026-10-15. Exact OSFP-XD/PCIe Gen5/3m/Broadcom-retimer description only. No cable drawing, power/temperature/ratings, host support, procurement or interchangeability claim.
- [A3 — Amphenol NJMMNK-0303 product description](https://www.amphenol-cs.com/product/njmmnk0303.html). Checked 2026-10-15. Exact OSFP/112G-per-lane/3m/Marvell-retimer description only. No aggregate-rate calculation, exact Ethernet/InfiniBand/PCIe application, host support, power/thermal limit, stock or substitution approval.
- [A4 — Amphenol: DAC, ACC and AEC evaluation using Z800 Freya](https://www.amphenol-cs.com/connect/evaluating-dac-acc-aec-cables-800g-data-center-z800-freya.html). Checked 2026-10-15. July 6, 2026 vendor setup and observation boundaries only; no reproduced ranking, adopted benchmark, catalogue-part association or test/tuning instructions.
- [T1 — Texas Instruments SNLA401: When Should a PCIe Retimer be Implemented?](https://www.ti.com/document-viewer/lit/html/SNLA401/GUID-2999360A-C3BC-4361-9D1E-D056ADB93188). Checked 2026-10-20. December 2021 PCIe brief, used only for equalization versus clock/data recovery and timing regeneration. No PCIe limits, device recommendations or tuning transferred to cable selection.
- [C1 — Cisco: Understanding FEC and Its Implementation in Cisco Optics](https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/transceiver-modules/implementation-optics-wp.html). Checked 2026-10-20. Updated May 13, 2022. Redundancy-based correction and its distinction from retransmission only; no product setting or performance limit adopted.

## Related Leviathan resources

- [GPU breakout cabling: separate cage, logical port and cable leg](/articles/transceiver-breakout-cabling-gpu)
- [400G, 800G and 1.6T optics: read the complete specification](/articles/400g-800g-1600g-optics-selection)
- [Single-mode versus multimode: start with the exact optic](/articles/single-mode-vs-multimode-ai-fabric)
- [Customer-furnished materials: identify the supplied assembly](/articles/customer-furnished-materials-installation-checklist)
- [FEC corrected errors, bit ratios and packet-loss evidence](/articles/gpu-ethernet-fec-counters-vs-fiber-test-reports)
- [Structured cabling and fiber installation scope](/services/structured-cabling)

## Scope installation of approved cable assemblies

Send the exact part list, endpoint plan, route and required physical handoff records.

[Discuss the scope](/contact?service=structured-cabling&from=/articles/dac-vs-aoc-vs-aec-cabling)
