CriticalFanFruFaultAlert raised periodically after failed firmware update
Applies to
- ONTAP 9
- AFF-A400 / FAS8300 / FAS8700
- BMC 13.11
Issue
FAN Fru errors reported by one of the controllers, in the example below, node 2:
- Alert seen in the event log:
Tue Sep 02 09:09:51 +0200 [cluster1-02: cphmd: hm.alert.raised:alert]: Alert Id = CriticalFanFruFaultAlert , Alerting Resource = 042352004520 raised by monitor chassis
Tue Sep 02 09:09:51 +0200 [cluster1-02: cphmd: hm.alert.raised:alert]: Alert Id = CriticalFanFruFaultAlert , Alerting Resource = 042352004524 raised by monitor chassis
system service processor showcommand shows that one of the nodes BMC is on below firmware revision.Node Type Status Configured Version IP Address
------------- ---- ----------- ------------ --------- -------------------------
cluster1-01 - unknown - 13.11 -
cluster1-02 - unknown - 13.12 -
2 entries were displayed.
- Investigating the EMS, the failed firmware update is observed:
Tue Sep 02 08:43:54 +0200 [cluster1-01: servprocd: sp.servprocd.upd.evts:debug]: params: {'reason': 'SP Firmware network update from 13.11P1 to 13.12 has been triggered.'}
Tue Sep 02 08:59:24 +0200 [cluster1-01: servprocd: sp.servprocd.upd.unexpt.evts:debug]: params: {'reason': 'BMC update - BMC Firmware update timed out.'}
Tue Sep 02 08:59:24 +0200 [cluster1-01: servprocd: sp.servprocd.upd.error:error]: SP update error: SP firmware update failure has been detected.
Tue Sep 02 09:18:08 +0200 [cluster1-01: servprocd: sp.servprocd.upd.error:error]: SP update error: SP Firmware network auto-update could not be scheduled.
Platform-Sensorsin AutoSupport via Active IQ digital advisor, shows that the FANs are reporting as disabled:
|
Sensor Name |
Sensor Type |
Sensor State |
|
SysFan1 F1 |
discrete |
disabled |
|
SysFan1 F2 |
discrete |
disabled |
|
SysFan2 F1 |
discrete |
disabled |
|
SysFan2 F2 |
discrete |
disabled |
|
SysFan3 F1 |
discrete |
disabled |
|
SysFan3 F2 |
discrete |
disabled |
|
SysFan4 F1 |
discrete |
disabled |
|
SysFan4 F2 |
discrete |
disabled |