Upgrade vCenter from 4.1 to 5.0
I received during the weekend my new license codes for the 5.0 lineup of VMware products, so I tried and found a couple of hours to test the upgrade process of vCenter.
This is the first element of a 4.1 cluster you need to upgrade to 5.0, cause it can manage both ESXi 4.1 and 5.0 at the same time.
Once I downloaded the iso image and started the autorun, the start screen give us many choices:
For the sake of it, I run first the Pre-Upgrade Checker. Thi tool checks if the database DSN and the ESXi hosts are compatible with the upgrade, and if it’s the case I think is going to tell us what to do; it’s only a guesswork since my environment was compatible and I was able to proceed with the upgrade.
Since my vCenter was already a 64 bit one (Windows 2003 R2 64 bit) there was no data migration to do, and installer warned me only about it found the former vCenter 4.1 and that it will be upgraded:
Then, installer suggested to upgrade also the database:
Another important step is the upgrade of the Virtual Center agents installed on the managed ESXi hosts. Installed suggests to upgrade them automatically, and I suggest you to use this method. Otherwise, as you can see in the screenshot, you can upgrade them manually, but be aware that in this way all ESXi hosts will be disconnected from vCenter until you will upgrade them.
Once you have answered to the other questions, such as installation folders and the several TCP ports for the services, installation starts and it completes after about 15 minutes wihtout any error or problem.
As stated also during the vCenter upgrade, it’s necessary to upgrade also the Update Manager, so I run also its installer. Right in the first screen, installer founded the former Update Manager and told me it was going to be upgraded to version 5:
Also Update Manager asked to upgrade its own database, and I agreed to it.
As a last step, I upgraded vSphere Client on the vCenter virtual machine, nothing special to say. I also installed the Web Client; since I use a Mac this tool is going to be really useful in the future. It will be reachable on tcp:9443 of the vCenter server, over the https protocol.
After about an hour from the start, I was ready to login inside my new vCenter 5.0.
Upgrade vCenter from 4.1 to 5.0 by Luca Dell'Oca is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This post is also available in: Italian
|Print article||This entry was posted by Luca Dell'Oca on August 29, 2011 at 09:00, and is filed under Tech. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site.|
No trackbacks yet.
about 1 month ago - No comments
TweetRecently a customer has added a new ESXi server to his vSphere cluster. Since he has vCloud Standard licenses, I already created a distributed switch to allow an automatic, consistent and error-free configuration of the network settings of all servers. The network migration wizard had worked great and the new server was added and configured…
about 4 months ago - No comments
TweetIn a previous post, I explained how to install and configure HP Insight Control for VMware vCenter 7.1.1 to monitor and manage an HP LeftHand storage directly inside vCenter Web Client. The HP software also adds VASA capabilities to vCenter, useful to create Storage Profiles based on effective storage capabilities directly acquired from the storage rather…
about 5 months ago - No comments
TweetHP has recently released the latest version of their Insight Control, numbered 7.1.1. As per the official webpage: The HP Insight Control extension for VMware vCenter Server delivers powerful HP hardware management capabilities to virtualization administrators, enabling comprehensive deployment, provisioning, monitoring, remote control and power optimization directly from the vCenter console. One of the most interesting…
about 5 months ago - No comments
TweetCustomazion Wizard is a really cool feature in vCenter, but I often found many customers not using it, mainly because they do not even know it exists, or because they had a weak knowledge about how to use it. This is even more true if the template is a linux VM. On CentOS, the main…