A change during a maintenance window breaks IP reachability to a POP router, leaving only console access available. A rescue configuration was saved earlier that day. What is the correct way to restore the router to that known-good baseline?
Select an answer to reveal the explanation.
Short Explanation
Saving and restoring are two different verbs here — save stores the safety copy, and rollback rescue is what actually pulls it back into the candidate config so you can commit it live again.
Full Explanation
Restoring a previously saved rescue configuration is done with rollback rescue, which loads the saved rescue configuration into the candidate configuration, followed by a commit to make it active, exactly the sequence needed to recover a router reachable only via console after a bad change. Running request system configuration rescue save again does the opposite of what is needed here — it overwrites the saved rescue configuration with whatever is currently active, which in this scenario is the broken configuration, destroying the very baseline the engineer needs. Power-cycling the router does not load the rescue configuration automatically; Junos boots with whatever configuration is already active or committed, and a reboot alone does nothing to restore a different one. Rescue configuration recovery is a standard administrator-level CLI operation performed locally via console or management access; it does not require Juniper support involvement. After running rollback rescue and committing, show configuration | compare rollback 1 or simply verifying reachability and expected settings confirms the known-good baseline is now active again.