The Junos OS operates using a candidate configuration model, where changes are made in a temporary buffer before being applied to the running system. To ensure accuracy and prevent unintended network disruptions, it is a critical best practice to review the differences between the candidate buffer and the currently active configuration. The command show | compare executed from the [edit] hierarchy level is the primary tool for this task.
When this command is issued, the CLI performs a line-by-line comparison. The output uses a " diff " format: lines prefixed with a plus sign (+) represent new statements added to the candidate configuration, while lines prefixed with a minus sign (-) indicate statements that have been removed. This visualization allows the architect to verify exactly what will change upon execution of the commit command. Unlike operational mode commands that only show the final state, show | compare highlights the delta, making it indispensable for auditing complex policy changes or interface reconfigurations. This step acts as a final manual validation gate, reducing the risk of syntax errors or logical misconfigurations entering the production environment. Using this command is a fundamental skill for passing the JNCIA-Junos exam and for professional day-to-day operations.
[Reference: Configuration Basics, Comparing Configurations, Candidate vs. Active., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit