Juniper JUNOSE 11.3, Configuration Manual

Page: 530 / 632

•
Use to specify the software release (.rel) file that your system will use when rebooting.
•
This command does not reboot the 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.
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 might 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 starts 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. For more information about stateful line module switchover, see
Managing Stateful
Line Module Switchover in the JunosE Services Availability Configuration Guide .
When stateful switchover for line modules is configured on a router and is activated, the
line modules undergo a cold boot and, during this process, the secondary line module
remains in the disabled or not online state. The primary line module returns to the online
state. If the primary line module fails to become active within the specified timeout value
(of less than 8.5 minutes), the secondary line module takes over as the primary and high
availability is retained in the disabled state. All warm switchover processes are recorded
in the reboot-history file on the currently active SRP module as warm restart.
reload
•
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
Copyright © 2010, Juniper Networks, Inc. 500
JunosE 11.3.x System Basics Configuration Guide