VMware Cloud Community
AneetuPrakash
Contributor
Contributor
Jump to solution

HA Config error - esx 4 system

Hi communities,

Getting the following error on a couple of my esx 4.1 hosts in a couple - others are ok

When i configure HA - the following error appears after a few moments:

"cmd addnode failed for primary node:error creating ramdisk for HA agent configuration,:unknown HA error"

Any help appreciated

Reply
0 Kudos
1 Solution

Accepted Solutions
JCMorrissey
Expert
Expert
Jump to solution

Np's Aneetu, glad the re-join worked - the other pieces can be messier to fix

Please consider marking as "helpful", if you find this post useful. Thanks!... http://johncmorrissey.wordpress.com/

View solution in original post

Reply
0 Kudos
4 Replies
JCMorrissey
Expert
Expert
Jump to solution


Hi,

Few ways to fix this


SSH to server and run: (technical support mode)

service mgmt-vmware stop

service vmware-aam stop

service vmware-vpxa stop


Rejoin the host back to vCenter - it should reinstall the agents.  

Stopping servics see:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100349...


Worse case scenario:

Right-click on the ESXi host and click Disconnect.  This disconnects the ESXi host from the VirtualCenter Inventory.

Log in to ESXi Troubleshooting Mode.  For more information, see Tech Support Mode for Emergency Support (1003677).

Uninstall the vpxa and aam components from the VMware ESXi host using the following commands:


/opt/vmware/uninstallers/VMware-vpxa-uninstall.sh


/opt/vmware/uninstallers/VMware-aam-ha-uninstall.sh

  
Right-click on the ESXi host and click Connect. This initiates a re-install of the vpxa agent. 

Add the host to the appropriate cluster. This initiates a re-install of the aam agent.


Rejoin to cluster.

Please consider marking as "helpful", if you find this post useful. Thanks!... http://johncmorrissey.wordpress.com/
AneetuPrakash
Contributor
Contributor
Jump to solution

Thanks you JC i will check this on my hosts

Reply
0 Kudos
AneetuPrakash
Contributor
Contributor
Jump to solution

Thank you JC removing from vcenter and re-joining helped resolve the problem

Reply
0 Kudos
JCMorrissey
Expert
Expert
Jump to solution

Np's Aneetu, glad the re-join worked - the other pieces can be messier to fix

Please consider marking as "helpful", if you find this post useful. Thanks!... http://johncmorrissey.wordpress.com/
Reply
0 Kudos