Potential Problem with ESX 3.0.x and VirtualCenter 2.5

Buffer

We are still running ESX 3.0.x and VC 2.0.x. I thought about upgrading vcenter first and then just upgrading the servers has time permits. But if there’s going to be odd issues like this, even if its only when you install some patches. I think I’ll try to put together a much shorter timeline to move to 3.5

Heads up—I’ve been alerted to a potential problem when using ESX Server 3.0.x with VirtualCenter 2.5. Quoting from this VMware KB article:

ESX Server 3.0.x hosts managed by VirtualCenter 2.5 must have their Host Agent (hostd) specially configured to work with VirtualCenter 2.5. This configuration is done automatically during the initial installation of the VirtualCenter Agent (vpxa). If an ESX Server patch is subsequently applied that includes the esx-hostd RPM package, like ESX Server patch 1002435, the patch replaces the existing Host Agent (hostd) configuration file (/etc/vmware/hostd/config.xml) and undoes vpxa’s changes. This reverting of the Host Agent configuration file breaks connectivity with VirtualCenter 2.5.

Potential Problem with ESX 3.0.x and VirtualCenter 2.5 – blog.scottlowe.org – The weblog of an IT pro specializing in virtualization, storage, and servers

[tags]vmware, esx, vcenter[/tags]

About the Author

Jason Benway Has Written 1361 Articles For Us!

I am the admin of this site and enjoy enterprise technologies and gadgets.
Getting The Latest Tweet...
Did you know Jason has a website? Go see what you're missing...

Related posts:

  1. VMware: Running VirtualCenter in a VM
  2. VMware ESX 3.5 upgrade path: Where to start
  3. Errors after upgrading vcenter?
  4. VMTSPatchManager: Free "Windows Update" For ESX Servers
  5. VirtualCenter 2.5 upgrade issue with SQL 2000

Related posts brought to you by Yet Another Related Posts Plugin.

April 5th, 2008

Filed under: Post from around the Net , technology , vmware

Post tags: • • • • • • •