Pressing OK closes the wizard and returns to Failover Cluster Management.

This happens if I add just one or both nodes to the Create cluster wizard.

However, using the cluster.exe command to form the cluster with just one node works successfully. Adding the second node through the GUI now works. Is this just a GUI BUG or is it something that the CLUSTER.EXE command isn't robust enough to handle when it forms the cluster?

Background Info:

I'm trying to form a two-node cluster for Exchange CCR using a File Share Withness. All validations comlpete successfully except for the tests for shared storage.

I managed to get around this problem by using the CLUSTER.EXE command but it would have been nice to know what causes the error in the GUI. (An error message that is a bit more descriptive would have been nice too...)

LA.

In Failover Cluster Manager, If I am on node 1. I can only connect to VM's that currently reside on node 1. Trying to connect to a vm on node 2 or 3 results in this error.

An authentication Error has occurred. The specific target is unknown or unreachable.

Remote Computer  servername.domainname.com  (example)"

In Hyper-V Manager  I get the same result.  Logged into Server1 , connect to Server1 roles, all okay. Add Server2 and Server3 to Hyper-V Manager, try to connect to VM's on Server2 or Server3.  Same above error.

DNS is perfect, I can ping each server from each server.

Cluster Verification is clean...

I have configured multiple client machine IP address and Port number in Database. whenever I want to send the data from server to client  that time server reading IP and Port number from database and sending message through TCP Client. 

Now the problem is my client machine IP and port already i configured but now my client machine working in WAN or ethernet, in this scenario my client machine IP will be different because of this sub-net has been changed.

TcpClient socketForServer = new TcpClient("192.168.2.54", 12345);

Acutally this is the configured IP and port number to connect my client but the problem is now my client machine connected with DHCP IP so it will not connect.That IP is 192.168.5.54

Anyone please help me how to connect my client machine from server through TCP listener or TCP client in C#

Try to update Windows 2012 HyperV Cluster but CAU wizard failed to preview needed updates with CIM exception FAILED HRESULT 0x8024401c message. Failover Cluster Management Console logs message with EVENT ID 2002 for all Cluster Nodes.

Last month CAU completed successfully.

Hello, MS specialist. I'm experiencing an issue about creating cluster. I have researched it for over one week, but I cannot resolved it, it really trouble me.

environment:
three guest machine in hyper-v.
DC
cluster1
cluster2

Host machine is windows2008 R2, three guest mancines are also windows2008 R2

First of all, validation is passed successfully without any error.
When I use wizard to create cluster, it stop at "Forming cluster "clusterdemo"" for a long time and failed with error:

An error occurred while creating the cluster.
An error occurred creating cluster "clusterdemo".
This operation returned because the timeout period expired.

Meanwhile I found message in event viewer:

Event 1570, Failoverclusting
Node 'cluster1' 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.

Event 1280, Failoverclusting
Sponsor tried to create security context using package='Kerberos' with context requirment='165910' and timeout='30000'

Event 1281, Failoverclusting
Joiner tried to create security context using package='Kerberos' with context requirement='83990' and timeout='30000' for the target='cluster2'

I have read http://technet.microsoft.com/en-us/library/dd301029(WS.10).aspx it's about Event ID 1570 — Node Membership in Cluster, but it's no help to me

Since two nodes cluster creating failed, I create a one node cluster, the node machine is cluster1. it is successfully created.

When I use wizard to add another node cluster2 to cluster, it failed with error :

The server "cluster2" could not be added to the cluster. An error occurred while adding node "cluster2" to cluster "clusterdemo". the cluser node is not reachable.

and meanwhile I found error message in event viewer said:
Event 10009, DistributedCOM
Dcom was unable to communicate with the computer cluster2 using any of the cofigured protocols

I have read this document http://technet.microsoft.com/en-us/library/dd337741(WS.10).aspx it's about Event ID 10009 — COM Remote Service Availability
I think it's also no help to me

So finally I have entered an dead lane, Could anyone help me or give some suggestion to me.
Waiting your post. Thanks.

Hi, we are having a 2-node fileserver failover cluster based on Windows Server 2012 Datacenter.

We are having 2 roles defined in the cluster, a File server for user data and a Scale-Out File Server for af different HYPER-V Failover cluster.

The problem I have observed is related to the SCFS part. After running for some time (typical 12 to 48 hours) I am no longer able to use the Move-SmbWitnessClient powershell command. Trying to results in the error:

In the SMBWitnessService eventlog I get the following warning (event 12):

Witness Service ignored the move client request for client (****blade0a04). Client is not registered with current Witness Service

I do get a lot of informal events and warnings in the SMBWitnessService eventlog at night while DPM 2012 takes backup of the Hyper-V VMs.

I can manuallu shutdown the SMBWitnessService on both nodes and after a short recovery time the Move-SmbWitnessClient works again.

Has anyone experienced the same?

Hi,

Im trying out Cluster-Aware Updating with windows server 2012. Have configured the clusterad its working, then i run the "cluster updating readiness" tool, and this shows only green, only warning on proxy configuration, but there is no need for proxy to connect to the internet.

Then i run the "Preview updates for this cluster" and it shows "no updates found".
I also did a windows update on the hyperv nodes, but no updates found.

Then i run the script from http://blogs.technet.com/b/cedward/archive/2013/05/31/validating-hyper-v-2012-and-failover-clustering-hotfixes-with-powershell-part-2.aspx and this shows many hotfixes and updates that should be applied to both the hyperv hosts and cluster.

So am i missing something in the cau, isn`t this what im supposed to use ?

Thanks for answers.

/Regards Andreas

Hi,

can a 10GB SPF be connected directly between 2 servers and not via a switch?

Thanks James.

Hello

We have two Windows 2008 R2 Enterprise Servers, configured as nodes for a failover cluster, hosting virtual machines. Both are connected to a SAS disks Storage system.

Although it work fine there is something I am a bit worried. Windows disk space is 130 GB in both servers, and in both of them there are only 30 GB free, I have been looking for the files or folders that take so much space, but I couldn't find it.

Is this normal? Does it has to do with the cluster configuration. I looked even in hidden files or folders but I didn't find the reason.

I could not understand how such a Windows installation take as much space.

Thank you very much.

Kind Regards.

David

Hi,

I am trying to build a SOFS cluster which is backed by two iSCSI NAS devices, but I seem to be having issues if one of the NAS devices fails.

here is what I have (all systems are based on SERVER 2012 R2 Preview):

two NAS devices NAS1 and NAS2, there are two iSCSI disks on each because the SOFS cluster storage pool seems to want to have a minimum of 3 disks, so I’ve got 4 between the 2 NAS.

FS1 and FS2, both file servers have the iSCSI initiator connect to all targets on the NAS - so in each FS I see four attached iSCSI disks in disk management. I create a cluster between FS1 and FS2, create a storage pool in failover cluster manager and include all 4 disks, then I create a virtual disk within this storage pool, finally I add the file server role under the role services section, create a share and assign relevant permissions.

Everything is online, everything looks good. I can transfer the scale out file service role between FS1 and FS2 as I expect, the cluster name for this role is SOFS1.

So to test that the backend disk system can fail, I turn off NAS1 but the storage pool in my cluster shows errors and warnings that disks are not available and I cant bring them online even though both FS1 and FS2 are online. The file services cluster role is showing that its online.

My question here is two part:

Have I completely missed the point of a scale out file server and this is not how its supposed to work (i.e. is it just meant to work if one of the FS goes down rather than the backend NAS)?

Or… is this is unexpected behaviour, is it not just meant to use NAS2?

I assumed that the storage pool I created which included disks from both NAS1 and NAS2 will mirror the data across those disks so removing either NAS shouldn’t fail the storage?

I would appreciate any advice on this matter.

Thanks

Steve

I've launched the ISCSI Initiator from both computers, and connected them to the target.  The two ISCSI disks show up in disk management.  On one computer, I initialized/brought online both disks, and formatted them with NTFS.

Next step was to create the failover cluster, but I can't make the disks appear in the cluster.  I've tried it with the disks online, with the disks offline, with no drive letters on the disks - no dice.

After the cluster is created, the disks don't appear in the Failover Cluster Manager Storage -> Disks area, and if I click the Add Disk link, I get the dreaded "No suitable disks for cluster disks were found" message.  Yet, the disks that were configured in Disk Management are not visible from either node.  They also aren't visible in the Server Manager -> File and Storage Services -> ISCSI area.  They are entirely missing in action.  No good recreating them in that tool either; it says, "No eligible servers are available".

What am I not doing that is preventing the ISCSI disks from being available to the Failover Cluster? 

I did many times , but i was not able to see the disk or add disk from cluster. Please provide me solution

We have a critical issue where our Windows 2012 Datacenter server which hosts MSMQ is unable to send message to BizTalk servers. I am seeing lots of FailoverClustering error in the System event logs. Earlier it was 

Cluster network name resource 'XXXXXXXXXXXX' failed registration of one or more associated DNS name(s) for the following reason:
DNS bad key.

Now when we have the issue I am seeing it as slightly different.

Cluster network name resource 'XXXXXXXXXXXX' failed registration of one or more associated DNS name(s) for the following reason:
The handle is invalid.

Any suggestions are appreciated.

-Thanks

Hello

Setup:

2-node cluster with physical servers. 3 network teams, 1 Heartbeat, 1 LAN and 1 SAN. Its the Windows Server 2012 Team SW thats been used.

Problem:

All fail-over tests work fine, except "pulling the network cable" on the LAN-network. By pulling the cable I mean disabling the NICs that creates the LAN-team. That triggers the fail-over from that server, but the IP-address in the cluster fails with following error messages: "

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"

 "Cluster resource 'Cluster IP Address' of type 'IP Address' in clustered role 'Cluster Group' failed."

I tried finding relevant information online, but nothing seems to clearly solve the issue. The Cluster Validation completes without any errors at all. The cluster can be brough online manually, but not by itself.

Are there any views on how the cluster is supposed to handle sudden network losses? Any suggestions?

Regards

Alex

I have a 3 node cluster and I am experiencing some strange network issues. 

I have 4 10G adaptors in each node.  2 teamed for normal network traffic using LACP and 2 for ISCSI using MPIO.

The cluster throws a ton of errors out if I select "do not allow cluster network communication on this network" on the ISCSI network.  I enabled it a while back, because the guests were failing over every 5 minutes.

I would think that with 2 10G NIC's there would be enough throughput for the heartbeat.  I am thinking that is what causes this.

Any ideas?

Thank you

Good Day Everyone,

I have inherited a Hyper-V cluster and it has some major errors on "Validate Configuration". I am trying to take care of the quorum disk specifically at this point though and I need some clarification. My cluster has 6 hosts with 3 iSCSI volumes mapped to them. 1 volume is Quorum, the other 2 are Cluster Shared Volumes.

I have questions regarding the setup of the volumes that are mapped to the individual Hyper-V hosts.

1. I only see 1 host with the Quorum volume showing as an attached disk. The rest of the servers have the volume mapped but they are not initialized so they do not show up in the OS as a drive/storage. I was under the assumption that all servers in the cluster had to have the Quorum drive at least mapped even if it is configured as "Node Majority". The one server that is the witness does have this drive mapped/initialized.

2. I ran "Configure Cluster Quorum Wizard" but I do not find "Disk witness in Quorum" under storage. I do see the Quorum disk volume but it shows up as Available Storage.

Any help or info would be very helpful.

Antony

We have a new Dell VRTX server with 2 blades and shared storage.

Its my first Cluster so I'm trying to get to grips with the design and terminology.

What I want to achieve (Goals):-

• Hyper-V Cluster to ensure resilience and no single point of failure
• Virtualise a number of older physical servers, such as Print Servers, consoles for managing systems, door access system etc
• Virtualised new file server with DFS for use access to data

Any advice on how best to configure this would be appreciated, not necessarily step by step but whether to use high availability file server?, do we use SMB?,  how to best partition the storage?, how best to provide storage for file server? etc etc

I will also be wanting to make snapshots of the Hyper-V servers onto another physical server off-site just in case of a disaster.

Hello,

we have a two node cluster running server 2012R2, at the weekend we had a power failure and one of the nodes (I presume it was the active node) has a hardware failure and won't come back up. I thought this will be fine because we have another node and that would take on the work - however, in failover cluster manager the it won't connect to the cluster name, or the local node which is running. if I run the command Start-ClusterNode -FixQuorum it shows that the node is in the state of "joining" but never seems to get any further than that. I can manually start the cluster service but after a while it seems to stop.

I believe this is all because the active node is not contactable now I think what I am asking is how to make this remaining node be the authoritative active node....but I don't know what to do to make that happen.....

I would appreciate any help,

thank you

Steve

Hello,

We have a two-node active/active SQL Server 2008 Std Cluster on Windows 2008 on Production.

After a network maintenance, the network card (not heart-beat) of one node has no gateway ip. We want to fix it without causing a failover.

I assume when we set gateway ip, the network card will be reset, and the ip will be temporarily unavailable, then fail-over happens. Am I right?

Is there a way to play with dependencies not to initiate failover during fixing network card?

Thanks,

Hi,

We have set up SQL Fail over Cluster (Windows Server 2012 Standard Edition). the 2 SQL Servers have access to 2 SAN Disks (2 x HP P2000 G3).

Now, we are able to see the 2 SANs as 2 drives in Windows Cluster without a problem, We need to set up SAN mirroring so if 1 SAN unit fails, the SQL serevr can retrieve the needed info from the second SAN unit.

We've realized that it's possible to mirror the 2 SAN disks from Windows rather (by going to computer management, and mirroring the disks) We tested and the mirrored volume seems to be accessible from SQL Server A and SQL Server B, as well as the cluster disks. We were  just wondering if setting up mirrored SAN disks from Computer Management is recommended for that purpose? open to any other suggestions.

Thanks

Hello Guys,

I have created a cluster to configure Hyper-V for 2 Nods, everything was greate and works perfectly, next day the storage hang and the cluster didn't work any more, I have destroyed the cluster the removed the cluster feature from both nods, deleted the cluster-computer from AD and the deleted the storage. after we fixed the storage, I have reconnect the storage, installed the cluster service on both nods, then I have validate the configuration and I had everything green 100%.

while creating the cluster, I faced an issue Unable "to successfully cleanup" I kept trying and removed the anti-virus, restarted the servers manytime, then I ended up to have another error, direclty when I add the server name on the creat cluster wizard, its telling me that the computer I'm adding is joined to cluster.

I think I need to do some cleaning to the previous cluster, can I have some help here ?

Regards..

Nour

Nour