Why "raid.timeout" option doesn't avoid a environmental shutdown?
- Views:
- 1,122
- Visibility:
- Public
- Votes:
- 0
- Category:
- aff-series
- Specialty:
- hw
- Last Updated:
- 4/10/2023, 8:48:08 AM
Applies to
ONTAP 9
Answer
- Bug 1466540 - ONTAP ignores the "raid.timeout" option for NV battery events that trigger a shutdown
- Environmental NVRAM battery full-charge capacity errors are not controlled by the
raid.timeoutoption. Example:
::> storage raid-options show -node * -name raid.timeout*
Node Option Value Constraint
-------- ---------------------------------------------- ------------ ----------
node_name-1
raid.timeout 60 only_one
node_name-2
raid.timeout 60 only_one
2 entries were displayed.
but:
[node_name: env_mgr: nvram.battery.fcc.low:error]: The NVRAM battery full-charge capacity is low (48 %). To prevent data loss, the system will shut down in 24 hours.
...
[node_name: env_mgr: nvram.battery.fcc.low:error]: The NVRAM battery full-charge capacity is low (48 %). To prevent data loss, the system will shut down in 60 minutes.
[node_name: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Battery PCT capacity low)
[node_name: env_mgr: nvram.battery.fcc.low:error]: The NVRAM battery full-charge capacity is low (48 %). To prevent data loss, the system will shut down now.
Additional Information
- Bug 1226105 Feature request: system environmental shutdown configuration control in ONTAP
- Bug 1226107 Feature request: SP/BMC support for system environmental shutdown configuration in ONTAP
- On AFF/FAS 80x0 platforms, this feature was implemented in ONTAP and it is not dependent on the Service Processor firmware
