An administrator would like to configure vSphere HA to use two isolation addresses.
How would this affect the behavior of HA?
A.
If both isolation addresses are not reachable, the host will be restarted by the HA agent.
B.
If both isolation addresses are not reachable, the host will use the vCenter Server IP address as a final
isolation address before being marked isolated.
C.
If only one of the isolation addresses is reachable, the host will not be marked isolated by HA.
D.
If only one of the isolation addresses is reachable, the host will be considered in an isolated by HA.
Haven’t found this in any documentation but A and B are both nonsense.
C seems to be correct more likely (to ensure that host is really isolated and not just ping dst gone down)
D would be more aggressive behaviour but not completely useless (you absolutely need access to both networks)
C – Isolation addresses are checked to test if the host’s networking is working when the slave host doesn’t hear heartbeats from a Master host. Only one needs to work for it to know that it’s network is working. The point in multiple isolation addresses is to provide redundancy in case one fails.
Well, if you have multiple isolation adresses, i.e. your iscsi storage switch and your normal default GW, you still might have troubles, bút your host isn’t fully isolated.
I think the point in using multiple isolation adresses is to determine if a host is really cut-off from everything, for example a host that only has uplinks to one physical switch and this switch fails.
Nevetheless I would go for C also.
I believe it’s C
B is wrong
If both isolation addresses are not reachable, the host will use the default Gateway IP address as a final isolation address before being marked isolated.
das.usedefaultisolationaddress
By default, vSphere HA uses the default gateway of the console network as an isolation address. This attribute specifies whether or not this default is used (true|false).