SRX Series Services Gateways · Topic 1 of 4

Junos Architecture and SRX Hardware

Learn the Junos OS control and data plane split, the Routing Engine and PFE, the SRX branch to high end product lines and chassis commands for JN0-232.

  • 5 min
In a nutshell
  • Junos OS separates the control plane (Routing Engine) from the data plane (Packet Forwarding Engine).
  • The RE runs routing protocols, the CLI and management, and builds the forwarding table that the PFE uses.
  • Transit traffic stays in the data plane; host-bound traffic is sent up to the RE.

What it is

Every SRX runs Junos OS, the same operating system that runs Juniper routers and switches. Junos OS separates the work of running the device, the control plane, from the work of moving packets, the data plane (also called the forwarding plane).

The SRX Series is the Juniper family of firewalls, also called services gateways. Models range from small branch boxes to large modular chassis, but they all share that architecture and the same CLI.

Routing Enginecontrol planeforwarding tablePacket Forwarding Enginedata planeTransit packetPacket Forwarding Engineflow processingOut an interface

How it works

Control plane and data plane

Control planeData plane
ComponentRouting Engine (RE)Packet Forwarding Engine (PFE)
JobRuns routing protocols, the CLI, management, the configuration and system logsForwards transit traffic and applies security processing
BuildsThe routing table and the forwarding tableUses the forwarding table copied from the RE
On an SRXJunos OS processes such as the routing and management daemonsFlow processing: sessions, screens, policies, NAT

The Routing Engine builds the routing table from static routes and routing protocols, selects the active routes and pushes a forwarding table down to the PFE. The PFE then forwards transit packets without asking the RE about each one.

Traffic addressed to the device itself, such as SSH, ping or OSPF to an SRX interface, is host-bound (exception) traffic. The data plane hands it up to the Routing Engine, after the security checks the ingress zone allows.

Why the split matters

Because the planes are separate, a busy control plane does not stop forwarding, and heavy transit traffic does not starve the CLI or the routing protocols. Junos OS processes also run in protected memory, so one failed process does not crash the whole system.

Junos OS is built from one code base. The commit model, the configuration hierarchy and most operational commands are the same on an SRX300 and on an SRX5800, which is why the exam treats them as one platform.

Where the SRX adds security

A router forwards each packet on its own. An SRX in its default flow mode forwards sessions: the first packet of a connection is checked against screens, routes, zones and policies, and later packets of the same session follow a fast path. The Traffic Flow and Security Processing page covers this in detail.

SRX product lines

LineExample modelsTypical useHardware notes
BranchSRX300, SRX320, SRX340, SRX345, SRX380Small and branch officesFixed form factor; control and data plane share one multicore CPU
MidrangeSRX1500, SRX1600, SRX2300Large branch, campus edge, small data centerFixed form factor with a dedicated management port
High endSRX4000 line, such as SRX4100 and SRX4600Data center edge, enterprise coreFixed form factor; high throughput
ModularSRX5400, SRX5600, SRX5800Service provider and large data centerChassis with separate cards for the Routing Engine, input and output, and services processing
VirtualvSRX Virtual FirewallHypervisors and public cloudsSame Junos OS in a virtual machine

On the modular SRX5000 line, Services Processing Cards hold the Services Processing Units (SPUs) that run flow processing, and adding cards adds capacity. On branch models there are no separate cards: the control plane and the flow process run as separate processes on different cores of the same CPU.

Management ports

Larger SRX models and the vSRX have a dedicated out-of-band management interface, fxp0. It is connected to the Routing Engine, belongs to no security zone and does not carry transit traffic. On branch SRX models in standalone mode, you manage the device through a revenue port such as a ge interface placed in a zone.

Every model also has a console port for direct serial access, which is how you reach a device with no configuration.

Chassis commands

CommandShows
show versionModel, host name and Junos OS release
show chassis hardwareInstalled components with part and serial numbers
show chassis routing-engineRouting Engine CPU, memory, uptime and load
show chassis environmentTemperatures, fans and power supplies
show chassis alarmsActive chassis alarms
show system storageFree space on the file systems
user@srx> show version
Hostname: srx-branch
Model: srx345
Junos: 23.4R2
Exam tip

When a question asks which plane runs OSPF, SSH or the CLI, the answer is the control plane (Routing Engine). When it asks which plane creates sessions or applies a security policy, the answer is the data plane.

Common mistakes

Thinking the Routing Engine forwards transit traffic. The RE builds the forwarding table, but the PFE forwards transit packets. Only host-bound traffic reaches the RE.

Thinking fxp0 needs a security zone. The out-of-band management port is not part of any security zone, and it never forwards transit traffic between zones.

Believing each SRX model runs a different OS. All SRX models, including the vSRX, run Junos OS with the same CLI and commit model. Feature support and scale differ, not the operating system.

Mixing up SPUs and the Routing Engine. SPUs process flows on the data plane. The Routing Engine is the control plane.

Watch out

A failed or busy Routing Engine process does not by itself stop existing sessions from forwarding. Exam options sometimes claim that the data plane stops whenever the control plane is under load.

What to remember for the exam

  • Junos OS separates the control plane (Routing Engine) from the data plane (Packet Forwarding Engine).
  • The RE runs routing protocols, the CLI and management, and builds the forwarding table that the PFE uses.
  • Transit traffic stays in the data plane; host-bound traffic is sent up to the RE.
  • The SRX data plane is flow-based for IPv4 by default and tracks sessions.
  • Branch SRX models share one CPU between control and flow processing; the SRX5000 line uses SPUs on Services Processing Cards.
  • fxp0 is the out-of-band management port on larger models and the vSRX; it is in no security zone.
  • show chassis hardware lists components; show version shows the model and release.

Check yourself

  • Which component builds the forwarding table on an SRX?

    The Routing Engine, the control plane. It copies the forwarding table to the Packet Forwarding Engine, which forwards transit traffic.

  • On an SRX5800, what hardware runs the flow sessions?

    The Services Processing Units on the Services Processing Cards, which are part of the data plane.

  • Does the fxp0 interface need to be assigned to a security zone?

    No. fxp0 is the out-of-band management port, belongs to no security zone and does not forward transit traffic.

Topic 1 of 4 in SRX Series Services Gateways

Test yourself on SRX Series Services Gateways

The full Juniper JNCIA-SEC JN0-232 question bank has 658 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.