Your Cart

DAC, AEC, AOC or Optical Transceivers for Data Center Links

Guide By
Bundles of blue network cables held with black straps, running into a cable tray.

At 400G, passive copper works only over short distances. If the required cable length exceeds even one connected port's passive-copper limit, you need an active cable or pluggable optics.

On Edgecore's AS9736-64D, ports 1 to 4, 29 to 36 and 61 to 64 supply up to 24 W per module. Those ports support 400G direct attach cables, or DACs, up to 2.5 m. The remaining ports supply up to 13 W and limit 400G DACs to 1 m. Choose a length supported by every connected port.

Each cable end must match its attached port's electrical lane count, rate and modulation. A 400G-to-four-100G breakout cable can plug into a switch and four 100G NICs but leave the links down.

Choose an active electrical cable, or AEC, for a copper link beyond passive-copper reach if every connected port supports the exact cable and length. An active optical cable, or AOC, suits a direct fiber run when replacing the whole cable is acceptable. Choose pluggable optics for patch panels or when the fiber and modules need separate replacement.

Copper and Fiber Carry Signals Differently

An Ethernet port sends data over one or more electrical paths called lanes. NRZ and PAM4 are modulation formats. NRZ uses two signal levels, while PAM4 uses four. A 100G interface can use four 25G NRZ lanes, two 50G PAM4 lanes or one 100G PAM4 lane. A passive cable does not convert NRZ to PAM4 or change the signaling rate of a lane.

A passive DAC carries electrical signals over copper without powered circuits in the data path. Some passive cables use passive equalization to compensate for signal loss. The host reads the cable's identity and capabilities from EEPROM in the connector.

A linear active copper cable, or LACC, adds powered equalizers to compensate for signal loss. An active electrical cable, or AEC, recovers the clock and retimes the data.

Some AECs contain gearboxes that change the number of lanes and the rate per lane while keeping the same total nominal Ethernet data rate. The cable ends can then use different electrical lane formats.

Active copper cable, or ACC, can mean a linear or a retimed design. Before ordering an ACC, check whether that part equalizes, retimes or converts lanes. You can reach out to our engineers with questions about the link you are planning.

Active optical cables, or AOCs, convert between electrical signals and light using transceivers permanently attached to the fiber. Use an AOC for a point-to-point connection where the fiber and optics can be replaced together. Pluggable optical transceivers also convert between electrical and optical signals, but use a fiber cable that detaches from the modules, so the modules and fiber cable can be replaced independently.

passive copperlinear active copperretimed active copperactive optical cablepluggable opticshosthostcable endcable endcopper pairseepromeepromhosthostlinear equalizerno retiminglinear equalizerno retimingcopper pairshosthostretimeroptional gearboxretimeroptional gearboxcopper pairshosthostfixed optical endfixed optical endfixed fiberhosthostremovable transceiverremovable transceiverseparate fiber plantelectrical signaloptical signal
Passive copper has no powered signal electronics, linear copper equalizes the signal, and retimed copper recovers the clock and data. AOC optics stay attached to the fiber.

Copper Reach Depends on the Lane Rate

A higher lane rate generally shortens passive copper reach. Nominal Ethernet data rates exclude encoding and FEC overhead. Those extra bits raise the transmitted bit rate above the nominal data rate. Symbol rate is a different measure, and PAM4 carries two bits per symbol.

An IEEE reach objective sets a design target of at least the stated distance. Actual ports have vendor-qualified cable lengths.

A number after CR in a copper interface name gives the lane count. The unnumbered 25GBASE-CR, 25GBASE-CR-S and 50GBASE-CR interfaces each use one lane. The Ethernet Technology Consortium’s eight-lane 400G CR8 format has no IEEE reach objective.

A host's supported cable length can be shorter than an IEEE reach objective. A vendor can also support a longer cable on specified ports. Use a cable length qualified for every connected port.

IEEE 802.3df was approved on 16 February 2024 and defines eight-lane 800G on 100G lanes. P802.3dj's four-lane 800G design uses 200G lanes. P802.3dj was still a draft on 9 November 2026.

The adopted P802.3dj objective for four-lane 800GBASE-CR4 is at least 1 m. Check whether an 800G port uses four or eight lanes before choosing its copper interface.

Copper interfaceReach objective
25GBASE-CR-S3 m
25GBASE-CR5 m
100GBASE-CR45 m
50GBASE-CR3 m
100GBASE-CR23 m
200GBASE-CR43 m
400G CR8No IEEE objective
100GBASE-CR12 m
200GBASE-CR22 m
400GBASE-CR42 m
800GBASE-CR82 m
800GBASE-CR41 m (draft)

Arista's 10G SFP+ and 40G QSFP+ DACs come in 0.5 to 5 m lengths. Those 10G and 40G links normally need no FEC.

A 100G CR4 cable uses four 25G NRZ lanes. Confirm support for the selected cable and length on both hosts before ordering.

At 50G PAM4 per lane, one lane carries 50G, two carry 100G CR2 and four carry 200G CR4. Arista's 200G CR4 DACs come in 1, 2 and 3 m lengths. NVIDIA's MCP1650-V 200G QSFP56 DAC comes in 0.5 to 3 m lengths.

Arista offers 1 to 3 m 400G CR8 cables using eight 50G PAM4 lanes. Both host ports must support the chosen cable's electrical interface and length.

With 100G PAM4 lanes, CR1 carries 100G, CR2 carries 200G, CR4 carries 400G and CR8 carries 800G. NVIDIA's MCP4Y10 OSFP cable comes in 0.5 to 2 m lengths. Its EEPROM reports modes including two four-lane 400GBASE-CR4 connections and one eight-lane 800GBASE-CR8 connection. The host must support and select the mode for the intended connection.

Arista's 800G passive DACs without breakout, with OSFP-to-OSFP or QSFP-DD-to-QSFP-DD connectors, have 1 m and 2 m versions. Choose the part for the host's supported electrical lane format as well as the length.

When Passive Copper Is Too Short

If the route exceeds either port's passive-copper limit, choose a different medium. An AEC or AOC can cover the distance when every attached port supports that part number. For the routed length, confirm that the selected active cable is orderable and supported by every attached port.

Match an active cable's connector variant to its host cage. OSFP-RHS, the riding-heat-sink variant, needs a matching keyed cage and uses a heat sink supplied by the host.

NVIDIA's MCA4J80 linear active copper cable comes in 3, 4 and 5 m lengths. It connects twin-port OSFP cages at both ends, carrying two 400G InfiniBand links. For Ethernet, confirm support on both connected hosts and their intended ports.

For a direct fiber run, Arista has 100G, 200G and 400G AOC families with 1 to 30 m versions. Its 800G OSFP-to-OSFP AOC also reaches 30 m. Arista's Transceiver Guide gives the A-O800-2Q400-xM breakout AOC a 50 m version, while its 800G FAQ gives a maximum length of 30 m for that family. In A-O800-2Q400-xM, xM also gives the cable length in meters. Confirm that the required length is orderable before choosing that breakout AOC.

Arista's 800G linear pluggable optics, or LPO, AOC family reaches 50 m. LPO removes the module's digital signal processor, or DSP, and leaves signal processing to the host ASIC. Both ends need LPO-capable host ports. Confirm the cable's support on the intended host hardware and software.

Edgecore also offers 400G AOCs from 1 to 30 m. Edgecore's ET7502-AOC family includes a 3 m version and reaches up to 30 m using OM4 multimode fiber inside the assembly. NVIDIA's MFS1S00-V 200GbE AOC reaches 100 m.

Matching the Breakout to the NIC

Breakout lets one high-speed port, called the parent, connect several lower-speed ports. The parent is configured with one logical port, or subport, for each lower-speed link. A passive breakout cable divides the parent's electrical lanes among the far-end connectors without changing the lane format.

For a 100G port connected to four 25G ports, Arista's passive breakout sends one 25G NRZ lane to each 25G SFP28 end. Arista's 100G-to-four-25G passive breakout comes in 1, 2, 3 and 5 m lengths. Each 25G link needs a FEC mode supported by the cable and both ports. The two ports must agree on that mode through supported negotiation or matching manual settings.

A 400G parent using eight 50G PAM4 lanes can split into two 200G links with four lanes each, or four 100G links with two lanes each. Arista offers passive 2 × 200G and 4 × 100G splits. Edgecore's ET7502-B4D breakout DAC connects one 400G port to four 100G ports and comes in 1 m and 2 m lengths. Each port must support the selected cable length.

Arista also offers passive breakout from 400G to eight 50G ports, with one 50G PAM4 lane at each remote end. The switch and network operating system, or NOS, must support the intended breakout mode on the parent port. Each remote port must support the lane count and modulation at its cable end.

Arista's OSFP/QSFP-DD passive breakout cables have 400G and 200G versions. Either version carries 200G when the parent supports and selects eight 25G NRZ lanes. The cable carries that lane format unchanged.

Arista's 400G and 200G versions have separate breakouts for two 100G QSFP28 ports, four 50G ports or eight 25G ports. With eight 25G NRZ lanes at the parent, each 100G end uses four lanes. Each 50G end uses two lanes, and each 25G end uses one.

The 400G cable version's EEPROM indicates support for up to 50G per lane with PAM4 signaling. The 200G version indicates up to 25G per lane with NRZ signaling. Software on an older NIC may not recognize the 400G version's 50G PAM4 EEPROM coding. For equipment that recognizes only 25G NRZ coding, choose Arista's 200G version and configure the parent for eight 25G NRZ lanes.

For an eight-lane 400G parent using 50G PAM4, a copper cable to four QSFP28 100G hosts must convert the lane format. Each 100G branch changes from two 50G PAM4 lanes to four 25G NRZ lanes. Arista's active copper breakout uses gearbox conversion and comes in 1, 2, 3 and 5 m lengths.

Arista's A-D400-4Q100-xM AOC connects a QSFP-DD parent at 400G to four QSFP28 100G hosts using fiber. In this Arista part number, xM gives the cable length in meters.

Equalization and retiming alone do not change the lane count or modulation. For any cable that converts the electrical lane format, confirm support on every attached host port and the host FEC settings for each end. Find out whether the cable passes FEC through or decodes and re-encodes it internally.

400G port8 × 50G PAM4100G leg, 2 × 50G PAM4passive wiringcannot convertQSFP28 host4 × 25G NRZport operated at 200G8 × 25G NRZpassive breakouttwo 100G connections4 × 25G NRZ each400G port8 × 50G PAM4active laneconversionfour 100G connections4 × 25G NRZ eachpassive wiring keeps the lane formatpassive breakout at 200Gfull 400G through active conversion
Passive breakout keeps the electrical lane format, while active lane conversion can connect an eight-lane 400G port to four QSFP28 100G hosts.

An 800G parent using eight 100G PAM4 lanes can split into two four-lane 400G links. Arista offers passive DACs and AECs for that split.

For four remote ports, Arista's passive 800G-to-four-200G cables come in 1 m and 2 m versions. They use two 100G PAM4 lanes at each remote end, and each 200G host must support that electrical format.

Arista's passive 800G-to-two-QSFP112 cables come in 1 to 4 m lengths. Each QSFP112 end uses four 100G PAM4 host lanes for its 400G connection. The 3 m and 4 m versions support switch-to-NIC connections. The 1 m and 2 m versions support both switch-to-switch and switch-to-NIC use.

Optics Must Match the Fiber

We have deployed Edgecore and generic optics for our customers. Select optics that match the fiber and are supported by the switch port and NOS release.

Arista's 400G SR8 uses multimode fiber, or MMF, and needs 16 fibers. Its FR4 uses one duplex pair of single-mode fiber, or SMF. Match the optical interfaces at both ends as well as the fiber type, count and connector on the route. The complete path loss must stay within both modules' optical loss budgets.

NVIDIA's MMS4X00-NS400 DR4 module has a 100 m maximum reach with two optical patch panels assumed in the link. The IEEE DR4 interface objective is at least 500 m, but this part is rated for 100 m. Choose the module for the distance and loss of the actual fiber route.

OM3, OM4 and OM5 are multimode fiber grades. For 25GBASE-SR, 100GBASE-SR4 and 200GBASE-SR4, 70/100 m means 70 m on OM3 and 100 m on OM4. The SR4.2 interface can reach 70 m on OM3, 100 m on OM4 and 150 m on OM5. Arista rates its 400G SR4.2 modules for 70 m on OM3 and 100 m on OM4. Check the selected part's OM5 rating before planning a 150 m route.

Coarse wavelength division multiplexing, or CWDM, puts data channels on different wavelengths of a fiber. CWDM4 and FR4 use one transmit fiber and one receive fiber. Each optical lane carries one data channel as light.

Optical interfaces can follow IEEE standards or multi-source agreements, or MSAs. They can also follow vendor formats or specifications from the Optical Internetworking Forum, or OIF. IEEE reach objectives are minimum design targets. Use the selected module's rated reach, fiber grade, required FEC and loss budget for the planned link.

Optical interfaceInterface reach
25GBASE-SR70/100 m
100GBASE-SR470/100 m
100G CWDM42 km
100GBASE-LR410 km
100GBASE-DR500 m
100GBASE-FR12 km
100G-FR2 km
100GBASE-LR110 km
100G-LR10 km
200GBASE-SR470/100 m
200GBASE-FR42 km
400GBASE-SR8100 m OM4
400GBASE-SR4.270/100/150 m
400GBASE-DR4500 m
400GBASE-DR4-22 km
400GBASE-FR42 km
400GBASE-LR4-6At least 6 km
400G-LR4-1010 km
800GBASE-DR8500 m
800G 2FR42 km per 400G link
400ZRDepends on amplification and loss

Arista's -E versions of 25G SR and 100G SR4 need FEC to reach 70 m on OM3 or 100 m on OM4. Choose the host-FEC setting required by the exact part for the planned distance.

The CWDM4 interface requires host RS(528,514), with no FEC bypass. Replacing a no-FEC DAC with an optical module can require a host-FEC change. Set the host FEC required by the selected module.

For 25GBASE-SR, one MMF pair carries a 25G NRZ lane at 850 nm. Arista's modules use duplex LC.

An MPO connector holds several fibers in one plug. Connector polish is the finish of the fiber end face. Angled physical contact, or APC, and ultra physical contact, or UPC, are different polish types. APC and UPC must not be mated together.

Both 100GBASE-SR4 and 200GBASE-SR4 use four MMF pairs with MPO-12 UPC on Arista's modules. The 100G interface carries four 25G NRZ lanes at 850 nm, while 200G uses four 50G PAM4 lanes.

At 400G, SR8 uses eight 50G PAM4 lanes at 850 nm over eight MMF pairs. Edgecore's ET7502-SR8 uses MPO-16 APC. SR4.2, also called BiDi, uses eight fibers in total, with both directions on each fiber at wavelengths near 850 and 910 nm. SR4.2 is available with MPO-12 connectors. Check the connector type and polish specified for the exact SR4.2 part before choosing its fiber cable.

Single-mode fiber can carry optical lanes on separate pairs or combine wavelengths onto one pair. The CWDM4 and FR4 interfaces use wavelengths near 1271, 1291, 1311 and 1331 nm, sharing one transmit fiber and one receive fiber.

100G CWDM4 combines four 25G NRZ lanes on the CWDM wavelengths. At 200G, FR4 carries four 50G PAM4 lanes on those wavelengths. Arista's modules for both interfaces use one duplex SMF pair with LC connectors.

Arista's 100GBASE-LR4 and CWDM4 modules both use duplex LC and SMF, but they use different wavelengths. An LC patch cable can physically fit both, so identify the optical interface before connecting the modules.

100G DR, FR and LR use a single 100G PAM4 optical lane near 1310 nm. Arista's single-wavelength modules use duplex SMF and LC. For FR and LR, match IEEE FR1/LR1 or the 100G Lambda MSA interface at both ends.

Optical Breakout Needs the Right Module Mode

400GBASE-DR4 uses four 100G PAM4 optical lanes near 1310 nm over four SMF pairs. Edgecore's ET7502-DR4 uses MPO-12 APC. Arista's DR4 also has an MPO-12 APC connector. The IEEE minimum reach objectives are 2 km for DR4-2 and 500 m for DR4.

Arista's 400G XDR4 format also uses four 100G PAM4 optical lanes over four SMF pairs. Its OSFP-400G-XDR4 and QDD-400G-XDR4 use MPO-12 APC. Choose the patch cable for the exact module part number.

Pluggable modules can convert different host electrical lane formats to the same optical interface. The fiber between the pluggable modules stays passive. For breakout from 400G DR4 on an eight-lane host to four 100G modules, the parent port runs as four 100G subports.

The Common Management Interface Specification, or CMIS, version 5.4 defines how the host manages a module. In CMIS, an application is a supported operating mode for carrying traffic. For a transceiver, it can pair the electrical interface at the host with the interface on the fiber, giving the host a mode it can select. The switch or NIC must support that application and its lane assignments.

Edgecore's DR4 is intended for 4 × 100G-DR connections. For 400G DR4 breakout to four 100G DR modules, the parent DR4 module must advertise a 100G application to the NOS, using two host lanes per subport. The NOS must support and select that application and assign its required host lanes.

At an MPO connection, a pinned male connector mates with an unpinned female connector. For an ET7502-DR4 connected to four QSFP28 100G DR modules with duplex LC receptacles, use a fanout with a female MPO-12 APC parent end and four matching duplex LC ends. The female MPO end mates with the Edgecore module's pinned receptacle.

Each duplex LC cable end must match the polish of its module's receptacle. The fanout must route each transmit fiber to its far-end receiver.

When a module decodes optical FEC internally, that FEC ends at the module. The parent and remote hosts can then need different FEC settings on their electrical connections.

400G Optics Can Use One Fiber Pair

For 400G optics on a duplex SMF pair, FR4 combines four 100G PAM4 lanes on CWDM wavelengths. Edgecore's ET7502-FR4 uses duplex LC. LR4-6 under IEEE 802.3cu and LR4-10 under the 100G Lambda MSA also combine four wavelengths onto one pair.

A module labeled 400G LR4 may meet IEEE LR4-6 or MSA LR4-10. IEEE LR4-6 specifies at least 6 km. MSA LR4-10 specifies 10 km. The modules at both ends of the link must support the planned distance and complete path loss, including connectors and patch panels. A short route can still exceed a module's loss budget.

400ZR uses a single optical carrier with dual-polarization 16-state quadrature amplitude modulation, or DP-16QAM. OIF defines amplified applications for links of 120 km or less, with a minimum target reach of 80 km.

The planned route must meet the selected modules' loss and dispersion limits and their optical signal-to-noise ratio, or OSNR, requirement. OIF's separate unamplified application is limited by optical loss. A 400ZR module uses RS(544,514), commonly called KP4, on its host interface and concatenated FEC, or C-FEC, on the optical connection between 400ZR modules.

Edgecore's ECPO-QDDZR400G is tunable across the C-band wavelength range and has duplex LC receptacles. Work out the route's loss budget and amplifier requirements.

800G Modules Can Need Different Patch Cables

For an 800G link, Arista's LPO DR8 and NVIDIA's MMS4X00-NM twin-port DR8 need different patch cables despite using 16 fibers each. The 802.3df DR8 interface uses eight 100G PAM4 optical lanes over eight SMF pairs. Arista's and NVIDIA's implementations operate near 1310 nm.

Arista's LPO DR8 has one MPO-16 APC connector. The MMS4X00-NM has two MPO-12 APC connectors, each serving a 400G link on four transmit and four receive fibers. The LPO DR8 also needs a host platform and software release qualified for that module.

800G 2FR4 combines two four-wavelength 400G links in one module. Each uses CWDM wavelengths and a duplex SMF pair for 2 km. Arista's implementation has two duplex LC connectors. Before ordering a 2FR4 module, confirm its optical connectors and choose matching patch cables.

Arista's 800G 2FR4 cannot break out into eight separate 100G optical links, even if the switch has eight configured 100G subports. For that split, Arista's parallel 2XDR4 has two four-lane 400G optical interfaces and can connect to eight 100G FR modules at up to 2 km.

The 2XDR4 fanout uses one fiber pair for each 100G FR link. Each branch must meet both modules' optical loss budgets, including its connectors and patch panels.

The P802.3dj task force's 14 March 2024 adopted baselines use four optical lanes for 800G DR4, FR4 and LR4. These designs differ from 802.3df's eight-lane 800G arrangement. A connection between modules needs compatible optical interfaces as well as the same total rate.

FEC Settings Depend on the Cable and Modules

Changing cable or module type at the same port speed can require a different FEC setting. On supported DAC links, auto-negotiation lets the hosts agree on speed and FEC. With pluggable optics, the FEC on the switch-to-module electrical connection can differ from the FEC used over the fiber.

CA-25G-N, CA-25G-S and CA-25G-L are 25G cable classes defined by electrical performance, including signal loss. The cable's EEPROM compliance code can identify its class and the FEC associated with that code. N identifies no FEC, S identifies BASE-R, also called Firecode or FC-FEC, and L identifies RS-FEC.

The host's physical-layer mode, cable class and both ports' supported settings determine which FEC can be used. In these 25G cases, RS-FEC is RS(528,514).

Two cables of the same length can need different FEC settings. NVIDIA's MCP2M00 has both CA-25G-N and CA-25G-L versions at 2.5 m and 3 m. The N version can operate without FEC, while L requires RS-FEC. MCP2M00 cables up to 2 m use CA-25G-N and do not require FEC. NVIDIA’s 4 m and 5 m MCP2M00 cables use CA-25G-L and require RS-FEC.

A CA-25G-N cable can carry a FEC-encoded signal when both hosts support and select the same FEC mode. For 25GBASE-CR hosts, the FEC options depend on the cable class. A 25GBASE-CR-S host has no RS-FEC and cannot use a CA-25G-L cable. With 25GBASE-CR-S hosts, CA-25G-N permits no FEC or BASE-R, and CA-25G-S requires BASE-R. Confirm the FEC setting for the exact cable and both hosts' software releases before using a setting that differs from the cable's datasheet requirement.

Cable classFEC with 25GBASE-CR hosts
CA-25G-NNone, BASE-R, RS(528,514)
CA-25G-SBASE-R, RS(528,514)
CA-25G-LRS(528,514)

Cumulus Linux 5.18 supports FEC negotiation on supported 25G, 50G, 100G, 200G and 400G DAC modes when auto-negotiation is enabled at both ends. Optical interfaces at those speeds do not negotiate FEC across the fiber. Without negotiation, the devices that encode and decode FEC need matching supported codes for the link to come up.

With auto-negotiation enabled on a link type that cannot negotiate, Cumulus 5.18 can try speed and FEC settings locally. This autodetect process does not exchange settings with the far end. If it cannot bring the link up, turn off auto-negotiation and explicitly set supported speed and FEC values at both ends.

Some 100G modules with four 25G NRZ host lanes pass host RS(528,514) through unchanged. Others use host FEC off. Match the host setting to the exact cable or module.

Host interfaces using 50G PAM4 lanes use RS(544,514). One-lane 50G, two-lane 100G, four-lane 200G and eight-lane 400G interfaces use this code.

In Cumulus 5.18, 400G links also use RS(544,514) when carried on four 100G PAM4 lanes. The Ethernet Technology Consortium's eight-lane 800G design combines two 400G physical coding sublayers, or PCS blocks, with always-enabled RS(544,514).

When a DAC or AOC passes FEC codewords through unchanged, the hosts encode and decode end to end. With pluggable optics, both modules must pass the codewords through for host FEC to span the whole link. A module that decodes optical FEC internally can use a different FEC code, or no FEC, on its host connection.

Each link segment covered by FEC needs matching codes at the device that encodes it and the device that decodes it. For an SR8, DR4 or FR4 module, check the host and optical FEC required by its selected operating mode.

In the 400G DR4 breakout, each two-lane 100G connection at the parent uses host RS(544,514). Some remote 100G DR modules decode optical RS(544,514) internally and use CAUI-4, a four-lane 25G NRZ host interface, with host FEC off. That operating mode needs different FEC settings at the parent and remote hosts.

Where a 100G DR module permits optional host KP4 with new hosts, confirm the exact module, electrical interface and host combination.

Arista gives conflicting optical formats for its OSFP-800G-XDR4-G and OSFP-800G-FR4-G. The part-specific descriptions use four 200G PAM4 lanes, while a general note assigns eight 100G lanes to all listed modules. Some modes support an additional error-correction code called inner FEC, while others operate without it. Before choosing remote optics, confirm the optical format and inner-FEC requirement for the exact part and mode.

Cable Routes Affect Space and Delay

Leave room behind the rack door for the cable diameter, connector and bends. NVIDIA's MCP1650-V DAC is thicker than its MFS1S00-V AOC, and the DAC diameter varies with American wire gauge, or AWG. The 0.5 m, 1 m and 1.5 m MCP1650-V cables use 30 AWG. Its 2 m, 2.5 m and 3 m cables use 26 AWG.

CableDiameter
MCP1650-V, 30 AWG7.1 ±0.35 mm
MCP1650-V, 26 AWG9.4 ±0.4 mm
MFS1S00-V AOC3 ±0.2 mm

Thick copper cables can reduce airflow and make a dense rack harder to cable. Compare the cable's diameter and bend radius with the space available behind the equipment.

For a single bend away from the connector, the MCP1650-V minimum radius is 35.5 mm with 30 AWG cable and 47 mm with 26 AWG. Near the connector, use at least 71 mm for 30 AWG or 94 mm for 26 AWG. The 71 mm and 94 mm limits also apply to repeated bends away from the connector.

The MFS1S00-V AOC has a 30 mm minimum radius. Confirm that part's limits near connectors and for repeated bends before routing it.

Before committing an AEC to the route, confirm its minimum bend radius and weight. Cable trays and cable supports must carry the selected cable's weight.

Propagation through InfiniBand and Ethernet cables takes roughly 5 ns per meter. For a timing-critical design, confirm the ordered part's propagation-delay limit.

FEC can add delay beyond propagation through the cable. When latency matters, confirm delay figures for the selected cable, modules and FEC mode. Measure the delay of the complete connection on the intended equipment.

The Switch Must Supply the Required Power

Edgecore's AS9726-32DB supplies up to 24 W on its upper 16 ports and 14 W on its lower 16. Edgecore's ECPO-QDDZR400G draws up to 19 W, so choose the upper 16 ports for that module.

Check the power supply units, or PSUs, for the number and types of modules you plan to install. Include the PSU configuration and input voltage. Specify what the remaining supplies must power if one PSU fails.

Module power classes 1 to 7 have fixed maximum draws, while Class 8 modules report their own maximum. The wattage for each class depends on the form factor. Class 7 has a maximum of 5 W for QSFP+/QSFP28 and 14 W for QSFP-DD (QSFP-DD Hardware Rev 7.1) or OSFP. Compare the module's maximum watts with the port budget as well as its class. Low-power mode caps module consumption under host control. Check how the host releases the module from that mode or enables a higher power class.

Power classQSFP+ / QSFP28 maxQSFP-DD / OSFP max
11.5 W1.5 W
22 W3.5 W
32.5 W7 W
43.5 W8 W
54 W10 W
64.5 W12 W
75 W14 W

QSFP-DD Class 1 stays within the 1.5 W low-power limit, while Classes 2 to 8 use high-power mode. OSFP permits up to 2 W in low-power mode. OSFP class ratings apply in high-power mode, where Class 1 has a 1.5 W maximum.

SFF-8636 defines management for QSFP+/QSFP28 modules and cables. In low-power mode, the host limits these modules to 1.5 W.

For SFF-8636 QSFP+/QSFP28 Classes 2 to 4, the host must release the low-power limit before the module can use its higher class rating. For Classes 5 to 7, the host must release that limit and set the higher-power-class enable bit. Class 8 also needs the low-power limit released, with a separate enable bit from the one used for Classes 5 to 7. Confirm the full enable sequence for the actual Class 8 module.

Under CMIS 5.4, the module's MaxPower field reports its worst-case power consumption over operating conditions and lifetime in 0.25 W steps. The host should use that value when deciding whether to enable high-power operation, rather than relying only on the power class.

Class 8 QSFP-DD and OSFP modules exceed 14 W and report their own maximum. Under SFF-8636, QSFP+/QSFP28 Class 8 instead reports maximum power in EEPROM byte 107 in 0.1 W steps.

NVIDIA's passive MCP1650-V has a 0.1 W maximum. NVIDIA's MCA4J80 linear active cable has a 1.5 W maximum per end. Confirm the ordered active cable's maximum watts per end before assigning it to a port.

NVIDIA's MFS1S00-V AOC draws 4.35 W typical and 4.55 W maximum per end with all lanes retimed. Each port connected to an active cable must supply the maximum watts required at that connector.

Edgecore's ET7502-SR8 has a 10 W maximum power-dissipation rating. Its ET7502-DR4 has a 10 W maximum, and its ET7502-FR4 is also rated for a 10 W maximum. All three Edgecore modules are within a 14 W port's power allowance. The chosen NOS release and switch cooling must also support the module. Arista's 400G OSFP/QSFP-DD AOC, SR8, DR4 and FR4 families have a 12 W maximum. Arista's 400G LR8 family has a 14 W maximum.

Arista's 800G OSFP and QSFP-DD AOCs have a 16 W maximum. The same maximum applies to its 800G 2XDR4, 2PLR4, 2FR4, 2LR4, VSR8 and DR8 families. Those QSFP-DD and OSFP modules require Class 8 because Class 7 allows up to 14 W.

NVIDIA's MMS4X00-NM twin-port DR8 has two 400G optical interfaces in one module. It draws 16 W typical and 17 W maximum for the whole module, so the connected port needs at least 17 W. For this module, Quantum-2 and Spectrum-4 switches need finned-top OSFP shells for cooling. A flat-top variant is offered for DGX-H100.

Arista's pluggable 800G LPO 2DR4, DR8 and 2FR4 optics have maximum power ratings below 9 W. Each host connected to one of these modules needs support for that linear interface.

Arista supports its 800G LPO 2DR4, DR8 and 2FR4 pluggables on specific hardware and releases of EOS, its network operating system. Check the module against that platform and software support list as well as the cage and port wattage. For the 800G LPO AOC, confirm the maximum watts per end before assigning it to ports.

Arista's active copper breakout from 400G to four QSFP28 ends draws up to 10 W at the parent end and 4 W at each remote end. Each QSFP28 port must supply 4 W and enable Class 5 or higher power operation. For the A-D400-4Q100-xM optical breakout, confirm its own per-end maximums before choosing the ports.

NVIDIA's SN6600 provides up to 30 W per OSFP port. OSFP800 is the OSFP speed grade for 100G per lane, with the same mechanical form as OSFP. A module that needs more than 30 W exceeds the SN6600's port budget. It also needs NOS support for its operating mode and firmware, plus adequate switch cooling.

Read Cable and Module Data

A passive QSFP+/QSFP28 cable using SFF-8636 can have powered management circuitry that reports live temperature and voltage. The cable's high-speed data path stays passive while the separate management circuitry draws power.

Paged memory lets the host select different pages of module data. A CMIS 5.4 flat-memory module provides only fixed read-only data, with no live measurements or selectable pages.

In CMIS, media type 03h includes passive and linear active copper. The MediaInterfaceTechnology field is separate from the media type. It distinguishes unequalized copper, passive equalization and linear active equalizers.

SFF-8636 modules use SFF-8024 extended specification compliance codes. A linear active copper cable can report a passive-cable compliance code. That code alone does not identify whether the cable has a linear equalizer. For an SFF-8636 module, read its separate transmitter-technology field to distinguish unequalized copper, passive equalization and linear active equalizers.

In CMIS, retimed active cables use media type 04h. A separate active-cable interface code can indicate a bit error ratio, or BER, limit. Active-cable interface codes 01h through 04h specify BER limits, while undefined and vendor-specific codes do not provide a standardized limit. Those interface codes are a different field from the media type.

SFF-8636 and CMIS each provide a connector-type field and a separate fiber-face-polish field. The connector-type value "No separable connector" identifies an end with no detachable media connection.

CMIS media type 01h identifies MMF optical interfaces, while 02h identifies SMF optical interfaces. An AOC with eight 50G host lanes can report active-cable media type 04h. Read the installed AOC's media type, connector field and application before choosing its port settings.

At each end, the electrical interface reported by the cable or module must be one the attached switch or NIC port supports. The optical interface must suit the fiber type. The module's optical connector and polish must match the fiber cable end plugged into it.

Physical contact, or PC, is another fiber-face polish. The polish code can identify PC/UPC or APC, or leave the polish unspecified. On a module with several optical connectors, check the specification of the connector you will use. For an unspecified code, confirm the receptacle's requirement before choosing the patch cable.

A module with paged management memory can report operating state and live measurements. NVIDIA's MFS1S00-V AOC reports temperature, supply voltage, laser bias, transmit and receive optical power, and warning and alarm thresholds. Use the installed part's warning and alarm thresholds when locating a fault.

Bring Up and Test the Link Before Service

Before mating detachable fiber connections, follow the module manufacturer’s cleaning procedure. Use the connector polish required by each module, and mate pinned MPO connectors with unpinned ones.

For a breakout connection that stays down, start with the cable's electrical format and EEPROM coding. Check each cable end's lane count and modulation against the requirements of the port it plugs into, including the parent port mode. On a CMIS module, read the advertised applications, selected application and lane assignments. The NOS release must support the module and port mode.

If a module stays in low-power mode, compare its maximum draw with the port budget. Check the NOS support for that module's application and firmware, then read the module temperature if the part exposes it. The switch must also keep the module within its operating-temperature limit.

After a FEC change, check each host's configuration against the cable or module specification for the selected electrical interface and operating mode. If the cable or both optical modules pass FEC codewords through unchanged, the hosts need matching codes. If a module decodes optical FEC internally, its host connection can need a different code or no host FEC.

For a cable that decodes and re-encodes FEC, confirm the host FEC setting at each end and which FEC segments it terminates or passes through. Use those per-end requirements when comparing the hosts' settings.

In Cumulus 5.18, read the operational FEC after the link comes up. A down link can show None/Off even when RS-FEC is configured. While the link is down, compare the configured settings at both ends. A configured Auto value does not identify the code currently being tried.

For an optical link with no usable receive signal, compare the optical interface types at both ends and the required MMF or SMF first. Use the module's lane-to-fiber map to check transmit-to-receive polarity. If the link flaps or accumulates errors, inspect bends and connector seating, and read receive power and temperature where available.

Record the error counters before sending traffic, then read them again after the test interval to measure the increase. In Cumulus 5.18, counters can retain old errors after a link transition. Watch whether the counts keep increasing during traffic. Where an enabled FEC decoder exposes corrected and uncorrected counters, read both and identify the device doing the decoding.

Corrected counts show that FEC has repaired errors. A corrected error alone does not establish that a link has failed. Before testing, agree on acceptance limits for the selected interface and products. Compare the corrected counts with those limits. Investigate uncorrected errors and interface errors that keep accumulating during traffic.

Record the hardware and software versions, port modes and cable length. Include configured FEC at each host and operational FEC where that host reports it. Add the traffic load, test duration and error counts from your network. Keep that record so the same test can be repeated after a firmware or hardware change. Put the connection into service after the complete link passes the traffic test on your network.

Choose the Cable Before Ordering

Choose a passive DAC for a short direct link when both ports support its electrical format and length. If the route exceeds that passive-copper limit, choose an active cable supported by every attached port. To connect different electrical formats, use a copper gearbox cable, a lane-converting AOC or compatible pluggable optical modules.

For Edgecore links, use the 400G guide when choosing port power and optical breakout. Use the SONiC supported platforms page to find releases containing platform code for the switch. Confirm that the actual SONiC image supports the module and port mode before ordering.

Before ordering, record the product number and hardware revision of each switch or NIC. Include the NOS and firmware releases. Specify the speed, electrical lane count, per-lane rate and modulation at each end. For a breakout, add the parent port mode and each remote end's lane assignment. Confirm support for that exact combination.

Record the routed length, including slack, and each port's length limit. Include the maximum power draw at every cable end and the power available at its port, plus the airflow direction and ambient temperature. Identify the FEC code and the devices that encode and decode it on each segment, from host to host, host to module or module to module.

Choose an AOC when replacing the entire cable assembly is acceptable. Use pluggable optics for a route through optical patch panels or when fiber and modules need separate replacement. Match the optical interfaces, fiber and connectors before comparing reach, and include patch panels and connections in the loss budget. Settle the lane format, routed length, power and FEC requirements before placing the order.

Hardware Nation is a partner of Accton/Edgecore, Arista and NVIDIA.

Alex Cronin

Alex Cronin is the founder of Hardware Nation and Nanites AI. He is a graduate of Georgia Tech with 20 years of experience in networking and data center infrastructure across enterprises, service providers and hyperscalers. His work spans traditional and open networking, production SONiC deployments, multivendor integration and direct collaboration with manufacturers and engineering teams. Hardware Nation has served organizations including NASA, Lockheed Martin, Accenture, Stanford University and Georgia Tech.

Alex leads engineering teams and contributes directly to architecture, code, integration and evaluation. At Nanites AI, he has led nearly two years of development of an agentic NetOps platform for network troubleshooting. He also develops AI automation for product research and leads business operations at Hardware Nation.

Nanites AI has been cited in Gartner’s Market Guide for Agentic NetOps Software, covered by InformationWeek and discussed by Cisco DevNet. It was selected as one of 12 finalists from more than 400 applicants in the 2025 T Challenge, organized by T-Mobile and Deutsche Telekom. Alex has presented his work at Deutsche Telekom in Bonn, CableLabs and Network X Americas.