Rebooting the switch, Configuration guidelines – H3C Technologies H3C S12500 Series Switches User Manual
Page 175

163
Step Command
Remarks
2.
Configure the exception
handling method of the
MPUs.
system-failure { maintain | reboot }
Optional.
By default, an MPU reboots when
an exception occurs to it.
In IRF mode, when the system detects any software abnormality on the active MPU on an IRF member
device, it handles the situation with one of the following two methods:
•
reboot—The device automatically reboots the failed active MPU to recover from the error condition.
•
maintain—The device stays in the error condition so you can collect complete data, including error
messages, for diagnosis. Using this method, you must manually reboot the device.
The system always reboots a card or the auxiliary CPU system when an exception occurs to them.
The exception handling method is effective only for the failed card, and does not influence the functions
of other cards or the IRF fabric.
To configure the exception handling method:
Step Command
Remarks
1.
Enter system view.
system-view N/A
2.
Configure the exception
handling method of the
MPUs.
system-failure { maintain | reboot }
By default, an MPU reboots when
an exception occurs to it.
Rebooting the switch
CAUTION:
Device reboot can interrupt network services.
You can reboot the switch in one of the following ways to recover from an error condition:
•
Reboot the switch 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 switch. This method might cause data loss and hardware
damage, and is the least preferred method.
Reboot at the CLI enables easy remote device maintenance.
Configuration guidelines
•
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.
•
If the switch has only one MPU, rebooting the MPU causes the device to reboot. If the switch 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 reboots a standby MPU. To reboot a standby MPU, use the
slave restart command (see High Availability Command Reference).
- H3C S12500-X Series Switches H3C S9800 Series Switches H3C S9500E Series Switches H3C S5560 Series Switches H3C S5130 Series Switches H3C S5120 Series Switches H3C SR8800 H3C SR6600-X H3C SR6600 H3C MSR 5600 H3C MSR 50 H3C MSR 3600 H3C MSR 30 H3C MSR 2600 H3C MSR 20-2X[40] H3C MSR 20-1X H3C MSR 930 H3C MSR 900 H3C WX3000E Series Wireless Switches H3C WX5500E Series Access Controllers H3C WX3500E Series Access Controllers H3C WX2500E Series Access Controllers H3C WX6000 Series Access Controllers H3C WX5000 Series Access Controllers H3C WX3000 Series Unified Switches H3C LSWM1WCM10 Access Controller Module H3C LSUM3WCMD0 Access Controller Module H3C LSUM1WCME0 Access Controller Module H3C LSWM1WCM20 Access Controller Module H3C LSQM1WCMB0 Access Controller Module H3C LSRM1WCM2A1 Access Controller Module H3C LSBM1WCM2A0 Access Controller Module H3C WA3600 Series Access Points H3C WA2600 Series WLAN Access Points H3C SecPath F5020 H3C SecPath F5040 H3C VMSG VFW1000 H3C S10500 Series Switches