Upgrading Sangfor aCloud Cluster Nodes Safely and Without Downtime
  

George Fady Lv2Posted 2026-Jun-07 03:14

Upgrading core platform elements demands precise compatibility validation. A misaligned upgrade sequence can disrupt physical nodes or crash active workloads. This post breaks down the platform criteria needed to maintain cluster stability.
1. Hot vs. Cold Upgrade Thresholds
  • Hot Upgrades Support (Zero Impact): If your cluster runs aCloud 5.8.6 or newer, the hypervisor platform supports hot upgrades. This operational mode updates underlying components without interrupting executing virtual machines or active physical hosts.
  • Cold Upgrade Requirements: For older infrastructure legacy environments updating to version HCI 6.7.0 and above, a cold upgrade strategy is mandatory due to deep underlying system kernel changes. For legacy variants between HCI 5.0 and HCI 5.8.5, all virtual instances must be systematically powered down prior to applying any upgrade packages.

2. Mandated Use of the aDeploy Tool
  • When transitioning a cluster to version HCI 6.3.0R1 or higher, it is a hard platform requirement to deploy the aDeploy utility.
  • Administrators must run this standalone application tool to perform cluster environment verification checks and execute the precheck package deployment sequence.
  • Pro-Tip: The aDeploy configuration tool can be directly retrieved via the download plugins panel located within the official technical portal.

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go

Humayun Ahmed Lv4Posted 2026-Jun-08 12:18
  
Thanks to share!
admin Posted 2026-Jun-11 17:05
  
This is a really solid framework — exactly the kind of structure that helps newcomers ramp up fast. Would love to hear more about a real deployment you walked through.