What Is Open Networking?
Open networking separates switch hardware from its network operating system (NOS), so a network team can choose them separately. The software still has to support the exact switch and the features required on your network.
What Open Networking Separates
Network disaggregation means separating network hardware from software. The NOS runs routing protocols, controls the switching ASIC and provides the CLI and APIs, while the hardware supplies the ports, CPU, ASIC, power and cooling.
White box switches are commonly offered for use with a separately chosen NOS. Bare metal usually describes hardware supplied without a production NOS. It can include the Open Network Install Environment (ONIE), which finds and runs the NOS installer. Vendors use these terms differently, so check what comes with the white box switches you are considering. Our white box switch guide explains the distinction.
Merchant silicon is a switching ASIC that a chip manufacturer sells to switch vendors. Broadcom’s Tomahawk and Trident families are examples. NVIDIA uses Spectrum ASICs in its own switches, and Cisco also uses them in the N9100 series. Switches with the same ASIC still need the correct software and platform support.
Commercial software is also an option. Choosing hardware and software separately does not require an open source NOS.
How the Hardware and Software Work Together
The NOS must control both the switching ASIC and the other components in the switch. SONiC uses the Switch Abstraction Interface (SAI) to program the ASIC through a common API.
Each ASIC manufacturer supplies its own SAI implementation for its chips. A SONiC image is built for one ASIC manufacturer’s chips and includes the drivers and settings for the switches it supports. Available features depend on the chip, its SAI implementation and the NOS release.
| Component | What It Does | SONiC Example |
|---|---|---|
| Switching ASIC | Forwards transit traffic in hardware | Forwarding entries programmed through SAI |
| ASIC manufacturer’s SDK and SAI implementation | Program the ASIC through chip-specific code | SAI library called by syncd |
| NOS services | Run routing protocols and maintain control plane state | FRRouting (FRR) for routing, and orchagent for converting routes and settings into SAI objects |
| Platform APIs and drivers | Monitor and control switch components | Fans, power supplies, sensors and transceivers |
| Management and automation | Configure the switch and collect operational information | CLI, SNMP and gNMI streaming telemetry |
FRR runs the routing protocols and passes its best routes to fpmsyncd, which writes them to SONiC’s application database, APPL_DB. orchagent converts them into SAI objects and writes them to ASIC_DB, the ASIC state database. syncd reads that database and calls the ASIC manufacturer’s SAI library to program the ASIC.
The ASIC normally forwards transit traffic in hardware. Packets for the switch itself, such as its BGP sessions and LLDP, are sent to the CPU, where Linux passes them to the BGP and LLDP services. Packets can also be sent to the CPU for exceptions such as an expired TTL.
An open source NOS can still depend on proprietary code. Some SDKs and SAI implementations used by SONiC are distributed as binaries under the ASIC manufacturer’s licensing terms.
Installing the NOS
ONIE combines a boot loader with a small operating system that discovers and runs a NOS installer. After installation, subsequent boots normally go directly into the NOS.
ONIE stays on the switch so that a different NOS can be installed later. Upgrades between SONiC releases are normally installed from SONiC itself.
ONIE does not establish whether a particular feature or optic works with the installed software. It is also not the only installation method. The Arista switches covered by the SONiC Project’s platform list use Arista’s own boot loader, Aboot, instead of ONIE.
What Changes for the Buyer
Teams can keep a common SONiC software stack across supported switches from multiple vendors. They can also automate configuration and monitoring through the APIs in the SONiC image they run.
With a traditional switch, the same vendor normally supplies the hardware and its NOS together. Disaggregation lets you select them separately, but someone still has to qualify the combination, maintain it and resolve faults.
Your team, a support partner or a vendor offering the complete system can do that work. Edgecore offers its own distribution of community SONiC, with support, on its switches. IP Infusion OcNOS Systems is another option, with disaggregated hardware and software covered by a single support contract.
| Decision | What to Check |
|---|---|
| Hardware and software choice | Whether the chosen switch, ASIC and NOS release support the features you need |
| Support | Who takes the first support call and is responsible for resolving faults that could involve hardware, drivers or the NOS |
| Upgrades | Which software and firmware combinations are supported, and how you will test an upgrade |
| Operations | Who will configure, monitor and troubleshoot the switches |
| Cost | Hardware, software licenses, support, and the work needed to test and operate the system |
Buying hardware and software separately is not automatically cheaper. Compare the complete cost with the traditional alternative, including the skills and time your team will need.
A separately purchased NOS still has to work with the switch hardware and firmware. Check compatibility before changing the NOS, firmware or hardware.
Choose the Switch, NOS and Support Together
Community SONiC is open source and supported through its community. You can run it with your own team, buy support for a particular SONiC image or choose a vendor’s SONiC distribution. Check who builds the image, which releases they maintain and what the contract covers.
NVIDIA Pure SONiC is NVIDIA’s supported SONiC offering for Spectrum switches, built from a community SONiC release. Confirm which image and release NVIDIA will support.
NVIDIA Cumulus Linux 5 runs only on NVIDIA Spectrum switches, so choosing it also means choosing NVIDIA hardware. Our Cumulus Linux article covers that hardware and software choice.
Other choices include IP Infusion OcNOS on qualified hardware and Pica8 PicOS on its verified platforms. Each has its own hardware compatibility and support requirements.
Start with the features and support you need. Choose the NOS, switch and ASIC together, then confirm that the organization providing support covers the combination.
For SONiC, use the supported platforms page as a starting point, then check the exact image and switch with the organization providing support. A switch appearing on a project list or in a SONiC release does not mean a vendor supports that switch and software combination or has tested the features you need.
Open Networking and SDN
Software defined networking (SDN) separates network control from forwarding and makes that control programmable and logically centralized. Open networking concerns whether switch hardware and the NOS can be chosen separately.
Like a traditional switch, an open networking switch can run its own routing protocols, such as BGP, on its CPU without an SDN controller. Using a controller is a separate decision from choosing the switch and NOS.
How Open Networking Developed
OpenFlow came from campus network research and made switch flow tables programmable from a remote controller, and it later became a foundation of SDN. ONIE gave bare metal switches a common way to install a NOS. SAI provided a common API for switching chips, and SONiC built on it as an open source NOS that Microsoft runs in its own data centers.
| Year | Development |
|---|---|
| 2008 | Researchers published OpenFlow, describing remotely controlled flow tables on Ethernet switches. |
| 2011 | Deutsche Telekom, Facebook, Google, Microsoft, Verizon and Yahoo founded the Open Networking Foundation to develop SDN and OpenFlow. |
| 2012 | Cumulus Networks created ONIE. |
| 2013 | The Open Compute Project adopted ONIE. |
| 2014 | OCP adopted Open Network Linux as its reference NOS. |
| 2015 | OCP accepted Microsoft’s SAI specification in July. |
| 2016 | Microsoft contributed SONiC as open source. |
| 2019 | The Linux Foundation launched DENT for networking at the enterprise edge, including campus and remote locations. |
| 2020 | NVIDIA acquired Cumulus Networks. |
| 2022 | SONiC moved to the Linux Foundation. |
Open Networking in Data Centers and AI
SONiC runs in large production data centers, including Microsoft’s. Vendors also offer it for the back-end networks that connect GPUs.
Edgecore’s AIS800-64D is an AI switch with SONiC as a software option. Cisco also offers validated SONiC on selected Nexus 9000 switches with Cloud Scale ASICs and on N9100 switches built on NVIDIA Spectrum-X for back-end AI networks. Cisco TAC supports the hardware and NOS together.
For RoCEv2 (RDMA over Converged Ethernet) traffic between GPUs, check how the switches use ECN to signal congestion to the NICs and whether the design also uses PFC to prevent packet loss. Test the settings, telemetry and failure recovery with the firmware and NOS you intend to deploy.
The Ultra Ethernet Consortium (UEC) develops Ethernet specifications for AI and high performance computing. Its current published specification is version 1.1, released on 12 October 2026.
A NOS hardware compatibility list does not show whether the NICs and switches in a GPU network support the UEC features you need. Check which UEC version and profile, if any, each NIC supports, and which UEC features each switch supports.
Software choice also does not remove component shortages. Switches from different vendors can use the same merchant ASIC family, so changing brands may leave you dependent on the same chip.
Our article on switch lead times into 2027 explains the current supply constraints. Confirm delivery dates for the exact switches, optics and cables you intend to order.
Before You Order
Choose a NOS and switch that provide the features you need, with support that covers both. Test the features, optics, failure recovery and upgrade process you will use on your network before committing to a deployment.
Get clear answers to these questions before ordering. Ask for the hardware and software details in writing so you can check that the proposed system matches what you tested.
- Which exact switch, ASIC, hardware revision, firmware and NOS release are supported together?
- Are the required features, optics and cables qualified for that combination?
- Who takes the first support call, and who is responsible for resolving faults involving both hardware and software?
- Which licenses, updates and support terms are included?
- What skills and tools will your team need to operate the switches?
- When can each part of the order arrive?
Hardware Nation is a partner of Accton/Edgecore, Arista and NVIDIA.
Alex Cronin, Solutions Architect
LinkedIn | GitHub
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.