PDF JN0-106 Study Guide

Junos OS features a sophisticated configuration management system that automatically creates a snapshot of the active configuration every time a commit is successfully performed. These snapshots are stored as rollback files in a historical archive. Within the configuration mode hierarchy, the rollback command allows an administrator to discard current candidate changes and load a previously committed configuration into the candidate buffer.

The numbering of these rollback files is sequential and follows a specific logic: rollback 0 represents the configuration that is currently active and running on the system. To revert to the state that existed immediately prior to the most recent commit, the administrator must use rollback 1. This command overwrites the current candidate configuration with the previous operational state. It is important to note that executing rollback 1 does not immediately impact the running system; it merely populates the candidate database. The changes must still be verified—often using show | compare—and then finalized by executing the commit command. By default, Junos maintains up to 50 of these rollback configurations (and up to 100 on certain platforms/versions), providing a robust safety net for operational recovery and auditing. Reference: Configuration Basics, Managing Configurations, Rollback configurations.

In the Junos OS architecture, the Routing Engine (RE) manages path selection by evaluating multiple potential routes to a specific destination found within the Routing Information Base (RIB). When multiple routing sources (such as static configuration, OSPF, IS-IS, and BGP) provide information for the exact same destination prefix—in this case, 192.168.100.100/32 —the device utilizes route preference as the primary tie-breaker to determine which entry becomes the " active " route.

The provided exhibit displays the default preference values for each protocol: Static is 5 , OSPF is 10 , IS-IS is 15 , and BGP is 170 . Junos OS follows a " lower is better " logic for preference; therefore, the Static route is selected as the most trustworthy path. In the command output, the active route is explicitly identified by the asterisk (*) and plus sign (+) symbols located next to the [Static/5] entry. Looking at the specific next-hop information for this active static route, the output indicates the traffic is sent to 192.168.0.2 via xe-0/0/0.0 . Consequently, the Packet Forwarding Engine (PFE) will install this specific path into the forwarding table, causing all traffic destined for 192.168.100.100 to be egressed over the xe-0/0/0.0 interface.

Maintaining the integrity of the Junos OS file system is a critical operational requirement, especially during maintenance that involves removing power from the hardware. To achieve a graceful power-down, the request system halt command must be used. This command initiates a systematic shutdown of all running software processes and daemons, flushes any pending data from the system ' s volatile memory (RAM) to the solid-state storage or hard disk, and unmounts the file systems correctly. Once the software has safely shut down, the console will typically display a message indicating that it is safe to turn off the physical power switch or remove the power cables.

Using request system halt prevents potential file system corruption that can occur if power is abruptly cut while the OS is actively writing logs or configuration data. This is distinct from request system reboot, which restarts the OS, or request system logout, which merely terminates the current CLI session. As a Senior Architect, it is essential to follow this procedure to ensure that the device remains in a reliable state for its next power-on cycle. For devices equipped with dual Routing Engines, the command can often be directed to a specific member or both simultaneously to ensure a synchronized and safe shutdown of the entire chassis. Reference: Operational Monitoring and Maintenance, System Halt and Reboot Procedures.

==========

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.