Skip to main content
NetApp Knowledge Base

"A power sensor P12V STBY in the controller module is not readable" occurs frequently on FAS8200 systems

Views:
261
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

FAS8200

Issue

  • The error monitor.power.unreadable occurs multiple times with the sensor P12V STBY in EMS log. 

 [?]  Tue Jul 16 00:21:11 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY in the controller module is not readable.
 [?]  Tue Jul 16 00:23:01 +0900 [node-1: env_mgr: monitor.chassisPower.ok:notice]: Chassis power is OK.
 [?]  Tue Jul 16 00:24:24 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY Curr in the controller module is not readable.
 [?]  Tue Jul 16 00:37:59 +0900 [node-1: env_mgr: monitor.chassisPower.ok:notice]: Chassis power is OK.
 [?]  Tue Jul 16 00:39:26 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY Curr in the controller module is not readable.
 [?]  Tue Jul 16 00:51:14 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V Curr in the controller module is not readable.
 [?]  Tue Jul 16 00:51:32 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY in the controller module is not readable.
 [?]  Tue Jul 16 00:59:52 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V Curr in the controller module is not readable.
 [?]  Tue Jul 16 04:39:23 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY in the controller module is not readable.
 [?]  Tue Jul 16 04:39:44 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY Curr in the controller module is not readable.
 [?]  Tue Jul 16 04:55:59 +0900 [node-1: env_mgr: monitor.chassisPower.ok:notice]: Chassis power is OK.
 [?]  Tue Jul 16 04:57:26 +0900 [node-1: env_mgr: monitor.power.unreadable:error]: A power sensor P12V STBY Curr in the controller module is not readable.

  • The SP-LATEST-SYSLOG shows reading errors with Sensor 212 and Sensor 213.

Jul 15 19:39:04 (none) : [392 WARNING][hal_api.c:356]Sensor 212 reading error
Jul 15 19:39:04 (none) : [392 WARNING][hal_api.c:356]Sensor 213 reading error
Jul 15 19:39:11 (none) hsam[357]: HSAM OS(0x5):cmd(2) FLD(controller):fault(Failed reading sensor: 212)
Jul 15 19:39:11 (none) : [392 WARNING][hal_api.c:356]Sensor 213 reading error
Jul 15 19:39:17 (none) : [392 WARNING][hal_api.c:356]Sensor 212 reading error
Jul 15 19:39:17 (none) : [392 CRITICAL][Porting/platform/PDKHooks.c:647]Error while reading sensor number : 212
Jul 15 19:39:17 (none) : [392 WARNING][hal_api.c:356]Sensor 213 reading error
Jul 15 19:39:24 (none) env_mgr[1109]: Payload EMS: EMS_monitor_power_unreadable(P12V STBY)

  • There are no issues with the P12V related sensors in PLATFORM-SENSORS.

P12V voltage normal 11904 mV   0   15810
P12V Curr current normal 7896 mA   0   21420
P12V STBY voltage normal 11904 mV   0   15810
P12V STBY Curr current normal 811 mA   0   3182

  • In SP-LATEST-IPMI, both P12V_STBY and P12V_STBY_Curr have an na status, and it shows Failed reading sensor: 213.

======================================
hsamcmd --fault-show-all
===============================
tag  origin  fld                                     fault reason                                    count  time
---- ------- ----                                    -------------                                   ------ -----
1    0x5     /chassis-1/controller-b                 Failed reading sensor: 213                      1      Mon Jul 15 20:04:51 2024

P12V             | 11.904     | Volts      | ok         | 0.000     | 0.000     | 15.810    | 15.810
P12V_Curr        | 7.728      | Amps       | ok         | 0.000     | 0.000     | 21.420    | 21.420
P12V_STBY        | na         | Volts      | na         | 0.000     | 0.000     | 15.810    | 15.810
P12V_STBY_Curr   | na         | Amps       | na         | 0.000     | 0.000     | 3.182     | 3.182 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.