Juniper migration · Service provider · BOFU

OcNOS for Juniper migrations: side-by-side, then assess.

Five Juniper anchor platforms (MX204, QFX5120-48Y, QFX5220-32CD, ACX7100, PTX10001-36MR) mapped to OcNOS on HCL-listed open hardware. Side-by-side CLI for the eight protocol areas your team uses every day. A phased migration path. No calendar widget: request a written assessment and an IP Infusion sales engineer will route from there.

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

HPE closed the Juniper acquisition on 2 July 2025.

HPE completed its acquisition of Juniper Networks on 2 July 2025 at an announced equity value of approximately 14 billion US dollars. A US DOJ consent decree required HPE to divest the Instant On wireless LAN business and license Juniper Mist AIOps source code to third parties. The combined networking organization is branded HPE Networking, with HPE Juniper Networking and HPE Aruba Networking retained as sub-brands. As of June 2026, HPE had not publicly issued roadmap commitments for Junos OS support windows past 2027 or for Apstra continuation. We do not speculate; the linked HPE and DOJ statements are the source.  HPE acquisition release.

Platform mapping

Five Juniper anchor platforms, OcNOS equivalents, every cell footnoted.

Mappings are by silicon class and role; the right platform for your network depends on its protocol set, scale, and port profile. The migration assessment confirms the fit against your specific deployment.

Juniper MX204 - SP edge / aggregation / DCI

AttributeOcNOS-SP on Edgecore AGR130 / UfiSpace S9510-28DCJuniper MX204
Role SP edge, PE, aggregation, DCI (OcNOS-SP / SP-PLUS) Ethernet-optimized SP edge / PE / broadband BNG / DCIsrc: juniper.net/documentation/.../mx204-description.html
Port profile AGR130: 1RU SP aggregation router (Broadcom Qumran MX, BCM88375; 48x10G SFP+ + 6x100G QSFP28, 800 Gbps). S9510-28DC: 24x25G + 2x100G + 2x400G, 800 Gbps - cell-site / 25G access gateway with 400G coherent uplinks (2x the MX204 400 Gbps), not a higher-density 100G aggregator. 4x QSFP28 (100G or 40G or 4x10G breakout) + 8x SFP+ 10G; 400 Gbps; 1 RUsrc: juniper.net/documentation/.../mx204-description.html
Public validation AGR130: OCP Solution Provider listing + AnschlussWerk wireline deployment (Nov 2024). S9510-28DC: MEF 3.0 Carrier Ethernet certification (Oct 2024). Junos Trio platform; standard Juniper certifications. An MX204 EoL notice was issued and later revoked for select variants in 2024; confirm current status against the Juniper EoL bulletin for your exact SKU.src: support.juniper.net/support/eol/
Mapping verdict Tier A OcNOS-SP evidence exists; Trio-specific BNG scale and DCI throughput depend on your specific port mix.

Juniper QFX5120-48Y - DC leaf / EVPN-VXLAN ToR

AttributeOcNOS-DC on Edgecore DCS-series 48x25G + 8x100GJuniper QFX5120-48Y
Role DC leaf, EVPN-VXLAN gateway, MAC-VRF, BGP-EVPN (OcNOS-DC) DC leaf / ToR, 25G leaf with 100G uplinks, spine-and-leaf fabricsrc: juniper.net/.../qfx5120-ethernet-switch-datasheet.html
Port profile Edgecore DCS-series with 48x25G SFP28 + 8x100G QSFP28 uplinks (specific HCL SKU per assessment) 48x SFP28 25G (10G/1G capable) + 8x QSFP28 100G uplinks; 4 Tbps; 1 RUsrc: juniper.net/.../qfx5120-ethernet-switch-datasheet.html
Public validation OcNOS-DC plus Edgecore Tomahawk-class spine pattern is publicly listed via OCP Solution Provider (AS7712-32X / DCS501, Tomahawk 1; different silicon class from a 48x25G Trident-3 leaf, cited as adjacent reference only). The 48x25G Trident-3 leaf SKU public validation is engineering-internal (Tier B) at this revision. Broadcom Trident 3 silicon; Apstra-managed; standard Juniper EVPN-VXLAN certifications.src: blogs.juniper.net welcome-qfx5120-48y
Mapping verdict Architectural fit is clean; the specific DCS SKU with a 48x25G + 8x100G profile depends on your copper-vs-fiber and uplink mix.

Juniper QFX5220-32CD - DC spine / 400G

AttributeOcNOS-DC on Edgecore DCS510 (AS9716-32D) / Tomahawk-3Juniper QFX5220-32CD
Role IP-fabric DC spine, EVPN-VXLAN, BGP underlay (OcNOS-DC). Not positioned as AI fabric on Tomahawk 3. DC spine in large IP fabrics; 400GbE aggregation; positioned for AI fabric leaf-spinesrc: juniper.net/documentation/.../qfx5220-system-overview.html
Port profile 32x 400GbE QSFP56-DD on Tomahawk 3; silicon-class match 32x 400GbE QSFP56-DD (200G/100G/50G/40G/25G/10G breakout); 12.8 Tbps; 1 RUsrc: juniper.net/documentation/.../qfx5220-system-overview.html
Public validation OcNOS-DC on the matching 32x400G Tomahawk-3 platform (Edgecore DCS510 / AS9716-32D) is publicly listed as an OCP Solution Provider solution - silicon-class and port-speed match to the QFX5220-32CD. Junos OS Evolved 19.1R1 baseline; Broadcom Tomahawk 3 siliconsrc: juniper.net/documentation/.../qfx5220-system-overview.html
Mapping verdict DC-spine portion is a silicon-class match. AI-fabric positioning belongs against Tomahawk-4 or higher, not against TH3.

Juniper ACX7100 - cloud-metro / 5G xHaul aggregation

AttributeOcNOS-SP / SP-PLUS on Edgecore AGR-series (Broadcom Qumran)Juniper ACX7100-32C / ACX7100-48L
Role Cloud-metro aggregation, 5G cell-site gateway, SR-MPLS PE, EVPN-MPLS metro (OcNOS-SP / SP-PLUS / DCSG profile) Cloud-metro / SP aggregation, multiservice 5G xHaul, SR-MPLS aggregationsrc: juniper.net/documentation/.../acx7100-48L-system-overview.html
Port profile AGR130 / AGR110 = Qumran-MX, AGR400 (AS7946-30XB) = Qumran2C, CSR440 (AS7535-28XB) = Qumran2A - all Broadcom StrataDNX Qumran-class. AGR400 is the closest 400G-capable match for ACX7100-32C. 32C: 32x100G QSFP28 + 4x400G QSFP56-DD. 48L: 48x10/25/50G SFP + 6x400G QSFP56-DD. 4.8 Tbps full-duplex.src: juniper.net/documentation/.../acx7100-48L-system-overview.html
Public validation AGR130 OCP listing + AnschlussWerk deployment. The SKT 400G OpenZR+ live PoC (Jun 2025) validated OcNOS-SP-PLUS on Edgecore whitebox; the specific SKU is not named in the press release. TIP DCSG Validated Solution Gold Badge (awarded 2022). KDDI DCSG validation. Junos OS Evolved 21.2R1 initial release; Broadcom Jericho2-family ASIC; Class C timingsrc: community.juniper.net everything-about-acx7000
Mapping verdict Strongest SP mapping of the five, but the silicon is not a Jericho2 match: the Edgecore AGR/CSR line uses Broadcom Qumran-class silicon (same StrataDNX/DNX generation as the ACX7100 Jericho2, not the same chip). MACsec port density at line rate and Class C timing certification (T-BC, SyncE, PTP, GPS) should be confirmed for 5G fronthaul deployments.

Juniper PTX10001-36MR - SP compact core / peering

AttributeOcNOS-SP / SP-PLUS on UfiSpace S9600-class (Qumran2c)Juniper PTX10001-36MR
Role SP compact core, peering, infrastructure-edge, IPoDWDM (OcNOS-SP / SP-PLUS) SP core / peering / infrastructure-edge in cloud, SP, content-provider networkssrc: juniper.net/documentation/.../ptx10001-36mr-system-overview.html
Port profile S9600-56DX / S9600-64X / S9600-32X / S9600-28DX / S9600-72XC; specific SKU pairing per assessment. SKT live PoC validated OcNOS-SP-PLUS on Edgecore whitebox for 400G OpenZR+ IPoDWDM. 24x QSFP56-DD (10/25/40/100/400G) + 12x QSFP28 (10/25/40/100G); 9.6 Tbpssrc: juniper.net/documentation/.../ptx10001-36mr-system-overview.html
Public validation Q2C SKU enumeration in OcNOS-SP release notes carries an open item per the validation evidence base, closed during the migration assessment. SKT live PoC (Jun 2025) is the public IPoDWDM proof point. Juniper Express 4 silicon (proprietary, deep-buffer); inline MACsec on 100G/400Gsrc: juniper.net/documentation/.../ptx10001-36mr-system-overview.html
Mapping verdict Weakest of the five mappings. Express 4 vs Q2C are both compact-core class but architecturally distinct. FIB / RIB / LSP scale and MACsec line-rate density differ, including by the exact Q2C SKU.

Verdict legend. Each mapping holds at the architectural and protocol level; specific feature areas (BNG scale, MACsec line-rate density, Class C timing, RSVP-TE facility-backup form, Q2C SKU) depend on your deployment, and the migration assessment confirms the fit for your network. We do not present any anchor SKU as a guaranteed 1:1 swap. OcNOS competes strongest in standards-based routing, EVPN fabrics, metro aggregation, and IP/optical transport; feature-rich service-edge (advanced BNG and subscriber management) and proprietary-silicon workloads warrant deeper architecture work. Public source citations are inline.

Why customers move

Three reasons, each one cited.

TCO

Hardware and optics independence.

OcNOS decouples NOS from hardware. HCL-listed Edgecore and UfiSpace platforms plus a multi-vendor optics ecosystem (including 400G ZR+ coherent) are the architectural cost levers customers use against single-vendor Juniper procurement on comparable workloads. Per-deployment TCO numbers come from the assessment, not from a marketing chart.

src: Haefele Connect, Vyve Broadband.

Openness

Open Compute Project + TIP path.

OcNOS ships on OCP Solution Provider listings for DC (AS7712-32X / DCS501) and SP (AS5916-54XKS / AGR130). OcNOS was awarded the TIP Validated Solution Gold Badge for the DCSG profile (2022). The hardware choice is yours; the NOS supports the standards bodies that publish the disaggregated reference designs.

src: opencompute.org Solution Provider listings; TIP Gold Badge press release.

Roadmap

Open optics and 400G ZR+ validated in a live PoC.

The SKT live PoC (Jun 2025) validated OcNOS-SP-PLUS on Edgecore whitebox for 400G OpenZR+ IPoDWDM. OcNOS-SP-PLUS holds MEF 3.0 Carrier Ethernet certification on UfiSpace S9510-28DC (Oct 2024). The disaggregated transport path is shipping today; AI-fabric SKU positioning belongs on Tomahawk 4 or higher, not on TH3.

src: SKT live PoC, MEF 3.0 release.

Junos to OcNOS CLI map

Eight protocol areas, side by side.

Compact previews. Full configuration forms, policy translation, route-map equivalents, and SR-TE policy construction live in the downloadable CLI cheat-sheet.

1. BGP - iBGP neighbor (loopback peering)

Junos
set protocols bgp group RR type internal
set protocols bgp group RR local-address 10.0.0.10
set protocols bgp group RR neighbor 10.0.0.1
OcNOS
router bgp 65000
 neighbor 10.0.0.1 remote-as 65000
 neighbor 10.0.0.1 update-source lo

2. OSPFv2 - area 0 interface enable

Junos
set protocols ospf area 0.0.0.0 interface et-0/0/0
set protocols ospf area 0.0.0.0 interface lo0.0 passive
OcNOS
router ospf 1
 network 10.0.0.0/24 area 0

3. IS-IS Level-2 - core IGP

Junos
set interfaces lo0 unit 0 family iso address 49.0001.0000.0001.00
set protocols isis interface et-0/0/0.0 level 2
set protocols isis level 1 disable
OcNOS
router isis ISIS-IGP
 is-type level-2-only
 metric-style wide
 net 49.0000.0000.0001.00

4. MPLS LDP - transit enable

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
OcNOS
router ldp
 router-id 192.168.0.1
 transport-address ipv4 192.168.0.1
interface xe1
 label-switching
 enable-ldp ipv4

5. SR-MPLS - SRGB + node-SID

Junos
set protocols isis source-packet-routing srgb start-label 800000 index-range 8000
set protocols isis source-packet-routing node-segment ipv4-index 100
OcNOS
segment-routing
 global block 30000 50000
router isis isis1
 isis segment-routing global block 30000 50000

6. EVPN-VXLAN - DC overlay

Junos
set protocols evpn encapsulation vxlan
set protocols evpn extended-vni-list 101
set switch-options vtep-source-interface lo0.0
OcNOS
nvo vxlan enable
nvo vxlan vtep-ip-global 1.1.1.1
nvo vxlan id 50 ingress-replication inner-vid-disabled

7. MPLS-TE - RSVP + primary path

Junos
set protocols mpls traffic-engineering
set protocols rsvp interface et-0/0/0.0
set protocols mpls label-switched-path L1 to 10.0.0.20
OcNOS
rsvp-trunk to_30 ipv4
 primary fast-reroute protection one-to-one
 primary path p21
 to 30.30.30.30

8. ACL / firewall filter - ingress

Junos
set firewall family inet filter IN term t1 from source-address 10.0.0.0/24
set firewall family inet filter IN term t1 then accept
set interfaces et-0/0/0 unit 0 family inet filter input IN
OcNOS
ip access-list T1
 permit any host 1.1.1.2 any
hardware-profile filter ingress-ipv4 enable
interface xe10
 ip access-group T1 in

Get the full CLI cheat-sheet →

Phased migration

Week 1, week 4, week 12.

Sketch from the migration playbook. The full version lives at the migration-playbook sibling URL; this is the high-level shape.

Week 1

Assessment and lab

  • Discovery: capture current Junos config, port mix, feature usage, peer counts, policy chains
  • Anchor mapping: which of MX204 / QFX5120 / QFX5220 / ACX7100 / PTX10001 applies to which sites
  • OcNOS HCL selection per site; license edition (SP, SP-PLUS, DC, DCSG)
  • Lab build: 1-2 nodes against a Junos peer; baseline BGP and IS-IS adjacency, OSPF, basic MPLS LDP
Week 4

Pilot and parity

  • Policy translation pass: Junos policy-statement chains to OcNOS route-map. SE-reviewed for nested cases.
  • Feature parity drills: SR-MPLS prefix-SID, EVPN MAC-VRF, RSVP-TE primary path with FRR one-to-one
  • Pilot site cutover: one PoP or one aggregation pair, dual-homed to Junos for safe fallback
  • Telemetry: gNMI / gRPC / OpenConfig models exported to your existing collector
Week 12

Rolling cutover

  • Region-by-region cutover with documented rollback per node and per service
  • Automation handoff: Ansible / NetConf / OpenConfig translation if applicable
  • Decommission Junos chassis on a planned schedule; preserve optics where economic
  • Post-cutover review: end-state TCO delta vs the original assessment, lessons logged for next region
Customer reference

A specific operator who moved off Juniper.

Public migration stories on file

HIGH-confidence Juniper-displacement stories already published include BroadStar (legacy Juniper switch replacement for MDU residential access), Celerity / Gallatin Wireless (MikroTik and Juniper upgrade to OcNOS on UfiSpace), Haefele Connect (traditionally a Cisco and Juniper operation, now OcNOS on Edgecore), and Vyve Broadband (200 OcNOS nodes replacing Cisco and Juniper).

BroadStar · Celerity · Haefele Connect · Vyve Broadband

FAQ

Frequently asked questions

Can OcNOS replace a Juniper MX204 1:1 for SP edge and aggregation?
At the protocol layer yes: OcNOS-SP carries BGP, IS-IS, OSPF, MPLS-LDP, SR-MPLS, EVPN-MPLS, RSVP-TE, L2VPN/L3VPN, QoS, and IEEE 1588v2 timing on Edgecore AGR-series and UfiSpace SP platforms. The MX204 port profile (4xQSFP28 + 8xSFP+, 1RU, 400 Gbps) is closest to Edgecore AGR130 (AS5916-54XKS) for low-density edge work, and to UfiSpace S9510-28DC for higher-density aggregation. Trio-specific BNG subscriber scale and DCI throughput do not have a published OcNOS comparison, so a 1:1 swap for those workloads needs an SE design review against your actual port mix and feature usage.
What is the OcNOS equivalent for a QFX5120-48Y DC leaf?
OcNOS-DC running on an Edgecore DCS-series 48x25G + 8x100G platform from the IP Infusion HCL is the architectural match. The QFX5120-48Y is a Trident-3 DC leaf with EVPN-VXLAN, BGP-EVPN, MAC-VRF, and JTI/OpenConfig telemetry; OcNOS-DC supports the same overlay primitives. The exact Edgecore SKU recommendation depends on copper-vs-fiber port preference and uplink mix - the migration assessment maps your specific port profile against the HCL.
Does OcNOS run on a 32x400G spine equivalent to the QFX5220-32CD?
Yes for the DC-spine role. OcNOS-DC ships on Edgecore Tomahawk-3 32x400G platforms (DCS510 / AS9716-32D class) for EVPN-VXLAN spine duty. The QFX5220 silicon is Tomahawk 3 (12.8 Tbps); the HCL match is silicon-class equivalent. For AI fabric workloads we steer customers to Tomahawk 4, Tomahawk 5, or Jericho3-AI platforms rather than TH3 - the QFX5220 is not the AI-fabric SKU.
How close is OcNOS-SP feature parity with the ACX7100 for 5G xHaul and SR-MPLS aggregation?
The ACX7100 uses Broadcom Jericho2-family silicon; OcNOS-SP runs on Edgecore AGR/CSR aggregation routers (AGR130, AGR110, AGR400, CSR440), which use Broadcom Qumran-class silicon from the same StrataDNX/DNX generation as the ACX7100 Jericho2, not the same chip. Public validation includes the SKT 400G OpenZR+ live PoC (Jun 2025), the AnschlussWerk Edgecore + OcNOS wireline deployment (Nov 2024), and the TIP Validated Solution Gold Badge for the OcNOS DCSG profile. It is the closest SP silicon-generation match of any Juniper-anchor mapping in this campaign. MACsec port density at line rate and Class C timing (T-BC, SyncE, PTP, 1PPS + 10 MHz GPS in/out) are the two feature areas that need SE confirmation against your specific deployment.
Is there an OcNOS-SP equivalent for the PTX10001-36MR compact core?
The candidate is OcNOS-SP on UfiSpace S9600-class (Broadcom Qumran2c) compact-core platforms. Silicon class is similar (both target compact-core duty), but Express 4 and Qumran2c are architecturally distinct - buffer depth, FIB/RIB scale, and label-stack depth need to be compared against your peering and core requirements. Of the five anchor mappings in this campaign, this one carries the most outstanding open items and is best handled as a per-deployment design exercise, not a SKU-for-SKU swap.
How does Junos route-policy translate to OcNOS route-map syntax?
Junos policy-statement is a chained match-and-then language attachable from any protocol; OcNOS route-map is the IOS-style sequence + match/set form, which covers most real BGP and IGP redistribution patterns but is structurally narrower. Migration projects need a policy-translation pass rather than a line-by-line port. The CLI cheat-sheet below shows the standard mappings; complex nested Junos policy chains should be validated before cutover.
Does OcNOS support sub-50 ms FRR 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 sub-50 ms 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.
Where does the HPE acquisition of Juniper actually leave service providers?
HPE closed the Juniper acquisition on 2 July 2025 at an announced equity value of approximately 14 billion US dollars. A US DOJ consent decree required HPE to divest the Instant On wireless LAN business and license Juniper Mist AIOps source code on a perpetual non-exclusive basis to third parties. Public roadmap signals at HPE Discover Barcelona (Dec 2025) and MWC 2026 include continued Juniper-branded MX, PTX, and QFX platforms under the HPE Juniper Networking sub-brand. As of June 2026, there is no public HPE commitment on Junos OS support windows past 2027, on Apstra continuation, or on EX/QFX consolidation with Aruba CX-OS. We do not make claims about those items; we point customers at the public statements that exist and let them weigh roadmap independence as one factor among several.
Resources

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

Democratizing the Network: the open successor to Juniper

The carrier-grade case for moving off Juniper: the end-to-end open OcNOS model, validated multi-vendor hardware, no optics lock-in, and side-by-side cost scenarios.

Get the brief
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 brief
Next step

Request a migration assessment.

Talk to an IP Infusion sales engineer about replacing your Juniper footprint. Written assessment of your current platforms, roles, and migration path.

Also available: Migration playbook (PDF) · CLI cheat-sheet (PDF)

Comparison: OcNOS vs Cisco · OcNOS vs SONiC

Juniper, Junos, MX, QFX, ACX, PTX, Apstra, Mist, and Trio are trademarks of Juniper Networks, Inc. HPE and Aruba are trademarks 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 June 2026 and are provided for evaluation purposes only.