I wrote about a new patch for ESX(i) 3.5 yesterday and the fact that VirtualCenter 3.5 Update 3 was mentioned. Well today VirtualCenter 2.5 Update 3 has been released! You can pick it up here.
I think the most important fixes are the ones for HA. With Update 2 VM started checking the subnets of the heartbeat network for HA. If these weren’t compatible than HA bailed out. With Update 3 a new advanced option has been introduced ,”das.bypassNetworkVerification”. When this setting is set to “true” the Network compatibility check isn’t done and thus it’s possible to have an incompatible but routable HA heartbeat network.
Another important one is that as of U3 it’s possible again to delete HA advanced options, this problem was introduced in U2 and has been fixed.
An error that was also much talked about on the VMTN forum was the fact that VM’s weren’t vmotioned when maintenance mode was entered even if the admision control was disabled. This error has also been fixed.
These are three most important fixes in U3 in my opinion. Be sure to update and read the release notes for more info and fixes. Please not that the plugins for Update Manager and Converter has also been updated.
That’s good news! It’s very annoying that after installing Update2 the virtual machines doesn’t migrate automatically when you put an ESX server into maintenance mode.
hi
after update to VC update 3…the 90% of the esx host result disconnected..and after reconnecting the error “failed to installa Virtual Center Agent Service” appeared..
i thin know i should remove the esx host from vc …restar mgmt and vpxa..and wait…
not very nice beginning of the weekend.
bye
I think you must be glad that you can update to Update 3…
Update 3 doesn’t appear in my virtual center update manager… :-S
Even when I scanned for updates and let the download manager check for updates by vmware it doesn’t work… 🙁
Grrr…I forgot that it wasn’t a ESX update and that I’ve to download and install this manually… 🙂
hehehe
by the way, i’ve solved it restarting the mgmt-vmware and vmware-vpxa agents and then connecting the hosts again…with 40 hosts i’ve spent all the moarning 🙂
bye
just called Vmware support.
statement should read das.bypassNetCompatCheck=true
there release notes had =yes.
Tested and works fine…now I can complete the rest of my upgrades, how frustrating this issue was.
Thank you Peter… i had this same issue and appreciate your saving me the call to support… This has been a most frustrating experience and i did give my VMWare TAM an earful about “… its not a good idea to make massive product behavior changes and then bury the heads up deep in release notes…”
Hi! Can anyone give the step-by-step process to upgrade the virtual centre 2.5 update 2 to update 3???
I have downloaded the .zip file – when executed Iam prompted with a question – the DSN points to an existing vmware virtual centre repository. Do you want to reinitialize the database and start over with a blank configuration?
What is the recommended way to go about this?
Any help would be appreciated.
Thank you
Harry
NO! You want to keep the database!!
But what does the database hold ? Since I am testing on the test machine, I reinitialized the database.
The first time I seletected not to reinitialize the database, and after installation – I could not logon to the VC. There was an error 1000 – initial connection could not be made.
So, I rerun the install process and reinitialized the database and I could logon. So I would like to know what happens if I do that – since Iam not finding any difference.
Am I Missing anything?
The database holds everything (configurations, performance stats, etc.). In general you don’t want to reinitalize when upgrading VC because you basically have to start over with a blank config of virtualcenter.