When a battery nears the end of its life, you must replace it if you intend to preserve the capacity to failover power to batteries.
Replace the battery by following this procedure as soon as you can.
If the node is in a clustered system, ensure that the battery is not being relied upon to provide data protection before you remove it. Issue the chnodebattery -remove -batterybattery_ID node_ID command to establish the lack of reliance on the battery.
If the command returns with a "The command has failed because the specified battery is offline"(BATTERY_OFFLINE) error, replace the battery immediately.
If the command returns with a "The command has failed because the specified battery is not redundant" (BATTERY_NOT_REDUNDANT) error, do not remove the relied-on battery. Removing the battery compromises data protection.
In this case, without other battery-related errors, use the chnodebattery -remove -batterybattery_ID node_ID command periodically to force the system to remove reliance on the battery. The system often removes reliance within one hour (TBC).
Alternatively, remove the node from the clustered system. Once the node is independent, you can replace its battery immediately. If the node is not part of a cluster, or the battery is offline, or the chnodebattery command returns without error, conduct the service action for 1130: The node battery requires replacing..
Possible Cause-FRUs or other: