Cisco 6800 Chassis Fan Tray - Reports Critical Alarm
book
Article ID: 331676
calendar_today
Updated On:
Products
VMware Smart AssuranceVMware Telco Cloud Service Assurance
Issue/Introduction
Symptoms:
CISCO 6800 Switches discover Chassis Fan Trays that are reporting false critical alerts.
The device SYSOID is .1.3.6.1.4.1.9.1.1934.
There are a number of Fans that have a similar description that show FEX-xxx Slot y Chassis Fan Tray that Smarts IP discovers. Smarts reports these Fans in this scenario report
StateNotNormalActive = TRUE Status = CRITICAL
Environment
SMARTS - 10.1.x
SMARTS - 2.x
TCSA - 2.x
Cause
Smarts properly discovers the Fans.
In reviewing the Instrumentation CISCO and Smarts is using the EnvMon MIB and the following OID to determine the Fan Status.
Object ciscoEnvMonFanState OID 1.3.6.1.4.1.9.9.13.1.4.1.3 Type CiscoEnvMonState 1:normal 2:warning 3:critical 4:shutdown 5:notPresent 6:notFunctioning
In this case the snmpwalk reports all of the discovered Fans that have the description of "FEX-xxx Slot y Chassis Fan Tray*" as a value of "3", Critical State. * Here xxx and y are numerical values specific to the discovered Fan.
What we can do is walk this oid on a few of CISCO 6800 devices and confirm that the Indexes that belong to the fans that have a the following "FEX-xxx Slot y Chassis Fan Tray..." are reporting a value of 3 sm_snmp -c <community string> -d <device name or IP> walk 1.3.6.1.4.1.9.9.13.1.4.1.3
The data from the snmpwalk of one of the impacted devices Line 638903: .1.3.6.1.4.1.9.9.13.1.4.1.3.101|1| Line 638904: .1.3.6.1.4.1.9.9.13.1.4.1.3.102|1| Line 638905: .1.3.6.1.4.1.9.9.13.1.4.1.3.103|1| Line 638906: .1.3.6.1.4.1.9.9.13.1.4.1.3.201|1| Line 638907: .1.3.6.1.4.1.9.9.13.1.4.1.3.202|1| Line 638908: .1.3.6.1.4.1.9.9.13.1.4.1.3.203|1| Line 638909: .1.3.6.1.4.1.9.9.13.1.4.1.3.311|3| These all have the FEX-xxx Slot y Chassis Fan Tray in the description. Line 638910: .1.3.6.1.4.1.9.9.13.1.4.1.3.322|3| Line 638911: .1.3.6.1.4.1.9.9.13.1.4.1.3.333|3| Line 638912: .1.3.6.1.4.1.9.9.13.1.4.1.3.411|3| Line 638913: .1.3.6.1.4.1.9.9.13.1.4.1.3.422|3| Line 638914: .1.3.6.1.4.1.9.9.13.1.4.1.3.511|3| Line 638915: .1.3.6.1.4.1.9.9.13.1.4.1.3.522|3|
Resolution
Please contact device vendor (CISCO), As there may be a configuration issue with the CISCO 6800 device or a bug with the CISCO snmpagent.
Smarts is working as designed as the MIB used is the same MIB that CISCO is using and the snmpagent is reported the Fan State as Critical as shown here in this KB.
Additional Information
From Smarts you can "Explicitly Unmanage" the Fans with the Fex Slot description. This can be done in a script during post processing or you can unmanage the Chassis Fans individually via the Smarts Console to remove the alarms.
Review the custom-end-post.asl file in your IP/smarts/local/rules/discovery/custom folder, or IP/smarts/rules/discovery/custom folder.