VMware Cloud Community
jasonboche
Immortal
Immortal

VI 3.5 Update 1 upgrade experiences

I upgraded VirtualCenter 2.5.0 to 2.5 Update 1 today (using SQL Server 2005 SP2 back end).

Observations:

1. The license server installation/upgrade is still not called as part of the autorun.exe as all other VI components are (VC server, VC client, VC Update Manager, VMware Converter for VC). The license server installation/upgrade must still be performed as a separate step at the very beginning.

2. SQL back end users are no longer allowed to use the SQL Server 2003 ODBC driver packaged with Windows Server. You must now download and use the SQL Native Client driver and rebuild your DSNs using this driver. Available at: http://www.microsoft.com/downloads/details.aspx?FamilyId=50b97994-8453-4998-8226-fa42ec403d17&Displa...

3. VMware took the feedback of all the database upgrade issues being had with the release of VC2.5.0. Helpful screens now guide us to the correct database upgrade permissions referencing the applicable VMware KB articles. Furthermore, if by chance you grant your VirtualCenter SQL account the sysadmin role to SQL server, the upgrade picks up on this and presents you with a warning message that a new parallel set of database tables will be created rather than upgrading the existing infrastructure. Failure to correct this situation will essentiall result in losing your datacenter after the upgrade is complete.

4. Database upgrade completed without any issues.

5. Once completed, Help|About reflects VIC and VirtualCenter versions 2.5.0 build 84767. Why not 2.5.1? Why is the incorrect build number of 84767 shown instead of what's listed on VMware's website build 84782






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
157 Replies
xcomiii
Contributor
Contributor

I just updated too, same problems. Luckily I can log in direct to the ESX hosts and startup VM's, but something is clearly wrong, as the ESX host is updating the resource pools (on the ESX) in an never ending loop. Any idea of what's my best option at this moment?

Reply
0 Kudos
FrancWest
Contributor
Contributor

Hi,

I reverted back to the old VI client (left the VI server at latest version) and everything is stable so far.

Franc.

Reply
0 Kudos
jasonboche
Immortal
Immortal

I just updated too, same problems. Luckily I can log in direct to the ESX hosts and startup VM's, but something is clearly wrong, as the ESX host is updating the resource pools (on the ESX) in an never ending loop. Any idea of what's my best option at this moment?

xcomiii, I rolled back to VirtualCenter 2.5.0 build 64192 (oh excuse me, that's the VC and VIC build number, not the VIM Installer number posted on the VMware download page...) using the following procedure:

On the VirtualCenter Server:

1. Uninstall all VirtualCenter, Virtual Infrastructure Client, Capacity Manager, Converter, License Server, etc. software using Add/Remove Programs

2. Reboot the VC Server

3. Restore from backup your SQL or Oracle datastore from a point in time BEFORE the VirtualCenter 2.5 Update 1 upgrade scripts were run against it.

4. Install License server build 64192

5. Install the remaining VirtualCenter components build 64192 (if using a SQL Server back end for the datastore, don't forget to temporarily grant your VirtualCenter SQL account DBO on the MSDB database, then remove the account from MSDB DBO when finished!)

6. No reboot required after this point but I'd reboot

7. Your hosts may now show up disconnected in VirtualCenter. Reconnect them, or remove/readd them. It may be prudent to remove/readd them to roll back the VC agent version on the ESX host although I simply reconnected the hosts and am not seeing any issue yet. Note I hadn't upgraded my hosts to ESX 3.5 Update 1 yet. They remain at the original ESX 3.5 2/20/08 build.

8. VC cleanup: Depending on whether or not VMs were added/removed between now and the tape back up you restored from, you may see some orphaned VMs in gray italics which you will need to remove from inventory. You may also have some VMs that were added after your backup which now will be found in the "Discovered VMs" folder. Move them to the appropriate folder. If any changes were made to VC folder structure or stored template customizations, you'll need to re-address those as well.

ESX host rollback

I'd rebuild from scratch. Never dabble with the integrity of your ESX host. If you have an automated or scripted build, you can do this in less than 1 hour per host.






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
xcomiii
Contributor
Contributor

Thanks Jason.

Is that the build 24201 from december-07 ?

I forgot to mention that I first upgraded both my 2 ESX hosts to 3.5 U1 (yeah, silly me, forgot that VC needs to be updated first). I have a backup of VC, but that's not a big issue, as my enviroment is pretty small and I can recreate resource pools, foldes, permissions etc in a short time. So if I uninstall all VC related sw, delete the db, create a new db and then install VC with the correct build, it should work again ?

Reply
0 Kudos
jasonboche
Immortal
Immortal

Thanks Jason.

Is that the build 24201 from december-07 ?

No. build 64201. But I'm assuming that's what you meant.

VMware VirtualCenter 2.5

Latest Version: 2.5 | 12/10/2007 | Build: 64201

I forgot to mention that I first upgraded both my 2 ESX hosts to 3.5 U1 (yeah, silly me, forgot that VC needs to be updated first). I have a backup of VC, but that's not a big issue, as my enviroment is pretty small and I can recreate resource pools, foldes, permissions etc in a short time. So if I uninstall all VC related sw, delete the db, create a new db and then install VC with the correct build, it should work again ?

yep, and roll back your hosts to ESX 3.5.0 2/20/08 build.






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
xcomiii
Contributor
Contributor

Sorry, a little typo Smiley Happy

But exactly how do I revert two ESX hosts back to 3.5.0 ? Is there any docs on this or kb?

Reply
0 Kudos
jasonboche
Immortal
Immortal

As I said previously:

ESX host rollback

I'd rebuild from scratch. Never dabble with the integrity of your ESX host. If you have an automated or scripted build, you can do this in less than 1 hour per host.






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
FrancWest
Contributor
Contributor

Hi,

why revert back the host also ? I installed the host updates using update manager this week (not knowing that it was update 1) and it keeped working fine with the old VI server and client.

Franc.

Reply
0 Kudos
Engelsman
Enthusiast
Enthusiast

I never upgrade before looking at VMTN, so thank you all for paving the path Smiley Happy

Since we are planning on upgrading to VI35, I did an upgrade of VC202U2 to VC250Update 1 in a lab environment and it ran just fine.

I've downloaded and used the Virtual Center ISO file since the MD5 Checksum for the zip doesn't match. The ISO file seemed fine, so I installed from that.

I always install the stuff from the vpx dir instead of using the "autorun installer thingie".

To make things more confusing about the build numbers:

In the "vpx" dir there is a file called 2.5.0.64207. Also the properties of the viclient and vcserver setup files say product version 2.5.0.64207

In VC, when I go to Help, About my build numbers are build 2.5.0.84767. And then there is the build number of the VMware Infrastructure Management Installer: 84782

Would be "nice" to keep the buildnumbers in line......!

Regards,

Henk

Reply
0 Kudos
xcomiii
Contributor
Contributor

Franc, that was just what I hoped for. Currently all VM's are running on a 3.5 Update 1 host and the second host (in maintance mode) is also running 3.5 Update 1. Reverting both back without a working VC seems to be a little exciting to me. Surely I can revert the host which is in maintance mode, but how would I migrate them to that host without VC ?

Reply
0 Kudos
FrancWest
Contributor
Contributor

Hi,

why not first try uninstalling the VI Client only and install the old version and look how it goes ? In my case everything works fine with the old VI client and the update 1 VI server and hosts.

Franc.

Reply
0 Kudos
java_cat33
Virtuoso
Virtuoso

Can someone from VMware please advise when the correct download is available for Update 1 (for ESX 3.5 and VC) - and also when the bugs have been fixed?

Reply
0 Kudos
xcomiii
Contributor
Contributor

Ah, thank you! Now I saved many hours of work, it works like a dream. Strange that the VI client is buggy though. Btw, I installed the VC update from the zip file, forgot to check the MD5.....

Reply
0 Kudos
FrancWest
Contributor
Contributor

Hi,

glad it worked. I mentioned this workaround a couple of post back already, but you and probably others overlooked it ?

Franc.

Reply
0 Kudos
xcomiii
Contributor
Contributor

Hi, yes I overlooked it in my frustration. Thank you for the solution.

Maybe Jason can make this thread sticky or make this information better viewable to other that are upgrading?

Reply
0 Kudos
jasonboche
Immortal
Immortal

Hi,

why revert back the host also ? I installed the host updates using update manager this week (not knowing that it was update 1) and it keeped working fine with the old VI server and client.

Franc.

Historically, the upgrade steps for VirtualCenter and ESX Server go in order as follows:

1. VirtualCenter upgrade (implies license server, VIC, and database back end upgrades)

2. ESX host upgrades

3. VMFS LUN upgrade(s)

4. VM Virtual Hardware upgrades

5. VM VMware Tools upgrades

My previous recommendation of rolling back the ESX hosts was based upon the upgrade path above

Currently, http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_compat_matrix.pdf makes no reference or distinguishment between VC2.5 and VC2.5U1 nor does it distinguish between ESX3.5 and ESX3.5U1. That said, it must be assumed that VC2.5 can manage ESX3.5U1 hosts so I will take back what I said previously and I will now say that based on the documentation, managing ESX3.5U1 hosts with VC2.5 looks to be supported. In other words, don't bother rebuilding your hosts with ESX3.5

Do let us know if you see any issues using VC2.5 to manage ESX3.5U1 hosts.

Thanks,

Jas






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
jasonboche
Immortal
Immortal

Hi, yes I overlooked it in my frustration. Thank you for the solution.

Maybe Jason can make this thread sticky or make this information better viewable to other that are upgrading?

I don't believe I have that as an available tool as a moderator. The best I could do is to create an "annoucement" which references the URL to this post. Announcements always stay at the top of the forum like a sticky.

The other option is people continue to reply to this thread sharing their upgrade experiences and with that, the thread will keep resurfacing at the top on its own.

Jas






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
jpoling
Enthusiast
Enthusiast

Just trying to bring some clarity to this situation for myself:

I installed VC from the zip file that was posted the day Update 1 was released. I upgraded from VC 2.0.x and now I am seeing very few problems. There are a couple oddities but nothing unusual. So, do I need to roll back? Do a re-install?

I would next like to upgrade my hosts from 3.0.1/3.0.2. Do I need to wait until all this is clarified?

Thanks,

Jeff

Reply
0 Kudos
jasonboche
Immortal
Immortal

Just trying to bring some clarity to this situation for myself:

I installed VC from the zip file that was posted the day Update 1 was released. I upgraded from VC 2.0.x and now I am seeing very few problems. There are a couple oddities but nothing unusual. So, do I need to roll back? Do a re-install?

I would next like to upgrade my hosts from 3.0.1/3.0.2. Do I need to wait until all this is clarified?

Thanks,

Jeff

Jeff,

Do us a favor and MD5SUM the VirtualCenter .ZIP file you downloaded and post the results here.

John Troyer emailed me late tonight. He is working with a few internal VMware employees to get to the bottom of the .ZIP file differences.

Here's what I've done since I last wrote:

Late this evening I re-downloaded the .ZIP file a few more times using different different PCs, different operating systems, saving to different disks, and using different web browsers (IE7 versus FireFox). One of the PCs I used to download the .ZIP file was the VMware Browser Appliance VM. I also used 3 different MD5SUM tools to validate the downloads. Each time I come up with an MD5SUM value of 6201bd703a932750ca2b4b9fe68996d8. This evening when VMware employees download the .ZIP file, they come up with an MD5SUM value of 9146aa4743c0a56e37921f62fb898a64 which is the value posted on the VMware downloads website.

Each time I downloaded tonight, I noticed my download comes from download2.vmware.com. The issue may have something to do with clustered web servers not having the same version of the .ZIP file on each cluster node. That's pure speculation on my part.

I expect John or someone from VMware will have more information for us early this week. I would hang tight until we have official clarification from VMware. Based on the scenario, the appropriate gameplan can be developed. Depending on what .ZIP file you got, you may not have to do anything. Let's wait and see.

Jas






[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
Reply
0 Kudos
java_cat33
Virtuoso
Virtuoso

Thanks for the update Jason - appreciate it.

Reply
0 Kudos