Edge-Core EXP100-32X 32x100G QSFP28 Ports Data Center Switch

Community SONiC and Xsight OS. ONIE is preinstalled, and Community SONiC is the open-source NOS option. Edgecore MACH NOS support for the EXP100-32X is planned for Q4 2026. Other NOS options may be available as the ecosystem evolves.

The Xsight Labs X2, a fully programmable chip. On the EXP100-32X it delivers 3.2 Tbps full-duplex throughput.

Yes. Each of the 32 QSFP28 ports can break out to 2 x 50G, 4 x 25G or 4 x 10G with breakout cables.

Edgecore designed it for data center, cloud and AI networks. Its X2 hardware supports programmable congestion signaling and congestion-aware load balancing, including flowlet-based load balancing and packet spraying. The features available in your deployment depend on the NOS and software release you choose.

Front-to-back, with 5+1 hot-swappable redundant fans.

Yes. Two redundant, load-sharing, hot-swappable AC power supplies (90 to 240 VAC).

Through an RJ-45 serial console port and an RJ-45 1G management port. There is also a USB storage port. A BMC is optional.

An Intel Xeon D-1713NTE (4 cores, 2.2 GHz), 32 GB of DDR4 ECC memory and a 1 TB M.2 NVMe SSD.

All three use the same Xsight Labs X2 chip and Intel Xeon CPU in 1RU. The EXP100-32X has 32 x 100G QSFP28 ports (3.2 Tbps). The EXP400-32X has 32 x 400G QSFP112 ports and the EXP800-16O has 16 x 800G OSFP ports, both 12.8 Tbps.

It’s a programmable alternative for a Tofino-based deployment. The EXP100-32X uses Xsight X2 with 32x100GbE QSFP28 ports and 3.2Tbps switching capacity. X2 uses a programmable instruction set with parallel execution. Moving from Tofino is a platform migration: the forwarding software and control-plane integration need to be adapted for X2. It isn’t a drop-in hardware or software replacement.

P4 applications can be ported to Xsight X2 using its P4 compiler and X-SDK development toolchain. The forwarding code and control-plane integration need to target X2; existing Tofino binaries are not interchangeable. Oxide has completed a Tofino 2-to-X2 migration of its P4 forwarding code. Custom P4 development uses the X2 toolchain separately from installing a standard NOS image.