Skip to main content
NetApp Knowledge Base

Why do nodes report SPARES_LOW during an upgrade?

Last Updated:

Applies to

  • ONTAP 9
  • Storage Pool


  • When there is one whole, unpartitioned SSD spare for Storage Pool assigned to only one node, you can receive this alert during takeover events as the takeover node replays the events for the node that is rebooting.
Tue Feb 01 11:14:22 EST [ntap-clus-01: config_thread: callhome.spares.low:error]: Call home for SPARES_LOW
Tue Feb 01 11:15:00 CST [ntap-clus-01: monitor: monitor.globalStatus.critical:EMERGENCY]: This node has taken over ntap-clus-02. There are not enough spare disks.
  • Example:
    • Node A owns the only unpartitioned SSD spare.
    • Node A takes over node B. Since node B did not own any spares for Storage Pool, node A replays this message.
    • Node B finishes upgrading, and giveback is performed.
    • Node B takes over node A. Since node B still does not own any spares, node B reports this message.


  • This is expected behavior and does not impact the system.

Additional Information

You can use only one spare SSD for Storage Pool. If the Storage Pool provides allocation units to hybrid aggregates that are owned by both nodes in the HA pair, then the spare SSD can be owned by either node. However, if the Storage Pool provides allocation units only to hybrid aggregates that are owned by one of the nodes in the HA pair, then the SSD spare must be owned by that same node.

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.