Hello
I'm trying to setup Failover Cluster. Using VMware ESX 4.1 to installed domain controller on Windows 2008 R2 and two cluster nodes also installed on Windows 2008 R2. Two Failover Cluster passed validate a configuration.
I want to confirm is it must required two NIC for each failover cluster node and Quorum in Istorage?
Which Istorage trial version for this solution?
Thanks !
Windows 2008 R2 Failover Cluster question
-
- Posts: 205
- Joined: Thu Nov 05, 2009 5:52 pm
- Contact:
Re: Windows 2008 R2 Failover Cluster question
Two nics are used for improving performance, it is not "must required" in your solution.
You may download the newest trial version at: http://www.kernsafe.com/download.aspx
You may download the newest trial version at: http://www.kernsafe.com/download.aspx
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
Re: Windows 2008 R2 Failover Cluster question
Hello Olivia
Nodes has NIC for external and internal, all test passed.
When creating cluster, it holding on forming cluster... expected time ....
the following is create cluster error message:
Create Cluster
Cluster: clusterrd
Node: a.xyz.local
Node: b.xyz.local
IP Address: 192.168.80.26
Started 11/11/2010 8:35:22 PM
Completed 11/11/2010 8:38:28 PM
Beginning to configure the cluster clusterrd.
Initializing Cluster clusterrd.
Validating cluster state on node a.xyz.local.
Searching the domain for computer object 'clusterrd'.
Creating a new computer object for 'clusterrd' in the domain.
Configuring computer object 'clusterrd' as cluster name object.
Validating installation of the Network FT Driver on node a.xyz.local.
Validating installation of the Cluster Disk Driver on node a.xyz.local.
Configuring Cluster Service on node a.xyz.local.
Validating installation of the Network FT Driver on node b.xyz.local.
Validating installation of the Cluster Disk Driver on node b.xyz.local.
Configuring Cluster Service on node b.xyz.local.
Waiting for notification that Cluster service on node a.xyz.local has started.
Forming cluster 'clusterrd'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'clusterrd'.
This operation returned because the timeout period expired
the following is event log message:
Node 'a' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
P.S. Windows Failover Cluster can't install on VMs ?
Thanks !
Nodes has NIC for external and internal, all test passed.
When creating cluster, it holding on forming cluster... expected time ....
the following is create cluster error message:
Create Cluster
Cluster: clusterrd
Node: a.xyz.local
Node: b.xyz.local
IP Address: 192.168.80.26
Started 11/11/2010 8:35:22 PM
Completed 11/11/2010 8:38:28 PM
Beginning to configure the cluster clusterrd.
Initializing Cluster clusterrd.
Validating cluster state on node a.xyz.local.
Searching the domain for computer object 'clusterrd'.
Creating a new computer object for 'clusterrd' in the domain.
Configuring computer object 'clusterrd' as cluster name object.
Validating installation of the Network FT Driver on node a.xyz.local.
Validating installation of the Cluster Disk Driver on node a.xyz.local.
Configuring Cluster Service on node a.xyz.local.
Validating installation of the Network FT Driver on node b.xyz.local.
Validating installation of the Cluster Disk Driver on node b.xyz.local.
Configuring Cluster Service on node b.xyz.local.
Waiting for notification that Cluster service on node a.xyz.local has started.
Forming cluster 'clusterrd'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
An error occurred while creating the cluster.
An error occurred creating cluster 'clusterrd'.
This operation returned because the timeout period expired
the following is event log message:
Node 'a' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
P.S. Windows Failover Cluster can't install on VMs ?
Thanks !
-
- Posts: 205
- Joined: Thu Nov 05, 2009 5:52 pm
- Contact:
Re: Windows 2008 R2 Failover Cluster question
Do you have selected the "Enable multiple initiators with full access connecte" on all the targets used for clustering?
Please first run the Validate a Configuration wizard, if you get some error, please send the log file to our support mail: [email protected]
Please first run the Validate a Configuration wizard, if you get some error, please send the log file to our support mail: [email protected]
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]
Re: Windows 2008 R2 Failover Cluster question
After used physical Dell R710 server avoid this problem ...