Performing Instant Upgrade for VCM
Procedure
Step1 Log in to the SEM and choose Resource management > Service management > System upgrade. Click Upload
upgrade package to upload the upgrade package to the SEM. For the upgrade of
the version that contains the sensitive feature, upload the VCM5000_Upgrade_Package.zip
package. For the upgrade of the version that does not contain the sensitive
feature, upload the VCM5000_ Noface_Upgrade_Package.zip package
Step2 Click Close only when a green tick is displayed in the status column.
Step3 Select the uploaded upgrade package.(If the upgrade package is being decompressed when you select it, the instant upgrade
button is unavailable.)
Step4 Click instant upgrade.
Step5 The background checks the disk spaceof all hosts. If the disk space of a host is insufficient, a message will be
displayed. Clear the disk space as prompted and then click instant upgrade.
Step6 Before the upgrade, the system checks the current version of the node. If the node is already the latest
version, the node will not be upgraded. When the upgrade is complete, the
system displays the upgrade results. If the upgrade of a node fails, rectify
the fault and perform the upgrade again.
Step7 Wait for about 30 minutes.
Step8 When the upgrade is successful,click Restart SEM to restart the SEM. The system then automatically jumps to
the login page.
PS:
1. Only one upgrade package can be uploaded at
a time. Otherwise, the upgrade package will fail to be uploaded. The newly
uploaded upgrade package will overwrite the old upgrade package. The uploaded
upgrade package area displays only the latest upgrade package.
2.You can determine whether a version contains
the sensitive feature based on the version number of an online board in the
cluster. A version number with the suffix _PATCH contains the sensitive
feature. A version number without the suffix _PATCH does not contain the
sensitive feature.
3. When the upgrade is successful, each service
module automatically restarts. Perform service operations after all modules are
started successfully.
4. Partial success may occur. That is, some
servers are upgraded successfully while others fail. The servers that fail to
be upgraded automatically roll back to the source version. You must find the
cause of failure. (For details about the upgrade logs, view the
/var/log/upgrade.log file of each server.) Rectify the fault first, and then
perform the upgrade again.
