1.2.4.1 Health Check
Click Health Check on the home page to go to the health check page. In
addition to the default entities, select Virtual Storage Data and click Start.
After the check is complete, if the score is lower than 100 points, handle the
identified problems according to the check results and solutions, and then
perform Health Check again. Before upgrading, please confirm that the health check score is 100 points.
1.2.4.2 Check with aDeploy
Apart from health check features, aDeploy supports checking common
problems of customers. It optimizes the platform-based check mechanism and can check the environment before upgrading. If faults or alerts are reported,
please handle the faults and alerts for the cluster before upgrading.
Refer toChapter 1.2.3.1 Packages, Documents, and Tools, for the download link.
1.2.4.3 HCI Pre-Upgrade Check
One week before upgrading HCI for a customer, please visit the customer or
establish a remote connection to check whether the customer's environment
meets the upgrade requirements using the pre-upgrade check package. This
will help facilitate the subsequent upgrade process and does not require
downtime. Make sure a pre-upgrade check is done before an official upgrade. If the pre-upgrade check for an official upgrade fails, it is recommended to
reschedule for the upgrade.
Step 1. Use aDeploy to perform a pre-upgrade check and wait for the check
to complete. Click Details next to the failed entities and handle them according to the solutions. Perform the pre-upgrade check again until all the entities pass the check.
SP pre-installation check is prohibited after the pre-upgrade check. Else, HCI will request you to run the pre-upgrade check again.
Step 2. After all the entities pass the check, click Install and wait for the installation to complete.
1. Troubleshooting instructions
a. For an offline upgrade, a message will be displayed after the pre-upgrade check is completed, indicating that a VM is running on the node. You may ignore this message temporarily. Before an official upgrade, all virtual devices must shut down, and run a pre-upgrade check again.
b. If the pre-upgrade check fails and a message indicates the pre-upgrade check failure, please contact a Sangfor technical support representative.
c. If a clustered node fails the pre-upgrade check and the pre-upgrade check does not proceed for more than 10 minutes, please contact a Sangfor technical support representative.
d. In versions earlier than HCI6.9.0, VM names can only contain digits, spaces, letters, Chinese characters, and special characters (()【】_-.+()@). Invalid VM names will cause the pre-upgrade check to fail.