Configure Sys-Health-Check Auto-Recovery - Extreme Networks ExtremeWare Command Reference Manual

Commands for Status Monitoring and Statistics

configure sys-health-check auto-recovery

configure sys-health-check auto-recovery <number> [offline | online]
Description
Configures the auto-recovery function of the system health checker.
NOTE
This command is available only on the "i" series switches.
Syntax Description
number Specifies the number of times that the health checker attempts to auto-recover a faulty module.
The range is from 0 through 255 times. Default is 3 times.
NOTE: This option is available only in BlackDiamond I/O modules.
offline Specifies that a faulty module is taken offline and kept offline if one of the following occurs:
• More than eight defects are detected.
• Three consecutive checksum errors were detected by the health checker, but no new defects
were found by the memory scanning and mapping process.
• After defects were detected and mapped out, the same checksum errors are again detected
by the system health checker.
online Specifies that a faulty module is kept online, regardless of memory scanning or memory
mapping errors.
Default
The default alarm level is log.
Usage Guidelines
This command allows you to configure the switch's reaction to a failed health check.
The system health checker tests I/O modules, MSM modules, and the backplane by forwarding packets
every 4 seconds. Additional checking for the validity of these packets is completed by performing a
checksum.
By isolating faults to a specific module, MSM, or backplane connection, the system health checker
prevents corrupted packets from being propagated to the CPU, upper layer modules, or the rest of your
network. If you observe a failure, please contact Extreme Technical Support.
Depending on how you have configured the system health checker, failed system health checks can
generate critical error messages in the syslog, and can also send a trap and/or shut down the system.
The system health checker continues to periodically forward test packets to failed components. If
auto-recovery is configured, the system attempts to automatically reset the faulty module and bring it
back on line.
In ExtremeWare versions prior to 6.2, you cannot use both mirroring and the system health checker at
the same time. If you configure mirroring with the system health checker enabled, the health checker
indicates that it has been disabled by sending a message to the syslog. In ExtremeWare 6.2 or later, this
restriction does not apply.
708 ExtremeWare 7.5 Command Reference Guide