VMware Cloud Community
infinitiguy
Contributor
Contributor
‎06-09-2008 12:20 PM

HA problems with 3.5.1 and vc 2.5.1

I'll start by saying.. HA used to work Smiley Happy

What I have is two hosts. Each runs about half its load and the plan is if one were to fail the other takes on the load. Simple.

Problem is somewhere along my upgrade path, something got screwed and now HA will not re-configure. I constantly get the "HA agent on amer-esx1.fqdn.com in cluster Production in Waltham(datacenter) has an error.

I get this on both hosts. I can ping from each host to the other host, I made entries in the /etc/hosts just to make sure although pinging back and forth was working before. I then started to think it may have been a 3.0.1/3.5 issue because I tried it again after upgrading one of my hosts but it still happens. I enabled HA again after everything was upgraded and I got the same error as well as a insufficient resources error.

Are there any HA logs in 3.5.1 that may tell me exactly what is going on? Nothing else has really changed in terms of netowrking etc and I sure am running out of ideas Smiley Happy

Reply
0 Kudos
4 Replies
kjb007
Immortal
Immortal
‎06-09-2008 12:58 PM

The agent may not have upgraded or installed properly. Remove the host from your cluster, and then add it back in. Restart hostd on the server, 'service mgmt-vmware restart'. Disconnect/reconnect the host in virtual center.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
infinitiguy
Contributor
Contributor
‎06-09-2008 01:01 PM

is there any danger in doing so? Will removing my host from the cluster cause any effect on my virtual machines? Will running service mgmt-vmware restart cause my virtual machines to reboot? Should I treat this as a software upgrade and migrate all my machines off.. follow this procedure on one box.. move all machines back to that box.. and then repeat?

Reply
0 Kudos
kjb007
Immortal
Immortal
‎06-09-2008 07:02 PM

There was a bug in previous versions of esx that would cause your virtual machines to restart, if you had automatic shutdown/restart enabled in the esx configuration startup/shutdown section. If you did not go in and enable that, then you should be fine, but move vm's off to add to the comfort level. Removing the host from the cluster takes that cluster's resources out of the pool, and as long as there is a host still in the cluster, and the cluster is in tact, it should not have any other effect.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
TomHowarth
Leadership
Leadership
‎06-10-2008 11:24 PM

Thread moved to the VI: ESX 3.5 forum

Tom Howarth

VMware Communities User Moderator

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
Reply
0 Kudos