•reboot—Rebooting the failed MPU so that the MPU restores to normal operating status.

•maintain—Maintaining the current status of the failed MPU so that the system does not take any restoration measures. Some software faults are hard to reproduce, and the printed information will be lost after the router reboots. In this case, you can maintain the current status of the router, facilitating fault location.

If the FIP or SAP/OAP module encounters software faults, the solving method is always reboot, which reboots the failed module.

On a router with two MPUs, rebooting the active MPU triggers an active and standby switchover, and the former standby MPU takes over. On a router with only one MPU, rebooting the active MPU reboots the router.

When system faults occur, the system fault solving method applies to only the failed module, and rebooting the module does not interrupt the other modules.

To configure the exception handling methods:

Step

 

Command

Remarks

1.

Enter system view.

system-view

N/A

 

 

 

 

 

 

 

Optional.

2.

Configure the exception

system-failure { maintain

By default, the system adopts the

 

handling methods.

reboot }

reboot method to handle

exceptions.

Displaying the exception handling method

Use the display system-failure command to display the exception handling method.

<Sysname> display system-failure System failure handling method: reboot

Rebooting a card or router

CAUTION:

Do not use the reboot command to reboot the standby MPU. To reboot it, use the slave restart command.

When upgrading and maintaining the system software image or configuration file for the router, you need to reboot the router. After you change the operating mode of a MPU or LPU, you must restart the corresponding module.

To reboot a router, use one of the following methods:

•Power off and then power on the router. This method might cause data loss, and is the least-preferred method.

•Immediately reboot the router at the CLI.

•Schedule a reboot at the CLI, so the router automatically reboots at the specified time or after the specified period of time.

The first method is called "cold reboot" or "cold startup". The second and third methods are called "warm reboot" or "warm startup", and can be used remotely.

65