Potential Problem with ESX 3.0.x and VirtualCenter 2.5
April 2nd, 2008 by slowe
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.
There is a workaround that involves re-initializing the VirtualCenter Agent on the affected ESX servers via a script. I didn’t have any ESX servers running ESX Server 3.0.x, but it appears that the referenced script is included with the agent when it is installed on the server.
Site Tags: Virtualization, VMware
Related Site Tags: ESX, Microsoft, Storage, Macintosh, Networking, Security, Linux, NetApp, Windows, Fusion, VDI, VMwareHA, HyperV, Citrix, iSCSI, Apple, NFS, Hardware, Interoperability, Xen, VLAN, VMotion, SAN, ActiveDirectory, Cisco, NAS, OSS, Snapshots, Solaris, Backup, Travel, Unix, BSD, CentOS, Kerberos, LDAP, ONTAP, SSH, RedHat, CLI, Exchange, HP, Snapshot, Blogging, IBM, IOS, Novell, P2V, Personal, Samba, SFTP, Standards, Telephony, Ubuntu, Vista, VMFS, VMwareSRM, VoIP, Wireless
This entry was posted on Wednesday, April 2nd, 2008 at 9:37 am and is filed under Virtualization. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
April 2nd, 2008 at 9:48 pm
ESX Server 3.0.x hosts in a VirtualCenter 2.5 Not Responding…
We have experienced a problem where after upgrading our Virtual Center to 2.5 and applying patches on 3.02 servers would not reconnect. We were at a loss at first. To remedy the problem we just went ahead and migrated the ESX servers to 3.5. After read…