1-3
z
After this command is configured, both the active SRPU and the standby SRPU adopt the same
method to handle exceptions. The system adopts the
reboot
method to handle exceptions
happened on an interface card or the auxiliary CPU system, that is, the system reboots the failed
card.
z
The exception handling method is effective to the failed card only, and does not influence the
functions of other cards.
Follow these steps to configure exception handling method (distributed IRF device):
To do…
Use the command…
Remarks
Enter system view
system-view
—
Configure exception handling
method on all member devices
system-failure
{
maintain
|
reboot
}
Optional
By default, all member devices
adopt the
reboot
method to
handle exceptions.
z
After this command is configured, all the member devices adopt the same method to handle
exceptions.
z
The exception handling method is effective to the failed member device only, and does not
influence the operations of other IRF members.
Rebooting a Device
When a fault occurs to a running device, you can remove the fault by rebooting the device, depending
on the actual situation.
You can reboot a device following any of the three methods:
z
Power on the device after powering it off, which is also called hard reboot or cold start. This method
impacts the device a lot. Powering off a running device will cause data loss and hardware damages.
It is not recommended.
z
Trigger the immediate reboot through command lines.
z
Enable the scheduled reboot function through command lines. You can set a time at which the
device can automatically reboot, or set a delay so that the device can automatically reboot within
the delay.
The last two methods are command line operations. Reboot through command lines is also called hot
start, which is mainly used to reboot a device in remote maintenance without performing hardware
reboot of the device.
Summary of Contents for S7902E
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1 ...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist ...
Page 598: ...ii ...
Page 1757: ...4 9 ...
Page 1770: ...6 4 ...
Page 2017: ...2 11 Figure 2 3 SFTP client interface ...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002 ...