Raj2796's Blog

December 15, 2010

Configuring VMware High Availability fails with the error: Cannot complete the configuration of the HA agent on the host

Filed under: ha,vmware — raj2796 @ 4:40 pm

Symptoms
Configuring VMware High Availability (HA) fails
The vSphere Client may show one service console, however running the esxcfg-vswif -l command while logged into the ESX service console, reveals additional service consoles
You see the messages:
Cannot complete the configuration of the HA agent on the host. See the task details for additional information.
Misconfiguration in the host network setup
Resolution
This issue occurs if all the hosts in the cluster do not share the same service console or management network configurations. Some hosts may have service consoles using a different name or may have more service consoles than other hosts.

Address the network configuration differences between the hosts if you are going to use the Shut Down or Power Off isolation responses because these options trigger a VMware HA isolation in the event of Service Console or Management Network failures.

If you are using the Leave VM Powered on isolation response, the option to ignore these messages is available in VMware VirtualCenter 2.5 Update 3.

To configure VirtualCenter to ignore these messages, set the advanced option das.bypassNetCompatCheck to true:

Note: When using the das.bypassNetCompatCheck option, the heartbeat mechanism during configuration used in VirtualCenter 2.5 only pairs symmetric IP addresses within subnets across nodes. For example, in a two node cluster, if host A has vSwif0 “Service Console” 10.10.1.x 255.255.255.0 and vSwif1 “Service Console 2” 10.10.5.x and host B has vSwif0 “Service Console” 10.10.2.x 255.255.255.0 and vSwif1 “Service Console 2” 10.10.5.x, the heartbeats only happen on vSwif1. Starting in vCenter Server 4.0, they can be paired across subnets if pings are allowed across the subnets. However, VMware recommends having them within subnets.
Right-click the cluster, then click Edit Settings.
Deselect Turn on VMware HA.
Wait for all the hosts in the cluster to unconfigure HA.
Right-click the cluster, and choose Edit Settings.
Select Turn on Vmware HA, then select VMware HA from the left pane.
Select Advanced options.
Add the option das.bypassNetCompatCheck with the value True.
Click OK on the Advanced Options screen, then click OK again to accept the cluster setting changes.
Wait for all the ESX hosts in the cluster to reconfigure for HA.

From http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1019200

Advertisements

September 11, 2009

Vmware HA

Filed under: ha — raj2796 @ 10:43 am

Whilst looking for an explantation on why HA seems to fail at random on my Vmware servers post reboots i found this nice explantation ! What i like most is that it confirms my theory of active primary ha servers, thus reinforcing my long held suspicion that I’m a genius and everyone else is stupid 🙂

Vmware HA

most usefull part of article:

das.ignoreRedundantNetWarning – Remove the error icon/message from your vCenter when you don’t have a redundant Service Console connection. Default value is “false”, setting it to “true” will disable the warning.

http://www.yellow-bricks.com/vmware-high-availability-deepdiv/

Create a free website or blog at WordPress.com.