So now with ESXi 5 and vSphere 5 dropping to the masses, it’s time to get some hands on experience with it.
So first things first, upgrade your vSphere 4 server to vSphere 5 and make sure to update VMware Update Manager (VUM) as well. Personally, I did a new install, but will cover an upgrade at a later date. Next, you’ll want to connect your ESXi 4 host to the vSphere 5 server’s DC. You’ll also want to download the ESXi ISO from VMware’s website. Now that we’re on the same page, here’s how the upgrade process goes:
Here’s an ESXi 4.1 host that I’ll be upgrading.
Now you’ll want to head over to the “Solutions and Applications” area, select “Update Manager” then click on the “ESXi Images” tab
You’ll want to click on “Import ESXi Image”, browse to where the ISO for ESXi 5 was downloaded and click “Next”, the image will be uploaded and imported to the VUM repository, and once the upload is done it will display a success note.
Then check the “Create a baseline” and name it something appropriate, then click “Finish”
Here’s how the ESXi Image looks once it’s upgraded in VUM
Go back to the VUM tab for the individual host and attach the baseline, by clicking “Attach”, then checkmark the Upgrade Baseline that was just created and click “Attach”. The Baseline will now show up in the “Attached Baseline” along with having an upgrade notice in the bottom portion
Click on the “Scan” button and ensure that “Upgrades” is checkmarked then click “Scan”
In most cases, the host will show up as “Non-Compliant” however my host has an added plugin which won’t work with ESXi 5 and will have to be removed during the VUM upgrade. The error I received in this case was: “Software modules oem-vmware-esx-drivers-net-vxge oem-vmware-esx-drives-scsi-3w-9xxx published by third party vendor(s) are installed on the host. Upgrading the host will remove these modules.”
We’re all set to proceed with the upgrade by clicking on “Remediate”, selecting the “Upgrade Baselines” followed by the Baselines which was created (should show VMware ESXi 5.0.0 in the Upgrades column), accept the EULA, remove the software which will be incompatible with the upgrade, give the task a name and select a time to schedule the remediation, modify any maintenance mode options, verify the information and click “Finish”
Here’s how the events went:
We have success!
My only problem with the whole process was after the host was upgraded, you have to physically push the “Enter” button to allow the machine to reboot. I was hoping for it to be a completely seamless and hands off experience, but a DRAC or iLO card makes up for it