Skip to main content
NetApp Knowledge Base

How to perform a health check in ONTAP 9

Views:
8,915
Visibility:
Public
Votes:
6
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • AFF & FAS Systems

Description

  • This article describes the procedure to conduct a basic system health check for the following scenarios:
    • ONTAP upgrades or Firmware upgrades
    • Hardware replacements
    • Maintenance activities
    • Power related events
  •  For a full list of commands to check system health, see How to perform a cluster health check with a script in ONTAP

Procedure

  1. Verify Cluster health:

::> cluster show

  1. From the command line, confirm the target node is reporting the proper MPHA state(multi-path, quad-path, single-path):

::> system node run -node <node_name> -command sysconfig -a

  1. Ensure SP/BMC is online and healthy:

::> system service-processor show

  1. Ensure storage is healthy and online:
  • Check the status of aggregates
  • Check status of assigned drives and spares

::> system node run -node <node_name> -c sysconfig -r

  1. Confirm all volumes are online:

::> vol show -state !online

  1. Confirm the state of each network port is as it should be:

::> network port show

  1. Confirm all LIFs are home and operational:

::> network interface show

  1. Confirm there are no system faults present:

::> system health alert show

  1. Confirm no storage faults are present:

::> system health subsystem show

  1. Confirm that any CIFS shares that should be connected are so:

::> vserver cifs show
::> vserver cifs session show
::> vserver cifs connection show

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.