Virtualization Pro

Jan 16 2008   8:42PM GMT

ESX 3.5: Configuring for HA errors



Posted by: Rick Vanover
Tags:
Rick Vanover
SQL
VI3
Virtualization
VMware ESX
VMware High Availability (VMware HA)

I recently upgraded to ESX 3.5 on a test system, and had an issue that was really stressing me out. The issue was that each time I would perform the “Reconfigure for HA” task, I had errors causing the task to fail and the new ESX host sits there with a red triangle like a car broken down on the side of the highway. The log message that runs in the Virtual Infrastructure Client was largely useless, so I jump into the VMware ESX database. For this situation, I have looked into the VPX_EVENT table and saw the following event:

Event_Type
vim.event.HostShortNameToIpFailedEvent

Host_Name
ESX-35-DEV-001.AMCS.TLD

This message gave me a starting point and I found that in my service console network configuration the DNS suffix order was not the same for all hosts. Specifically, I forgot one DNS suffix in the order and that name made sense to me:

DNS Configuration

Therfore, the takeaway is when building ESX servers, ensure the configuration for all hosts in a cluster (or datacenter) within Virtual Center have the correct configuration where relevant for DNS, subnet mask, interface naming, and storage configuration.

1  Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Akutz
    Great job Rick! Just to add a little bit to what Rick has already explained quite thoroughly, you can also edit the host files on the ESX server(s) in order to make this work (http://searchservervirtualization.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid94_gci1281218,00.html). The HA agent runs *on* the ESX server and despite appearances relies on VC for configuration, not to function. HA will work if the VC is down. This means that all of the DNS matching must function from the ESX server, and that is where it can be fixed.
    270 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: