Vmware – Error while configuring HA

Posted: June 4, 2010 in VMware

Error : Got the following error while configuring HA on 2 ESX Cluster.

  • HA agent configuration errors on ESX hosts:
    • Failed to connect to host
    • Failed to install the VirtualCenter agent
    • cmd addnode failed for primary node: Internal AAM Error – agent could not start
    • cmd addnode failed for primary node:/opt/vmware/aam/bin/ft_startup failed
  • Solution :

    It could be for several Reason Like below.

  • Check the release notes for current releases to see if the problem has been resolved in a bug fix. See the Documentation page for vSphere 4 or VMware Infrastructure 3.

  • Verify that there are enough licenses to configure VMware HA. For more information, see Verifying that the feature is licensed (1003692).
  • Verify that name resolution is correctly configured on the ESX Server. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).

  • Verify that name resolution is correctly configured on the vCenter Server. For more information, see Configuring name resolution for VMware VirtualCenter (1003713).

  • Verify that the time is correct on all ESX Servers with the date command. For more information on setting up time synchronization with ESX Server, see Installing and Configuring NTP on VMware ESX Server (1339).

  • Verify that network connectivity exists from the VirtualCenter Server to the ESX Server. For more information, see Testing network connectivity with the Ping command (1003486).

  • Verify that network connectivity exists from the ESX Server to the isolation response address. For more information, see Testing network connectivity with the Ping command (1003486).

  • Verify that all of the required network ports are open. For more information, see Testing port connectivity with the Telnet command (1003487).

  • Determine if there is a cluster resource issue. For more information, see Advanced Configuration options for VMware High Availability (1006421).

  • Verify that the correct version of the VirtualCenter agent service is installed. For more information on determining agent versions and how to manually uninstall and reinstall the HA agents on an ESX host, see Verifying and reinstalling the correct version of VMware VirtualCenter Server agent (1003714).

  • Verify the VirtualCenter Server Service has been restarted. To restart the VirtualCenter Server Service, see Stopping, starting, or restarting the vCenter Server service (1003895).
  • Verify that VMware HA is only attempting to configure on one Service Console. For more information, see VMware High Availability configuration issues when an iSCSI Service Console is on the same network (1003789).

  • Verify that the VMware HA cluster is not corrupted. To do this you need to create another cluster as a test. For more information, see Recreating VMware High Availability Cluster (1003715).
  • Verify that that UDP 8043 packets used for the HA backbone communications are not dropped between the ESX hosts. For more information see HA fails to configure after task passes 90% “Internal AAM Error – agent could not start” (1018217).
  • Ensure that the ESXi host userworld swap option is enabled. For more information see ESXi hosts without swap enabled cannot be added to a VMware High Availability Cluster (1004177).
  • My one was with Time configuration Mismatch beetween two esx.

    Follow my following Blog to set time and zone correctly.

    https://ashraf9719.wordpress.com/2010/05/31/redhat-changing-timezone/

    Advertisements
    Comments
    1. luga says:

      Great post!!

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s