Skip to content
Uniqcli

Junos OS & Junos OS Evolved

One network operating system across routers, switches, and firewalls, open and programmable enough to automate instead of babysit.

Overview

Junos OS is the network operating system that runs Juniper's routers, switches, and firewalls, now sold under HPE Juniper Networking following HPE's 2025 acquisition of Juniper Networks. It gives network teams a single operating model, CLI, and API surface across MX and ACX routers, EX and QFX switches, and SRX firewalls, so the same skills and automation scripts carry from the data center edge to the WAN core. Junos OS Evolved is the companion build for cloud-scale environments: it runs natively on Linux with a microservices architecture instead of the traditional FreeBSD-heritage design, trading nothing in CLI familiarity for added resiliency and faster feature delivery on the PTX Series and select high-performance QFX and ACX platforms.

This page is for network architects, NetOps teams, and IT directors deciding how to standardize operations across a multi-platform Juniper estate, and for federal, SLED, healthcare, and enterprise buyers who need to know exactly what they're licensing before a hardware order goes out. Junos is built around open programmability: NETCONF with YANG data models, the Juniper Extension Toolkit (JET) for direct API access to control and data planes, the Junos Telemetry Interface (JTI) for real-time streaming state, and native integration with Puppet, Chef, Ansible, Salt, and Juniper's own PyEZ Python framework. None of that requires ripping out tooling your team already runs.

High availability is built into the design, not bolted on. In-Service Software Upgrades (ISSU), link aggregation, and Junos Continuity let you patch software and swap hardware without turning maintenance into an outage, which matters when downtime carries mission, patient-safety, or compliance consequences. Junos also connects into Juniper's AI-Native Networking Platform through Paragon, Apstra, and Mist AI, so device-level telemetry feeds platform-wide automation and assurance instead of sitting in a silo.

Request a quote
Junos OS & Junos OS Evolved

A closer look

Junos OS & Junos OS Evolved — view 1

Why Junos OS & Junos OS Evolved

For federal, SLED, healthcare, and enterprise teams running MX, ACX, EX, QFX, and SRX hardware side by side, one operating model means fewer platforms to certify, train staff on, and prove configuration state for during an audit. ISSU, link aggregation, and Junos Continuity keep services running through patches and hardware swaps, which matters when downtime carries mission, patient-safety, or compliance consequences. Open APIs (JET), streaming telemetry (JTI), and standards-based NETCONF/YANG configuration let you automate change control and feed real-time state into the AIOps and orchestration tooling your team already operates, instead of standing up something new.

One operating model, five hardware families

The same Junos operating model spans MX and ACX routers, EX and QFX switches, and SRX firewalls, so your team plans, deploys, and audits infrastructure without juggling separate platforms or retraining for each one.

Programmable at every layer

JET exposes control, management, and data-plane APIs independent of the release cycle; NETCONF with YANG models makes configuration machine-readable; and PyEZ gives Python-based automation a direct hook into the device.

Telemetry that streams, not polls

The Junos Telemetry Interface (JTI) is a distributed analytics engine built to gather and stream accurate, real-time network data and event states at scale, feeding your monitoring stack continuously.

Maintenance windows that don't take the network down

In-Service Software Upgrades (ISSU), link aggregation, and Junos Continuity let you patch software and install new hardware as non-service-impacting events instead of scheduled outages.

Junos OS Evolved for cloud-scale and faster iteration

A Linux-native microservices architecture with a Distributed Data Store lets failed processes restart from preserved state without a full reboot, on top of the same Junos CLI and operating model.

Built for the AI-Native Networking Platform

Junos integrates with Juniper Paragon, Apstra, and Mist AI so device-level state feeds platform-wide automation, assurance, and AIOps-driven troubleshooting.

Digitally signed, quality-gated releases

Every mainline release ships simultaneously across product lines and must clear zero critical regression errors before release, with executables validated against a digitally signed manifest to block unauthorized binaries.

What it does

Automate with the tools your team already runs

Junos OS integrates with Puppet, Chef, Ansible, and Salt out of the box, plus PyEZ, Juniper's own Python micro-framework for remote device automation, so you extend existing playbooks instead of learning a new toolchain.

Program the device directly with JET

The Juniper Extension Toolkit exposes control-plane, management-plane, and data-plane services through a rich API set that runs independently of the Junos release cycle, giving custom applications a stable interface across hardware generations.

Stream real-time state with JTI

The Junos Telemetry Interface is a distributed analytics engine that gathers, aggregates, and streams accurate network data and event states at scale, feeding your monitoring and assurance stack continuously instead of on a polling interval.

Configure through NETCONF, YANG, and gRPC

Standards-based NETCONF transport with YANG data models, plus gRPC and JSON support, make configuration and state fully machine-readable so changes are version-controlled, reviewed, and applied the same way every time.

Patch hardware without an outage

Junos Continuity lets you install and bring up new hardware as a non-service-impacting event, and combined with ISSU and link aggregation, planned maintenance stops interrupting production traffic.

Slice one chassis into multiple logical routers

Junos Node Slicing converges multiple independent network functions onto a single physical chassis, which cuts rack footprint and power draw while keeping each logical instance independently managed.

Script four ways depending on the trigger

Op-scripts run on demand, event-scripts fire on system events, commit-scripts validate or transform configuration at commit time, and SNMP scripts extend custom MIB support, covering the automation patterns most NetOps teams actually need.

Run Evolved on native Linux for faster iteration

Junos OS Evolved's Distributed Data Store lets applications publish and subscribe to state independently, so a failed process restarts from preserved state without a full reboot, and direct Linux access speeds debugging and third-party tool integration.

The Junos OS & Junos OS Evolved lineup

Junos OS

The proven, broadly deployed Junos build that runs across the MX, EX, QFX, ACX, and SRX families.

The flagship network operating system delivering a consistent, unified experience across routing, switching, and security platforms.

Junos OS Evolved

The Linux-native, microservices version of Junos for high-performance, cloud-scale infrastructure that keeps the same Junos operating model.

Cloud-optimized OS with a microservices architecture running natively on Linux for resiliency and feature velocity.

At a glance

Operating systems
Junos OS and Junos OS Evolved, aligned code and nearly identical CLI across both
Junos OS architecture
Modular software; each module runs in its own protected memory space and can restart independently
Junos OS Evolved architecture
Native Linux, microservices design using a Distributed Data Store (DDS) for centralized state management
Platforms running Junos OS
MX Series and ACX Series routers; EX Series and QFX Series switches; SRX Series firewalls (physical, vSRX virtual, cSRX containerized)
Platforms running Junos OS Evolved
PTX Series routers and select high-performance QFX and ACX platforms built for cloud-scale deployment
Automation and APIs
NETCONF with YANG data models, gRPC, JSON, Juniper Extension Toolkit (JET), PyEZ Python framework, Puppet/Chef/Ansible/Salt integration
Telemetry
Junos Telemetry Interface (JTI), a distributed analytics engine for real-time streaming network data and event states
Scripting
Op-scripts, event-scripts, commit-scripts, and SNMP scripts for on-demand, event-driven, and commit-time automation
High availability
In-Service Software Upgrades (ISSU), link aggregation, and Junos Continuity for non-service-impacting hardware changes
Release quality gate
Mainline releases ship simultaneously across product lines with zero critical regression errors and digitally signed executable manifests

How to buy Junos OS & Junos OS Evolved

Junos OS ships pre-loaded on every HPE Juniper Networking router, switch, and firewall it supports, so in most orders you are not licensing the base OS separately, you are selecting the platform, the feature/software tier attached to it, and the support contract that keeps releases and TAC coverage current.

Bundled with platform hardware

MX, ACX, PTX routers, EX and QFX switches, and SRX firewalls ship with Junos OS or Junos OS Evolved factory-installed and matched to that platform's architecture. You order the box; Uniqcli confirms the correct image and initial release train for your design.

Feature and capacity licenses

Advanced feature sets (routing scale, security services, high-availability add-ons) are licensed per platform on top of the base OS. We map required features to license SKUs during scoping so the quote reflects what your design actually needs, not a guess.

Software support and subscription

Ongoing access to Junos OS releases, patches, and TAC support runs through Juniper (now HPE Juniper Networking) support contracts. Uniqcli sizes the right coverage tier and tracks renewal dates so you are never caught running an unsupported release.

GPC and standard purchase order

Smaller software add-ons and license renewals are GPC-payable; larger platform and multi-year support commitments run through standard purchase order or your agency's contract vehicle. Tell us which applies and we align the quote paperwork accordingly.

State, education, and healthcare cooperative contracts

HPE Juniper Networking participates in cooperative purchasing vehicles including NASPO ValuePoint, Costars, PEPPM, HealthTrust, MiCTA, and multiple state-specific schedules, which can shorten your procurement cycle versus an open bid.

Where it fits

Standardizing NetOps on one operating model across data center, campus, and WAN to cut tooling, licensing, and training overhead
Automating configuration and change control with NETCONF/YANG, JET, and PyEZ instead of manual CLI changes across the fleet
Maintaining service continuity through ISSU, link aggregation, and Junos Continuity in environments where downtime carries mission or compliance impact
Streaming real-time telemetry through JTI into existing monitoring and assurance platforms for faster troubleshooting
Building cloud-scale, high-throughput fabrics on Junos OS Evolved's Linux-native microservices architecture on PTX and select QFX/ACX platforms
Converging multiple logical network functions onto shared chassis hardware with Junos Node Slicing to cut rack and power footprint
Connecting device-level Junos state to Juniper Paragon, Apstra, and Mist AI for platform-wide AIOps and automation

Frequently asked

What's the real difference between Junos OS and Junos OS Evolved?

Junos OS is the broadly deployed, FreeBSD-heritage operating system running across MX, ACX, EX, QFX, and SRX platforms. Junos OS Evolved runs natively on Linux with a microservices architecture and a Distributed Data Store for state, which gives it hitless upgrades, direct Linux tooling access, and faster feature velocity on the PTX and select QFX and ACX platforms it supports. Both keep nearly identical CLI and operating model, so the learning curve between them is minimal. We confirm the right one for your target hardware during scoping.

Which Juniper platforms actually run Junos?

Junos OS runs on MX Series and ACX Series routers, EX Series and QFX Series switches, and SRX Series firewalls including the vSRX virtual and cSRX containerized forms. Junos OS Evolved runs on the PTX Series and specific high-performance QFX and ACX models built for cloud-scale deployment. As an authorized HPE Juniper Networking partner, Uniqcli maps the right platform and OS variant to your design.

How does Junos plug into automation we already have?

Junos integrates directly with Puppet, Chef, Ansible, and Salt, and ships PyEZ for Python-based device automation. For deeper integration, the Juniper Extension Toolkit (JET) exposes control, management, and data-plane APIs, NETCONF with YANG models handles configuration, and the Junos Telemetry Interface (JTI) streams real-time state. None of this requires replacing your existing orchestration stack.

How do we patch and upgrade without an outage?

In-Service Software Upgrades (ISSU) and link aggregation keep services running through most software upgrades, and Junos Continuity treats new hardware installation as a non-service-impacting event. Junos OS Evolved adds hitless upgrades on top of that. We build maintenance runbooks around these features so planned work doesn't turn into an unplanned outage.

Can Uniqcli supply TAA-compliant configurations for federal buyers?

Yes. As an authorized HPE Juniper Networking reseller we can source TAA-compliant hardware and software configurations for federal requirements, and HPE Juniper Networking hardware is also available to state, local, education, and healthcare buyers through cooperative contract vehicles like NASPO ValuePoint, Costars, PEPPM, HealthTrust, and MiCTA. Tell us your contract vehicle or agency requirement and we align the quote and documentation to it.

What certifications validate our team's Junos skills?

Juniper's certification track runs Associate (JNCIA-Junos, the baseline for every specialty track), Specialist (JNCIS), and Professional (JNCIP), with dedicated tracks for enterprise routing and switching, data center, service provider, security, and automation. JNCIA exams run around $100, JNCIS around $200, and JNCIP around $300, with free and instructor-led training available through Juniper's learning portal.

Do we need a separate license for the base OS?

No, Junos OS or Junos OS Evolved ships factory-installed on the platform you order. What you license separately are advanced feature sets, capacity add-ons, and the software support subscription that gets you ongoing releases, patches, and TAC access. We map those to your actual design requirements so the quote isn't padded with features you won't use.

Where do we get pricing for Junos-based platforms?

Uniqcli quotes complete configurations, hardware plus the right Junos OS variant, feature licenses, and support tier, sized to your environment. Start a request through /quote and we'll return a configuration built around your platform, scale, and compliance requirements rather than a generic list price.

Does Junos support multi-tenant or sliced deployments?

Yes. Junos Node Slicing converges multiple independent network functions onto a single chassis, and the disaggregated modular software architecture underlying Junos gives you a flexible consumption model for network applications as your scale and tenancy requirements change.

Works with

Junos OS is the operating layer under Juniper's routing, switching, and security hardware, and it is built to feed the automation and AIOps tools your team already runs rather than replace them.

Build your HPE bill of materials.

Send us the requirement, the project, or an existing quote to beat. We come back with a validated, TAA-compliant HPE configuration and a real price, often below list.

connect [at] getuniqcli.com · Chicago, IL