R3303-HP 6600/HSR6600 Routers Fundamentals Configuration Guide

133
Rebooting the device
CAUTION:
• A device reboot interrupts network services.
• To avoid data loss, use the save command to save the current configuration before a reboot.
• Use the display startup and display boot-loader commands to verify that you have correctly set the
startup configuration file and the main system software image file. If the main system software image file
has been corrupted or does not exist, the device cannot reboot. You must re-specify a main system
software image file, or power off the device and then power it on so the system can reboot with the
backup system software image file.
You can reboot the device by using one of the following methods to recover from an error condition:
• Reboot the device immediately at the CLI.
• At the CLI, schedule a reboot to occur at a specific time and date or after a delay.
• Power off and then power on the device. This method might cause data loss, and is the
least-preferred method.
Reboot at the CLI enables easy remote device maintenance.
Rebooting devices immediately at the CLI
If an 6604, 6608, or 6616 has only one MPU, rebooting the MPU causes the device to reboot. If the
device has two MPUs, rebooting the active MPU causes the active MPU to reboot and an active/standby
switchover. You cannot use the reboot command to reboot a standby MPU. To reboot a standby MPU, use
the slave restart command (see High Availability Command Reference).
To reboot an 6602, execute the following command in user view:
Task Command
Reboot a subcard or the device immediately. reboot [slot slot-number ]
To reboot an HSR6602, 6604, 6608, 6616, execute the following command in user view:
Task Command Remarks
Reboot a card, a subcard, or the
device immediately.
reboot [ slot slot-number [ subslot
subslot-number ] ]
If no card is specified, the
command reboots the device.
Scheduling a device reboot
The device supports only one device reboot schedule. If you configure the schedule reboot delay
command multiple times, the most recent configuration takes effect. The schedule reboot at command
and the schedule reboot delay command overwrite each other, and whichever is configured last takes
effect.
For data security, if you are performing file operations at the reboot time, the system does not reboot.