Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Trouble Setting Up VMWare HA

Posted on 2008-06-22
7
Medium Priority
?
1,703 Views
Last Modified: 2012-06-27
So, my goal with this project is to set up a simple VMWare HA Cluster.  I am currently getting an error in Virtual Center on one of the hosts I have placed in my cluster (it has a small red triangle and exclamation mark) and in the event log says "Failed to Resolve Short Name [Name] to IP Address on Host [Public IP]"  I did make an attempt to set up a Virtual Machine, but, when I did that it seems as though the Virtual Machine is not able to establish an Internet connection.  I think something is wrong with my Networking setup.  

Here is the description of my setup:
1.  For my shared array, I am using an EMC Clariion AX150i (iSCSI)
2.  The storage array is connected to two separate switches, one for network 10.100.0.x and one for network 10.101.0.x
3.  Each host in my cluster is able to connect to the virtual drive on the disk array, and is already formatted with VMFS
4.  I have the following network setup for each host in VMWare:

a: vswitch0
a(i): VM Network
a(ii) Service Console ([Public IP])

b:vswitch1 (Note, this adapter is connected to a crossover cable, which is connected to by other ESX Host)
b(i):  VMKernel: 10.102.0.2 *Also configured as my VMotion adaptor/virtual switch

c:vswitch2
c(i) Vkernel2 (10.101.0.12)
c(ii) Service Console 2 (10.101.0.14)

d:vswitch3
d(i) Vkernel3 (10.100.0.12)
d(ii) Service Console 3 (10.100.0.14)


Please, please help me try to understand what I did wrong here and how to fix it.  I have been looking at this for a long time and am a bit frustrated, and really need some help.  I do not have a lot of experience with VMWare, and really want to get this working.  Please, Please!

Thanks in advance!
0
Comment
Question by:superfly18
  • 6
7 Comments
 
LVL 5

Accepted Solution

by:
HeinoSkov earned 2000 total points
ID: 21841531
Hi,

VMware HA is extremely dependent on name resolution. So you have 2 choices.

1. Use a DNS server and create a records for each of your ESX hosts. Also point the ESX hosts to use that name server

2. Use a hosts file on each ESX server and define the other ESX servers in the cluster.

Remember that ESX also is case sensitive. So create all your ESX server names with small letters and use small letters in either DNS or the hosts file.

DNS configuration is under Configuration / DNS

The hosts file is located under /etc/hosts in the service console.
0
 
LVL 1

Author Comment

by:superfly18
ID: 21841603
Is there anyway to configure the hosts in Virtual Center?  For some reason I can't seem to connect to the service console through ssh right now...
0
 
LVL 1

Author Comment

by:superfly18
ID: 21841655
All of the DNS Settings on the service console of vswitch0 seem proper (small letters, right dc's, right gatways, etc.)
0
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.

 
LVL 1

Author Comment

by:superfly18
ID: 21841727
It seems as though the DNS entries have not been created (e.g. the computer settings have not been established in my DC/Active Directory).  

Below is the hosts file that is currently installed on server 1:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
[public ip 1]          name1.nod.com name1

Here is the hosts file that is currently installed on server 2:
 Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
[public ip 2]           name2.nod.com name2

I assume what you are suggesting is to copy name2 to the server 1 file, and name 1 to the server 2 file (e.g. copy entries from one file to another?  If I do that do I need to restart the ESX Servers?

Please let me know
0
 
LVL 1

Author Comment

by:superfly18
ID: 21841781
Ok!  I made that entry, and now I have no more red x next to my cluster. :-) :-)  However, I still have the issue with the virtual machine, as it seems as though that vm cannot access the network.  Additionally though I should mention that when I look at the 'map' diagram from my VM it shows both of the IP addresses from either cluster host with big red x's in front of them.  On the virtual machine, I am still unable to ping anything (e.g. www.google.com) even though the network.interfaces on the virtual machine looks fine.  
0
 
LVL 1

Author Comment

by:superfly18
ID: 21841845
Just another quick update:  I changed the network on the virtual guest to 'Virtual Machine Network'.  Now on my map I have one host with a green dot, and one with a red x (instead of two red x's).  However, I still am unable to ping anything (e.g. www.google.com) from the virtual guest itself.  I think this is the last bit to figure out, and then I'm finally done!  Please help!
0
 
LVL 1

Author Comment

by:superfly18
ID: 21850388
The issue that I had was related to two things (1) configuration of the Service Console gateway; and (2) configuration of my virtual switches.   HeinoSkov's answer definately got me pointed in the right direction, and I owe him a LOT of thanks!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

879 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question