VMware
 

Knowledge Base

Search the Knowledge Base:

Products:
Search In:
 

Verifying and reinstalling the correct version of the VirtualCenter Server agents

Symptoms

  • Configuring VMware High Availability (HA) fails
  • If you try to configure VMware HA, you see the error:

    Could not Enable aam firewall ruleset :vim.fault.HostConfigFault

  • You cannot connect an ESX host to VirtualCenter
  • If you try to connect an ESX host to VirtualCenter, you see the error:

    unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem

  • The hostd.log file contains the entry: 

    [2008-05-26 10:45:51.463 'Vmomi' 15752112 info] Throw vim.fault.AlreadyExists
    [2008-05-26 10:45:51.463 'Vmomi' 15752112 info] Result:
    (vim.fault.AlreadyExists) {
       name = "vpxuser"
       msg = ""
    }

Purpose

This article helps you determine the version of the VirtualCenter agent that is installed on an ESX host, and provides steps to reinstall the VMware HA and vpxa agents if the version is incorrect.

Resolution

Note: Proceed directly to Reinstalling the agents if you see the following error when you try to connect an ESX host to VirtualCenter:
 
unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem.

Verifying that the correct version of VirtualCenter is installed

To verify that the correct version of VirtualCenter is installed:
  1. To determine the version and build number of your VirtualCenter installation, click Help > About from within VirtualCenter.
  2. Right-click on the ESX host and click Disconnect to disconnect the ESX host from VirtualCenter.
  3. Log in as root to the ESX host using an SSH client.
  4. Run the following command to determine the version of the VirtualCenter agent (vpxa) that is installed:

    [root@esx-server /]# rpm -qa | grep vpxa

    The output appears similar to:

    VMware-vpxa-2.5.0-64192

  5. Ensure that the output matches the information from step 1. If the versions do not match, reinstall the agents.

Reinstalling the agents

  1. Disconnect the ESX host in VirtualCenter. Right-click the host and click Disconnect.
  2. Log in as root to the ESX host using an SSH client.
  3. Paste the following string of commands into the SSH session:

    service mgmt-vmware stop && service vmware-vpxa stop && service vmware-vmkauthd stop && service xinetd restart && rpm -qa | grep -i vpxa | awk '{print $1}' | xargs rpm -ef $1 && userdel vpxuser && rpm -qa | grep -i aam | awk '{print $1}' | xargs rpm -ef $1 && service mgmt-vmware start && service vmware-vmkauthd start

    Note: This is a concatenated list of commands strung together with the "&&" operator. This is useful in stringing together multiple commands as the next command does not start until the previous one has completed successfully.

    Here is a description of the commands:
    • The service mgmt-vmware stop && service vmware-vpxa stop && service vmware-vmkauthd stop && service xinetd restart command stops the management services for the service console.
    • The rpm -qa | grep -i vpxa | awk '{print $1}' | xargs rpm -ef $1 command removes the vpxa agent.
    • The userdel vpxuser command removes the vpxa user that gets installed once you connect the host to VirtualCenter.
    • The rpm -qa | grep -i aam | awk '{print $1}' | xargs rpm -ef $1 command removes the AAM RPM (HA) which gets reinstalled when you configure HA.
    • The service mgmt-vmware start && service vmware-vmkauthd start command following restarts the services.
    • The vmware-cmd -l command lets you know when hostd is up and running so you can reattach it to VirtualCenter.

      Note: When you see a list of virtual machines output, the command sequence is complete.


  4. Log in to the VirtualCenter Server u sing VMware Infrastructure (VI) Client.
  5. Choose the ESX host from the inventory list.
  6. Right-click on the ESX host and click Connect. This step initiates a re-install of the agent. 

To reinstall the VMware HA components on vCenter 2.5.x and vCenter 4.0.x:

  1. Remove the ESX Server from VirtualCenter Inventory.
  2. Log in as root to the ESX Server service console.
  3. Type rpm -qa | grep -i aam
  4. This returns two packages that are named similar to VMware-aam-haa-#.#.#-# and VMware-aam-vcint-#.#.#-#
  5. Remove these packages using rpm -e followed by the name of one of the returned packages. Repeat for both files.
  6. Type rpm -qa | grep -i vpxa. A package named VMware-vpxa-#.#.#-##### is returned.
  7. Remove this package using rpm -e followed by the name of one of the returned packages.
  8. Test adding the host to the newly created cluster to see if this has resolved the issue. 

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (16 Ratings)   

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)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (16 Ratings)   
Actions