Kezaworld
Contributor
Contributor

Using VUM To Upgrade to ESX 4.1 from 3.5

I was pondering on my upgrade that I have planned next week to upgrade my test enviroment ESX hosts using the update manger through vCenter.

Would I still need to disconnect my esx host from the SAN during the upgrade?

Normally if I was planning to upgrade the ESX host manually or a fresh install I would detach from my SAN but do I need to do it when VUM is upgrading for me?

Any suggestions

Tags (3)
0 Kudos
3 Replies
AWo
Immortal
Immortal

Welcome to the forums!

Would I still need to disconnect my esx host from the SAN during the upgrade?

Unfortunately I can't tell you that.

What I can tell you is that I cdisabled the SAN switch ports for each ESX host everytime I did an upgrade and thereby I never run into trouble. And I will keep it that way. If something goes wrong, once, that is one time too much.

BTW, I upgraded all hosts via VUM, no problems encountered.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
AndreTheGiant
Immortal
Immortal

Would I still need to disconnect my esx host from the SAN during the upgrade?

You can also do the upgrade with the SAN connected.

But when you choose where put the service console vmdk, be sure to choose the local storage and not the shared one.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
Kezaworld
Contributor
Contributor

Thanks all for your comments. I upgraded hosts without masking the SAN. Creating the upgrade job through Update Manager ensured that I selected the local storage option for the COS.

All went well.

Thanks

0 Kudos