Skip to main content
NetApp Knowledge Base

What does each status returned by GET /devmgr/v2/storage-systems mean?

Views:
92
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

E-Series

Answer

  • NeverContacted: The storage-system has not been contacted since being added or since the startup of the Web Services instance. This would only be returned by the web services proxy. 
  • offline: The storage-system was accessible at one time, but is now inaccessible and may be offline. This is most likely to be returned by the web services proxy but could also be returned by the storage array in some corner case error scenarios (internal networking and/or application failures.)
  • optimal: The storage-system is currently in an optimal status. This can be returned by both the web services proxy and the storage array.
  • needsAttn: The storage-system has a warning/failure condition that needs to be resolved, but it is available to management operations. This can be returned by both the web services proxy and the storage array.
  • removed: This status is used in event reporting to denote that the system has been removed from management. This status will not be returned by the storage-systems end points.
  • newDevice: This status is used in event reporting to denote that a new system has added under management. This status will not be returned by the storage-systems end points.
  • lockDown: The storage-system is reporting that it is in a lock-down state (limited management). This can be returned by both the web services proxy and the storage array. This status will only show for a limited lockdown. In a full lockdown the storage array would be inaccessible and the web services proxy would show it as offline or neverContacted depending on whether it had contacted it previously.

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.