Here is a quick-steps guide on how to upgrade the vCloud Connector 2.5 to version 2.6. In this case I will perform an in-place upgrade of vCloud Connector Server and Nodes running on vSphere. Before we begin, let’s take a look at what’s new in vCloud Connector 2.6.
- Removal of Licensing Requirements
- Copy Validation
- Guest Customization option for deployment
- Network connection mode for deployment
For full description of the new features and fixed bugs, please refer to the vCloud Connector 2.6 release notes.
Please note that you can upgrade to vCloud Connector 2.6 only from vCloud Connector version 2.5. You cannot upgrade from earlier versions to version 2.6.
Before you begin with the upgrade, read the following documents and guides.
Before you upgrade the vCloud Connector Server and Nodes, you must update their virtual hardware settings to match the vCloud Connector 2.6 level, because the upgrade process does not update the virtual hardware settings. Update the settings described below for the vCloud Connector Server and for all the Nodes.
This procedure describes the steps for upgrading the hardware level on vSphere. If you need to upgrade the hardware level for vCloud Connector Server and Nodes running on vCloud Director, please refer to the vCloud Connector 2.6 Installation and Configuration guide.
- Open the vSphere Client and log in to your vCenter Server with an administrative account.
- Shut down the vCloud Connector Server and all Nodes.
- Edit the hardware settings of the virtual machine and assign 4 vCPUs and 4 GB of memory for the vCloud Connector Server and all Nodes.
- Power the vCloud Connector Server and all Nodes back on.
- Close the vSphere Client.
Upgrade Server & Nodes
Procedure described below is the same for vCloud Connector Server and a vCloud Connector Node. At this point, you should make a snapshot of the vCloud Connector Server and vCloud Connector Node so you can roll back in case something goes wrong.
- Open the vCloud Connector Server or Node admin web console by navigating to https ://<FQDN_or_IP_Address>:5480
- Log in with the admin account and select the Update tab.
- On the status page, click the Check Updates button under the Actions pane. An update should be available as depicted below.
- Click the Install Update button.
- Accept the EULA.
- Confirm the update by clicking OK.
- When the update is completed successfully, a message stating that a reboot is required to complete the update will be displayed.
- Select the System tab and click Reboot button under the Action pane.
- When the vCloud Connector Server or Node is rebooted, you can remove the snapshot if you created one earlier.
Modify Permissions on Nodes
After you upgrade a vCloud Connector Node to version 2.6 you will also have to change the permissions on the node staging directory.
- Select the vCloud Connector Node and open the console in vSphere Client.
- Select the Login option and log in as the root user.
- Type the following command: # chmod 777 /opt/vmware/hcagent/staging and press enter.
- Type exit to return to the welcome page.
- Close the console.
Repeat the steps above for all vCloud Connector Nodes.
When you upgrade the vCloud Connector Server and Nodes, you must update the registration of the vCloud Connector UI with the vSphere Client. If you do not update the registration, vCloud Connector does not appear in the Solutions and Applications panel in the Home tab in vSphere Client.
- Open the vCloud Connector Server admin web console by navigating to https ://<FQDN_or_IP_Address>:5480
- Log in with the admin account and select the Server tab.
- Select the vSphere Client tab, provide the vCenter username and password and click the Update Registration button.
- You should receive a message that registration has been updated.
- Log out from the admin web console.
Note: If you cannot log in to the web console of the vCloud Connector Server or Node after the upgrade and you receive the “Unable to authenticate user. Please try again.” error, you have to change the password for the admin user from the console because it has expired.
At this point the vCloud Connector is upgraded to version 2.6 and is ready to move your virtual machines. Before you begin to use the vCloud Connector, clear your browser cache.