HA Failover Cluster Errors on VSpere

Jaime Campos
Jaime Campos used Ask the Experts™
on
Hello,

I have three ESX Servers running vSphere ESXi 4.1. I have noticed that my ESX server within vCenter Server under events has errors. Not sure where to troubleshoot or how to ensure these servers do not go down.

Show all Cluster entrys
HA recovered from a total cluster failure in cluster
DC Cluster in datacenter RAPA DC
Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/16/2011 5:38:15 PM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/16/2011 5:38:15 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/16/2011 5:37:47 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/16/2011 5:37:47 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/16/2011 5:37:47 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/16/2011 5:37:47 PM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/16/2011 5:37:47 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/16/2011 6:35:13 AM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/16/2011 6:34:45 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/16/2011 6:34:45 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/16/2011 6:34:45 AM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/16/2011 6:34:44 AM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 11:18:02 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 11:17:20 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 11:17:20 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 11:17:20 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 11:17:19 PM
DC Cluster

HA enabled on cluster DC Cluster in RAPA DC
info
5/15/2011 11:16:13 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

Reconfigured cluster DC Cluster in datacenter
RAPA DC
info
5/15/2011 11:16:13 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

Task: Reconfigure cluster
info
5/15/2011 11:16:13 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

HA disabled on cluster DC Cluster in RAPA DC
info
5/15/2011 11:15:44 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

Reconfigured cluster DC Cluster in datacenter
RAPA DC
info
5/15/2011 11:15:44 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

Task: Reconfigure cluster
info
5/15/2011 11:15:44 PM
Reconfigure cluster
DC Cluster
RAPA\nimda

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 10:24:41 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 10:24:41 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 10:24:41 PM
DC Cluster

HA recovered from a total cluster failure in cluster
DC Cluster in datacenter RAPA DC
warning
5/15/2011 10:24:33 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 10:24:22 PM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/15/2011 10:24:22 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 10:16:44 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 10:16:44 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 10:16:44 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 10:16:43 PM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/15/2011 10:16:43 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 8:47:17 PM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/15/2011 8:47:17 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 8:46:48 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 8:46:48 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 8:46:48 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 8:46:48 PM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/15/2011 8:46:48 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 2:08:06 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 1:59:40 PM
DC Cluster

HA recovered from a total cluster failure in cluster
DC Cluster in datacenter RAPA DC
warning
5/15/2011 1:59:32 PM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/15/2011 1:58:58 PM
DC Cluster

HA initiated a failover action in cluster DC Cluster
in datacenter RAPA DC
warning
5/15/2011 1:58:41 PM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/15/2011 1:58:31 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 1:58:15 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 1:58:15 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 1:58:15 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 1:58:13 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 12:11:45 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 12:11:18 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 12:11:18 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 12:11:18 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 12:11:17 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 7:17:15 AM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/15/2011 7:17:15 AM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 7:16:47 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 7:16:47 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 7:16:47 AM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 7:16:46 AM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/15/2011 7:16:46 AM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/15/2011 1:09:14 AM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/15/2011 1:08:45 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/15/2011 1:08:45 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/15/2011 1:08:45 AM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/15/2011 1:08:45 AM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/14/2011 7:01:13 PM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/14/2011 7:00:45 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/14/2011 7:00:45 PM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/14/2011 7:00:45 PM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/14/2011 7:00:44 PM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/14/2011 4:18:10 AM
DC Cluster

Re-established contact with a primary host in this
HA cluster
info
5/14/2011 4:18:10 AM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/14/2011 4:17:42 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/14/2011 4:17:42 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/14/2011 4:17:42 AM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/14/2011 4:17:41 AM
DC Cluster

Unable to contact a primary HA agent in cluster
DC Cluster in RAPA DC
error
5/14/2011 4:17:41 AM
DC Cluster

Sufficient resources are available to satisfy HA
failover level in cluster DC Cluster in RAPA DC
info
5/14/2011 3:04:40 AM
DC Cluster

Alarm 'Cluster high availability error': an SNMP
trap for entity DC Cluster was sent
info
5/14/2011 3:04:11 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster triggered an action
info
5/14/2011 3:04:11 AM
DC Cluster

Alarm 'Cluster high availability error' on DC
Cluster changed from Gray to Gray
info
5/14/2011 3:04:11 AM
DC Cluster

Insufficient resources to satisfy HA failover level
on cluster DC Cluster in RAPA DC
error
5/14/2011 3:04:11 AM
DC Cluster

All Entrys

Host esx3.rapa.local could not reach isolation
address: 192.168.1.250
error
5/16/2011 10:36:57 PM
esx3.rapa.local

Alarm 'Host service console swap rates' on
esx1.rapa.local changed from Gray to Green
info
5/16/2011 10:33:00 PM
esx1.rapa.local

Alarm 'Host memory usage' on esx1.rapa.local
changed from Gray to Green
info
5/16/2011 10:33:00 PM
esx1.rapa.local

Alarm 'Host cpu usage' on esx1.rapa.local
changed from Gray to Green
info
5/16/2011 10:33:00 PM
esx1.rapa.local

Alarm 'Host service console swap rates' on
esx3.rapa.local changed from Gray to Green
info
5/16/2011 10:32:47 PM
esx3.rapa.local

Alarm 'Host memory usage' on esx3.rapa.local
changed from Gray to Green
info
5/16/2011 10:32:47 PM
esx3.rapa.local

Alarm 'Host cpu usage' on esx3.rapa.local
changed from Gray to Green
info
5/16/2011 10:32:47 PM
esx3.rapa.local

Alarm 'Host service console swap rates' on
esx2.rapa.local changed from Gray to Green
info
5/16/2011 10:32:45 PM
esx2.rapa.local

Alarm 'Host memory usage' on esx2.rapa.local
changed from Gray to Green
info
5/16/2011 10:32:45 PM
esx2.rapa.local

Alarm 'Host cpu usage' on esx2.rapa.local
changed from Gray to Green
info
5/16/2011 10:32:45 PM
esx2.rapa.local

Alarm 'Host connection and power state' on esx1.
rapa.local changed from Red to Green
info
5/16/2011 10:32:41 PM
esx1.rapa.local

Connected to esx1.rapa.local in RAPA DC
info
5/16/2011 10:32:40 PM
esx1.rapa.local

Virtual machine VM3 - Fileserver is connected
info
5/16/2011 10:32:40 PM
VM3 - Fileserver

Virtual machine VM2 - Domain Controller, DNS,
DHCP, AD is connected
info
5/16/2011 10:32:40 PM
VM2 - Domain Controller, DNS, DHCP, AD

Virtual machine VM1 - vCenter is connected
info
5/16/2011 10:32:40 PM
VM1 - vCenter

Connected to esx1.rapa.local in RAPA DC
info
5/16/2011 10:32:40 PM
esx1.rapa.local

Alarm 'Host connection and power state' on esx3.
rapa.local changed from Red to Green
info
5/16/2011 10:32:38 PM
esx3.rapa.local

Connected to esx3.rapa.local in RAPA DC
info
5/16/2011 10:32:37 PM
esx3.rapa.local

Virtual machine VM10 - EMR eBO/Report 1 is
connected
info
5/16/2011 10:32:37 PM
VM10 - EMR eBO/Report 1

Virtual machine VM9 - EMR Interface is
connected
info
5/16/2011 10:32:37 PM
VM9 - EMR Interface

Connected to esx3.rapa.local in RAPA DC
info
5/16/2011 10:32:37 PM
esx3.rapa.local

Alarm 'Host connection and power state' on esx2.
rapa.local changed from Red to Green
info
5/16/2011 10:32:36 PM
esx2.rapa.local

Connected to esx2.rapa.local in RAPA DC
info
5/16/2011 10:32:35 PM
esx2.rapa.local

Virtual machine VM6 - EMR App 2 is connected
info
5/16/2011 10:32:35 PM
VM6 - EMR App 2

Virtual machine VM8 - EMR Test is connected
info
5/16/2011 10:32:35 PM
VM8 - EMR Test

Virtual machine VM7 - EMR FTP is connected
info
5/16/2011 10:32:35 PM
VM7 - EMR FTP

Virtual machine VM5 - EMR App 1 is connected
info
5/16/2011 10:32:35 PM
VM5 - EMR App 1

Connected to esx2.rapa.local in RAPA DC
info
5/16/2011 10:32:35 PM
esx2.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx3.rapa.local was sent
info
5/16/2011 10:32:34 PM
esx3.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx2.rapa.local was sent
info
5/16/2011 10:32:34 PM
esx2.rapa.local

Alarm 'Host connection failure' on esx3.rapa.local
triggered an action
info
5/16/2011 10:32:34 PM
esx3.rapa.local

Alarm 'Host connection failure' on esx3.rapa.local
changed from Gray to Gray
info
5/16/2011 10:32:34 PM
esx3.rapa.local

Alarm 'Host connection failure' on esx2.rapa.local
triggered an action
info
5/16/2011 10:32:34 PM
esx2.rapa.local

Alarm 'Host connection failure' on esx2.rapa.local
changed from Gray to Gray
info
5/16/2011 10:32:34 PM
esx2.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx1.rapa.local was sent
info
5/16/2011 10:32:34 PM
esx1.rapa.local

Alarm 'Host connection failure' on esx1.rapa.local
triggered an action
info
5/16/2011 10:32:34 PM
esx1.rapa.local

Alarm 'Host connection failure' on esx1.rapa.local
changed from Gray to Gray
info
5/16/2011 10:32:34 PM
esx1.rapa.local

Alarm 'Host service console swap rates' on
esx3.rapa.local changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx3.rapa.local

Alarm 'Host memory usage' on esx3.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx3.rapa.local

Alarm 'Host cpu usage' on esx3.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx3.rapa.local

Alarm 'Host connection and power state' on esx3.
rapa.local changed from Green to Red
info
5/16/2011 10:32:33 PM
esx3.rapa.local

Alarm 'Host service console swap rates' on
esx2.rapa.local changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx2.rapa.local

Alarm 'Host memory usage' on esx2.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx2.rapa.local

Alarm 'Host cpu usage' on esx2.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx2.rapa.local

Alarm 'Host connection and power state' on esx2.
rapa.local changed from Green to Red
info
5/16/2011 10:32:33 PM
esx2.rapa.local

Alarm 'Host service console swap rates' on
esx1.rapa.local changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx1.rapa.local

Alarm 'Host memory usage' on esx1.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx1.rapa.local

Alarm 'Host cpu usage' on esx1.rapa.local
changed from Green to Gray
info
5/16/2011 10:32:33 PM
esx1.rapa.local

Alarm 'Host connection and power state' on esx1.
rapa.local changed from Green to Red
info
5/16/2011 10:32:33 PM
esx1.rapa.local

VM10 - EMR eBO/Report 1 on host
esx3.rapa.local in RAPA DC is disconnected
info
5/16/2011 10:32:33 PM
VM10 - EMR eBO/Report 1

VM9 - EMR Interface on host esx3.rapa.local in
RAPA DC is disconnected
info
5/16/2011 10:32:33 PM
VM9 - EMR Interface

Host esx3.rapa.local in RAPA DC is not
responding
error
5/16/2011 10:32:33 PM
esx3.rapa.local

VM6 - EMR App 2 on host esx2.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM6 - EMR App 2

VM8 - EMR Test on host esx2.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM8 - EMR Test

VM7 - EMR FTP on host esx2.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM7 - EMR FTP

VM5 - EMR App 1 on host esx2.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM5 - EMR App 1

Host esx2.rapa.local in RAPA DC is not
responding
error
5/16/2011 10:32:33 PM
esx2.rapa.local

VM3 - Fileserver on host esx1.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM3 - Fileserver

VM2 - Domain Controller, DNS, DHCP, AD on host
esx1.rapa.local in RAPA DC is disconnected
info
5/16/2011 10:32:33 PM
VM2 - Domain Controller, DNS, DHCP, AD

VM1 - vCenter on host esx1.rapa.local in RAPA
DC is disconnected
info
5/16/2011 10:32:33 PM
VM1 - vCenter

Host esx1.rapa.local in RAPA DC is not
responding
error
5/16/2011 10:32:33 PM
esx1.rapa.local

Alarm 'Host service console swap rates' on
esx1.rapa.local changed from Gray to Green
info
5/16/2011 9:19:19 PM
esx1.rapa.local

Alarm 'Host memory usage' on esx1.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:19 PM
esx1.rapa.local

Alarm 'Host cpu usage' on esx1.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:19 PM
esx1.rapa.local

Alarm 'Host service console swap rates' on
esx3.rapa.local changed from Gray to Green
info
5/16/2011 9:19:06 PM
esx3.rapa.local

Alarm 'Host memory usage' on esx3.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:06 PM
esx3.rapa.local

Alarm 'Host cpu usage' on esx3.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:06 PM
esx3.rapa.local

Alarm 'Host service console swap rates' on
esx2.rapa.local changed from Gray to Green
info
5/16/2011 9:19:04 PM
esx2.rapa.local

Alarm 'Host memory usage' on esx2.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:04 PM
esx2.rapa.local

Alarm 'Host cpu usage' on esx2.rapa.local
changed from Gray to Green
info
5/16/2011 9:19:04 PM
esx2.rapa.local

Alarm 'Host connection and power state' on esx1.
rapa.local changed from Red to Green
info
5/16/2011 9:18:59 PM
esx1.rapa.local

Connected to esx1.rapa.local in RAPA DC
info
5/16/2011 9:18:59 PM
esx1.rapa.local

Virtual machine VM3 - Fileserver is connected
info
5/16/2011 9:18:59 PM
VM3 - Fileserver

Virtual machine VM2 - Domain Controller, DNS,
DHCP, AD is connected
info
5/16/2011 9:18:59 PM
VM2 - Domain Controller, DNS, DHCP, AD

Virtual machine VM1 - vCenter is connected
info
5/16/2011 9:18:59 PM
VM1 - vCenter

Connected to esx1.rapa.local in RAPA DC
info
5/16/2011 9:18:59 PM
esx1.rapa.local

Alarm 'Host connection and power state' on esx3.
rapa.local changed from Red to Green
info
5/16/2011 9:18:57 PM
esx3.rapa.local

Connected to esx3.rapa.local in RAPA DC
info
5/16/2011 9:18:56 PM
esx3.rapa.local

Virtual machine VM10 - EMR eBO/Report 1 is
connected
info
5/16/2011 9:18:56 PM
VM10 - EMR eBO/Report 1

Virtual machine VM9 - EMR Interface is
connected
info
5/16/2011 9:18:56 PM
VM9 - EMR Interface

Connected to esx3.rapa.local in RAPA DC
info
5/16/2011 9:18:56 PM
esx3.rapa.local

Alarm 'Host connection and power state' on esx2.
rapa.local changed from Red to Green
info
5/16/2011 9:18:55 PM
esx2.rapa.local

Connected to esx2.rapa.local in RAPA DC
info
5/16/2011 9:18:54 PM
esx2.rapa.local

Virtual machine VM6 - EMR App 2 is connected
info
5/16/2011 9:18:54 PM
VM6 - EMR App 2

Virtual machine VM8 - EMR Test is connected
info
5/16/2011 9:18:54 PM
VM8 - EMR Test

Virtual machine VM7 - EMR FTP is connected
info
5/16/2011 9:18:54 PM
VM7 - EMR FTP

Virtual machine VM5 - EMR App 1 is connected
info
5/16/2011 9:18:54 PM
VM5 - EMR App 1

Connected to esx2.rapa.local in RAPA DC
info
5/16/2011 9:18:54 PM
esx2.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx3.rapa.local was sent
info
5/16/2011 9:18:51 PM
esx3.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx2.rapa.local was sent
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Alarm 'Host connection failure' on esx2.rapa.local
triggered an action
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Alarm 'Host connection failure' on esx2.rapa.local
changed from Gray to Gray
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Alarm 'Host connection failure': an SNMP trap for
entity esx1.rapa.local was sent
info
5/16/2011 9:18:51 PM
esx1.rapa.local

Alarm 'Host connection failure' on esx3.rapa.local
triggered an action
info
5/16/2011 9:18:51 PM
esx3.rapa.local

Alarm 'Host connection failure' on esx3.rapa.local
changed from Gray to Gray
info
5/16/2011 9:18:51 PM
esx3.rapa.local

Alarm 'Host connection failure' on esx1.rapa.local
triggered an action
info
5/16/2011 9:18:51 PM
esx1.rapa.local

Alarm 'Host connection failure' on esx1.rapa.local
changed from Gray to Gray
info
5/16/2011 9:18:51 PM
esx1.rapa.local

Alarm 'Host service console swap rates' on
esx2.rapa.local changed from Green to Gray
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Alarm 'Host memory usage' on esx2.rapa.local
changed from Green to Gray
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Alarm 'Host cpu usage' on esx2.rapa.local
changed from Green to Gray
info
5/16/2011 9:18:51 PM
esx2.rapa.local

Any idea what is going on? Is this just VCenter communicating with ESX Host? I appreciate your help and support.

nimdatx
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Paul SolovyovskySenior IT Advisor
Top Expert 2008
Commented:
HA failure occurs for two reasons:

1.  DNS issues - Ensure that you can ping hosts to vcenter and visa versa
2.  host responce: Make sure your ESX hosts can ping the default gateway
Sikhumbuzo NtsadaIT Administration

Commented:
When you check on the Summary Tab, How much RAM is left and how much CPU is left?
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
You need to work through this Troubleshooting HA Document by VMware in the Knowledge Base

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001596
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Danny McDanielClinical Systems Analyst

Commented:
Host esx3.rapa.local could not reach isolation
address: 192.168.1.250
error
5/16/2011 10:36:57 PM
esx3.rapa.local

Looks like networking issues.  Have there been any issues with your switches or cables getting pulled?

Author

Commented:
Yes. I rebooted my router lastnight. Sorry to mention I didn't mention that. I have pinged from ESX HOSTS to DG and from VCenter to ESX HOST visa versa. All was successful. I have reset my VCenter Services, rebooted and I also reconfigure HA Cluster. Now can this potentially bring the ESX Host down?
Danny McDanielClinical Systems Analyst
Commented:
It won't crash your hosts to lose network connectivity but it can tell ha to shutdown your vm's if you have it set to power off vm's in event of host isolation
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
If you router was the gateway that was defined, that was the issue. The gateway is used as a device to test the network, that never goes down.

If you are going to regularly do router maintenance, and take it offline, maybe select an IP address, which is always ONLINE.
Danny McDanielClinical Systems Analyst

Commented:
Or...before doing the maintenance, go into your cluster settings and uncheck the box for 'enable Host Monitoring'.  Just remember to re-check it when you're done or enable the alarm for HA at the top level.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
If you fancy some bedtime reading about HA and DRS, I definately recommend

VMware vSphere 4.1 HA and DRS Technical deepdive (Volume 1)

By Duncan Epping and Frank Denneman

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

ISBN-10: 1456301446
ISBN-13: 978-1456301446

Written by Duncan Epping and Frank Denneman, both of whom are Consulting Architects at VMware and are perceived by the industry as Subject Matter experts on VMware High Availability and VMware Distributed Resource Scheduler.
This book zooms in on two key components of every VMware based infrastructure. It covers the basic steps needed to create a VMware HA and DRS cluster, and goes on to explain the concepts and mechanisms behind HA and DRS which will enable you to make well educated decisions. You will get the tools to understand and implement e.g. HA admission control policies, DRS resource pools and resource allocation settings and more.

On Amazon US

[Paperback]

http://www.amazon.com/gp/product/1456301446?ie=UTF8&tag=yellowbricks20&linkCode=as2&camp=1789&creative=9325&creativeASIN=1456301446

[ebook]

http://www.amazon.com/dp/B004V49JGW/ref=as_li_tf_til?tag=yellowbricks20&camp=0&creative=0&linkCode=as1&creativeASIN=B004V49JGW&adid=0ED4RKK85G6ZTGTH9ENP

on Amazon UK


[Paperback]

http://www.amazon.co.uk/Vmware-Vsphere-4-1-Technical-Deepdive/dp/1456301446/ref=sr_1_2ie=UTF8&s=books&qid=1305637596&sr=8-2


[ebook]

http://www.amazon.co.uk/VMware-vSphere-4-1-technical-deepdive/dp/B004V49JGW/ref=sr_1_1?ie=UTF8&s=digitaltext&qid=1305637596&sr=8-1

Available in Europe from

http://www.comcol.nl/detail/73133.htm

Author

Commented:
Hanccocka,

Are you availiable for hire? I'd like to speak with you. Need some help and I've done all I can to get this project up and running. All seemes to be good except for these warnings/alarms. Let me know.

Thanks,

nimdatx
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Contact through profile please.

Author

Commented:
What is the maximum CPU, Memory, Network (Mbps), Disk  % my VMs should be at for best performance?

This is what my Performance reading so far and I'm not sure how to determine if I have any issues?

  App1 App1 Network
vDisk App1
Do I need to make any changes?

Thanks,

nimdatx
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
are you still getting issues with HA

Author

Commented:
Yes
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
if you have followed that document, and all thevsteps have been completed, if you have a valid support agreement with VMware I would log a support request with them.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial