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

Version 7.0.0
Hide thumbs Also See for ExtremeWare:
Table of Contents

Advertisement

config sys-health-check auto-recovery

config sys-health-check auto-recovery <number of tries> [offline | online]
Description
Configures the system health checker.
Syntax Description
number of tries
offline
online
Default
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, MSM64i 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, MSM64i, 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 may
generate critical error messages in the syslog, and may also send a trap and/or shut down the system.
The system health checker will continue to periodically forward test packets to failed components. If
auto-recovery is configured, the system will attempt to automatically reset the faulty module and bring
it back online.
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
will indicate that it has been disabled by sending a message to the syslog. In ExtremeWare 6.2 or later,
this restriction does not apply.
ExtremeWare Software 7.0.0 Command Reference Guide
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.
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.
Specifies that a faulty module is kept online, regardless of memory scanning
or memory mapping errors.
config sys-health-check auto-recovery
517

Advertisement

Table of Contents
loading

This manual is also suitable for:

Extremeware 7.0.0

Table of Contents