OcNOS feature & hardware coverage report
What OcNOS covers, which standards it implements, and the hardware it is qualified on. Every figure below is pulled straight from the OcNOS Feature Matrix and Hardware Compatibility List that IP Infusion publishes and maintains, last refreshed 7 August 2026.
At a glance
Source: OcNOS Feature Matrix dataset (schema v3), refreshed 2026-08-07, and the OcNOS Hardware Compatibility List.
Feature coverage by category
OcNOS groups its documented features into 13 functional categories and 65 subcategories. Routing, MPLS, and Carrier Ethernet make up the core of the catalog, reflecting the platform's service-provider heritage, while newer categories such as segment routing and AI fabric round out modern data-center and transport roles.
| Category | Examples |
|---|---|
| Layer 3 Routing | BGP, OSPF, IS-IS, VRF, BFD, policy routing |
| MPLS | LDP, RSVP-TE, L2VPN/L3VPN, TE, FRR |
| Carrier Ethernet | EVCs, ELINE/ELAN/ETREE, OAM, MEF services |
| Layer 1 & 2 | VLANs, LACP, STP/RSTP/MSTP, xConnect |
| Management & Automation | NETCONF/YANG, gNMI, telemetry, ZTP, Ansible |
| Multicast | PIM-SM/SSM, IGMP/MLD, MVPN |
| Hardware | platform, optics, sensors, resiliency |
| VXLAN & EVPN | EVPN-VXLAN, multihoming, symmetric IRB |
| Segment Routing | SR-MPLS, SRv6, Flex-Algo, TI-LFA |
| QoS | classification, queueing, shaping, WRED |
| Security | ACLs, DHCP snooping, IP source guard, storm control |
| Timing & Sync | IEEE 1588v2 PTP, SyncE, ToD |
| AI Fabric | RoCEv2, PFC/ECN, DLB |
Standards posture
Open networking only delivers interoperability if the software actually implements public standards. About seven in ten documented OcNOS features reference a public standard (an IETF RFC, ITU-T or IEEE), and the rest are IP Infusion enhancements such as hardware-accelerated OAM and proprietary resiliency options. The Feature Matrix marks which is which, feature by feature.
Standards-referenced
Implement an IETF RFC, ITU-T or IEEE standard for multi-vendor interoperability.
IP Infusion enhancements
Value-add capabilities beyond the base standards, such as accelerated OAM and resiliency options.
Hardware coverage
OcNOS is qualified on 44 open networking platforms from three open-hardware vendors, Edgecore, UfiSpace, and Celestica, split across 26 service-provider and 18 data-center systems. Those platforms are built on 17 distinct Broadcom ASICs spanning four silicon families, so a feature qualified once carries across competitively sourced boxes rather than locking you to a single vendor.
| Silicon family | ASICs in the HCL | Platforms | Typical role |
|---|---|---|---|
| Jericho | Jericho2C+ | 2 | Deep-buffer SP edge and aggregation routing |
| Qumran | Qumran 2A, 2C, 2C+, 2U, AX, MX, UX | 24 | Service-provider routing, cell-site and access |
| Trident | Trident3 (X2/X4/X5/X7), Trident4 | 12 | Data-center leaf, top-of-rack and out-of-band management switching |
| Tomahawk | Tomahawk 2, 3, 4, 5 | 6 | High-radix data-center and AI-fabric spine |
| All Broadcom | 17 ASICs · 4 families | 44 | SP routing, DC and AI fabric, edge |
License model
OcNOS is licensed in five tiers, so operators pay for the protocol set a role actually needs rather than one monolithic bundle. Tiers stack from a Layer 2/3 base up to a full carrier-grade superset and are mapped per platform capacity in the feature matrix.
| Tier | What it adds |
|---|---|
| IPBASE | Layer 2/3 base: switching, IPv4/IPv6 routing, OSPF/BGP, management. |
| MGMT | Management and automation add-on: programmability and telemetry. |
| MPLS | MPLS transport: LDP, RSVP-TE, L2VPN/L3VPN, traffic engineering. |
| CSR | Cell-site router profile: mobile backhaul, timing, and synchronization. |
| PLUS | Full carrier-grade superset, including segment routing and advanced services. |
How this report is produced
This is original data, not a marketing estimate. IP Infusion maintains a structured feature-support dataset and a hardware compatibility list, both published as live, browsable tools.
- Source of record: the OcNOS Feature Matrix dataset (schema v3), which records per-feature support across license tiers and qualified platforms, refreshed 7 August 2026.
- Categories group the documented entries in that dataset by function; subcategory granularity de-duplicates features that appear under more than one use case.
- Standards posture reflects whether each feature entry references a public standard (IETF RFC, ITU-T, IEEE) versus an IP Infusion enhancement.
- Hardware coverage is drawn from the Hardware Compatibility List: 44 qualified platforms, their Broadcom ASIC, and their qualified OcNOS release.
Figures are derived from IP Infusion's own OcNOS Feature Matrix and Hardware Compatibility List as of 7 August 2026 and describe documented feature support for shipping OcNOS releases; consult the live tools for the authoritative, per-platform detail. Broadcom, Jericho, Qumran, Trident, and Tomahawk are trademarks of Broadcom Inc.; other product and company names are the trademarks of their respective owners and are used for identification only.