We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

VMware HA AAM error

8r0k3n71nX
8r0k3n71nX asked
on
Medium Priority
3,295 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
Comment
Watch Question

Senior IT Advisor
CERTIFIED EXPERT
Top Expert 2008
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Paul SolovyovskySenior IT Advisor
CERTIFIED EXPERT
Top Expert 2008

Commented:
Please post the exact error, this should help in troubleshooting

Author

Commented:
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.
Paul SolovyovskySenior IT Advisor
CERTIFIED EXPERT
Top Expert 2008
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Look at my post about the FT_HOSTS file not being updated for an additional solution.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.