Log in

Sangfor Support Center

Table of Contents
< All Topics
Print

【HCI】Release Notes_V6.8.0_R1

Posted
Updated
Byhuijun.chan@sangfor.com
Views6

Overview

Features

New Features

The HCI6.8.0_R1 aims to improve product quality without new features, providing a better user experience.

This version fixed the bugs discovered while improving the quality of the managed cloud product that existed in previous versions, as well as critical issues with private cloud product feedback by customers.

Others

  1. HCI6.7.0R3_EN does not support upgrading to HCI6.8.0_R1. The upgrade will be supported in a future release.
  2. If HCI has been managed by SCP (earlier than SCP6.7.30) before upgrading to HCI6.8.0_R1, please upgrade SCP to SCP6.7.30 and later (including SCP6.8.0) before upgrading HCI.
  3. After upgrading SCP6.7.0 to SCP6.7.30 and later (including SCP6.8.0), please contact Sangfor Support for further inspection.
  4. Since SCP6.8.0 has been containerized, to upgrade an earlier version to SCP6.8.0, please add a disk (400 GB) to the platform for container image storage so that databases will not be affected by disk IO from container images.

Warning:

  1. The offline licensing(virtual key) method is supported only when SCP6.8.0 is deployed on HCI6.8.0 or later.
  2. When using a virtual key to upgrade to SCP6.8.0, the original license key file will become invalid, and required to renew the license key with the new device info. This licensing method is supported only when SCP6.8.0 is deployed on HCI6.8.0 or later. Therefore, resource pools of earlier versions may cause SCP licensing to fail.
  3. It is required to use the licensing method with a USB key if aSecurity needs to be licensed.

Upgrade Impacts

Services will be interrupted during an offline upgrade because all VMs and NFV devices need to be shut down before the upgrade. After the upgrade is complete, all nodes need to restart.

Note:

  1. Only offline upgrade is supported for HCI6.3.0_R2 and earlier versions.
  2. The active upgrade is supported for HCI6.7.0 and above.

Impacts on Services

  1. HCI6.7.0 and above can be upgraded to HCI6.8.0_R1 through an active upgrade, which does not impact services and does not require VMs and NFV devices to be shut down. After the upgrade is completed, there is no need to restart nodes. However, in the final stage of the upgrade, VMs not installed with vmTools need to be manually migrated without being powered off or restarted to make new features take effect.
  2. For the active upgrade, the service interruption time depends on service and cluster load during the upgrade. In fact, an active upgrade may take longer than expected, but service interruption during the upgrade will last for only 3 seconds or shorter. It is recommended to perform the upgrade during non-peak hours.
  3. Services will be interrupted during the offline upgrade of HCI because all VMs and NFV devices need to be shut down before the upgrade.
  4. After the offline upgrade of HCI is completed, VMs cannot be powered on before all HCI6.8.0 features take effect. Therefore, it will take about 20 minutes for the new version to take effect.
  5. After the offline upgrade is completed for HCI5.8.6 or later, cached data in data disks will be written back to the node cache, so it will take some time for the new version to take effect. Therefore, planning in advance and upgrading during non-peak hours is recommended.
  6. After the offline upgrade of HCI is completed, if NFV devices need to be upgraded, they will be restarted after the upgrade, which will affect services.

Impacts on O&M

  1. During the HCI upgrade, O&M personnel should not log in to the platform for operation and maintenance.
  2. After the SCP upgrade is completed, the Self-Service Portal of SCP is unavailable during the restart of SCP.

Impacts on Customer Network

  1. HCI upgrade has no impact on network communications outside the platform.
  2. SCP upgrade has no impact on network communications outside the platform.

Other Impacts

None.

Upgrade Instructions for Customers

Upgrade Preparations

  1. The Offline upgrade may take 4 to 6 hours. Please make appropriate time arrangements and prepare for service interruption during the upgrade to reduce impact.
  2. Before the active upgrade, please confirm whether NFV component versions need to be upgraded and evaluate the time and personnel arrangements for the upgrade.

Notes

  1. During the upgrade, O&M personnel of customers should not log in to the platform for operation and maintenance.
  2. Customers’ business departments should not access HCI before the offline upgrade is complete.

Implementation Procedure

Active Upgrade Process

Type Item Estimated Time Check with √ When Complete
Preparing for Upgrade Check upgrade path
Preparing for Upgrade Prepare an update package for the pre-upgrade check
Preparing for Upgrade Prepare the HCI update package
Preparing for Upgrade Check version information
Preparing for Upgrade Prepare license key
Preparing for Upgrade Read upgrade notes
Upgrade Process Make sure there are no ongoing tasks 5 mins
Upgrade Process General page check 10 mins
Upgrade Process Health check 10 mins
Upgrade Process Enable maintenance mode 1 min
Upgrade Process Test before upgrading HCI 5 mins
Upgrade Process Upload HCI upgrade package/verify authentication 3 mins
Upgrade Process Distribute update package Package size*number of nodes/Transfer rate
Upgrade Process Pre-upgrade check 15 mins. The time varies according to virtual storage capacity. The larger the storage capacity is, the longer the upgrade process takes.
Upgrade Process Control plane active upgrade 11 mins
Upgrade Process VM active upgrade 5 secs for every 5 VMs with vmTools installed.
2 mins for each VM without vmTools installed.
Upgrade Process Virtual storage active upgrade Number of clustered nodes*10 mins Related to the scale and load of VMs
Upgrade Process Active upgrade for virtual network 5 mins Related to the scale and load of VMs
Upgrade Process Apply new virtual storage version Number of clustered nodes*10 mins Related to the scale and load of VMs
Upgrade Process Check business 30 mins
Upgrade Process License after upgrade 5 mins

Notice:

  1. Moving a VM that runs on external storage to another group will cause the VM to crash. After an active upgrade, the node needs to be restarted. Restart the nodes one by one during non-peak hours after an active upgrade is recommended.
  2. During the active upgrade of the network, services may be interrupted for about 1 minute.

Offline Upgrade Process

Type Item Estimated Time Check with √ When Complete
Preparing for Upgrade Check upgrade path
Preparing for Upgrade Obtain the latest version of aDeploy
Preparing for Upgrade Prepare the HCI update package
Preparing for Upgrade Check version information
Preparing for Upgrade Prepare license key
Preparing for Upgrade Read upgrade notes
Upgrade Process Make sure there are no ongoing tasks 2 mins
Upgrade Process General page check 10 mins
Upgrade Process Health check 5 mins
Upgrade Process Shut down all VMs 20 to 30 mins
Upgrade Process Shut down all NFV devices 10 mins
Upgrade Process Enable maintenance mode 1 min
Upgrade Process Check Environment 1 min
Upgrade Process Upload HCI update package 1 min
Upgrade Process Verify the update package via the QR code. 1 min
Upgrade Process Distribute update package Package size * Number of nodes/Transfer rate
Upgrade Process Check environment 15 mins
Upgrade Process Perform offline upgrade 30 mins
Upgrade Process Power on VM 10 mins
Upgrade Process Check business 5 mins

Note:

The larger the cluster is, the longer it takes to convert the configuration file and the longer the upgrade time.

Upgrade Notes

  1. After the HCI upgrade is completed, nodes will restart to have the new version take effect. To use the ECC memory isolation feature, please manually restart the nodes and modify the BIOS options (enable ECC scan and ECC isolation).

Note:

Forced shutdown is not recommended before the upgrade is completed.

  1. Before upgrading, please use the latest version of aDeploy (refer to Chapter 2.1.1 Upgrade Packages, Documents, and Tools for the download link) to perform the pre-upgrade check and install a pre-upgrade check package.

  2. Please contact a Sangfor technical support representative for pre-upgrade evaluation and check if the following conditions are met:

  • The current version is earlier than HCI5.8.6 and needs to be upgraded to a version later than HCI5.8.6.
  • The customer uses the platform for high-performance database services and is demanding performance.
  • More than ten nodes are involved.

  1. Before upgrading, please check whether the license key is valid.

  2. When graphics cards (including Passthrough and vGPU) are in use, ensure the IOMMU is enabled and restart the node.

  3. If graphics cards are used in versions earlier than 6.2.0, aGPU license key is required after the upgrade. Otherwise, GPU-related features cannot be used.

  4. HCI cannot be upgraded when it provides services as an iSCSI server. Therefore, please go to iSCSI clients before upgrading to disconnect all related connections.

  5. During the pre-upgrade check for the offline upgrade, if "A VM is running on the node. Please shut down the VM and try again." pops up, you can ignore it temporarily. Before an official upgrade, all virtual devices and VM need to be shut down and perform pre-upgrade checks again.

  6. If the current version contains custom packages (Custom-XXX, as shown in the figure below), please contact a Sangfor technical support representative for upgrade evaluation.

  1. If the current version contains SPs (sp-XXX packages), it can be upgraded directly. However, if the SPs cause the upgrade failure, please contact Sangfor Technical Support for assistance.

  2. If the upgrade is performed when the storage network is not configured for computing nodes in the cluster, the pre-upgrade check will fail. Therefore, you can only upgrade after configuring the storage network.

  3. Suppose VDI is required to upgrade because the bad sector check mechanism for disks before the VDI upgrade is inconsistent with the new version. After the upgrade is completed, various alerts may be triggered for virtual storage disks.

Post Upgrade Check

After the upgrade is completed, start and verify the business services.

Rollback

If the HCI upgrade fails, do not close the upgrade page and contact a Sangfor technical support representative for rollback.

Upgrade Guide

Note:

Please upgrade following the sequence below:

SCP > NFV > HCI

Upgrade Preparations

Upgrade Packages, Documents, and Tools

Packages

Name Description Obtain Through
HCI6.8.0_R1 update package Used for upgrading from an earlier version to HCI6.8.0_R1. Sangfor Community https://community.sangfor.com/plugin.php?id=service:download&action=view&fid=47#/12/all
Witness node update package of HCI 6.8.0_R1 (stretched cluster) Used for upgrading from an earlier version to HCIWitness HCI6.8.0_R1. Sangfor Community https://community.sangfor.com/plugin.php?id=service:download&action=view&fid=47#/12/all

Documents

Name Description Obtain Through
HCI6.8.0 User Manual. Describes the basic O&M and configuration in HCI. Sangfor Knowledge Base https://knowledgebase.sangfor.com/home
aDeploy User Guide Provides instructions for using aDeploy. Sangfor Knowledge Base https://knowledgebase.sangfor.com/home

Tools

Name Description Obtain Through
Chrome/Edge The browser that uses to access HCI and SCP web console. Obtain from the internet.
PuTTY/MobaXterm An SSH client for troubleshooting if needed. Obtain from the internet.
MD5 Verify the integrity of the upgrade package. Check it when downloading the package file.
aDeploy Used for pre-upgrade checks and other checks with aDeploy. Sangfor Community https://community.sangfor.com/plugin.php?id=service:download&action=tool
License key 1. For a version earlier than HCI5.8.2, please apply for a new HCI license key.
2. If the NFV devices used need to be upgraded according to Chapter 2.3.1.2 NFV Device Versions Supported by HCI&SCP, please apply for a new NFV license key.
3. Before upgrading, please confirm that the customer’s license is not expired. Otherwise, the environment needs to be renewed.
4. Before upgrading, please check that the original NFV license key has not expired. Otherwise, the license needs to be renewed.		 Contact corresponding personnel to obtain or confirm.

Environment Information

None.

Customer Resources

  1. During the upgrade, O&M personnel of customers should not log in to the platform for operation and maintenance.

  2. The Offline upgrade may take 4 to 6 hours. Please make appropriate time arrangements and prepare for service interruption during the upgrade to reduce impact.

  3. Before the active upgrade, please confirm whether NFV component versions need to be upgraded and evaluate the time required.

  4. Please coordinate resources in advance according to the following requirements to ensure a smooth upgrade:

    a) Determine when to upgrade and fully prepare for service interruption during the upgrade to reduce impact.

    b) Obtain contact information of the responsible persons.

    c) Ensure a computer (with Internet access and a stable connection to the device) is ready and can be installed with and run the upgrade client software.

Type Name Contact Responsible For
Sangfor Technologies Inc. Assist with troubleshooting if any issue happens during the HCI upgrade.
Customers Upgrading HCI
Customers Coordinating resources and upgrade time. (Upgrade time: )
Customers Ensure O&M personnel will not log in to the platform for operation and maintenance.
Customers Arrange a responsible person for application systems to handle service opening and verification issues.

Pre-upgrade Check

Health Check

Click Health Check on the home page to access the health check page. In addition to the default entities, select Virtual Storage Data and click Start. After completing the check, 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.


Check with aDeploy

Apart from health check features, aDeploy supports checking common problems. It optimizes the platform-based check mechanism and can check the environment before upgrading. If faults or alerts are reported after the check, please handle them before upgrading.

Refer to Chapter 2.1.1 Upgrade Packages, Documents, and Tools for the download link.

Check Before Upgrading

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 the pre-upgrade check is done before an official upgrade. If the pre-upgrade check for an official upgrade fails, you need to make another appointment with the customer for an upgrade.

The checking is shown below.

  1. Use aDeploy to perform the pre-upgrade check and wait for it to complete. Click Details next to the failed entity and handle them according to the solutions. Perform the pre-upgrade check again until all the entities pass the check.

Notice:

After the pre-upgrade check is done, do not perform the SP pre-installation check. Otherwise, HCI will require a pre-upgrade check again.

  1. After all the entities pass the check, click Install and wait for the installation to complete.

  1. Troubleshooting instructions
    a) For the offline upgrade, after the pre-upgrade check is completed, a message will indicate that a VM is running on the node. You can temporarily ignore this problem. Before an official upgrade, all virtual devices must be shut down, and perform a pre-upgrade check again.

    b) If the pre-upgrade check fails and a message indicates a 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.8.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.

Upgrade Procedure

Upgrade Path

Versions Can Be Upgraded to HCI6.8.0_R1

Download aDeploy (refer to Chapter 2.1.1 Upgrade Packages, Documents, and Tools) to check for the HCI upgrade path.

Note:

  1. For upgrades from versions earlier than 5.8.3_EN to 5.8.3_EN, please select 5.8.8_R1_EN as the target version, pass the pre-upgrade check on aDeploy, and install the pre-upgrade check package.
  2. You need to first upgrade versions earlier than 5.8.3_EN to 5.8.3_EN before upgrading to subsequent versions.
  3. 5.8.3_EN to 6.0.0_R3_EN must be upgraded to 6.0.0_R5_EN, 6.2.0_EN, 6.3.0_R1_EN, or 6.3.0_R2_EN first before being upgraded to 6.8.0_R1.
  4. 6.0.0_R5_EN and later can be directly upgraded to 6.2.0_EN, 6.3.0_R1_EN, 6.3.0_R2_EN, 6.3.0_R3_EN, 6.7.0_EN, 6.7.0_R2_EN, and 6.7.0_R3_EN.
  5. 6.3.0_R1_EN can only be upgraded to 6.3.0_R2_EN, 6.3.0_R3_EN.
Series
aCloud6.0.0 Series 6.0.0_R5_EN Offline Upgrade
HCI6.0.1 Series 6.0.1_EN 6.0.1_R1_EN Offline Upgrade
HCI6.1.0 Series 6.1.0_EN 6.1.0_R1_EN Offline Upgrade
HCI6.2.0 Series 6.2.0_EN 6.2.30_EN 6.2.70_EN Offline Upgrade
HCI6.3.0 Series 6.3.0_EN 6.3.0_R1_EN 6.3.0_R2_EN 6.3.0_R3_EN Offline Upgrade
HCI6.7.0 Series 6.7.0_EN 6.7.0_R2_EN Active Upgrade
HCI6.8.0 Series 6.8.0 Active Upgrade

NFV Device Versions Supported by HCI&SCP

  1. For NFV devices earlier than the versions listed in the table below, please upgrade them first before upgrading HCI.
  2. For versions earlier than SCP6.1.0_EN, after being upgraded to SCP6.1.0_EN and above, please import the NFV device images of versions corresponding to SCP6.1.0_EN if using VPC. You can obtain the NFV device images by contacting Sangfor Technical Support or via community live chat.
  3. The following is the list of NFV device versions supported by HCI&SCP:
Device Version SCP Classic Network SCP VPC Notes
vAD vAD 6.6_EN √
vAD vAD 7.0.9R1_EN √ √
vNGAF vNGAF7.1_R3 √
vNGAF vNGAF8.0.8 √
vNGAF vNGAF8.0.17 √ √ The upgrade is not supported once deployed in VPC, else the integration with SCP will fail.
vIAG vIAM11.9 √
vIAG vIAG12.0.14 √
vIAG vIAG13.0.47 √
vSSL vSSL7.6.0 √
vSSL vSSL7.6.8_R2 (20200928) √ √ Version patched supports both being installed using SSL service packs and being deployed.
EDR EDR3.6.35_EN Only support deployment with aSEC.

Note:

The NFV device licensing standards of versions earlier than HCI5.3.0 is based on CPU and memory usage; HCI5.8.3 and above are based on traffic usage. Therefore, please prepare the upgrade packages of NFV devices accordingly.

Upgrade Procedure

  1. Record the on/off of VMs and NFV devices.

Record the on/off of VMs and NFV devices and power on them according to the information after the upgrade.

VM templates will be permanently powered off after the upgrade. If a VM template is running business services, please use it to clone a new VM to run business services before the upgrade.

No. VM/NFV Device Status Template VM
1 VM 01 Running No
2 vAD 01 Off
3 VM Template 01 Running Yes

How to view powered-off VM templates:

Go to Virtual Machine > Advanced, select Powered off as the Status and Template as the VM Type, and click OK.


How to view powered-on NFV devices:

Go to Virtual Network > Devices, and the NFV devices that display CPU and memory usage are powered on.

  1. Upgrade the witness node. (Optional)

Please upgrade the witness node before upgrading the stretched cluster (skip if the HCI cluster is non-stretched).

  • Go to the Witness Node page, and click the Upgrade button.

  • During the upgrade, the witness node will enter cluster Maintenance Mode, and the environment check will be performed.

  • Upload the witness node update package.


  • Check the update package. (If the current version does not support the active upgrade using the update package, click Next to perform the offline upgrade. If the active upgrade is supported, please wait until all checking steps are finished before the upgrade. If any step fails, fix the issues first.)

Offline Upgrade Check

Active Upgrade Check

  • Confirm the upgrade information and start the upgrade.
    Offline Upgrade (Business services will be temporarily interrupted. It is recommended to perform the upgrade during non-peak hours.)





Active Upgrade (During the control plane upgrade, you will be logged out. Please wait about 1 minute and then reload the page to log in again.)



After the upgrade, please wait for the background witness node to take effect before upgrading other nodes in the cluster.

Notice:

After the offline upgrade of the witness node of HCI 6.8.0_R1 is completed and the witness node is restarted, its status will still display as offline. This is because the version of the witness node is inconsistent with those of other nodes in the cluster. To solve this problem, please upgrade other nodes.

  1. Shut down all VMs. (Skip this step for the active upgrade.)

Select all VMs and shut them down. If the operation fails, go to their consoles to shut them down separately (including suspended VMs).

  1. Shut down all NFV devices. (Skip this step for the active upgrade.)

Go to Virtual Network > Running to shut down all NFV devices (excluding routers and switches).

Notice:

Upgrading versions earlier than 5.8.6 requires shutting down NFV devices and VMs.

  1. Use aDeploy to perform the pre-upgrade check and install the pre-upgrade check package (see Chapter 2.3.2 Check Before Upgrading). Then, go to System > Upgrade and click the Upgrade button. The cluster will enter Maintenance Mode, and it will perform the environment check.

Note:

After installing the pre-upgrade check package, you may see the physical nodes’ Current Version.


  1. Upload the HCI update package and click Next.


  1. Check the update package. If the current version does not support the active upgrade using the update package, you can check again, upload another update package, or click Next to perform an offline upgrade. If an active upgrade is supported, please ensure all check steps are finished before the upgrade.

a) Check the offline upgrade.

b) Check the active upgrade.

  1. Confirm the upgrade information, including time taken, update method, and impact.

a) Confirm the offline upgrade information.

b) Confirm the active upgrade information. VMs and NFV devices that do not support the active upgrade will be displayed in a list. After the upgrade, restart or migrate them to another run location.

  1. Wait for the upgrade to complete. Then, each upgrade step will be displayed in the Details list.

a) Offline upgrade

b) Active upgrade (during the control plane upgrade, you will be logged out. Please wait about 1 minute and then reload the page to log in again.)

  1. After the upgrade is complete, there are different operations for offline upgrade and active upgrade.

a) After the offline upgrade, click Restart Now.

If there are VMs and NFV devices that have not been shut down, follow the prompts to shut them down and restart the nodes immediately. If all VMs have been shut down, check I have powered off all the virtual machines and want to restart all the hosts and click Reboot.

b) After the active upgrade, VMs and NFV devices that failed to be upgraded will be displayed. Please restart or migrate them to another node to run. If there is no VM or the device fails to be upgraded, click Finish to log out, and the upgrade will take effect after logging in again.

  1. Suppose there are VMs and NFV devices that fail the active upgrade. In that case, you can migrate them to another datastore and run location or another run location only (generally selected for upgrade migration). Using the storage network interface for migration is recommended, and you can set the migration speed based on the business services.



Notice:

  • Restart is not required for the active upgrade to complete.
  • Restart is required for the offline upgrade to complete.
  1. After the restart, perform Health Check on the platform. If the score is less than 100, fix the issues according to the check results or contact a Sangfor technical support representative.

  1. Start VMs and NFV devices (skip for active upgrade).

Start the recorded VMs and NFV devices and ensure they can run normally.

Post-upgrade Check

Platform

  1. Perform a health check on the HCI platform (Virtual Storage Data Check must be selected) and ensure all services work.

  2. Use aDeploy to perform a health check on the HCI platform and fix the issues according to the check results.

Service Status

Performs the health check on the HCI platform to check whether the business services work.

Abnormalities Troubleshooting

Pre-Upgrade Failures

Scenario Upgrades Solutions Notes
Timeout while distributing installation package because the management interface of the cluster controller only supports 100 Mbps. Upgrade from earlier versions to HCI6.0.1 and above. Make sure the management interface supports at least 1000 Mbps before the upgrade. Management interfaces less than 1000 Mbps cannot be used concurrently.
Timeout while checking update.suc.exec.precheck.flag and update.rep.finished.flag during the upgrade. Upgrade from versions earlier than 5.8.6 to versions earlier than 6.0.1. Check the configuration of nodes in the cluster. Then, contact a Sangfor technical support representative to mark low-configuration nodes to skip the check. This problem has been fixed and will not occur while upgrading versions earlier than HCI5.8.6 to HCI6.0.1 and later.
Pre-upgrade check failed because the memory usage occupied by the running services is too high, exceeding expectations. Upgrade from HCI5.8.6 and later versions to HCI6.0.0. Contact a Sangfor technical support representative to skip this check step. This problem has been fixed and will not occur while upgrading earlier versions to HCI6.0.1 and later.
The VXLAN interface is configured with an IP address but without an IP address pool. Active upgrade. Configure the VXLAN IP pool before the upgrade. This problem will be detected by the pre-upgrade check. You must configure the IP address pool to start the upgrade.
aCloud cannot be upgraded after powering off the aCMP VM because aCloud is licensed by aCMP. Offline upgrade from HCI5.8.5. Power on the aCMP VM to activate the license, and do not power off it before restarting aCloud.
In the upgrade retry scenario, because other nodes already have the success flag of the pre-upgrade check, that of the cluster control will be deleted after the pre-upgrade check, thus blocking the upgrade process. Upgrade from earlier versions to HCI5.8.6 and above. Contact a Sangfor technical support representative to clean up the success flag of the pre-upgrade check of other nodes.
0x0006/0x0005 is reported during the pre-upgrade check of the offline upgrade. Upgrade from earlier versions to HCI5.8.6 and above. Contact a Sangfor technical support representative. This problem has been fixed and will not occur while upgrading earlier versions to 6.0.1 and later.
The ZK service encountered an error during the active upgrade. Upgrade from earlier versions to HCI5.8.6 and above. Upgrade again. If the problem persists, please contact a Sangfor technical support representative.
The virtual storage service encountered an error during the pre-upgrade check. Upgrade from earlier versions to HCI6.0.1. Contact a Sangfor technical support representative.

Upgrade Failures

Method Stage Failure Solutions Whether Rollback Is Supported
Offline Upgrade/Active Upgrade Check Environment The environment check failed. Troubleshoot the failure and try again. If the problem persists, please contact a Sangfor technical support representative. Yes, exit the upgrade to roll back to the original version.
Offline Upgrade/Active Upgrade Upload Update Package The update package upload failed. Troubleshoot the failure and try again. If the problem persists, please contact a Sangfor technical support representative. Yes, exit the upgrade to roll back to the original version.
Offline Upgrade/Active Upgrade Pre-upgrade Check Pre-upgrade check failed. Troubleshoot the failure and try again. If the problem persists, please contact a Sangfor technical support representative. Yes, exit the upgrade to roll back to the original version.
Offline Upgrade/Active Upgrade Upgrade Step Host power encountered an error. Troubleshoot the failure and try again (upgrades from earlier versions to 5.8.6 and later do not support retry). If the problem persists, please contact a Sangfor technical support representative. No. To roll back to the original version, please contact a Sangfor technical support representative.
Offline Upgrade/Active Upgrade Upgrade Step The Host management interface encountered an error. Troubleshoot the failure and try again (upgrades from earlier versions to 5.8.6 and later do not support retry). If the problem persists, please contact a Sangfor technical support representative. No. To roll back to the original version, please contact a Sangfor technical support representative.
Offline Upgrade/Active Upgrade Upgrade Step Other errors occurred. Troubleshoot the failure and try again (upgrades from earlier versions to 5.8.6 and later do not support retry). If the problem persists, please contact a Sangfor technical support representative. No. To roll back to the original version, please contact a Sangfor technical support representative.
Offline Upgrade Restart Any error occurred. Contact a Sangfor technical support representative. Contact a Sangfor technical support representative to confirm whether rollback is supported.