VMTN

FrancWest wrote:

 

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]

xcomiii wrote:

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]

jpoling wrote:

 

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]

mittell wrote:

Hi Jason,

 

I get 6201bd703a932750ca2b4b9fe68996d8 for the download VMware-VIMSetup-2.5.0-84782.zip too. Tried it 3 times, same result each time. My download is also coming from download2.vmware.com.

 

Cheers,

 

Alex

Thank you Alex.  That is very helpful!  You are getting the same incorrect MD5SUM value that I have been getting for the VirtualCenter .ZIP file.

Jas

[i]Jason Boche[/i]

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

dmadden wrote:

The md5sum for the zip file is not correct.

Based on my email discussions with VMware, last night a VMware employee downloaded the .ZIP file and the MD5SUM value matched what is published on the website.

Thus far it has been confirmed that when Alex (Mittell) or myself downloads the .ZIP file, the MD5SUM value does not match what is published on the website.

My biggest concern is that 2 different .ZIP files are being downloaded from the VMware website evidenced by the 2 different MD5SUM values we are seeing. It's a version control issue. How many people have downloaded the .ZIP file since the release on 4/10/08 and which version of the .ZIP file did each person get? Which version is the correct version?

So far it has not been proven that there is any correlation between the different .ZIP files/MD5SUM values and the other issues being reported such as VIC client crashing, complaining about a vpx log file being in use, inability to vmotion, inability to view remote console, inability to deploy a template with a customization, inability to enable the Update Manager plugin, etc. For now I would treat those as separate issues.

Jason Boche

VMware Communities User Moderator