Upgrade requirements

Before upgrading to CloudLink version 7.0, ensure that the following requirements are met.

Upgrade paths

NOTE: Customers must be using the version 6.9.0 (build 899.7) before upgrading to CloudLink 7.0.

Log in to the CloudLink Center to verify the CloudLink version and build number. The version and build number is displayed in the Information box on the CloudLink Center Home panel.

NOTE: If your CloudLink Center was originally deployed using a version older than CloudLink 6.9, such as 6.8 or earlier, the CloudLink upgrade includes an update to Ubuntu Server 16.04. This increases the time required for the update process.


  • Ensure that your CloudLink Center virtual appliance is running version 6.9.0 (build 899.7)
  • All CloudLink Center VM must have at least 6 GB of RAM and 4 vCPUs before you upgrade. If a CloudLink Center VM does not have sufficient resources for the upgrade, a System does not meet requirements alarm is raised.
  • To automatically upgrade all CloudLink Agents, ensure that all machines that are registered with CloudLink Center are online and display as Connected in CloudLink Center. The Machine Agent Upgrade policy must be set to Auto.
  • If the Machine Agent Upgrade policy is set to Auto, any CloudLink Agent that is not connected to CloudLink Center is automatically upgraded the next time the CloudLink Agent connects. Performing the postupgrade verification is more efficient if machines are online and connected during the upgrade. For more information, see Postupgrade verification.
    • If the Machine Agent Upgrade policy is set to Manual, then each machine in the machine group that uses that policy must be upgraded manually.
  • CloudLink Center cluster servers must be online and synchronized with each other.


It is recommended that you back up CloudLink Center and all VMs before starting the upgrade process. Perform backups by using virtual machine snapshots or traditional backup tools.

Meet the following critical backup requirements:

  • Back up your CloudLink Center configuration data. For more information, see the chapter "Back up and restore CloudLink Center" in the Dell EMC CloudLink Administration Guide.
  • If you are using Microsoft Active Directory, Amazon S3 external storage, or an S3-compatible bucket, back up your encryption keys by using tools that are specific to those environments.


If you are using an external keystore, ensure that the keystore is connected before starting the upgrade process.

CloudLink licenses

Before starting the upgrade process, check that licenses have not expired.

Licenses that are past their support duration, typically one, two, or three years from the date of purchase, are blocked from being uploaded. If licenses have expired after being uploaded, all the existing CloudLink functionalities will continue to work including releasing of keys. However, new CloudLink agent installation and encryption of machines and SDS devices cannot be performed. To reenable encryption, purchase a new license and upload it.


You need the CloudLink secadmin user's password, the CloudLink console password, one of the CloudLink Vault passwords, and the passwords of the encrypted virtual machines.

CloudLink Center clusters

The upgrade process upgrades all servers in a cluster. Ensure that all servers are accessible and upload the upgrade ISO to any server in a cluster. Wait until the ISO is uploaded to all servers before you begin the upgrade.


Before starting the upgrade process, ensure that TCP ports 80 and 1194 and UDP port 1194 are open. For more information, see the section "Software requirements for deploying CloudLink Center" in the Dell EMC CloudLink 7.0 Deployment Guide.