Juniper migration · Service provider · Open networking

IP Infusion vs Juniper MX, PTX, ACX and QFX: a technical comparison.

Platform by platform, silicon by silicon: how IP Infusion routers and switches line up against the MX204, QFX5120, QFX5220, ACX7100 and PTX10001, with a Junos-to-OcNOS CLI map and what published operators said about the move.

Download the white paper Request migration assessment Junos to OcNOS CLI cheat-sheet

The MX204 last order date is 15 June 2027.

OcNOS-SP on the UfiSpace S9510-28DC is IP Infusion's option for the SP edge, PE and aggregation roles the Juniper MX204 fills today. Juniper announced end of life for the MX204 on 15 June 2026 in TSB107750 and publishes these milestones:

  1. 15 June 2026End of life announced (TSB107750)
  2. 15 June 2027Last order date for MX204 hardware
  3. 15 June 2028End of hardware failure analysis
  4. 15 June 2030End of engineering; 27.4 is the last software version
  5. 30 June 2032End of support

The OcNOS-SP platform for the MX204 role

  • UfiSpace S9510-28DC front panel
    UfiSpace S9510-28DCFor 10G or 25G access with 400G uplinks

Sizing notes for the MX204 role

  • The Edgecore AGR130 (AS5916-54XKS), a 48 x 10G platform, is under an End of Sale notice announced on 6 October 2026, with a last order date of 2 February 2027, and no successor has been published. For a 10G-dense edge, the qualified OcNOS-SP platforms with a similar port mix are the UfiSpace S9510-28DC and the Edgecore AS7535-28XB (CSR440), each with 24 x 1/10/25G SFP28 ports.
  • For a full Internet routing table, the OcNOS-SP platform with a published deployment is the UfiSpace S9600-72XC with OP2 external TCAM. NWP Services runs it with the full IPv4 and IPv6 table, more than 1.27 million routes, in hardware.
  • Route, VRF and label scale depend on the platform and the OcNOS release.

The MX204 row in the platform mapping below compares the two routers by ports and capacity. Before any unit is replaced, a migration assessment confirms scale and features against your configuration. Dates are as published by Juniper and were checked in October 2026; Juniper's page is the authoritative source.

See the MX204 platform mapping ↓ See the MX204 migration runbook ↓ Request migration assessment → OcNOS Feature Matrix → Free OcNOS VM → Juniper M and MX Series hardware dates and milestones ↗

Who supplies each layer of the router

A router is four layers either way: hardware, network OS, optics and support. What differs is who supplies each layer, and whether you can change one of them without changing the rest.

IP InfusionSourced separately, shipped as one system
HardwareEdgecore, UfiSpace, Celestica
Network OSOcNOS-SP or OcNOS-DC
OpticsMultiple suppliers, including 400G ZR and ZR+
SupportIP Infusion: one support contract and one RMA path

Different suppliers per layer, qualified together by IP Infusion and delivered as one product on one support contract and one RMA path.

JuniperSourced and shipped as one stack
HardwareJuniper MX, QFX, ACX, PTX
Network OSJunos OS or Junos OS Evolved
OpticsJuniper
SupportJuniper JTAC

One supplier for every layer: Juniper hardware, Junos, Juniper optics and JTAC support.

DimensionIP Infusion (OcNOS)Juniper (Junos)
What you buyThe finished router or switch: open hardware, OcNOS, optics and support as one system. Or OcNOS on its own, for hardware you already run.The finished router or switch: Juniper hardware, Junos and support from one vendor.
HardwareOpen platforms from Edgecore, UfiSpace and Celestica. One OcNOS operating model across all of them.Juniper-branded systems: MX, QFX, ACX, PTX.
SiliconBroadcom merchant: Qumran and Jericho for routing, Trident and Tomahawk for switching.Junos Trio chipset on the MX204 and 4th generation Express silicon on the PTX10001-36MR, as Juniper documents them.
Operating systemOcNOS-SP for service-provider routing, OcNOS-DC for the data center.Junos OS and Junos OS Evolved across the MX, QFX, ACX and PTX lines.
LicensingLicensed separately from the hardware, as editions with a perpetual use license.Juniper Flex three-tier model (Standard, Advanced, Premium); subscription and perpetual licenses on MX Series.
SourcingHardware and software are bought separately, so platforms can be competed across ODMs.Hardware, software and support are sourced from Juniper.
ProtocolsBGP, OSPF, IS-IS, MPLS, SR-MPLS, EVPN-VXLAN, EVPN-MPLS, RSVP-TE, IEEE 1588v2, and initial SRv6 support on selected routers with more in development. Per-platform detail in the Feature Matrix.Per-platform detail in Juniper Feature Explorer.
OpticsMulti-vendor pluggables with proven interoperability, including 400G ZR/ZR+ coherent.Juniper optics.
ManagementIndustry-standard transactional CLI with explicit commit. NETCONF, OpenConfig, gNMI, YANG, Ansible, IP Maestro EMS.Junos OS and Junos OS Evolved CLI with commit. Juniper Routing Director for onboarding and management.
SupportFor an OcNOS System, one support contract and one RMA path from IP Infusion cover the software and hardware. For hardware you buy yourself, the manufacturer supports the hardware.Single-vendor JTAC for hardware and software.

Five Juniper anchor platforms, mapped by capacity and role.

Each row pairs a Juniper anchor platform with its IP Infusion equivalent, the one-way capacity comparison, the fit verdict and the key caveat. Where one IP Infusion platform does not carry the capacity, the row says so and names the combination that does.

Juniper platform IP Infusion equivalent Ports Capacity Match Notes
Juniper MX204SP edge / aggregation / DCI · Junos Trio S9510-28DCOcNOS-SP 8×10G + 4×100G → 24×10/25G + 2×100G + 2×400G 400G → 800G Capacity headroom Confirm in the assessment: scale and DCI throughput against your port mix and feature use.
Juniper QFX5120-48YDC leaf / EVPN-VXLAN ToR · Junos OS AS7326-56X / S8901-54XCOcNOS-DC 48×25G + 8×100G → 48×25G + 8×100G 2.0T → 2.0T (one way) Port-for-port match SKU selection depends on copper-versus-fiber ports and uplink mix, mapped against the HCL in the assessment.
Juniper QFX5220-32CDDC spine / 400G · Junos OS Evolved Edgecore AS9716-32DOcNOS-DC 32×400G → 32×400G 12.8T → 12.8T Port-for-port match For AI fabrics, OcNOS-DC runs on Broadcom Tomahawk 4 and Tomahawk 5 platforms.
Juniper ACX7100-32C / 48LMetro aggregation · Junos OS Evolved S9600-56DX / AGR560OcNOS-SP 32×100G + 4×400G → 48×100G + 8×400G 4.8T → 4.8T / 7.2T Same capacity class Confirm for your deployment: G.8273.2 Class C boundary clock timing with SyncE. MACsec is not offered on these OcNOS platforms.
Juniper PTX10001-36MRSP compact core / peering · Juniper Express4 S9610-36DOcNOS-SP 12×100G + 24×400G → 36×400G 9.6T → 14.4T Different silicon The most design-dependent mapping in the set. The SKT live PoC (Jun 2025) is the public IPoDWDM proof point.
Role, ports and capacity all line up Same capacity class Design review

How to read these. Rows are matched on role, port profile and capacity, and capacity is stated one way on both sides. Juniper figures are as Juniper documents them, and silicon is named only where the vendor documentation names it: the Junos Trio chipset for the MX204 and 4th generation Express silicon for the PTX10001-36MR. Scale, timing and the specific features you use depend on your deployment and are confirmed by the migration assessment, so no row is presented as a guaranteed one-to-one swap.

Move MX204 configurations to OcNOS, one site at a time.

Six steps from inventory to a verified cutover. Each OcNOS block in step 3 was typed on a lab router running OcNOS-SP or taken from its running configuration, and names that router.

  1. 1. Inventory every MX204 by roleBuild one row per router: site, serial number, software release in production, support contract end date and the role it plays (PE, P, peering, aggregation or lab). The list shows which routers carry critical traffic, which can move first, and which reach a contract renewal before a replacement could be in place.
  2. 2. Map the features each role depends onList the protocols and services each configuration actually uses and check them in the OcNOS Feature Matrix for the platform and release you plan to run. Route policy needs its own review: each Junos policy statement is rewritten as an OcNOS route map that expresses the same intent, rather than ported line by line.
  3. 3. Translate the configurationTranslate one protocol area at a time, keeping the intent of each stanza rather than its shape. Junos groups most protocol settings under protocols; OcNOS sets them in a router process and on each interface. The translator below covers the common areas.
  4. 4. Test one site safelyAgree the pass criteria first: convergence time, control-plane load, telemetry and the upgrade procedure. Build the OcNOS-SP router in a lab, or as a shadow peer that learns the same routes under the same policy but carries no customer traffic, and move production traffic only after the criteria are met. The free OcNOS VM runs in GNS3, EVE-NG and KVM, so configuration work can start before hardware arrives.
  5. 5. Cut over with a way backMove one site at a time during a maintenance window. Keep the MX204 configured and racked until the OcNOS router meets the step 4 pass criteria with production traffic. Moving back is then a cabling and routing change rather than a rebuild.
  6. 6. Verify after cutoverCheck the new router for the same items you checked on the old one: adjacencies, BGP sessions, label bindings and routes. Each translator tab pairs the Junos show command with its OcNOS equivalent.
  1. Lab Test the translated configuration on the OcNOS VM or a lab router.
  2. Shadow peer OcNOS learns the same routes while the MX204 carries the traffic.
  3. Cutover OcNOS carries the traffic while the MX204 stays configured.
  4. MX204 removed Once the pass criteria hold with production traffic.
Carries customer traffic Routing only, no customer traffic
One site through steps 4 and 5. The MX204 stays configured until the OcNOS router meets the pass criteria with production traffic.

Junos to OcNOS, stanza by stanza

Basics

The commands and names that differ in every configuration you translate.

TaskJunosOcNOS
Apply the candidate configurationcommitcommit
Discard uncommitted changesrollbackabort transaction
Show the configurationshow configurationshow running-config
Enable MPLS on an interfacefamily mpls + protocols mpls interfacelabel-switching
Make a BGP session internaltype internalremote-as <local AS>
Source BGP from the loopbacklocal-addressneighbor <peer> update-source lo
Route policypolicy-statementroute-map
Layer 3 VPN instancerouting-instances <name> instance-type vrfip vrf <name>
Interface filterfirewall family inet filterip access-list + ip access-group <name> in
Link bundleae + 802.3adpo + channel-group <n> mode active
Loopbacklo0.0lo
Port namesge-, xe-, et-ge, xe, ce, cd

OcNOS port names follow the port speed, and the set of names depends on the platform.

Interfaces

Break out a 100G port, then bundle two of its 10G sub-ports with LACP.

Junos
set chassis aggregated-devices ethernet device-count 4
set interfaces xe-0/0/2 ether-options 802.3ad ae3
set interfaces xe-0/0/3 ether-options 802.3ad ae3
set interfaces ae3 aggregated-ether-options lacp active
set interfaces ae3 unit 0 family inet address 10.1.3.0/31
OcNOS
port ce22 breakout 4X10g
!
interface po3
 ip address 10.1.3.0/31
!
interface ce22/1
 channel-group 3 mode active
!
interface ce22/2
 channel-group 3 mode active
  • channel-group 3 mode active on each member does the work of 802.3ad ae3 and lacp active. OcNOS has no device count step.
  • The IP address goes on the po interface, as on the Junos ae unit.
  • On this router, port ce22 breakout 4X10g creates the sub-ports ce22/1, ce22/2 and so on. Breakout modes and port names depend on the platform.
Verify
JunosOcNOS
show lacp interfacesshow etherchannel

From the running configuration of a UfiSpace S9600-28DX, OcNOS-SP-PLUS 7.0.1.

IS-IS

Level 2 only, with wide metrics, traffic engineering and CSPF in the IS-IS process.

Junos
set interfaces lo0 unit 0 family iso address 49.0001.0000.0000.0001.00
set interfaces et-0/0/0 unit 0 family iso
set protocols isis level 1 disable
set protocols isis interface et-0/0/0.0 point-to-point
set protocols isis interface lo0.0 passive
OcNOS
router isis CORE
 is-type level-2-only
 metric-style wide
 mpls traffic-eng router-id 10.0.0.1
 mpls traffic-eng level-2
 capability cspf
 dynamic-hostname
 net 49.0001.0000.0000.0001.00
!
interface lo
 ip router isis CORE
!
interface ce4
 isis network point-to-point
 ip router isis CORE
  • level 1 disable maps to is-type level-2-only.
  • Set the NET in the IS-IS process with net, not on the loopback. The format is the same.
  • Each interface joins with ip router isis <tag>, and isis network point-to-point matches the Junos point-to-point statement.
Verify
JunosOcNOS
show isis adjacencyshow clns neighbors
show isis databaseshow isis database

From the running configurations of a UfiSpace S9600-56DX, OcNOS-SP-PLUS 7.0.1 and a UfiSpace S9510-28DC, OcNOS-SP-PLUS 7.0.1.

OSPF

A point-to-point link and the loopback in area 0.

Junos
set routing-options router-id 10.10.100.11
set protocols ospf area 0.0.0.0 interface et-0/0/0.0
set protocols ospf area 0.0.0.0 interface lo0.0 passive
OcNOS
router ospf 100
 ospf router-id 10.10.100.11
 network 10.2.2.28/31 area 0.0.0.0
 network 10.10.100.11/32 area 0.0.0.0
!
interface ce22
 ip address 10.2.2.29/31
 ip ospf network point-to-point
  • OcNOS selects OSPF interfaces by prefix, using network statements under router ospf. Junos lists interfaces under the area.
  • The loopback joins through its /32 network statement, and ip ospf network point-to-point sets the link type on the interface.
  • On this router, the ce ports are the 100G ports.
Verify
JunosOcNOS
show ospf neighborshow ip ospf neighbor

From the running configuration of a UfiSpace S9600-56DX, OcNOS-SP-PLUS 7.0.1.

BGP

IPv4 unicast iBGP, sourced from the loopback, with the loopback advertised.

Junos
set routing-options autonomous-system 65000
set protocols bgp group internal-peers type internal
set protocols bgp group internal-peers local-address 10.0.0.1
set protocols bgp group internal-peers export send-direct
set protocols bgp group internal-peers neighbor 10.0.0.4
set policy-options policy-statement send-direct term 1 from protocol direct
set policy-options policy-statement send-direct term 1 then accept
OcNOS
router bgp 65000
 bgp router-id 10.0.0.1
 neighbor 10.0.0.4 remote-as 65000
 neighbor 10.0.0.4 update-source lo
 !
 address-family ipv4 unicast
  network 10.0.0.1/32
  neighbor 10.0.0.4 activate
 exit-address-family
  • A remote-as equal to the local AS makes the session internal, the role of type internal.
  • update-source lo takes the place of local-address. The network statement advertises the loopback, as the Junos example does with the send-direct export policy.
  • Activate each neighbor inside its address family. OcNOS-SP 7.0.1 reports activation at the router level as deprecated. IPv6 peers activate under address-family ipv6 unicast.
Verify
JunosOcNOS
show bgp summaryshow ip bgp summary

From the running configuration of a UfiSpace S9510-28DC, OcNOS-SP-PLUS 7.0.1; update-source lo was typed and accepted on the same router.

MPLS and LDP

LDP on a core interface, with the transport address set on the loopback.

Junos
set interfaces et-0/0/0 unit 0 family mpls
set protocols mpls interface et-0/0/0.0
set protocols ldp interface et-0/0/0.0
set protocols ldp interface lo0.0
OcNOS
router ldp
 router-id 10.0.0.8
 transport-address ipv4 10.0.0.8
!
interface xe20
 label-switching
 enable-ldp ipv4
  • label-switching on the interface does the job of family mpls and protocols mpls interface.
  • enable-ldp ipv4 on the interface replaces protocols ldp interface.
  • Use a loopback address for transport-address and carry it in the IGP.
Verify
JunosOcNOS
show ldp sessionshow mpls ldp session
show ldp databaseshow mpls ldp fec

From the running configuration of a UfiSpace S9501-28SMT, OcNOS-SP-MPLS 7.0.1.

SR-MPLS

A segment routing global block and a node SID on the loopback, with IS-IS.

Junos
set interfaces et-0/0/0 unit 0 family mpls
set protocols mpls interface et-0/0/0.0
set protocols isis source-packet-routing srgb start-label 400000
set protocols isis source-packet-routing srgb index-range 4000
set protocols isis source-packet-routing node-segment ipv4-index 2001
OcNOS
segment-routing
 global block 16000 23999
!
router isis 1
 isis segment-routing global block 16000 23999
 segment-routing mpls
!
interface lo
 prefix-sid index 8
! or an absolute label inside the block:
! prefix-sid absolute 16001
  • Junos srgb start-label and index-range map to global block <first> <last>, which is set under segment-routing and in the IGP.
  • segment-routing mpls sits under router isis, as it does on the lab router.
  • prefix-sid index maps to node-segment ipv4-index. The index is relative to the block, and an absolute label must fall inside it.
Verify
JunosOcNOS
show route forwarding-table family mplsshow mpls forwarding-table

From the running configuration of a UfiSpace S9501-28SMT, OcNOS-SP-MPLS 7.0.1; prefix-sid absolute was typed and accepted on a UfiSpace S9510-28DC, OcNOS-SP-PLUS 7.0.1.

L3VPN

A customer VRF on a PE router, with VPNv4 routes exchanged between loopbacks over iBGP.

Junos
set interfaces xe-0/0/0:0 unit 0 family inet address 172.16.1.2/30
set routing-instances CE1_L3vpn instance-type vrf
set routing-instances CE1_L3vpn interface xe-0/0/0:0.0
set routing-instances CE1_L3vpn route-distinguisher 192.168.0.1:12
set routing-instances CE1_L3vpn vrf-target target:65412:12
set protocols bgp group ibgp type internal
set protocols bgp group ibgp local-address 192.168.0.1
set protocols bgp group ibgp family inet-vpn unicast
set protocols bgp group ibgp neighbor 192.168.0.3
OcNOS
ip vrf CUST
 rd 10.0.0.1:1
 route-target both 65000:1
!
interface eth2
 description to ce1
 ip vrf forwarding CUST
 ip address 192.0.2.1/24
!
router bgp 65000
 bgp router-id 10.0.0.1
 neighbor 10.0.0.3 remote-as 65000
 neighbor 10.0.0.3 update-source lo
 address-family vpnv4 unicast
  neighbor 10.0.0.3 activate
 exit-address-family
 address-family ipv4 vrf CUST
  redistribute connected
 exit-address-family
  • The VRF is defined once with ip vrf CUST, rd and route-target both, where Junos uses a routing instance with instance-type vrf, route-distinguisher and vrf-target.
  • ip vrf forwarding CUST on the customer-facing interface replaces listing the interface in the routing instance.
  • VPNv4 routes are activated under address-family vpnv4 unicast, the role of family inet-vpn unicast, and customer routes enter the VRF under address-family ipv4 vrf CUST. This lab redistributes connected routes; the Junos example runs eBGP to the CE.
  • The eth port names are the VM's; on a router they follow the platform, as in the other tabs.
Verify
JunosOcNOS
show bgp summaryshow ip bgp vpnv4 all summary
show route table bgp.l3vpn.0show ip bgp vpnv4 all
show route table CE1_L3vpn.inet.0show ip route vrf CUST

Tested on the free OcNOS-SP VM 7.0.0-262 as BGP L3VPN over IS-IS SR-MPLS between two PE routers and a P router, with traffic passing between the two customer sites. The VM is a lab image for learning the CLI and control-plane configuration: its data plane is limited, it does not show hardware features, scale or performance, and production feature support is per qualified platform and edition in the Feature Matrix.

EVPN-MPLS, RSVP-TE fast reroute, EVPN-VXLAN, ACLs, QoS and NETCONF are in the CLI cheat sheet and are checked the same way.

Get the full CLI cheat-sheet → QFX EVPN-VXLAN migration guide →

HPE closed the Juniper acquisition on 2 July 2025.

HPE completed its acquisition of Juniper Networks on 2 July 2025.  HPE acquisition release.

Operators who made the move, and why.

Operators who have moved production traffic off Juniper, and in some cases Cisco, onto OcNOS on open hardware. Each reason below is the one the operator gave in its own published story.

BroadStar Replaced Juniper switches for MDU residential access. Cited OcNOS interoperating with other vendors, so hardware could be matched to budget and feature requirements, and a return on investment in months rather than years. Read the story → Celerity Internet / WispWest Replaced a MikroTik and Juniper network. Cited greater scalability from edge to core, better BGP router scalability, and compact, energy-efficient MPLS routing for tower sites with limited space. Read the story → Haefele Connect A former Cisco and Juniper network, now OcNOS-SP on Edgecore for L3 aggregation. Cited high-density 10G with medium-density 100G ports, equipment available in weeks instead of years, and interoperation with the Juniper system already deployed. Read the story → Vyve Broadband On track to 200 OcNOS nodes, displacing Cisco and Juniper. Cited the flexibility to convert existing hardware to OcNOS while gaining service-provider feature sets, and quicker deployment cycles on one standardized platform. Read the story →

Frequently asked questions

Does IP Infusion sell complete switches and routers, or just the OcNOS software?
Both. The main offering is the finished product: a carrier-grade router or switch with OcNOS pre-installed on open hardware, plus the optics and the support contract, delivered as one system and qualified on the Hardware Compatibility List. If you already run open hardware, you can license OcNOS on its own for it. Because hardware, software and optics stay separable, you can change any one of them later without replacing the others.
Can OcNOS replace a Juniper MX204 1:1 for SP edge and aggregation?
OcNOS-SP supports BGP, IS-IS, OSPF, MPLS LDP, SR-MPLS, EVPN-MPLS, RSVP-TE, L2VPN and L3VPN, QoS and IEEE 1588v2 timing on Edgecore and UfiSpace service provider platforms. Juniper documents the MX204 as a 1 U router with four QSFP28 ports, eight 10GbE SFP+ ports and 400 Gbps of throughput. The closest OcNOS-SP platform is the UfiSpace S9510-28DC (24 x 1/10/25G SFP28 + 2x100G + 2x400G, 800 Gbps, 1 U) for 10G or 25G access with 400G uplinks. The PE role (L3VPN with LDP or SR-MPLS) needs the OcNOS-SP MPLS or PLUS edition. Whether one unit replaces another one to one depends on your port mix, scale and feature use. The migration assessment checks these against the Feature Matrix.
When is the Juniper MX204 end of life?
Juniper announced end of life for the MX204 on 15 June 2026 in TSB107750. The last order date for MX204 hardware is 15 June 2027, hardware failure analysis ends on 15 June 2028, engineering ends on 15 June 2030 with 27.4 as the last software version, and support ends on 30 June 2032. These dates are as published on Juniper's M and MX Series hardware dates and milestones page, checked in October 2026; Juniper's page is the authoritative source.
What is the OcNOS equivalent for a QFX5120-48Y DC leaf?
Edgecore AS7326-56X (DCS203) is the port-for-port match: 48x25G SFP28 with 8x100G QSFP28 uplinks at 2.0 Tbps one way. Juniper documents the QFX5120-48Y with 48 SFP28 ports, 8 QSFP28 ports and 4 Tbps of aggregate bidirectional throughput, which is 2 Tbps one way. UfiSpace S8901-54XC is the same class with 6x100G uplinks rather than 8. Both run OcNOS-DC with EVPN-VXLAN. The match is made on role, ports and capacity, and the SKU choice depends on the uplink mix, which the migration assessment maps against the Hardware Compatibility List.
Does OcNOS run on a 32x400G spine equivalent to the QFX5220-32CD?
Yes. OcNOS-DC runs on the Edgecore AS9716-32D (Broadcom Tomahawk 3, 32x400G, 12.8 Tbps) as an IP-fabric spine, with the BGP underlay and EVPN route reflection, while the VXLAN tunnels terminate on the leaf switches. Juniper documents the QFX5220-32CD as a 1 U switch with 32 400GbE ports and 12.8 Tbps of bandwidth, so ports and capacity line up. For AI fabrics, OcNOS-DC runs on Broadcom Tomahawk 4 and Tomahawk 5 platforms.
How close is OcNOS-SP to the ACX7100 for metro and SR-MPLS aggregation?
On capacity the OcNOS-SP match is the UfiSpace S9600-56DX (48x100G + 8x400G, 4.8 Tbps, Broadcom Qumran2c), with the Edgecore AS9947-36XKB (AGR560, 12x400G + 24x100G, 7.2 Tbps, Jericho2C+) where more capacity is needed. Juniper documents the ACX7100-32C (32 QSFP28 and 4 QSFP56-DD ports) and the ACX7100-48L (48 SFP ports at 10, 25 or 50G and 6 QSFP56-DD ports) as 1 U routers with 4.8 Tbps of throughput. For smaller access and cell-site roles, the Qumran-class AGR400 and CSR440 cover the tier below. Published OcNOS references include the SKT 400G OpenZR+ live proof of concept (June 2025), the AnschlussWerk aggregation routing deployment on Edgecore (November 2024) and the TIP Validated Solution Gold Badge for the OcNOS Disaggregated Cell Site Gateway (2022). Timing to confirm for your deployment: G.8275.1 boundary clock with G.8273.2 Class C and SyncE, in the CSR and PLUS editions. MACsec is not offered on these platforms: it is coming in OcNOS 7.1 on the UfiSpace S9610-46DX and S9610-36D only, with the OcNOS SP PLUS SEC license.
Is there an OcNOS-SP equivalent for the PTX10001-36MR compact core?
Yes. The single-platform answer is OcNOS-SP on the UfiSpace S9610-36D: 36x400G at 14.4 Tbps on Broadcom Jericho2C+, in 2 RU. Juniper documents the PTX10001-36MR as a 1 U router with 24 QSFP56-DD and 12 QSFP28 ports, 9.6 Tbps of throughput and 4th generation Express silicon. The Edgecore option is two AS9947-36XKB (AGR560) units at 7.2 Tbps each, also Jericho2C+; one unit on its own does not reach 9.6 Tbps. Because the forwarding silicon differs, buffer behavior and FIB, RIB and LSP scale are compared against your peering and core requirements. MACsec on the S9610-36D is coming in OcNOS 7.1 and requires the OcNOS SP PLUS SEC license. This is the most design-dependent of the five mappings and is handled as a design exercise rather than a SKU-for-SKU swap.
How does Junos route-policy translate to OcNOS route-map syntax?
OcNOS uses industry-standard route maps: numbered sequences of match and set clauses, applied to BGP neighbors and to redistribution. Each Junos policy statement is rewritten as an OcNOS route map that expresses the same intent, rather than ported line by line, and the rewritten policy is tested in a lab or on a shadow peer before cutover.
Does OcNOS support fast reroute with RSVP-TE the way Junos does?
OcNOS-SP MPLS documents RSVP-TE FRR one-to-one with node-protection and the corresponding configuration form. BFD provides the fast failure detection that, combined with pre-computed FRR backup paths, supports fast protection; achievable times depend on the BFD interval/multiplier, hardware offload, and platform (OcNOS BFD minimum 3 ms hardware, 10 ms software). Facility-backup (link-protection / bypass) and auto-bandwidth are documented in the broader OcNOS-SP MPLS tree. For the specific FRR coverage you need - detour vs facility, link vs node protection, and CSPF constraints - contact us for the detailed mapping.
When did HPE complete its acquisition of Juniper?
HPE completed its acquisition of Juniper Networks on 2 July 2025, as announced in its press release of that date. For support dates on a specific platform, Juniper publishes end-of-life milestones per product, such as TSB107750 for the MX204.
How does OcNOS licensing compare to Juniper licensing?
OcNOS is licensed separately from the hardware. Each OcNOS-SP edition (IPBASE, MPLS, PLUS, CSR) and OcNOS-DC edition (MGMT, IPBASE, PLUS) comes with a perpetual use license sized to the platform, and the hardware can be sourced from any vendor on the Hardware Compatibility List. Juniper documents the Juniper Flex three-tier license model (Standard, Advanced, Premium) and lists subscription and perpetual licenses for MX Series routers. Cost figures for a specific network come from a migration assessment.

Migration resources

Two gated downloads: the Democratizing the Network white paper (the open-networking case for moving off Juniper) and the full Junos-to-OcNOS CLI cheat-sheet. Short form, then the PDF opens in a new tab.

White Paper

Moving from Junos to OcNOS

A plan for Junos operators: which OcNOS-SP router takes each role, which OcNOS feature covers each function, and how the CLI maps.

Get the white paper
Engineer Reference

Junos to OcNOS CLI cheat-sheet

Side-by-side Junos and OcNOS for the protocol areas your team uses daily: BGP, OSPF, IS-IS, LDP, SR-MPLS, EVPN-VXLAN, EVPN-MPLS, MPLS-TE, ACL, QoS, NetConf, and interface/breakout.

Get the PDF

A finished router or switch, sourced on open terms.

IP Infusion delivers a finished router or switch qualified on the Hardware Compatibility List: merchant-silicon hardware that can be sourced from more than one ODM, OcNOS licensed separately from the box with a perpetual use license, and optics from more than one supplier.

Feature Matrix

Per-feature, per-platform support across the OcNOS portfolio.

Hardware Compatibility List

The qualified set of open platforms OcNOS runs on.

OcNOS-SP

Service-provider routing for edge, aggregation and core.

OcNOS-DC

EVPN-VXLAN data-center and AI-fabric switching.

OcNOS vs Cisco

Cisco Nexus, NCS and 8000, platform by platform.

OcNOS vs SONiC

Open network operating systems for the data center.

Juniper, Junos, MX, QFX, ACX, PTX and Trio are trademarks of Juniper Networks, Inc. HPE is a trademark of Hewlett Packard Enterprise. Cisco is a trademark of Cisco Systems, Inc. All other marks are the property of their respective owners. IP Infusion is not affiliated with, endorsed by, or sponsored by Juniper Networks, Hewlett Packard Enterprise, or Cisco Systems. Platform comparisons reflect publicly documented specifications as of October 2026 and are provided for evaluation purposes only.

Request a migration assessment.

Request a written assessment of your current Juniper platforms, roles, and migration path from IP Infusion.