VMware upgrade

[rayan68]

I am trying to upgrade from 3.X to 3.5 ESX , the upgrade scenario will be according to hosts on a SAN using VMotion with DRS and HA , during my reading in the upgrade documentation the scenario like this ,

upgrade virtual center 2.0 to VC 2.3

Upgrade VC database

Place the ESX server host into maintenance mode

wait until the software evacuates all the VMs from the ESX server host

upgrade ESX server 3 to ESX 3.5

add the upgraded esx server to the DRS cluster

repeat step 3 to step 6 for each esx server host ,

my question is , after upgrading VC from 2. to 2.5 and upgrade the VC Database , which client I will use to access my ESX hosts , the old VI client 2 , or I will download the new client 2.5 , to complete all steps ?

[chandlm]

Once you upgrade VC you should use the new 2.5 VC client to access your VirtualCenter server. Are you asking about directly attaching to the ESX hosts? You should be able to use either version on the older hosts I think.

Your process is pretty much what I have done other than upgrading, I generally wipe and rebuild.

[rayan68]

So is that mean if I login with the new VI client I can see all my ESX servers hosts and I can use Vmotion to complete the upgrade ? in that case do I have to add again the LUNs to the upgraded host or it will keep the same configuration from the old version ?

[azn2kew · Accepted solution]

If you have to do a fresh install of ESX 3.5 hosts, I suggest you to unplug the HBA connection to prevent from wiping out your SAN LUN or you can use other technique on Xtravirt.com site to disable the HBA drivers from loading during installation. If you upgraded your ESX 3.5 than your storage and settings are in tact so no configuration is need unless you made changes to your systems.

Steps procedure:

1. Backup all the VMs if possible.

2. Backup your virtual center database and records tasks and jobs info in case you have to reconfigure VC Server.

3. Upgrade to VC 2.5 Update 1

4. Migrate all VMs off ESX host and neither upgrade or fresh install (your choice)

5. Once completed the installation, reboot and add your ESX host back to virtual center using VI client. (both old and new should work fine)

6. Connect your browser to your VC 2.5 Update 1 server to download the latest VC 2.5 client.

7. Configure your ESX TCP/IP, storage etc...if needed.

8. Test your VMotion to see if you can migrate between host. Repeat same steps until all hosts upgraded/installed.

Troubleshooting:

Sometimes ESX host doesn't like to be added back to the virtual center or failed to enable HA.

1. Restart hostd and vxpa services

2. Make sure DNS is working and place static DNS entries for /etc/hosts file

3. Make sure / partition doesn't fill up and /tmp/vmware-root folder is created.

4. Manually remove and reinstall VPX agent build with the latest installed.

5. Manually remove and reinstall aam package for HA issue.

Good luck to your smooth upgrades!

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant

[rayan68]

I am using ISCSi NetApp , should I isolate the LUNs or no ?

[azn2kew]

Better safe than sorry, i would remove connection from SAN until completed install. Unless you follow instruction on xtravirt.com site how to isolated your SAN for fresh installation.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant

[chandlm]

I agree, I always disconnect. It is a pretty easy step compared to an enormous OOPS moment... :_|