153
NOTE:
In an IRF fabric, the exception handling method applies to all member switches, but the member switches
handle system exceptions independently without affecting one another.
Rebooting the device
You can reboot the device in one of the following ways 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 re-power on the device. This method might cause data loss and hardware
damage, and is the least preferred method.
Reboot at the CLI enables easy remote device maintenance.
CAUTION:
•
A reboot can interrupt 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 check 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.
Rebooting devices immediately at the CLI
Perform the following command in user view to reboot a device:
To do…
Use the command…
Remarks
Reboot a switch or all IRF member
switches immediately
reboot
[
slot
slot-number
]
Required
If you do not specify any IRF
member ID for the
slot-number
argument, all IRF member switches
reboot.
Scheduling a device reboot
Perform one of the following commands in user view to schedule a device reboot:
To do…
Use the command…
Remarks
Schedule a reboot to occur at a
specific time and date
schedule reboot at
hh:mm
[
date
]
Schedule a reboot to occur after a
delay
schedule reboot delay
{
hh:mm
|
mm
}
Required
Use either command.
The scheduled reboot function is
disabled by default.
