Home/Products/OcNOS-SP
Service Provider

OcNOS-SP: the service provider router.

Carrier-grade router software for SR-MPLS, EVPN, Carrier Ethernet, PTP and SyncE timing, and 400G IPoDWDM. IP Infusion ships it as a complete router on 26 qualified Edgecore and UfiSpace platforms, in editions sized to each role from the cell site to the IP core.

Download OcNOS VM SP Datasheet SP Networks Solution
OcNOS-SP core router
$show mpls forwarding-table
FTN-ECMP LDP: Disabled, SR: Enabled
Code FEC Out-Label Out-Intf
i> 10.0.0.2/32 16002 xe1
i> 10.0.0.3/32 16003 xe2
$show bgp summary
BGP router identifier 10.0.0.1, local AS number 65001
Neighbor V AS Up/Down State/PfxRcd
10.0.0.2 4 65001 02w0d21h 14
10.0.0.3 4 65001 02w0d21h 12
$show isis segment-routing state
SR State SR_ENABLED
SRGB Start 16000 SRGB Range 8000
Operational state enabled
$

Complete routers for every SP role.

OcNOS-SP is the software, and IP Infusion ships the complete router. One vendor for the software, the qualified hardware, and the support contract, from the cell site to the IP core.

The complete router, on one PO

Hardware, the OcNOS-SP license, and IP Infusion support on one PO and one support contract. No separate procurement for the software and the bare-metal router, and one vendor answers for both when a link goes down.

One OcNOS family across every SP role

OcNOS-SP editions share one CLI and one automation model across the cell site router, the metro and aggregation nodes, the SR-MPLS core, and the IPoDWDM edge. Each router runs the edition its role needs, with one toolchain for the whole network.

Licensed by edition and capacity

OcNOS-SP comes in IPBASE, MPLS, CSR and PLUS editions, each sized to the platform's capacity. IEEE 1588v2 timing and SyncE are in CSR and PLUS. PLUS also adds initial SRv6 support on selected routers, with more in development.

Pre-loaded and qualified as an OcNOS System

Want it racked and running? OcNOS-SP ships pre-loaded on qualified Edgecore and UfiSpace platforms, tested and shipped by IP Infusion as a complete OcNOS System.

OcNOS Systems

Carrier-grade features on open hardware.

Carrier Ethernet services on open hardware

E-Line, E-LAN and E-Tree services over MPLS and EVPN, with CFM, Y.1731 performance monitoring and a three-level queuing hierarchy for per-service shaping. OcNOS earned MEF 3.0 Carrier Ethernet certification (E-Line, E-LAN, E-Tree) on the UfiSpace S9510-28DC.

TI-LFA Protection

Topology-Independent Loop-Free Alternate computes a loop-free backup path for each protected destination ahead of time. A link or node failure moves traffic to it without waiting for the IGP to reconverge.

Fast Reroute

400G ZR and OpenZR+ in the router

On 7 of the 26 routers, 400G ZR and OpenZR+ coherent pluggables in QSFP-DD ports carry DCI and metro wavelengths from the router itself, without a separate transponder shelf.

IEEE 1588v2 & SyncE for mobile backhaul

PTP boundary clock with the G.8275.1 full on-path and G.8275.2 partial timing profiles, plus SyncE frequency synchronization, on 23 of the 26 routers. 11 routers can also act as a grandmaster with antenna compensation.

Timing

BGP peering and controller export

BGP peering with RPKI invalid-route rejection. BGP-LS exports the IGP and segment routing topology to controllers, and PCEP lets a controller program SR paths.

One support contract: software, hardware, RMA

Buy the router as an OcNOS System and one contract covers OcNOS-SP, the qualified Edgecore or UfiSpace platform, and RMA coordination. One vendor answers for the whole router.

OcNOS-SP routers at every tier.

From internet peering and the SR-MPLS core to the 5G cell site and the IPoDWDM edge, every node is a complete OcNOS router, running the edition its role needs. One CLI and one vendor, from end to end.

OcNOS-SP network topology: internet peering through an SR-MPLS core to 5G backhaul and IPoDWDM metro
OcNOS-SP: internet peering, SR-MPLS core, 5G backhaul, and IPoDWDM metro, in the OcNOS-SP edition each role needs.

SKU & platform comparison

OcNOS-SP ships in four editions. Buy the router as an OcNOS System and one IP Infusion contract supports the software and the hardware.

OcNOS-SP: Service Provider SP-IP-BASE SP-MPLS CSR SP-PLUS
Layer 2 / Layer 3••••
EVPN-VXLAN••••
Carrier Ethernet•••
MPLS w/ EVPN•••
SR-MPLS•••
SRv6 (initial support)•
Timing Synchronization (1588v2 / SyncE)••
Qualified Platforms
ASICCapacityPort Speeds SP-IP-BASE SP-MPLS CSR SP-PLUS
QUX32 to 120G1/10G•••
QAX300G1/10/25/100G•••
Q2U360G25/100G•••
QMX800G10/100G•••
Q2A800G25/100/400G•••
Q2C2.4 to 4.8T25/100/400G•••
Q2C+7.2T25/100/400G•••
J2C+7.2 to 14.4T10/100/400G•••

*Feature support depends on the platform and edition. Check each router in the Feature Matrix. 26 qualified SP platforms; 400G ZR and OpenZR+ run on 7 of them.

Protocols across the OcNOS-SP editions
SR-MPLSPCEPFlex-Algo TI-LFABGP-LSL3VPN IS-ISOSPFv3EVPN-VXLAN Carrier EthernetY.1731IEEE 1588v2 SyncEOpenZR+NETCONF gNMIOpenConfigRPKI
Test Drive Free Qualified Platforms Interactive Feature Matrix

Open routing on the merchant silicon you choose.

Carrier-grade routing on merchant silicon and open hardware. Separate the software from the hardware to lower CapEx and OpEx, with one accountable vendor for all of it.

✕  Proprietary SP chassis
Proprietary ASICs: a hardware premium over open ODM platforms built on the same merchant silicon
Licensing and support renewals tied to a vendor-controlled hardware refresh cadence
Software licenses that run only on the same vendor's hardware
Single-source lock-in for hardware refresh and roadmap
Vendor-specific management stacks: limited automation portability across platforms
✓  OcNOS-SP on open hardware
Merchant silicon at open-ODM hardware pricing, not a proprietary ASIC premium
One IP Infusion support contract covers software, hardware, and RMA for an OcNOS System
Editions sized to the network: IPBASE, MPLS, CSR and PLUS
Qualified hardware from Edgecore and UfiSpace: 26 routers from 32 Gbps to 14.4 Tbps
Linux-based, open APIs: NETCONF/YANG, gNMI, OpenConfig

Want the platform-by-platform detail? OcNOS-SP is commercial carrier-grade software with IP Infusion support behind it, so there is no in-house routing stack to integrate and maintain. Ask our engineers to map OcNOS-SP routers against your current network.

OcNOS-SP in production

Carriers, regional ISPs, and broadband operators running OcNOS-SP on open hardware.

MetaLINK Technologies
Americas

MetaLINK Technologies deployed IP Infusion OcNOS SP on Edgecore and UfiSpace open networking switches for aggregation, with full interoperability across…

Read story →
Africell
Africa

Africell Sierra Leone deployed IP Infusion OcNOS SP on Edgecore hardware to build an open IP/MPLS backbone that backhauls both…

Read story →
Amplex
Americas

Amplex Internet upgraded its carrier-class aggregation network with OcNOS SP on Edgecore and UfiSpace hardware, reaching 100GB capacity without the…

Read story →
Broadstar
Americas

BroadStar deployed OcNOS SP on white box switches to replace its Juniper hardware, delivering symmetric broadband with up to 10G…

Read story →
Browse all customer deployments →

Ready to deploy OcNOS-SP?

Talk to a network engineer about your topology, or download the free OcNOS VM.

Talk to an engineer Download OcNOS VM → How to buy →

Frequently asked questions

Is OcNOS-SP a router, or just a network operating system?
Both. OcNOS-SP is the carrier-grade network operating system, and IP Infusion also ships the complete router: the software, qualified merchant-silicon hardware from Edgecore or UfiSpace, and one support contract and one PO. You can license the software for a qualified platform you source yourself, or buy the whole router pre-loaded and qualified as an OcNOS System. See how OcNOS Systems ship.
What is SR-MPLS and how does OcNOS-SP implement it?
Segment Routing (SR-MPLS, RFC 8402) carries the path as a stack of MPLS labels in the packet, so the core does not need LDP or RSVP-TE signaling. OcNOS-SP runs SR-MPLS with IS-IS and OSPF segment routing extensions, IS-IS Flex-Algo (RFC 9350) for constraint-based paths, and TI-LFA fast reroute, which computes backup paths before a failure. A PCE controller can program SR paths over PCEP. OcNOS-SP also has initial SRv6 support on selected routers, with more in development.
Does OcNOS-SP support 400G ZR+ optics for IPoDWDM?
Yes, on 7 of the 26 OcNOS-SP routers. These routers take 400G ZR and OpenZR+ coherent pluggables in QSFP-DD ports, so a routed port carries a DWDM wavelength without a separate transponder shelf. Port counts vary by router: on the UfiSpace S9610-36D, 18 of the 36 400G ports are ZR+ capable. OcNOS-SP has proven interoperability with coherent optics from multiple vendors.
Does OcNOS-SP support IEEE 1588v2 timing for mobile backhaul?
Yes. IEEE 1588v2 PTP boundary clock with the ITU-T G.8275.1 and G.8275.2 profiles, plus SyncE (G.8262), runs on 23 of the 26 OcNOS-SP routers. 11 can also act as grandmasters with antenna compensation. The G.8265.1 frequency profile is supported too. Check the timing role of each router in the Feature Matrix.
Which edition matches my role: core router, cell site router, or IPoDWDM edge?
IPBASE covers Layer 2 switching, Layer 3 routing (OSPF, IS-IS, BGP) and EVPN-VXLAN, typical for access and aggregation. MPLS adds MPLS, SR-MPLS, EVPN over MPLS, Carrier Ethernet and ring and linear protection: the baseline for PE and core routers. CSR is the cell site router edition: IP/MPLS with PTP and SyncE timing for cell site and microwave backhaul. PLUS combines MPLS, SR-MPLS, CE 3.0 and 1588v2/SyncE timing, and adds initial SRv6 support on selected routers, with more in development. 400G ZR and OpenZR+ depend on the router. See the OcNOS Feature Matrix for each feature per platform and edition.
Can I migrate an existing router configuration to OcNOS-SP?
Yes. OcNOS-SP uses an industry-standard CLI that engineers who run other carrier routers will find familiar. IP Infusion professional services provide config translation, design review, and migration runbooks for operators moving production traffic onto OcNOS-SP. Talk to our team to scope a migration for your topology.
What hardware platforms does OcNOS-SP run on?
OcNOS-SP is qualified on 26 open hardware routers from Edgecore and UfiSpace, built on Broadcom Qumran and Jericho 2C+ merchant silicon. They range from 32 Gbps access routers to a 14.4 Tbps core router, and 7 of them take 400G ZR and OpenZR+ coherent optics. See every router in the Hardware Compatibility List. Read the Broadcom silicon guide for chip details and SP roles.
Can OcNOS-SP replace a proprietary carrier router?
Yes. OcNOS-SP runs SR-MPLS, BGP, EVPN, Carrier Ethernet and IEEE 1588v2 timing on qualified open hardware, and IP Infusion ships it as a complete router with one support contract. IP Infusion is in production with 600+ operators across 60+ countries. Read how operators run OcNOS in production.
What is the OcNOS-SP support model?
OcNOS-SP customers get one support contract from IP Infusion covering the software, the hardware when bought as an OcNOS System, and RMA coordination. Licensed customers reach TAC by email and through the customer support portal; Premium and Enterprise tiers add 24/7 portal access for production outages. Migration consulting, design review and topology runbooks are available as professional services. See support tiers and response times.

Where OcNOS-SP fits next

SP Networks Core, metro, 5G backhaul architecture. Broadband & Access ISP aggregation, FTTx, BEAD-funded builds. IPoDWDM 400G OpenZR+ IP/optical convergence. Automation & APIs Ansible, NETCONF/YANG, gNMI, ZTP.