Home > Ask the Server Virtualization Experts > VMware Questions & Answers > Misconfigured HA agent troubleshooting
Ask The Server Virtualization Expert: Questions & Answers
EMAIL THIS

Misconfigured HA agent troubleshooting

Andrew Kutz EXPERT RESPONSE FROM: Andrew Kutz

Pose a Question
Other Server Virtualization Categories
Meet all Server Virtualization Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 07 November 2007
VirtualCenter keeps telling me that the HA agent is misconfigured on two of my ESX servers. What is wrong?

>
EXPERT RESPONSE

Well, the first thing to try in these instances is reconfiguring the HA agent by right-clicking on the ESX host in VirtualCenter and clicking "Reconfigure HA." If this doesn't work, try removing the ESX servers from VirtualCenter and then re-adding them. If this still doesn't work, from what I have seen you have two options: 1) reinstall ESX, or 2) stop fearing text mode and learning to love the console!

The reason options 1 or 2 are necessary is because you most likely entered the wrong host name when configuring the server upon installation. I have done this myself. If you check the Tasks and Events log repository for the ESX server that is throwing the HA error "hostipaddrsdiffer:cmd remove failed ft_guesthostbyname and hostname - i return different addresses 192.168.0.40 and 192.168.0.41". This error is occurring because the 'hostname' returns the incorrect host name which appears to then be used by 'ft_gethostbyname' to get the internet protocol (IP) address from one of the ESX server's domain name service (DNS) servers. However, the IP address returned does not match the IP address the ESX server is configured with. This causes HA to be misconfigured, hence the warning.

The solution is to change the host name of the ESX server to the correct value. This value has to be set in three files: P>/etc/hosts
/etc/sysconfig/network
/etc/vmware/esx.conf

Replace all instances of the incorrect host name with the correct value, reboot the server, and presto, no more HA warnings. One caveat, if you have configured iSCSI adapters then you may need to reconfigure them since the initiator name that is created is created with the host name of the server.

Hope this helps!


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   





Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



More Expert Analysis on Virtual Machines and Integrating Virtualization
HomeNewsTopicsITKnowledge ExchangeTipsBlogsAsk the ExpertsMultimediaWhite PapersEvents
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts