Multiple fans has failed. Chassis temperature is too high
Applies to
- FAS2720
- ONTAP 9.5P16
- BMC
Issue
- The
EMS-LOG-FILE
section of AutoSupport:
[Node-01: monitor: monitor.globalStatus.critical:EMERGENCY]: Multiple fans has failed. Chassis temperature is too high.
[Node-01: env_mgr: monitor.fan.warning:notice]: multiple fans have failed. Replace it to avoid overheating
[Node-01: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Module B Expander Temp) is not readable.
...
[Node-01: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 4 Temp) is not readable.
[Node-01: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Midplane 3 Temp) is not readable.
...
[Node-01: env_mgr: monitor.temp.unreadable:error]: The controller temperature (Ambient Temp) is not readable.
[Node-01: monitor: monitor.globalStatus.critical:EMERGENCY]: Multiple fans has failed. Chassis temperature is too high.
[Node-01: env_mgr: callhome.c.fan.fru.fault:error]: Call home for CHASSIS FAN FRU FAILED: Multiple fans have failed
- The latest version of BMC Firmware does not clear the alert
- The
IFSTAT-A
section of the AutoSupport for interface e0M has high Transmit values
(Or use Cluster::*> system node run -node Node-01 -command ifstat e0M)
-- interface e0M (292 days, 7 hours, 50 minutes, 35 seconds) -- TRANSMIT Total frames: 322g | Frames/second: 12785 | Total bytes: 1386t Bytes/second: 54899k | Total errors: 0 | Errors/minute: 0 ... TSO segments: 321g | TSO bytes: 1340t | TSO6 segments: 0 TSO6 bytes: 0 | HW UDP cksums: 53871 | HW UDP6 cksums: 0 HW TCP cksums: 322g | HW TCP6 cksums: 0 | Mcast v6 solicit: 0
- The system is used for Network Data Management Protocol (NDMP) based backup
- The
NDMP
section of the AutoSupport provides the IP-addresses used for NDMP
[kern_ndmpd:info:5238] [93154] DEBUG: NDMP Connect: Successfully connected to [10.xx.x.xxx].39441, using local address [10.xx.x.x].24858
[kern_ndmpd:info:5238] [93159] DEBUG: NDMP Connect: Successfully connected to [10.xx.x.xxx].39487, using local address [10.xx.x.x].49987
[kern_ndmpd:info:5238] [93165] DEBUG: NDMP Connect: Successfully connected to [10.xx.x.xxx].39545, using local address [10.xx.x.x].28630 (+0:00:01)
[kern_ndmpd:info:5238] [93170] DEBUG: NDMP Connect: Successfully connected to [10.xx.x.xxx].39591, using local address [10.xx.x.x].17084
- The
NETSAT-NRGD
section of the AutoSupport present the routing tables:
---- Default IPSpace ----
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Metric Netif Expire
default xx.xx.x.xxx UGS 0 53480 1500 110 a0a-704 => xx.xx.x.x
default xx.xx.x.xxx UGS 0 78163 1500 65 e0M => xx.xx.x.xxx
default xx.xx.x.xxx UGS 0 202969 1500 65 e0M xx.xx.x.xxx
10.0.0.205 xx.xx.x.xxx UGHS 0 133280 1500 110 a0a-704 xx.xx.x.x
10.0.0.206 xx.xx.x.xxx UGHS 0 133280 1500 110 a0a-704 xx.xx.x.x
10.52.2.0/23 link#1 U 4 28857602472 1500 60 e0M => xx.xx.x.xxx
- Traffic is directed to interface e0M with the same subnet