Checking for upgrade readiness

You can verify that the cluster is ready to be upgraded by using the sfupgradecheck command. This command verifies information such as pending nodes, disk space, and cluster faults. If your management node is at a dark site, the upgrade readiness check needs the metadata JSON file to run successfully.

About this task

This procedure describes how to address upgrade checks with any of the following results:

Running the sfupgradecheck command does not give an error. Your cluster is upgrade ready.
Checks within the sfupgradecheck tool fail with an error message. Your cluster is not upgrade ready and additional steps are required.
Your upgrade check fails with an error message that HealthTools is out-of-date.
Your upgrade check fails because your management node is on a dark site.

Procedure

Run the sfupgradecheck command.

sfupgradecheck -u <cluster-user-name> -p <cluster-password> MVIP

Note: For passwords that contain special characters, add a backslash (\) before each special character. For example, mypass!@1 should be entered as mypass\!\@.

See the following sample input command:

sfupgradecheck -u admin -p admin 10.117.78.244

A sample output is as follows. In this result, no errors appear and you are ready to upgrade.

check_pending_nodes:
Test Description:     Verify no pending nodes in cluster
More information:     https://kb.netapp.com/support/s/article/ka11A0000008ltOQAQ/pending-nodes
check_cluster_faults:
Test Description:     Report any cluster faults
check_root_disk_space:
Test Description:     Verify node root directory has at least 12 GBs of available disk space
Passed node IDs:      1, 2, 3
More information:     https://kb.netapp.com/support/s/article/ka11A0000008ltTQAQ/SolidFire-Disk-space-error
check_mnode_connectivity:
Test Description:     Verify storage nodes can communicate with management node
Passed node IDs:      1, 2, 3
More information:     https://kb.netapp.com/support/s/article/ka11A0000008ltYQAQ/mNode-connectivity
check_files:
Test Description:     Verify options file exists
Passed node IDs:      1, 2, 3
check_cores:
Test Description:     Verify no core or dump files exists
Passed node IDs:      1, 2, 3
check_upload_speed:
Test Description:     Measure the upload speed between the storage node and the management node
Node ID: 1 Upload speed: 90063.90 KBs/sec
Node ID: 3 Upload speed: 106511.44 KBs/sec
Node ID: 2 Upload speed: 85038.75 KBs/sec

If there are errors, additional actions are required:

Your cluster is not upgrade ready. Review the sfupgradecheck error message.

A sample output is as follows:

The following tests failed:
check_root_disk_space:
Test Description: Verify node root directory has at least 12 GBs of available disk space
Severity: ERROR
Failed node IDs: 2
Remedy: Remove unneeded files from root drive
More information: https://kb.netapp.com/support/s/article/ka11A0000008ltTQAQ/SolidFire-Disk-space-error
check_pending_nodes:
Test Description: Verify no pending nodes in cluster
More information: https://kb.netapp.com/support/s/article/ka11A0000008ltOQAQ/pending-nodes
check_cluster_faults:
Test Description: Report any cluster faults
check_root_disk_space:
Test Description: Verify node root directory has at least 12 GBs of available disk space
Passed node IDs: 1, 3
More information: https://kb.netapp.com/support/s/article/ka11A0000008ltTQAQ/SolidFire-Disk-space-error
check_mnode_connectivity:
Test Description: Verify storage nodes can communicate with management node
Passed node IDs: 1, 2, 3
More information: https://kb.netapp.com/support/s/article/ka11A0000008ltYQAQ/mNode-connectivity
check_files:
Test Description: Verify options file exists
Passed node IDs: 1, 2, 3
check_cores:
Test Description: Verify no core or dump files exists
Passed node IDs: 1, 2, 3
check_upload_speed:
Test Description: Measure the upload speed between the storage node and the management node
Node ID: 1 Upload speed: 86518.82 KBs/sec
Node ID: 3 Upload speed: 84112.79 KBs/sec
Node ID: 2 Upload speed: 93498.94 KBs/sec

In this example, node 1 is low on disk space. You can find more information in the knowledge base article listed in the error message.

HealthTools is out-of-date. Review the error message and note that the upgrade check fails.

Sample output is as follows:

sfupgradecheck failed: HealthTools is out of date: installed version: 2018.02.01.200 latest version: 2018.03.05.901.
The latest version of the HealthTools can be downloaded from: https://mysupport.netapp.com/NOW/cgi-bin/software/ 
Or rerun with the -n option

When this happens, you must follow the steps described in the output.

Your management node is on a dark site. Review the message and note that the upgrade check fails.
A sample output is as follows:
```
sfupgradecheck failed: Unable to verify latest available version of healthtools.
```
1. When this happens, get and save the metadata.json file on a computer that is not the management node and run the following command: sfupgradecheck -l --metadata=<path-to-metadata-json>
  For details, see additional upgrade information for dark sites.
  
  Upgrading Element software at dark sites
2. Verify that the HealthTools suite is up-to-date by running the following command:sfupgradecheck -u <cluster-user-name> -p <cluster-password> MVIP