System generates the AutoSupport alert, ‘Call home for BATTERY (wrong charge) WARNING’, in FAS8300, FAS8700, AFF-A400. KB article explains the steps to resolve this issue, based on the BMC firmware ve...System generates the AutoSupport alert, ‘Call home for BATTERY (wrong charge) WARNING’, in FAS8300, FAS8700, AFF-A400. KB article explains the steps to resolve this issue, based on the BMC firmware version.
Mar 12 07:26:05 BMC kernel: [2831352.560000] i2c bus 0x3: !!!!!! master-abnormal stop-start !!!!!!!!! Mar 12 07:26:06 BMC kernel: [2831353.560000] i2c i2c-3: send_receive: Timed out on i2c data Operat...Mar 12 07:26:05 BMC kernel: [2831352.560000] i2c bus 0x3: !!!!!! master-abnormal stop-start !!!!!!!!! Mar 12 07:26:06 BMC kernel: [2831353.560000] i2c i2c-3: send_receive: Timed out on i2c data Operating Mar 12 10:20:43 BMC kernel: [2841830.380000] i2c i2c-3: send_receive: Timed out on i2c data Operating SP-login: login: Mar 12 18:13:07 [node_name:monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Battery not present)
[ClusterA-01: env_mgr: nvmem.battery.FET.off:alert]: The NVMEM battery charge FET is off. To prevent data loss, the system will shut down in 24 hours. The issue appears only during a learning cycle, v...[ClusterA-01: env_mgr: nvmem.battery.FET.off:alert]: The NVMEM battery charge FET is off. To prevent data loss, the system will shut down in 24 hours. The issue appears only during a learning cycle, verify SP event logs for the last learning cycle time stamp (beware that the SP event log tracks time in GMT only): Check the output of "system battery show" form the Service Processor to see when the latest learning cycle started
Post motherboard (PCM) replacement of the models in the Applies to section, the following errors occur during boot: Apr 27 08:31:18 [Node1:nvmem.battery.unread:EMERGENCY]: The NVMEM battery state cann...Post motherboard (PCM) replacement of the models in the Applies to section, the following errors occur during boot: Apr 27 08:31:18 [Node1:nvmem.battery.unread:EMERGENCY]: The NVMEM battery state cannot be determined because the 'Bat Initial FCC' sensor is unreadable. WARNING: The battery is unfit to retain data during a power When the battery is ready, the boot process will Power down the system and verify that the battery is
Fix false auto support battery full charge or nvmem battery full-charge capacity notification. SP-LATEST-SYSTEM-EVENT-LOG indicate learning cycle takes place at time of messages.
Sat Dec 19 16:22:32 +0100 [CLUSTERBA-CTRLA: env_mgr: nvmem.battery.wrongCharge:alert]: The NVMEM battery charger is charging the battery even though the battery is not requesting to be charged. Sun De...Sat Dec 19 16:22:32 +0100 [CLUSTERBA-CTRLA: env_mgr: nvmem.battery.wrongCharge:alert]: The NVMEM battery charger is charging the battery even though the battery is not requesting to be charged. Sun Dec 20 15:23:38 +0100 [CLUSTERBA-CTRLA: env_mgr: nvmem.battery.wrongCharge:alert]: The NVMEM battery charger is charging the battery even though the battery is not requesting to be charged.
Record 342: Mon Jun 01 15:48:26.930000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not charging Record 402: Mon Jun 22 11:43:49.530000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Batte...Record 342: Mon Jun 01 15:48:26.930000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not charging Record 402: Mon Jun 22 11:43:49.530000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present Record 427: Mon Jun 22 12:01:30.780000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present Record 538: Mon Jun 22 14:19:46.300000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present
