Changed IP on ESX, HA fail

[peaj]

Hello

Hope this is correct forum.

Running 3 ESX 3.5 servers in a cluster with shared storage on SAN. My network department wanted me to change the VLAN of the ESX server. So I chnged the IP adress of the ESX server, using this guide: <![endif]><![if gte mso 9]>[http://www.vladan.fr/how-to-change-ip-address-of-the-esx-server-console/]

I then changed the VLAN on the port. Before the ESX server had IP 156.52.X.X

Now it have 10.1.2.X

Removed the ESX servers from Virtual Client, and added them. So far so good. But when trying to enable HA, I get error: Insufficient resources to satisfy HA failover. Unable to contact a primary HA agent in cluster.

I'm sure this have to do with the fact that I changed the IP on the ESX Server, but I'am not sure to fix this HA error. In Ifrastructure Client, on ESX Config tab, I can see the new "Service Console" port with the new IP of the ESX server. I this this Serice Console port is placed under wrong vmnic, because vmnic0/vSwitch0 is not right VLAN for this IP. Correct VLAN for this IP vminc4/vSwitch5. Is I on the track here? And what do I do to correct it ??

Below see screencaptures from Network config from my Virtual Client:

Glad for all help in this case..!!

Best regards

Oyvind

[AntonVZhbankov]

Disable admission control, reconfigure for HA all servers and enable admission control back.

Also check HA Runtime Info.

---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

[peaj]

Tested with setting Admission Control to 'Allow VMs to be powered on even..' but no changes.

[AntonVZhbankov]

Can you run vmkping on both hosts to check if there is connectivity between ESXes?

---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

[prudhviraj]

Keep the service console that you use to manage the ESX server and remove the unwanted service console. You remove the service console by entering into properties of the vswif. (Note: This may result in loosing remote connectivity to the ESX server so make sure you have the alternative service console is working properly.)

Make sure to apply the same changes in the DNS also.

Regarding the HA issue make sure all the ESX servers are able to perform the name lookup correctly b/w each other.

[jfelinski]

I'll start with name resolution and connectivity tests.

1. can you resolve short and fqdn name of the server from other Cluster mebers and other members from the server?

2. try vmkping to test connectivity from and to the host

---

MCSA+S, VCP3, VCP4

[Troy_Clavell]

one final thing if it hasn't been done. Check to ensure your FT_HOSTS file has the correct Host names and IP's

/etc/opt/vmware/aam

[peaj]

Hello guys..!!

Think we are on track in this case. Doing a vmkping from one of the host, indicate that it is trying to reach the hosts on the old IP. How to correct this ?? Is the last post from Troy the answer?

I'm not good at Linux. I logged in at one of the host using Putty. Typed: nano /etc/opt/vmware/aam but no file to edit.

[jfelinski]

Hi peaj,

You have a problem with name resoultion on your hosts. It might be casued by either local hosts file enty or misconfiguration on dns. Check following

• any old entries in local hosts file /etc/hosts

• dns configuration onhosts

Cheers

---

MCSAS,CompTIA Security, VCP

[peaj]

Ok. Logged on with Putty on one the host (vm01-1). Changed the hosts info and saved the file. When I try do to a Vmkping to my-self (vm01-1), I do not get any answer. But when I do a regulary ping I get answer....

[jfelinski]

You've been saying about changing IP for one of the Servers only. Do you have a proper gateway configured on vmKernel interface and is there a proper routing between those two networks (old vmkernel range/new vmkernel range)?

You should be using vmkping to ping VMKERNEL ip addresses of other hosts and ping to ping service console addresses, doing vmkping NAME will not work if there is no routing between vmkernel/sc networks.

---

MCSAS,CompTIA Security, VCP

[peaj]

Ok, sorry if I have not make myself clear in this case. But the issue is that my network department wanted me to change the IP adress of all the 3 ESX hosts we have. The 3 hosts:

vm01-1, had IP 156.52.19.X, should now have 10.1.2.X

vm01-2, had IP 156.52.19.X, should now have 10.1.2.X

vm01-3, had IP 156.52.19.X, should now have 10.1.2.X

I have done this guide:

Maybee I have done wrong here? Have I only changed the IP of the 'Service Console', and not the actually IP of the host ??

Yes, I have a valid Gateway that is 10.1.0.1

[jfelinski]

So in this case for proper HA configuration you need to check following:

1. SC network ping on both name ip from any host to all other ones

example. from vm01-1

ping vm02-2

ping vm02-2.domainname

ping 10.1.2.X (ip address of vm-02-2)

2. from vCenter server ping SC domain names and ip's of all other hosts

example from vCenter

ping vm01-1

ping vm01-1.domainname

ping 10.1.2.X (ip of vm01-1)

this should be enough to make HA work. Generally 90% of problems with it ends up in wrong name resolution, so make sure it is all correct.

---

MCSAS,CompTIA Security, VCP

[peaj]

I have now done all pinging as you asked me to do. Everything answers OK.

All the hosts file looks the same now:

10.1.2.201 vm01-1.frstad.local

10.1.2.202 vm01-2.frstad.local

10.1.2.203 vm01-3.frstad.local

What is strange, is that enabling HA on vm01-1 now is working, but fails in vm01-2 and vm01-3

[jfelinski]

Try to remove AAM agent before trying again. On affected hosts execute /opt/vmware/aam/bin/VMware-aam-ha-uninstall.sh , if it will still fail after that, review logfies in

/var/log/vmware/aam directory

---

MCSAS,CompTIA Security, VCP

http://wirtualizacja.wordpress.com

[peaj]

Now I'm not able to right-click on a VM server in Infrastructure Client, and do a 'Open Console'.... strange.

Fail to uninstall AAM:

# /opt/vmware/aam/bin/VMware-aam-ha-uninstall.sh

/opt/vmware/aam/bin/VMware-aam-ha-uninstall.sh: line 28: /sbin/backup.sh: No such file or directory

#

[peaj]

Here is a screendump when trying to open console on a VM

[jfelinski]

if you ping vm01-1.frstad.local from the box you have this error, does it give you the new ip?

---

MCSAS,CompTIA Security, VCP

[peaj]

If a ping the host from the VM adm14, it reply when pinging the IP, but not when pinging the name. DNS issue? But doing ping on the IP on VM01-1 from my local computer does not work... I get confusing now.

[jfelinski]

I'm afraid you still have name resolution issue. Start with troubleshooting local hosts files (on windows C:\Windows\System32\drivers\etc\hosts ) and DNS configuration. This must be accurate, you can also try to clear up local and server DNS cached entries. (Locally ipconfig /flushdns)

---

MCSA+S, VCP 3, VCP 4