Support > Knowledge Base

Knowledge Base

Search the Knowledge Base:

Guided Search

Products:

Search In:

ESX Server 3.0.x hosts managed by VirtualCenter 2.5 may not respond after applying ESX Server patches

Symptoms

ESX Server 3.0.x hosts in a VirtualCenter 2.5 environment enter a not responding state after applying certain ESX Server patches.

Resolution

Overview

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.

Workaround

For ESX 3.0.1, KB 1004182 provides a fix to the workaround, and for ESX 3.0.2, KB 1004211 provides a fix to the workaround.

After applying an ESX Server patch that includes a Host Agent update:

Log in to the ESX Server service console as root.
Type service vmware-vpxa stop and press Enter.
Type /opt/vmware/vpxa/vpx/init_vpxa.sh and press Enter.
Note: This command automatically starts vpxa after fixing the Host Agent (hostd) configuration. After a few moments, the host recovers from the not responding state.

Note: It is not necessary to manually uninstall and reinstall the VirtualCenter Agent RPM on the host.

Feedback

Actions

KB Article: 1004137
Updated: Aug 14, 2009

Products:
VMware ESX
VMware VirtualCenter
Product Versions:
VMware ESX 3.0.x
VMware VirtualCenter 2.5.x

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)