Solved

vSphere and the isolation adress

Posted on 2010-11-29
6
1,748 Views
Last Modified: 2012-05-10
We had network problems yesterday and our 2 host ESX cluster couldn't see the default gateway, so (this is what i think anyway) HA was activated and things got in a right state. The gateway was down for a while and and we then couldn't start VMs due to "insufficient resources to satisfy configured failover level for HA."

Why does vSphere activate HA when it can't see the default gateway, I guess there's some logic behind but i can't figure out why?   That's the question.

Cheers
0
Comment
Question by:kswan_expert
6 Comments
 
LVL 14

Accepted Solution

by:
Deepak Kosaraju earned 300 total points
ID: 34233718
To avoid this, you create an advanced parameter by clicking the advanced tab in HA settings and then enter das.isolationaddress and set the value to a pingable IP address you deem fit to serve as the IP address used by the HA cluster to determine whether or not the host has become isolated from the network.  YOu then create another parameter call das.usedefaultisolationaddress and set a value of FALSE.  You can a couple of IPs using this method, but if you do you should also increase the timeout value, this is das.failuredetectiontime, the default is 15 seconds, increase it to 30 seconds when more than 1 isolation address is used.  Refer to your ESX 3.5 resource management pdf, I've attached it for you.
0
 

Author Comment

by:kswan_expert
ID: 34233996
Cheers for speedy reply!   We've set "dasiolation host = false" for the Cluster HA which apparently should fix the problem.  
We've made this change but are still wondering why HA is activated if it can't see the GW??
There's obviously some reason\logic behind it and now that we've disabled the feature will it have unexpected consequnces??


0
 
LVL 3

Assisted Solution

by:Virtalicious
Virtalicious earned 100 total points
ID: 34234340
The underlying reason is that the guests may be in a dual brained mode in which it tries to run on multiple machines.  It engages HA to take ownership and ensure the guest is only run in one location.

The Theory being that although network is compromised the SAN may not be.

-Virt
0
Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

 
LVL 5

Expert Comment

by:ianmellor
ID: 34248000
Hi kswan_expert,

HA will only try and contact the default gateway if it is unable to communicate with the other hosts. This is it's isolation check. You can change the address it checks for isolation but if the gateway goes down HA won't start, your host have to lose connection to each other.

Hope this helps.  
0
 

Author Comment

by:kswan_expert
ID: 34254414
Cheers guys, humour me here but Vmware have set me wrong so I want to be 100% we get this right.

We set the HA advanced option to "dasiolation host = false"  as advised by a Vmware tech but this ain't worked!  We lost access to the GW again last night, HA failed on a host wouldn't restart and we received the message "Host ******* could not reach isolation address: #.#.#.#"

So, if i set the following for HA advanced options will it fix our probs

das.usedefaultisolationaddress = false


Do we have to set  a value for “dasiolation host” what happens if we don’t?  What do people usually use for these values.  I was thinking of using a local physical 2003 DC and a physical  file server that it pretty much never rebooted.
0
 
LVL 5

Assisted Solution

by:ianmellor
ianmellor earned 100 total points
ID: 34255283
Hi,

I have never seen the advanced option "dasiolation host = false" , I think you mean the below setting.

das.usedefaultisolationaddress = <value>

This option/value pair disables the use of the default gateway as an isolation address, where <value> is either true or false. By default this value is set to true. This parameter is generally used in conjunction with the das.isolationaddress1 to das.isolationaddress10 parameter(s) listed below.

das.isolationaddress1 to das.isolationaddress10 = <value>

These option/value pair(s) specify more than one alternate isolation address for VMware HA to use, where <value> represents the IP address to be used for isolation detection. When using more than one isolation address it is recommended that the das.failuredetectiontime parameter be increased to ensure proper failover detection can occur. Also, although up to 10 different isolation addresses can be specified one or two addresses should be sufficient for proper failover detection

das.failuredetectiontime = <value>

This option/value pair changes the default failure detection timeout, where <value> represents the failure time in milliseconds. VMware HA uses this timeout in declaring an isolation response, and does not declare a host as isolated until this timeout has been reached without any heartbeats received. By default the default failure detection time is 15 seconds (15000 ms). However, another common alternative is 60 seconds (60000 ms).

Hope this helps you.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Error upgrading from esxi 5.5 to 6.5 15 200
Remove Disconnected ESX Hosts 3 56
host cache 3 53
Remove VEEAM BACKUP TEMPORARY SNAPSHOT 8 55
HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

860 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