• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

VMWARE ESX 4.1 HA Error

Hi

We are getting the below error message in our VM envirinment. There are 13 ESX 4.1 hosts are there in a cluster. Out of 13, we are receiving this error in 11 ESX hosts.

HA agent has an error : cmd addnode failed for
primary node: Internal AAM Error - agent could
not start. : Unknown HA error
error
Reconfigure HA host

Please help me out to resolve this issue

Regards,
VL
0
valuelabs97
Asked:
valuelabs97
  • 3
  • 2
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you tried reconfiguring a node?
0
 
larry urbanDevOps EngineerCommented:
try restarting the HA agent on the 11 ESXi servers. (turn off HA, turn HA back on)
0
 
valuelabs97Author Commented:
Hi All

Those are production servers:

@hanccocka: How can I reconfigure. can you give me step by steps
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Click the Host and Click Reconfigure.
0
 
valuelabs97Author Commented:
Hi All

Its a nework issue, we resolved it. Thank for your comments

0
 
valuelabs97Author Commented:
We found that, there is a network issue in th enetwork due to that, HA is not worked
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now