Link to home
Start Free TrialLog in
Avatar of Carl Billington
Carl BillingtonFlag for Australia

asked on

Exchange 2010 DAG configuration - Failover Cluster Manager – network offline

I did not configure this so I will try and provide as much information as I can.

We have 4 Exchange servers:

SYD01
SYD02
MEL01
MEL02

Our DAG was configured with two IP addresses. One IP address relates to the Sydney office (10.10.1.*) and the other relating to Melbourne (10.10.12.*) over our WAN.

DAG configuration:
SYDDAG01
IPv4 - 10.10.1.71 - Online
IPv4 - 10.10.12.73 - Offline

In Failover Cluster Manager.

The following IP address for DAG: 10.10.1.71 is currently online however 10.10.12.73 is offline (see screenshot), and I am unable to enable it.

1) Is there any reason to why I cannot bring this resource online?
2) Is the second IP necessary?
3) How do I troubleshoot?
4) If I deleted it, how do I add the IP address back in again?
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

There is no screenshot attached.
Is the DAG completely online? Do the databases say mounted and healthy?
Are you using DAC mode?

Simon.
Avatar of Carl Billington

ASKER

Sorry it has been a long day. I hope these screenshots show things a little clearer. All my databases are healthy. I just feel that my Failover setup is not quite right.

User generated image
User generated image
Avatar of vicky19
vicky19

Can you please share the cluster logs .... have you tried to bring the resource Online or you get this error while normally accessing Failover cluster.

Regards
It's difficult to state from just screenshot for me to help you. if you can provide the cluster log, I can read and help you with it - provided you let me know the exact time when the error occurred as per UTC.

Regards,
Exchange_Geek
are you implementing DAG in a virtual envirnment? if so then you have a problem with the virtual network, try to associate your virtual network with another physical external network and see if the problem is resolved.
regards
We backup our Exchange servers VM via CommVault. When this backup occurs it causes the Exchange server is lose network for a second and the DAG failover over to an available Exchange server. You can see in the logs below when this happens. This is fine, I just want to get to the bottom of the way the Failover Cluster Manager is configured.


Level	Date and Time	Source	Event ID	Task Category
Error	10/11/2012 9:37:28 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 9:37:28 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 9:22:27 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 9:22:27 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 9:07:26 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 9:07:26 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 8:52:25 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 8:52:57 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 8:52:47 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:46 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 8:52:47 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:43 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:43 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:35 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 8:52:25 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:25 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 8:52:25 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 8:52:25 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 8:37:25 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 8:37:25 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 8:22:25 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 8:22:25 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 8:07:24 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 8:07:24 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 7:52:24 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 7:52:24 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 7:37:23 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 7:37:23 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 7:22:22 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 7:22:22 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 7:07:21 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 7:07:21 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 6:52:20 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 6:52:20 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 6:37:20 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 6:37:20 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Critical	10/11/2012 6:25:02 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 6:25:02 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 6:25:01 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 6:25:01 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Error	10/11/2012 6:22:19 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Critical	10/11/2012 6:25:01 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 6:25:01 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 6:25:01 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Warning	10/11/2012 6:22:19 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 6:07:18 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 6:07:18 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 5:52:18 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 5:52:18 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 5:37:18 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 5:37:18 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 5:22:18 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 5:22:18 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 5:07:17 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 5:07:17 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 4:52:16 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 4:52:16 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 4:37:15 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 4:37:15 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 4:22:14 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 4:22:14 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 4:07:13 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 4:07:13 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	10/11/2012 3:18:22 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	10/11/2012 3:07:12 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 3:07:12 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 3:07:12 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 2:52:12 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 2:52:12 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 2:37:11 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 2:37:11 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 2:22:10 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 2:22:10 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 2:07:10 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 2:07:10 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 1:07:09 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 12:32:10 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 1:07:09 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 1:07:09 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 12:52:09 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 12:52:09 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 12:37:08 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 12:37:08 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	10/11/2012 12:32:42 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 12:32:31 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:31 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:24 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 12:32:14 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:13 AM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	10/11/2012 12:32:14 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:10 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:10 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	10/11/2012 12:32:10 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 12:32:10 AM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	10/11/2012 12:22:08 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 12:22:08 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	10/11/2012 12:12:09 AM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	10/11/2012 12:07:08 AM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	10/11/2012 12:07:08 AM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 11:52:26 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 11:52:08 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 11:52:08 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 11:49:14 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 11:47:48 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 11:11:34 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 11:11:34 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 11:11:34 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 11:01:33 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 11:01:33 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 10:51:34 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 10:46:33 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 10:46:33 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 10:31:33 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 10:31:33 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 9:31:31 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 9:31:31 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 9:31:31 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 9:25:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 9:25:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 9:10:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 9:10:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 8:55:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 8:55:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 8:51:31 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 8:40:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 8:40:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 8:30:31 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 8:25:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 8:25:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 8:10:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 8:10:29 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Critical	9/11/2012 7:54:05 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:54:05 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:54:05 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:54:04 PM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 7:54:04 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:54:04 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:54:04 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:53 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:53 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:53 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:43 PM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 7:49:43 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:43 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 7:49:43 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	9/11/2012 7:10:28 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 7:10:28 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 7:10:28 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 6:58:26 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 6:58:26 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 6:50:28 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 6:43:26 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 6:43:26 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 6:29:49 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 6:28:58 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 6:28:49 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:49 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:48 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 6:28:37 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:37 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:36 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 6:28:26 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:26 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 6:28:25 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 6:28:25 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 6:28:25 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 6:24:29 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:15:13 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	9/11/2012 6:13:25 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 6:13:25 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 6:04:04 PM	Microsoft-Windows-FailoverClustering	1562	File Share Witness Resource	File share witness resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' failed a periodic health check on file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local'. Please ensure that file share '\\asydhub01.COMPANY.local\asyddag01.COMPANY.local' exists and is accessible by the cluster.
Error	9/11/2012 6:03:06 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	9/11/2012 6:03:03 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	9/11/2012 6:03:03 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 6:03:02 PM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Error	9/11/2012 5:58:25 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 5:58:25 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 5:43:24 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 5:43:24 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 5:28:23 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 5:28:23 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 5:13:22 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 5:13:22 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 4:58:22 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 4:58:22 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 4:43:21 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 4:43:21 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 4:28:20 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 4:28:20 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 4:13:20 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 4:13:20 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 3:58:19 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 3:58:19 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 3:43:18 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 3:43:18 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 3:28:17 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 3:28:17 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 3:13:17 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 3:13:17 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 2:58:16 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 2:58:16 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 2:43:16 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 2:43:16 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 2:28:15 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 2:28:15 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 2:13:14 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 2:13:14 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 1:58:14 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 1:58:14 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 1:43:13 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 1:43:13 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 1:28:12 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 1:28:12 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 1:13:11 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 1:13:11 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 12:58:11 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 12:58:11 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 12:43:10 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 12:43:10 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Warning	9/11/2012 12:13:08 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 12:28:09 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'File Share Witness (\\asydhub01.COMPANY.local\asyddag01.COMPANY.local)' in clustered service or application 'Cluster Group' failed.
Warning	9/11/2012 12:28:09 PM	Microsoft-Windows-FailoverClustering	1558	Quorum Manager	The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
Error	9/11/2012 12:23:24 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:22:32 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:17:29 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 12:17:29 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:14:48 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:36 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 12:13:25 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:25 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:25 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 12:13:13 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 2 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:12 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error	9/11/2012 12:13:13 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:09 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:09 PM	Microsoft-Windows-FailoverClustering	1069	Resource Control Manager	Cluster resource 'IPv4 Static Address 1 (Cluster Group)' in clustered service or application 'Cluster Group' failed.
Error	9/11/2012 12:13:08 PM	Microsoft-Windows-FailoverClustering	1205	Resource Control Manager	The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Critical	9/11/2012 2:52:25 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:52:25 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:52:25 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:52:24 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 2:52:24 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:52:24 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:52:24 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:56 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:56 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:56 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:55 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 2:46:55 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:55 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 2:46:55 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:19 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:19 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:19 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:18 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 12:49:18 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:18 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:49:18 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:39 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:39 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:39 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE04' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:38 AM	Microsoft-Windows-FailoverClustering	1177	Quorum Manager	"The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."
Critical	9/11/2012 12:46:38 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:38 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ADRXGE01' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Critical	9/11/2012 12:46:38 AM	Microsoft-Windows-FailoverClustering	1135	Node Mgr	Cluster node 'ASYDXGE03' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Open in new window

The cluster network appears to be fine (as per screenshot)

I just do not understand why the second IP address of asyddag01 will not come online (see screenshot)

Does it need to be associated with both subnets? We have Exchange servers in both Sydney and Melbourne so it makes sense that it should.

User generated image
User generated image
What is the Sydney and Melbourne IP subnet as per AD ?

Regards
Hi the networks below:

Sydney - 10.10.1.255
Melbourne - 10.10.12.255
run cmd from an elevated Admin prompt

 

type the following To see who are the possible owners :

Cluster res <resource name> /listowners

 

To to add a server to the list

Cluster res <resource name> /addowner :<servername>
So according to that article (last comment), it is normal behaviour for one IP address to be online and the other to remain offline.

User generated image
At present, a server in Melbourne is holding the quorum. How can I avoid this? The file share witness is currently offline in result of this I'm guessing.

User generated image
What are your thoughts?
If I right click the File Share Witness I am able to bring it online but shouldn't this be done automatically?
the witness server should be local to your site otherwise it will fail (in this current version of exchange 2010), my advice is:
to avoid such problems, you really must use 2 different DAGs.  one DAG for each site, One DAG where the file share witness (FSW)is in the First Site and a second DAG where its FSW is in the Second Site.  here is a good article that describe the best practice:
http://www.shudnow.net/2011/09/07/exchange-2010-site-resilient-dags-and-majority-node-set-clustering-%E2%80%93-part-3/
Hi emadallan, thanks for this link. I will give it a read.

Should it matter if the second site (Melbourne) is only used for DR? Would you still recommend 2 different DAG environments?
Yes the MNS\FSW should be online always as that will help in ownership in case of issue .... but i would strongly recommend you to check network related stuff between both environments.

No issues is Melbourne is used as DR its more of a HA in DAG and can be termed as DR as you can have upto 16 servers in DAG

I would say plan for 2 DAG's but thats cost as well and you can then have the DAG copy of Melbourne on Sydney and otherway as well.

Regards
But if I create a DAG in DR, then the failover from Production to our Disaster Recovery Exchange will no longer work..?
ASKER CERTIFIED SOLUTION
Avatar of Carl Billington
Carl Billington
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Resolved myself.