VMWare host IP isolation issue ?
Hi all,
All in a sudden, two of my ESXi 5.1u3 hosts in the DRS cluster of 4 reported:
Host Isolation IP not available
Time: 15/05/2016 4:42:37 PM
Details: Fired by event: HostIsolationIpPingFailedE
Event description: vSphere HA agent on host PRODESXi03.domain.com in cluster Production in Primary DataCentre site.
Why is that happening and what's the fox of this issue ?
I don't have the capacity to failover the VMs to run in just two hosts.
All in a sudden, two of my ESXi 5.1u3 hosts in the DRS cluster of 4 reported:
Host Isolation IP not available
Time: 15/05/2016 4:42:37 PM
Details: Fired by event: HostIsolationIpPingFailedE
Event description: vSphere HA agent on host PRODESXi03.domain.com in cluster Production in Primary DataCentre site.
Why is that happening and what's the fox of this issue ?
I don't have the capacity to failover the VMs to run in just two hosts.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I wonder if this is caused by the network maintenance in the head office. But then it would happens to all of my ESXi hosts rather than this two ESXi servers on the DRS cluster.
depends how they've been configured. possibly.
is the fault still present, or now cleared ?
is the fault still present, or now cleared ?
ASKER
I think it is doing fine now:
But how to prevent that issue happening again ?
All vSphere HA isolation addresses are reachable by host
info
15/05/2016 4:23:57 PM
PRODESXi03.domain.com
The vSphere HA availability state of this host has changed to Election
info
15/05/2016 4:24:00 PM
PRODESXi03.domain.com
The vSphere HA availability state of this host has changed to Slave
info
15/05/2016 4:24:01 PM
PRODESXi03.domain.com
vSphere HA agent is healthy
info
15/05/2016 4:24:01 PM
PRODESXi03.domain.comBut how to prevent that issue happening again ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Andrew, the Default Gateway IP value is always there in the Configuration | DNS routing | Default Gateways.
The Ip address is ping-able now from both ESXi hosts hence it didn't crash or evacuating the VM.
The Ip address is ping-able now from both ESXi hosts hence it didn't crash or evacuating the VM.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Can I look it up from vsphere client ?
There is no changes on the ESXi server / hardware that I know of so far.