Article ID: 13323
SecureStack C3, C2, B3, B2, A2
Determining the failing unit from a fan failure syslog
message is explained in 5743
Fan failure traps
are not specifically controllable but may be generated from the fanFail section of the cabletron-traps MIB, when traps are enabled and a fan has failed.
In NetSight Console, the trap summary line looks something like: Notice SNMP v2 09/09/2010 01:28:27 PM 10.20.109.50 --- SNMP Trap Trap fanFail Fan Failure.[/code]Double-clicking on a summary line to pull up event details looks something like: Timestamp: 09/09/2010 01:28:27 PM Acknowledged: No
Type: Trap Source: 10.20.109.50
Event Name: fanFail Client: ---
Severity: Notice User: SNMP Trap
Category: SNMP v2
Information: Fan Failure.
Enterprise: Cabletron Trap Number: .22.214.171.124.126.96.36.199.286
Description: This trap is generated when the device detects that
the system fans have failed.[/code]Such traps are not formulated to provide detailed information of the failing unit within a stacked topology, however do serve the purpose of alerting the network administrator to look in the syslog for more detailed diagnostic information.
If a current syslog repository is not available in NetSight or some other network management application, a current.log (5487
) file would provide fan failure information for a standalone or a stack, with any firmware version. A simpler approach that would work for this purpose is to issue a 'show support' command while running "higher firmware". The items listed at the end of that output - as read from the manager unit - may be interpreted as explained in 5743