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
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.
When you issue this command, the system prompts you for
a confirmation before the procedure starts.
If you remove a standby SRP module without issuing the slot erase command to delete the configuration, the
E-series router cannot guarantee that the SRP modules were synchronized.
In this situation, you must do either of the following to reload the
router:
Issue the reload command with
the force keyword.
Issue the slot erase command
followed by the reload command.
Use to reload the software on the system at an absolute
time.
This command halts the system.
Reloads the system software (.rel) file and the configuration
(.cnf) file on the system.If the system is in a state that could lead
to a loss of configuration data or an NVS corruption, it will delay
the procedure for one minute. Each time the system delays the procedure,
it adds a message to the os log that explains why the procedure was
delayed. If the system cannot reload on its sixth attempt, the reboot
procedure will fail, and the system will add an explanation to the
os log.
Example
host1#reload at 10:10 May 5
This command reloads the software 10
minutes after 10 on May 5th.
Use to reload the software on the system in a relative
period of time.
This command halts the system.
Reloads the system software (.rel) file and the configuration
(.cnf) file on the system.
If the system is in a state that could lead to a loss
of configuration data or an NVS corruption, it will delay the procedure
for one minute. Each time the system delays the procedure, it adds
a message to the os log that explains why the procedure was delayed.
If the system cannot reload on its sixth attempt, the reboot procedure
will fail, and the system will add an explanation to the os log.
Reloads the system software (.rel) file and the configuration
(.cnf) file on the module in the selected slot.
When you issue this command, the system prompts you for
a confirmation before the procedure starts.
If you specify the force keyword
and the slot number of the primary SRP module, 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 using the synchronization of SRP modules, it displays a message
that describes the state, and asks you to confirm (enter yes or 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.
Rebooting When a Command Takes a Prolonged Time to Execute
Although some commands might take a relatively
long time to execute, most do not. If the CLI displays no output other
than “ Please wait...” for a prolonged period, you can
press Ctrl+x to reset the system. Use Ctrl+x only as a last resort;
if at all possible, wait until the command is completed, or attempt
to connect to the system through a Telnet or SSH client through which
you can use the reload command.
service ctrl-x-reboot
Use to enable the Ctrl+x key combination to reset the
system from any location.
Issuing the Ctrl+x command has no effect if you are accessing
the system through Telnet.
This feature is disabled by default.
Loading the factory default configuration does not override
this feature.
Configuration caching prevents the system from
being partially configured with changes in the event of a reset. When
a script or macro begins execution, the resulting configuration changes
are automatically cached in system RAM rather than being committed
to nonvolatile storage (NVS). When the script or macro completes execution,
the cache is flushed as a background operation, saving the configuration
changes to NVS.
If the SRP module resets during the script or macro
execution, the system boots as though the script were never started
because no NVS files have changed. If the SRP module resets during
the flush operation, the system boots with factory defaults.
If you start another script or macro in the middle
of an ongoing flush operation, the current flush is halted; now if
the SRP module resets during the script, the system boots with factory
defaults.
If you issue the reload command to manually reset the system, the system checks for an ongoing
cache flush and warns you if a flush operation is discovered.
