The Routing Engine (RE) is the " brains " of a Juniper device, representing the control plane in the Junos dual-plane architecture. One of its primary functions is that it runs the Junos OS . The RE is essentially a high-performance workstation running a specialized version of FreeBSD that hosts the various software daemons responsible for the device ' s logic, such as the Routing Protocol Process (rpd) and the Device Control Process (dcd).

The second core function is that the RE processes all management traffic . Any packet destined for the router itself—such as an SSH session, an SNMP poll, a NETCONF request, or an NTP update—is handled by the Routing Engine ' s CPU. The RE also maintains the master routing table, manages configuration commits, and provides the CLI environment for the administrator.

It is critical to distinguish these control-plane duties from the duties of the Packet Forwarding Engine (PFE) . The PFE is responsible for the " heavy lifting, " such as processing transit traffic (data passing through the router) and evaluating firewall filters at wire speed. While the RE defines the policies and routing tables, it hands off a streamlined version of this information to the PFE so the RE isn ' t bogged down by millions of individual packets. This separation ensures that a busy management session or a complex routing calculation on the RE doesn ' t impact the device ' s ability to forward traffic at maximum capacity.