Skip to main content
NetApp Knowledge Base

Why does ONTAP still shut down after automatic environment shutdown is disabled

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • NetApp ONTAP 9
  • Systems reporting low NVRAM or NVMEM battery alerts
  • HA environments with partner takeover after node shutdown

Answer

  • Low battery starts a timed automatic shutdown countdown.

[statd: monitor.shutdown.nvramLowBattery.pending:alert]: NVRAM battery is dangerously low. Halting system in 3 hours. Replace the battery immediately!
[statd: monitor.shutdown.nvramLowBattery.pending:alert]: NVRAM battery is dangerously low. Halting system in 2 hours. Replace the battery immediately!

  • Shutdown enters a final committed phase at the last checkpoint (about 1 hour before halt).
  • If the disable environment shutdown setting is executed after the final checkpoint, the shutdown is not canceled.

Commands to disable environment shutdown:
::> set diag
::*> system environment shutdown modify -node * -is-automatic false

Additional Information

additionalInformation_text
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.