Choose Edgecore's own optics if you want the switch and modules from one vendor. Optics from other manufacturers are another option when Edgecore or the module manufacturer documents the exact switch, module and NOS combination, or when Edgecore qualifies it.
In its March 2024 Community SONiC case study, Edgecore says its solutions are validated with optics and cables from Edgecore and other industry sources, and offers qualification services for 400G optics. That statement names no switch, module part number or NOS release.
This guide covers the AS9716-32D, AS9726-32DB, AS9726-32DBS, AS9736-64D and AS9737-32DB in the Edgecore 400G switch family. It does not cover the EXP400-32X or the 800G switches.
Documented means the named manufacturer or standards source describes the capability. Inference means a conclusion drawn from those documents or the code versions cited here. Unresolved means the evidence does not establish that a combination works. Hardware Nation has not tested the combinations described in this guide.
Start With the Switch and Port
These switches use eight electrical lanes for a 400G connection, with 50G PAM4 signalling per lane. These are nominal Ethernet rates, excluding overhead. Edgecore calls some of these ports QSFP56-DD, meaning QSFP-DD ports using those lane rates.
The AS9716-32D's lane arrangement is an inference from its chip and port configuration. Power in the table is the electrical power each port is rated to supply to a module.
| Switch and source | ASIC | 400G ports and host lanes | Power budget per port |
|---|---|---|---|
| AS9716-32D, R11 | Tomahawk 3 | 32 QSFP-DD ports. Eight 50G PAM4 lanes per port is an inference. | Not stated in R11. The budget remains unresolved. |
| AS9726-32DB, R07 | Trident 4 | 32 QSFP56-DD ports, eight 50G PAM4 lanes each | 24 W on the 16 ports in the top row, 14 W on the 16 in the bottom row |
| AS9726-32DBS, R03 | Trident 4 | 32 QSFP56-DD ports, eight 50G PAM4 lanes each | 24 W on the 16 ports in the top row, 14 W on the 16 in the bottom row |
| AS9736-64D, R04 | Tomahawk 4 | 64 QSFP56-DD ports, eight 50G PAM4 lanes each | 24 W on ports 1 to 4, 29 to 36 and 61 to 64. All other ports are rated at 13 W. |
| AS9737-32DB, R02 | Tomahawk 4 | 32 QSFP56-DD ports, eight 50G PAM4 lanes each | 24 W on the 16 ports in the top row, 14 W on the 16 in the bottom row |
On the AS9726 variants and AS9737, Edgecore calls the top physical row the upper 16 ports and the bottom physical row the lower 16 ports. Confirm the port numbers on the front-panel label.
The following hardware capabilities are documented by Edgecore. Each breakout still needs support in the chosen NOS image and the intended cable or optic.
| Switch | Breakouts documented by Edgecore | Coherent optics | Airflow and switch operating temperature |
|---|---|---|---|
| AS9716-32D | 4 × 100G and 4 × 25G. R11 does not establish 2 × 200G. | R11 and the compatibility filter list no ZR or ZR+ module. Per-port power is not stated. | Front to back and back to front, 0 to 45 °C |
| AS9726-32DB | 2 × 200G, 4 × 100G, 4 × 25G and 4 × 10G | Edgecore documents ZR/OpenZR+ on the 16 ports in the top row. | Front to back, 0 to 45 °C. Back to front, 0 to 35 °C. |
| AS9726-32DBS | 2 × 200G, 4 × 100G, 4 × 25G and 4 × 10G | Edgecore documents ZR/OpenZR+ on the 16 ports in the top row. | Front to back, 0 to 45 °C. Back to front, 0 to 35 °C. |
| AS9736-64D | 2 × 200G, 4 × 100G, 2 × 50G, 4 × 25G and 4 × 10G | Edgecore's product page and filter together list ZR and ZR+. R04 does not state coherent support or identify ports for that use. Only the 24 W ports are rated for the cited modules' maximum power, an inference. | Front to back only in R04. 0 to 40 °C at sea level, 0 to 35 °C at 1,828 m. |
| AS9737-32DB | 2 × 200G, 4 × 100G, 4 × 25G and 4 × 10G | Edgecore documents ZR/OpenZR+ on the 16 ports in the top row. | Front to back, 0 to 45 °C. Back to front, 0 to 30 °C. |
No 8 × 50G breakout is documented in these datasheets or the inspected Edgecore platform files. Do not choose an eight-way cable from the cage's lane count alone.
Edgecore's datasheets also name the following 400G optics and cables for each switch. Edgecore directs readers to its website for additional parts, so check these lists alongside its compatibility filter.
| Switch | 400G types in the switch datasheet |
|---|---|
| AS9716-32D | SR8, DR4, FR4, DAC and AOC |
| AS9726-32DB, AS9726-32DBS and AS9737-32DB | FR4, ZR, DAC and AOC |
| AS9736-64D | FR4, DAC and AOC |
Choose the Optical Interface
The electrical connection to the switch and the optical connection to the fiber can use different lane arrangements. A DR4 module, for example, converts eight 50G electrical lanes into four 100G optical lanes.
The table describes optical interfaces and specific module implementations. It does not establish Edgecore switch compatibility. Multimode fiber is shown as MMF and single-mode fiber as SMF. Reach is nominal and depends on the specified fiber and optical loss budget.
| Optical interface | Optical lanes and modulation | Wavelengths | Fiber and connector | Nominal reach |
|---|---|---|---|---|
| 400GBASE-SR8 | Eight 50G PAM4 lanes | 850 nm | Eight MMF pairs, MPO-16 APC in Edgecore's module | 100 m on OM4 |
| 400GBASE-SR4.2 (BiDi) | Eight 50G PAM4 lanes on four MMF pairs. Each fiber carries one wavelength in each direction. | Near 850 and 910 nm | Four MMF pairs, MPO-12 | 70 m on OM3, 100 m on OM4, 150 m on OM5 |
| 400GBASE-DR4 | Four 100G PAM4 lanes | Around 1310 nm | Four SMF pairs, male MPO-12 APC in Edgecore's module | 500 m |
| 400GBASE-FR4 | Four 100G PAM4 wavelengths | Around 1271, 1291, 1311 and 1331 nm | Duplex SMF, duplex LC | 2 km |
| 400GBASE-LR4-6 | Four 100G PAM4 wavelengths | CWDM grid around 1270 to 1330 nm | Duplex SMF, duplex LC in module implementations | 6 km under IEEE 802.3cu |
| 400G-LR4-10 | Four 100G PAM4 wavelengths | CWDM grid around 1270 to 1330 nm | Duplex SMF, duplex LC in module implementations | 10 km under the 100G Lambda MSA |
| 400ZR | One coherent carrier using DP-16QAM | Tunable C-band | Duplex SMF, duplex LC in Edgecore's module | Up to 120 km for the specified amplified point-to-point applications. Unamplified reach is loss limited. |
| OpenZR+ | At 400G, one coherent carrier using DP-16QAM in Edgecore's module | Tunable C-band | Duplex SMF, duplex LC in Edgecore's module listing | Unresolved for a particular link. Edgecore advertises 400 km+ amplified, which requires a line-system design. |
The SR4.2, LR4-6 and LR4-10 rows describe interface specifications. They do not identify modules documented for use with these switches. No Edgecore module or switch datasheet cited here lists those three interfaces.
A module offered as 400G LR4 may meet IEEE 400GBASE-LR4-6, the 100G Lambda MSA 400G-LR4-10, or both. IEEE specifies 6 km with a loss budget equivalent to a 10 km link, while the MSA specifies 10 km. Unless both ends are rated for 10 km, plan for 6 km and check the complete loss budget.
For 10 km, IEEE also defines 400GBASE-LR8 on eight wavelengths, and Edgecore offers a 400G PLR4 module for parallel SMF. Neither appears in the checked filter views for these switches, so confirm the exact switch and NOS combination before choosing either.
When choosing 400G optical transceivers, match the interface at both ends. SR8, DR4 and FR4 need different fiber arrangements and connectors, so check polarity, polish and the loss through the complete cable plant.
Check Port Power for Coherent Optics
Edgecore's 400ZR module has a maximum power consumption of 19 W. Its OpenZR+ module has a maximum of 21.5 W in 400G OpenZR+ mode and 19.1 W in 400ZR mode.
These figures exceed the 13 W and 14 W port ratings, so those ports are not rated for either module. This conclusion follows from the published power budgets. On a 24 W port, also confirm software support, module firmware, cooling and Edgecore's qualification of the exact combination.
Edgecore documents ZR/OpenZR+ on the top row of the AS9726-32DB, AS9726-32DBS and AS9737-32DB. The AS9716-32D R11 datasheet and the checked compatibility filter do not list coherent optics for that switch. The R11 datasheet also gives no per-port power budget.
In Edgecore's SONiC 202311.X source, the transceiver daemon (xcvrd at 7035c7a) switches the module to high-power mode without comparing its power class with the port budget. Do not rely on that code to stop a module that exceeds the rating.
On the AS9736-64D's 13 W ports, a Class 7 module may draw up to 14 W. Check its declared maximum as well as its power class. Edgecore's SR8, DR4, FR4 and AOC modules cited here are rated below 10 W.
A ZR+ module can support 400ZR and OpenZR+ while using the same 400G electrical interface to the switch. Each advertised application describes a module operating mode. The inspected SONiC selectors choose the first advertised application that matches the host lane count and speed. The inspected configuration paths provide settings for channel frequency and transmit power, but do not provide a way to choose the optical operating mode.
Confirm which optical application the NOS selects, then set the channel frequency and transmit power for the line system. Both ends must run the same optical mode and its line FEC, C-FEC for 400ZR or OFEC for OpenZR+.
DAC, AEC and AOC Cables
A passive direct attach cable (DAC) connects the electrical lanes through copper. An active electrical cable (AEC) adds active electronics, while an active optical cable (AOC) has optical conversion at each end with fiber between them.
| Cable | Documented length or limit | Compatibility status |
|---|---|---|
| Edgecore ET7502-DAC | Ordering options stop at 2.5 m | Documented by Edgecore, subject to the switch's own limit |
| 400G DAC on AS9736-64D 24 W ports | Up to 2.5 m | Documented by Edgecore R04 |
| 400G DAC on AS9736-64D 13 W ports | Up to 1 m | Documented by Edgecore R04 |
| Edgecore ET7502-B4D breakout DAC | 1 m and 2 m ordering options | Documented by Edgecore. Confirm the port modes at both ends. |
| 400G AEC | One AEC manufacturer documents QSFP-DD to QSFP-DD ordering options from 1 to 3 m. | Not listed by Edgecore in the checked views. Qualification on these switches is unresolved. |
| Edgecore ET7502-AOC | Up to 30 m over OM4 | Documented by Edgecore. Confirm the exact switch and NOS combination. |
On these ports, a passive 400G cable uses the Ethernet Technology Consortium's eight-lane 50G PAM4 interface, 400G CR8. IEEE's 400GBASE-CR4 uses four 100G lanes, which these ports do not provide. SFF-8024 Rev 4.14 distinguishes the interfaces and identifies the consortium's CR8 auto-negotiation specification.
IEEE defines no 400G CR8 interface, so auto-negotiation advertises it through the consortium's extension to IEEE Clause 73. Set auto-negotiation and link training the same way at both ends of a DAC link, and confirm that the chosen NOS lets you set them.
Check the DAC length limit for the port you intend to use. The AS9736-64D has different DAC limits even though all its cages support 400G. The other datasheets state no per-port DAC limit, so confirm the length with Edgecore.
Choose DAC cables or AOC cables by exact part number, length and interface at both ends. For an AEC, also confirm its host interface, electrical power requirements and firmware version.
Check These Six Things Together
The Switch and Port
Use the exact switch name and hardware revision, then identify the port group. The AS9736-64D's 24 W ports are spread across the chassis. Use the port numbers in the table rather than assuming they occupy the top row.
Host Lanes and CMIS Applications
QSFP-DD optics use the Common Management Interface Specification (CMIS). The advertised electrical mode must match the port's configured speed and lane count. A QSFP28 or QSFP+ module in the same cage skips this CMIS selection step.
The inspected SONiC selectors choose the first advertised application with a matching host lane count and speed. The module must also allow the electrical and optical lane assignments used by each port or breakout port.
If these checks fail, the system log can show no suitable app for the port, Invalid lane mask received or Invalid media lane mask received. A matching electrical mode does not establish that the optical interface matches the far end.
The upstream sonic-platform-daemons selector at 591f872e is used by sonic-buildimage 202511 at 3bdc87dd. Edgecore's xcvrd at 7035c7a is used by its 202311.X source at d39662e9. Their handling of other steps differs, including breakout changes while a module is inserted. Confirm the behavior of your own image.
Module Firmware
Record the module firmware version, CMIS version and exact NOS image identifier. The switch can read a module's details correctly and still fail to set it up for the port's speed and lanes.
FEC and Signal Settings
On these switches, the eight-lane 400G, four-lane 200G and two-lane 100G PAM4 host interfaces require RS(544,514) FEC, often called KP4. A 400ZR module also expects RS(544,514) from its host. Set the FEC required by the module at each switch port.
On a DAC or AOC, and on an optical link where both modules pass the FEC through, such as SR8, DR4 or FR4, RS(544,514) runs from one switch port to the other, so both ports must use it. A QSFP28 100G module using four 25G NRZ host lanes can instead require RS(528,514), RS(544,514) or no host FEC, depending on the module and host application.
In the inspected Edgecore device files, signal settings are selected by copper or optical medium and lane speed. Those files have no vendor or part-number keys. No rejection based on module brand was found in that signal-setting path.
This finding is limited to Edgecore sonic-buildimage at d39662e9 and its platform daemon at 7035c7a. It does not establish whether other parts of that image, other SONiC images or OcNOS restrict modules by EEPROM data.
The commands below are present in Edgecore's SONiC 202311.X source, with sonic-utilities at 1dd6bcf4. They have not been run on a switch for this guide.
show interfaces transceiver eeprom
show interfaces fec status
show interfaces counters fec-stats
show interfaces autoneg status
show interfaces link-training status
show interfaces transceiver pmUse the EEPROM output to check the module's advertised applications, the active application on each host lane, its CMIS revision and its active firmware. Adding --dom shows its monitoring data. Use the status commands to check FEC, auto-negotiation and link training. Record counters before and after a period of real traffic. Corrected FEC codewords are normal on 50G PAM4 links, so look for uncorrected codewords and interface errors that keep rising. Link up alone does not complete a compatibility test.
When a module terminates optical FEC internally, host FEC counters describe its electrical host connection. On a coherent module, show interfaces transceiver pm shows the module's pre-FEC and post-FEC BER, OSNR and eSNR.
Breakout at Both Ends
A passive 400G to 4 × 100G cable carries each 100G leg on two 50G PAM4 lanes. Edgecore documents this arrangement for the AS9726 variants, AS9736 and AS9737. On the AS9716-32D, it is an inference from Edgecore's listed breakout cable and its SONiC port configuration.
The far-end port must run 100G on two 50G PAM4 lanes. That passive cable leg will not work with a QSFP28 port using four 25G NRZ lanes or a port using one 100G PAM4 lane.
Optical breakout is different. Edgecore documents 4 × 100G-DR applications for its DR4 module. The port must be in 4 × 100G mode, and the module must advertise a 100G mode on two electrical lanes that allows each breakout port's lane assignment.
Edgecore's DR4 has a male MPO-12 APC receptacle, while 100G-DR modules use duplex LC. Use a female MPO-12 APC to four duplex LC harness or cassette, with polish matching each end and the correct polarity.
A far-end QSFP28 100G-DR transceiver using the CAUI-4 no-FEC host application handles RS(544,514) internally and presents four 25G NRZ lanes to its switch. That port uses no host FEC, while the Edgecore two-lane 100G breakout port uses RS(544,514). Other module applications can use host RS(544,514), so confirm the exact module and host application at each end.
Fiber, Connectors and Reach
Match the optical interface and fiber at both ends. Check connector polish, MPO pin gender and polarity. Include patch panels, splices and connectors in the loss calculation.
SONiC Support Depends on the Image
At upstream sonic-buildimage 202511 commit 3bdc87dd, only the AS9716-32D and AS9726-32D have platform folders from this family. Neither has the platform.json file that SONiC needs for dynamic port breakout. The AS9726 hardware profile also lacks a chip configuration, so its folder name alone does not establish a working image. SONiC uses the platform name AS9726-32D for the AS9726-32DB.
Edgecore offers its own SONiC for the AS9736-64D and AS9737-32DB. Its 202311.X source at d39662e9 and its 202411.0 source at 4c0f49e9 contain AS9716, AS9726, AS9736 and AS9737 platform folders. Its 202505 source at 19920f2a has only the AS9716 and AS9726 folders, so a branch name alone does not establish support for a switch.
The hardware breakout table is not a promise for every image. In Edgecore's 202311.X build files, the AS9736-64D and AS9737-32DB omit the 4 × 25G and 4 × 10G modes described by their datasheets. Its 202411.0 build files add them back for the AS9736-64D only. Which modes the shipped image provides is unresolved.
Confirm the NOS distribution, release and hardware profile for your switch, and verify that they support the port mode you plan to use. For project listings, code and documented commercial releases, use the SONiC supported platforms page.
Check Edgecore's Compatibility List and Support
Edgecore's public compatibility filter shows Edgecore part numbers. It helps identify Edgecore's own modules, but is not a matrix of qualified third-party part numbers.
The filter views for the AS9737-32DB (DCS511) and AS9736-64D (DCS520) do not show ET7502-FR4 or the ET7502-DAC QSFP-DD to QSFP-DD cable, although both switch datasheets list FR4 and 400G DAC. Those views do show Edgecore's 400G breakout DACs. The filter views for all five switches also show Edgecore's SR8 and DR4 modules, which the AS9726, AS9736 and AS9737 datasheet lists do not name.
Use the web filter together with the switch datasheets. Which source reflects the current qualified combinations is unresolved, so confirm any difference with Edgecore.
If a combination needs qualification, ask Edgecore about its qualification service. Confirm who supports the switch, NOS and module together before ordering.
Before You Order
Write down the switch model and hardware revision, port numbers, NOS distribution and release, and exact optic or cable part number. Record the module firmware version if applicable. Include the power class, maximum electrical power, module case temperature range, host lanes, FEC, breakout mode and equipment at the other end.
The Edgecore optics and cables cited here are rated for a case temperature of 0 to 70 °C. Where an optic or cable provides digital optical monitoring (DOM), confirm that the chosen NOS can read it, including temperature when available.
For optical links, specify fiber, connector polish, MPO pin gender, polarity, distance and loss budget. Ask whether Edgecore or the module manufacturer documents the exact combination, or whether it needs Edgecore qualification. Agree who will handle faults involving the hardware, NOS and optics.
Hardware Nation is a partner of Accton/Edgecore.
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.