Rebooting Your System - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x System Basics Configuration Guide

Rebooting Your System

You can reboot your system as a whole or select a single slot in the system to be
rebooted. You can reboot your system immediately or in a designated interval of
time, and can configure the system to prompt you if the modules are in a state that
could lead to a loss of configuration data or an NVS corruption.
If you reboot the system before it has completely written configuration updates to
NVS, the system will start with the last saved configuration. If you reboot the system
after it has written the configuration updates to NVS, but before it has applied those
updates to actual configuration data, the configuration update process resumes
immediately following the reboot and completes before any application accesses its
configuration data.
reload
514
Rebooting Your System
In a dual SRP configuration, when this information is synchronized to the standby
SRP, the standby SRP is reloaded to boot the specified release. The high
availability feature requires the release to be the same on the active and the
standby SRP. This means that arming the system to boot with a different release
causes the standby to reload and prevent high availability from becoming active
or disable high availability it if it is active or pending.
Example
host1(config)#boot system release1.rel
There is no no version.
See boot system.
Use to reload the software on the system immediately.
Reloads the system software (.rel) file and the configuration (.cnf) file on the
system.
When you issue this command, the system prompts you for a confirmation
before the procedure starts.
If you specify the force keyword, the procedure will fail if the system is updating
the boot prom. In this case, the system will display a message that indicates that
the procedure cannot currently be performed and the cause. However, if the
system is in a state that could lead to a loss of configuration data or an NVS
corruption, such as during the synchronization of SRP modules, the system
displays a message that describes the state, and asks you to confirm (enter y for
yes, n for no) whether you want to proceed.
If you do not specify the force keyword, the procedure will fail if the system is
in a state that could lead to a loss of configuration data or an NVS corruption,
and the system will display a message that explains why the procedure failed.
Use the standby-srp keyword to reload the system software (.rel) file and the
configuration (.cnf) file on the standby SRP module without having to look up
its slot number to use with the reload slot command.