Solved

VMware HA AAM error

Posted on 2009-07-07
5
3,278 Views
Last Modified: 2012-05-07
I am running into a problem. I have recently changed the IP configuration on my 2 ESX servers and vCenter. I am trying to re-enable HA and it fails after about 3 hours. The error is an INTERNAL AAM ERROR - agent could not start.

I have performed/checked the following:

DNS is functioning properly and the records are correct
Hosts file on both ESX servers are correct
Hosts file on vCenter even edited appropriately
Removed each host from the cluster and added back
AAM IS installed and running on both hosts
Pinging from both ESX and all guests works with IP, Name, and FQDN
Can ping gateway from all hosts and guests
All hosts and guests on same subent
licensing is correct
0
Comment
Question by:8r0k3n71nX
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 42

Accepted Solution

by:
paulsolov earned 250 total points
ID: 24800584
Did you change the ip address on your hosts from the service console you were modifying or from a different service console?

Changing the DNS server settings
 
Check DNS server settings, update the nameserver IPs and search domain the /etc/resolv.conf file.
 

Note: Disable VMware High Availability if you do not want virtual machines to failover during the hostname IP change.


To change the default gateway, click the Routing tab and enter the appropriate value.
Update the etc/opt/vmware/vpxa/vpxa.cfg file to reflect the new settings.
Reboot the ESX host for the changes to take place

Also check

* /etc/hosts
* /etc/sysconfig/network
* /usr/lib/vmware-mui/apache/conf/httpd.conf

0
 
LVL 42

Expert Comment

by:paulsolov
ID: 24800601
Please post the exact error, this should help in troubleshooting
0
 

Author Comment

by:8r0k3n71nX
ID: 24804438
When the IP changes were made, I changed them on the ESX from a rack console (local). The IP change for vCenter was done within vCenter. All of the files above were correct.

I was however able to get it fixed this morning. When looking for the FT_HOSTS file from the path that I was searching, the directory was invalid. Manually navigating to /etc/opt/vmware/aam and looked at the FT_HOSTS file. Sure enough, the file contained both the new and old IP addresses. IMO, it appears that the agent only looks for the first IP  address of the LAN side and then the first IP of the iSCSI and does not look at the additional IP addresses. OR that the error is generated because of the first IP is bombing out and the second (correct IP) doesn't matter. I backed up the FT_HOSTS file and removed the old IP information and it worked. I even contacted my vendor and they did not even know about this file being the possible issue.
0
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 250 total points
ID: 24804963
I've had to do that before as well but it is normally removed when removing HA from the cluster.  Another issue that may arise is an issue with the vcp.cfg file

/etc/opt/vmware/vpxa/vpxa.cfg

to change above you may need to remove host from VC, rename vpxa.cfg and add back in to create new file
0
 

Author Closing Comment

by:8r0k3n71nX
ID: 31600943
Look at my post about the FT_HOSTS file not being updated for an additional solution.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question