Extreme Networks ExtremeWare 7.7, Command Reference Manual

Page: 720 / 2620

720 ExtremeWare 7.7 Command Reference Guide
Commands for Status Monitoring and Statistics
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.
In the BlackDiamond switches , the
<number>
option configures the number of times the system health
checker attempts to automatically reset a faulty module and bring it online. If the system health checker
fails more than the configured number of attempts, it sets the module to card-down. This threshold
applies only to BlackDiamond I/O modules.
In ExtremeWare 6.2.1 or later, when auto-recovery is configured, the occurrence of three consecutive
checksum errors causes the packet memory (PM) defect detection program to be run against the I/O
module. Checksum errors can include internal and external MAC port parity errors, EDP checksum
errors, and CPU packet or diagnostic packet checksum errors. If defects are detected, the module is
taken off line, the memory defect information is recorded in the module EEPROM, the defective buffer
is mapped out of further use, and the module is returned to operational state. A maximum of 8 defects
can be stored in the EEPROM.
After the PM defect detection and mapping process has been run, a module is considered failed and is
taken off line in the following circumstances:
• 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.
The auto-recovery repetition value is ignored in these cases. In any of these cases, please contact
Extreme Technical Support.
Auto-recovery mode only affects an MSM if the system has no slave MSM. If the faulty module is the
only MSM in the system, auto-recovery automatically resets the MSM and brings it back on line.
Otherwise, auto-recovery has no effect on an MSM.
If you specify the
online
option, the module is kept on line, but the following error messages are
recorded in the log:
<WARN:SYST> card_db.c 832: Although card 2 is back online, contact Tech. Supp. for
assistance.
<WARN:SYST> card_db.c 821: Card 2 has nonrecoverable packet memory defect.
To view the status of the system health checker, use the
show diagnostics
command.
To enable the health checker, use the
enable sys-health-check
command.
To disable the health checker, use the
disable sys-health-check
command.
If the faulty module is a master MSM, the slave MSM automatically becomes the master and sets the
faulty MSM to
card-down
. The new master MSM re-initializes and brings up all the I/O modules.
If the faulty module is a master MSM and there is no slave MSM, the system continues operation in a
“limited commands” mode. In the “limited commands” mode, the I/O slots are not initialized, and the
only commands allowed are those that do not affect the switch hardware configuration.
If the faulty module is a slave MSM, the fault is recorded in the slave MSM NVRAM, and the slave
MSM is taken off line.