Extreme Networks ExtremeWare Version 7.8, Troubleshooting Manual

Page: 41 / 122

Configuring System Recovery Actions
Advanced System Diagnostics and Troubleshooting Guide 41
Configuring System Recovery Actions on “ e ” Series Switches
To specify a system recovery scheme for “ e ” series switches when a software exception occurs, use this
command:
configure sys-recovery-level [none | [all | critical]] [reboot]
where:
Usage Notes
When you configure the
shutdown
option, and a software exception occurs, the system takes these
actions:
• All watchdogs and timers are stopped.
• All tasks except the following are suspended:
— tSwFault
— tLogTask
— tSyslogTask
— tShell
— tConsole
— tExtTask
— tExcTask
— The root task
• On BlackDiamond and Alpine switches, the I/O modules are powered down.
• On BlackDiamond switches, the slave MSM is instructed not to monitor the master MSM.
When the
MSM-failover
option is configured on a system equipped with MSM-64i modules and an
error occurs, the system requires a system reboot, so the impact to the system is basically the same as
for the
reboot
option.
When the
MSM-failover
option is configured on a system equipped with MSM-3 modules and an error
occurs, the system does not require a system reboot, so there is no service outage.
When the
reboot
option is configured on a system and an error occurs, the system is rebooted, causing
loss of connectivity to all modules. All software tasks are restarted, so any exception error is cleared and
the task restarted. If the task cannot be restarted, the system will fail the POST and will remain in
limited operation mode for further troubleshooting.
When the
shutdown
option is configured on the system and an error occurs, the system is shut down
and held out of service. This option offers administrators the ability to restore the system and reinsert it
none
No recovery action is taken when a software exception occurs (no system shutdown or
reboot, etc.). This is the default action.
all
If
any task exception occurs, ExtremeWare logs an error in the system log and, if
configured, automatically initiates the optional response action
reboot
(reboots the
switch).
critical
If a critical task exception occurs, ExtremeWare logs an error in the system log and, if
configured, automatically initiates the optional response action
reboot
(reboots the
switch). Critical tasks include the tBGTask, tNetTask, tEdpTask, and tEsrpTask.