Filter
Top Products
Upgrading from 3.0.x to 4.5.0
47
2. Start the Usage Servers that you have stopped (if they were running on your previous version).
Perform this on each Usage Server host.
# service cloudstack-usage start
3. Do the following procedures, if required:
• (KVM Only) Upgrade and start the agent on a KVM host.
For more information, see Section 9.7, “Upgrading KVM Agents (KVM Only) ”
• (Hyper-V only) Upgrade and start the agent on a Hyper-V host.
For more information, see Section 9.8, “Upgrading Hyper-V Agents (Hyper-V Only) ”
4. Log on to the CloudPlatform UI using administrator privileges and check the status of the hosts.
All hosts must be in the Up state (except those hosts that you know to be offline). Depending on
the number of hosts, you may need to wait for 20 or 30 minutes to complete this.
Do not proceed to the next step until the hosts display in the Up state. If the hosts do not display in
the Up state, you need to contact Citrix support.
Note
If you cannot log on to CloudPlatform UI, clear your browser cache and reload the page.
5. Upgrade Secondary Storage VMs and Console Proxy VMs.
For more information, see Section 9.11, “Upgrading Secondary Storage VMs and Console Proxy
VMs ”
6. Upgrade and restart virtual routers.
For more information, see Section 9.12, “Upgrading the Virtual Routers Selectively ”
7. If you would like additional confirmation that the new system VM templates were correctly applied
when these system VMs were rebooted, SSH into the System VM and check the version.
Use one of the following techniques, depending on the hypervisor.
XenServer or KVM:
SSH in by using the link local IP address of the system VM. For example, in the command below,
substitute your own path to the private key used to log in to the system VM and your own link local
IP.
Run the following commands on the XenServer or KVM host on which the system VM is present:
# ssh -i /root/.ssh/id_rsa.cloud <link-local-ip> -p 3922
# cat /etc/cloudstack-release
The output should be like the following: