What Is Open Networking?
Open networking is an approach to building networks in which the network operating system, the hardware and the management tools come from separate suppliers and connect through open, standard interfaces, so operators choose each part on its merits instead of buying one closed system. IP Infusion develops OcNOS, a commercial network operating system, and ships it as software and as complete, validated systems on 40+ open hardware platforms.
What is open networking?
Open networking separates the network operating system from the switch or router hardware. Instead of buying software and hardware locked together from one vendor, you run a network operating system on validated open hardware from multiple manufacturers. That restores competitive hardware sourcing, decouples the hardware refresh cycle from the software, and removes single-vendor lock-in, while keeping a familiar CLI and standard protocols.
Open networking describes the whole approach: open hardware, an independently chosen operating system, and open interfaces for installing, configuring and monitoring it. Network disaggregation is the step that makes it possible, splitting one closed product into parts. The result forwards packets the same way any router or switch does. What changes is who supplies each part, how they are bought, and how often each one can be replaced.
Open networking vs traditional networking
A traditional network is built from integrated systems: each router or switch comes from one vendor with its operating system installed, and the vendor decides which hardware the software runs on. Open networking keeps the same protocols and the same packet forwarding, and changes how the parts are sourced.
| Question | Traditional networking | Open networking |
|---|---|---|
| What you buy | A router or switch with the vendor's operating system installed | Open hardware and a network operating system, sourced as separate layers |
| Hardware choice | The vendor's own product line | Platforms on merchant silicon from several manufacturers |
| Operating system | Tied to the vendor's hardware | Chosen on its own, and it can stay the same when the hardware changes |
| Management and automation | The vendor's CLI and interfaces, consistent across that vendor's products | Standard interfaces such as NETCONF, YANG, gNMI and OpenConfig, consistent across hardware suppliers |
| New silicon | Arrives as a new vendor product, on the vendor's schedule | Arrives as new open hardware under the same operating system |
| Integration and support | The vendor integrates and supports the system | The operator integrates, or a supplier validates and supports the combination as one product |
Both run the same standard protocols, such as BGP, IS-IS and EVPN, so open and traditional equipment can work in the same network and a migration can proceed one role at a time.
Pros and cons of open networking
Open networking changes who does the integration work. The benefits come from choice; the costs come from making separately sourced parts behave as one system.
The open networking stack
An open network is built in three independently sourceable layers. IP Infusion provides the network operating system layer and validates it across the hardware layer.
1. Merchant silicon
The switching and routing ASICs, for example Broadcom Qumran, Jericho, Trident, and Tomahawk.
2. Open hardware
Switches and routers built around that silicon by open hardware manufacturers. OcNOS is validated on platforms from Edgecore, UfiSpace and Celestica.
3. Network operating system
The routing and switching software, for example IP Infusion OcNOS, that turns open hardware into a production router or switch.
Open networking, term by term
Five terms carry most of the conversation about open networking. Each has its own page; the short version is below.
Network disaggregation
Buying the software and hardware of a router or switch separately. It is the mechanism behind open networking, and it moves integration work from the vendor to whoever assembles the parts.
White box switch
A data center Ethernet switch on merchant silicon, sold without a bundled operating system. The operator decides which NOS it runs, in leaf, spine and management roles.
White box router
The routing counterpart for service provider networks: open cell site, aggregation and core routers that run a separately chosen routing operating system.
Network operating system
The software that runs the device: routing protocols, control of the forwarding chip, and the CLI and APIs. In an open network it is the layer that stays constant while the hardware changes.
AI networking switch
A high-capacity data center switch for GPU cluster fabrics, where Ethernet has to carry RDMA traffic without loss. Open AI switches are white box switches sized for that job.
Open network hardware, by role
Open network hardware covers the whole path from the cell site to the data center. The table groups the platforms validated with OcNOS by the job they do. Every one is built on Broadcom merchant silicon by Edgecore, UfiSpace or Celestica.
| Role | Type | Broadcom silicon | Capacity per system | OcNOS edition |
|---|---|---|---|---|
| Cell site router | Open router | Qumran UX, Qumran AX | 32 to 300 Gbps | OcNOS-SP |
| Aggregation and edge router | Open router | Qumran UX, AX, 2U, MX, 2A, 2C | 32 Gbps to 2.4 Tbps | OcNOS-SP |
| Core router | Open router | Qumran 2C, Qumran 2C+, Jericho2C+ | 2.4 to 14.4 Tbps | OcNOS-SP |
| IP over DWDM | Open router or switch | Qumran 2A, 2C, 2C+, Jericho2C+, Trident4, Tomahawk5 | 800 Gbps to 51.2 Tbps | OcNOS-SP, OcNOS-DC |
| Data center leaf and spine | Open switch | Trident3, Trident4, Tomahawk2 to Tomahawk5 | 1.08 to 51.2 Tbps | OcNOS-DC |
| Management network | Open switch | Trident3 X2 | 120 Gbps | OcNOS-DC |
The full list, with every model, port configuration and status, is in the OcNOS Hardware Compatibility List. Per-silicon detail is on the white box router and white box switch pages.
The open standards that hold it together
Parts from different suppliers only work as one network if they meet at shared interfaces. These are the ones that matter most in practice.
- ONIE. The Open Network Install Environment, an installer environment on open switches and routers that lets an operating system from any supplier be installed on the hardware.
- Standard routing protocols. BGP, IS-IS, OSPF, MPLS, segment routing and EVPN are open standards, most of them defined by the IETF, so an open router or switch interoperates with the rest of the network whatever runs it.
- NETCONF and YANG. A configuration protocol and a data modelling language that let automation tools configure devices through structured models instead of screen-scraping a CLI.
- gNMI and OpenConfig. Streaming telemetry and vendor-neutral data models, so monitoring works the same way across hardware suppliers.
OcNOS supports NETCONF, YANG and zero-touch provisioning, and gNMI and OpenConfig streaming telemetry, alongside a CLI in the industry-standard style.
Types of open networking options
Open networking is not one product. The options below differ in how much of the stack is open and who carries the integration and support work. The right one depends on the engineering team you have and how much of that work you want to own.
| Question | Integrated system with open interfaces | Self-integrated open stack | Commercial NOS on open hardware | Validated open system |
|---|---|---|---|---|
| Hardware choice | One vendor | Any open hardware | The NOS supplier's supported list | Named, validated platforms from several manufacturers |
| Operating system | The vendor's own, bundled | Open source or in house | Commercial, licensed separately | Commercial, tested on each platform |
| Who integrates | The vendor | The operator | The operator, with software support | The supplier |
| Who answers a fault | One vendor | The operator, with community or partner help | Software and hardware suppliers separately | One supplier for software and hardware |
| Operator engineering effort | Low | High | Medium | Low |
| Suited to | Single-vendor environments that do not need hardware sourcing flexibility. | Teams with large in-house network software engineering. | Operators with lab capacity to qualify their own hardware. | Operators that want open hardware with one accountable supplier. |
A fifth path applies to networking product companies: they license a commercial network operating system and build it into their own hardware, as with OcNOS for OEMs. For a closer look at the operating system choice itself, see network operating system models compared.
Open networking vendors: who supplies each layer
A list of open networking vendors is really a list of four kinds of supplier. One company can fill more than one role, and the questions to ask differ by layer.
- Silicon vendors design the forwarding ASICs. Every platform validated with OcNOS uses Broadcom merchant silicon from the Qumran, Jericho, Trident and Tomahawk families.
- Hardware manufacturers build open switches and routers around that silicon. OcNOS platforms come from Edgecore, UfiSpace and Celestica.
- Network operating system developers write the routing and switching software, as commercial, open source or embedded products.
- Systems suppliers test the software on the hardware, qualify the optics, and support the combination as one product.
When comparing suppliers, ask for three things in writing: which features run on which hardware model and release, who owns a fault that could sit in either the software or the hardware, and whether the same operating system covers every role you run, from the cell site to the data center.
Open networking solutions from IP Infusion
IP Infusion develops commercial networking software and ships it as complete, validated systems. OcNOS runs service provider routing, data center fabrics and AI fabrics on open hardware, and IP Maestro adds assurance across the network.
This is the combination open networking is built to deliver: hardware, the network operating system, optics, and support are sourced as separable layers, each competed on its own merits, then qualified together by IP Infusion and delivered as one product on one purchase order, one support contract, and one RMA path.
Service provider networks
OcNOS-SP on validated open routers for Tier 2 and Tier 3 ISPs, regional telcos, carriers, and mobile and broadband operators, from cell site to core, including IP over DWDM.
Data center and AI fabrics
OcNOS-DC on validated open switches for large enterprise data centers, MSPs and AI infrastructure: EVPN-VXLAN leaf-spine fabrics and lossless Ethernet for GPU clusters.
OEM partners
Networking product companies embed OcNOS in their own hardware instead of writing a network operating system of their own.
- One software, every role: service-provider routing, data-center and AI fabric, IPoDWDM, and edge, on OcNOS-SP and OcNOS-DC.
- Three ways to buy. OcNOS software for hardware you choose from the HCL, pre-integrated OcNOS Systems ready to deploy, or OcNOS for OEMs built into your own product.
- Published validation. The OcNOS Feature Matrix maps 700+ features to 40+ validated platforms.
- Licence tiers. OcNOS is licensed in tiers named IPBASE, MGMT, MPLS, CSR and PLUS.
Frequently asked questions
What is open networking?
Who are the open networking vendors?
What is open network hardware?
What is an open networking solution?
Is open networking ready for production?
What is the difference between open networking and traditional networking?
What is the difference between open networking and SDN?
Can open networking be used in AI data centers?
Keep reading
- OcNOS-SP for service provider routing and OcNOS-DC for data center and AI fabrics.
- OcNOS Systems: open networking routers and switches, ready to deploy.
- Open NOS options for the data center, compared.
- What is an IP fabric and what is an AI fabric.
- State of Open Networking 2024: from niche to mainstream.
- Open networking: the TCO advantage goes mainstream.
- Why service providers are deploying open networking.
- All technology deep-dives.
Building an open network? Start from the roles you run.
The Hardware Compatibility List shows which validated platforms fit each role, the Feature Matrix shows what runs on each, and an IP Infusion architect can size the rest with you.
Go deeper. Take it with you.
Two short, technical downloads that go further than this page: the full OcNOS-SP datasheet and the full OcNOS-DC datasheet.
OcNOS-SP Datasheet
Full OcNOS-SP specification: the access, cell site and aggregation feature set, software SKUs, supported hardware platforms, and the solution ordering guide.
Get the datasheetOcNOS-DC Datasheet
Full OcNOS-DC specification: the EVPN-VXLAN and Ethernet for AI feature set, software SKUs, supported hardware platforms, and the solution ordering guide.
Get the datasheetOcNOS-SP Datasheet
Quick form. Your PDF opens in a new tab immediately after submit.
✓ Opening your PDF in a new tab…
If it didn't open, use the link below.
OcNOS-DC Datasheet
Quick form. Your PDF opens in a new tab immediately after submit.
✓ Opening your PDF in a new tab…
If it didn't open, use the link below.