I have 2 Windows Server 2008 servers and I'm using a Dell Equallogic SAN.  these 2 servers are setup as a cluster.  I originally configured them a few  months ago and then I didn't touch them for about 2 months.  Now I went back to them and all of the disks are showing up as reserved on both servers.  There's no options in disk management, everything is greyed out. 

I have tried to take the SAN offline, bring it back online and then bring the servers up 1 at a time.  that didn't help. 

It's the same for all of the SAN disks.  I contacted Dell Equallogic and they do not see a reservation on the SAN.  They asked me to contact Microsoft. 

I verified that the Cluster service is running. 

I also tried using "cluster node w2k8 /clear:3" where 3 is the number of the disk.

I also tried running the Validation tests again. 

Hi,
 
I have just tried to configure 2 node Windows 2008 NLB cluster and I run into problem.
Until now I have successfully installed Windows Server 2003 NLB clusters. I used 2 nic per node and unicast mode.

For example

    Node1                                                        Node2
                Pub Interface (default)                                Pub Interface (default)
                        IP:192.168.1.11/24                                    IP:192.168.1.12/24
                        GW: 192.168.1.1                                        GW: 192.168.1.1


                NLB Interface*                                                 NLB Interface*
                        IP:192.168.1.12/24                                    IP: 192.168.1.13/24
                        GW:-                                                           GW:-

*DNS registration, File Share client and server, NetBIOS over TCP/IP disabled on this interface.

After configuring IP addresses I would run NLB manager and configure cluster in unicast mode.


When I tried this on Windows Server 2008, I could not access NLB address outside local subnet. Only when I configure DEFAULT GATEWAY on both NIC's, NLB started working.

When I run network monitor I notices that in this configuration, Windows 2003 would always respond using Public LAN (source MAC address would be from public NIC), no matter if i tried to connect to Public or NLB IP address.

In Windows 2008 if I tried to connect to Public IP, response packet would had source MAC address from Public NIC and when I accessed NLB address then source MAC would be from NLB NIC. For me this looks like change from 2003.

So how do we correctly configure unicast NLB cluster with 2 NIC's in Windows Server 2008? Do we just add default gateway to NLB NIC?


Krunoslav

P.S.
When I tried to search for solution I found that other people had this issue.

 

Hi all,

I am trying to create a 2 node cluster on two x64 Windows Server 2008 Enterprise edition servers. I am running the setup from the failover cluster MMC and it seems to run ok right up to the point where the snap-in says creating cluster. Then it seems to hang on "forming cluster" and a message pops up saying "The operation is taking longer than expected". A counter comes up and when it hits 2 minutes the wizard cancels and another message comes up "Unable to sucessfully cleanup".

The validation runs successfully before I start trying to create the cluster. The hardware involved is a HP EVA 6000, two Dell 2950's

I have included the report generated by the create cluster wizard below and the error from the event log on one of the machines (the error is the same on both machines).

Is there anything I can do to give me a better indication of what is happening, so I can resolve this issue or does anyone have any suggestions for me?

Thanks in advance.

Anthony

Create Cluster Log
==================

Beginning to configure the cluster <cluster>.
Initializing Cluster <cluster>.
Validating cluster state on node <Node1>

Searching the domain for computer object 'cluster'.
Creating a new computer object for 'cluster' in the domain.
Configuring computer object 'cluster' as cluster name object.
Validating installation of the Network FT Driver on node <Node1>

Validating installation of the Cluster Disk Driver on node <Node1>
Configuring Cluster Service on node <Node1>
Validating installation of the Network FT Driver on node <Node2>
Validating installation of the Cluster Disk Driver on node <Node2>
Configuring Cluster Service on node <Node2>
Waiting for notification that Cluster service on node <Node2>
Forming cluster '<cluster>'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.

Event Log
=========

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          29/08/2008 19:43:14
Event ID:      1570
Task Category: None
Level:         Critical
Keywords:     
User:          SYSTEM
Computer:      <NODE 2>
Description:
Node 'NODE2' 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 Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{baf908ea-3421-4ca9-9b84-6689b8c6f85f}" />
    <EventID>1570</EventID>
    <Version>0</Version>
    <Level>1</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2008-08-29T18:43:14.294Z" />
    <EventRecordID>4481</EventRecordID>
    <Correlation />
    <Execution ProcessID="2412" ThreadID="3416" />
    <Channel>System</Channel>
    <Computer>NODE2</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NodeName">node2</Data>
  </EventData>
</Event>

====

I have also since tried creating the cluster with the firewall and no success.

I have tried creating the node from the other cluster and this did not work either

I tried creating a cluster with just  a single node and this did create a cluster. I could not join the other node and the network name resource did not come online either. The below is from the event logs.

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          01/09/2008 12:42:44
Event ID:      1207
Task Category: Network Name Resource
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Node1.Domain
Description:
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'Domain' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.

The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.

 
The cluster identity 'CLUSTER$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Hi,

I have a two nodes Windows 2008 and SQL 2008 cluster running in active\passive.  I was restarting my nodes after applying windows update then I received the following error message below within Failover Cluster Manager.  The drive it is referring to is the Quorum drive.  I checked the current owner and I see the Quorum drive is set to reserve and its available in the second node.  Is there anything I need to check to fix this error?

Cluster resource "Cluster Disk 2" in clustered service or application "Cluster Group" failed. 
Event ID: 1069
Task Category: Resource Control Manager

Thanks

We tried every option suggested in the above article and also lot of other things in technet site.

But still we have some issues in DAG, where it automatically failover from one mailbox server to another.

Hello.

I’m hoping to get some help with a cluster issue I’m having using Windows Storage Server 2012.

When the cluster is created my Cluster Core Resources are all happy and online.

I can more the Cluster Name using “move Core Cluster Resources” between the two nodes without any problems.

If I select ‘Simulate Failure’ on the IP Address resource, it works the first time

If I do it again shortly after it fails and I get an Event ID 1254, 1205 and 1069.

Event ID 1254

Clustered role 'Cluster Group' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Event ID 1205

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.

Event ID 1069

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

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Basically I’m trying to simulate a network failure to make sure the failover kicks in.

If I click on it and ‘Bring Online’ it comes up fine.

Where do I find this Threshold Policy and set it to initiate failover if the IP Address resources fails?

Thank you in advance for your help.

We are running a Windows Server 2012 cluster and I see the following error in the System folder of Event Viewer.

"DCOM was unable to communicate with the computer SQL9 using any of the configured protocols; requested by PID     46a8 (C:\Windows\system32\ServerManager.exe)."

SQL9 was in the cluster at one point, but it had hardware issues so it was removed from the cluster in the cluster admin.  Because it had bad hardware, SQL9 was taken off the network and salvaged for parts.  

I have searched the registry for any reference to SQL9 and did not find anything.  I have searched the C: drive of all servers in the cluster and not found anything.

I would like to eliminate this error, does anyone know how to?

Hello.

I’m hoping to get some help with a cluster issue I’m having using Windows Storage Server 2012.

When the cluster is created my Cluster Core Resources are all happy and online.

I can more the Cluster Name using “move Core Cluster Resources” between the two nodes without any problems.

If I select ‘Simulate Failure’ on the IP Address resource, it works the first time

If I do it again shortly after it fails and I get an Event ID 1254, 1205 and 1069.

Event ID 1254

Clustered role 'Cluster Group' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Event ID 1205

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.

Event ID 1069

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

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Basically I’m trying to simulate a network failure to make sure the failover kicks in.

If I click on it and ‘Bring Online’ it comes up fine.

Where do I find this Threshold Policy and set it to initiate failover if the IP Address resources fails?

Thank you in advance for your help.

Last week we had a major failure with our failover cluster and I had to rebuild it from jump street.  Everything is back online and working again, except for the Cluster IP Address and the Cluster Name resource.  This resource fails on all 6 nodes with the following errors:

and

Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed

When I try to start the resource I get the following error:

Error Code: 0x80071736 - The resource failed to come online due to the failure of one or more provider resources

and

Error Code: 0x80071397 - The operation failed because either the specified cluster node is no the owner of the resource, or the node is not a possible owner of the resource.

I am new to failover clustering and do not have much back ground with Windows at all other than what I have forced myself to learn in this environment.  I created this cluster and every part of it seems to work except for this resource.  Any help is appreciated.

I am having a problem with one of our cluster nodes and it's connection the SAN where all the VMs are stored.  I came in this morning to find a warning on the SAN, with a bit of further investigation I found that one of the sessions on the iSCSI initiator was in a "Reconnecting" status.  I removed it, but was unable to re-add it, every time I try I get the error "Connection Failed".

I migrated all VMs off the node and restarted it to see if that would make a difference, it hasn't.

In the System event log, when I try and create the connection I am getting 2 errors:

1) Initiator failed to connect to the target.  Target IP address and TCP Port number are given in dump data

and

2) Error occurred when processing iSCSI logon request.  The request was not retried.  Error status is given in the dump data.

There doesn't appear to be a problem with the SAN as other nodes are connected to it perfectly fine.

OS is Windows Server 2008 R2 SP1 Datacenter

Does anybody have any ideas on how to resolve this?

Cheers

Adam.

Hi,

I have 2 Node Cluster on windows 2012.This cluster is used for SQL Server 2012 with High Availability group. in AG storage not shared, each node has its in depended storage.

Cluster was working find. Due to some issue Disk was not presented/offline at node 2. so  i just removed storage/disk from node 2 using failover cluster. I went to failover cluster --> storage and remove disk.

now disk is online on node 2. restart both node. I run cluster validation test and it also show disk in result. But problem is that node 2 disk is not listed under cluster disk resource. I try to add disk resource and getting following error

kindly advice how to fix the issue.

thx

iffi

My cluster consists of two nodes. Node-A is working fine, however Node-B is giving me the following error when trying to use the Failover Cluster Manager.

The operation has failed.

An error occurred connecting to the cluster '.'.

An error occurred trying to display the cluster information. Connection to the cluster is not allowed since you are not an administrator on the cluster node(s) Node-A, Node-B.

The strange thing is that Node-A is able to connect to the cluster and shows that Node-B is online and working. I am however, unable to migrate any resources over to Node-B. The live migration fails. The cluster has been working fine for several weeks. I did just install some Windows and HP Driver updates. Updated Node-A first and did not experience any issues. Then updated Node-B and after rebooting it started giving me this error. Has anyone run into this before? I am desperate for a fix.

Thanks!

I have a 3 node hyper-V cluster:

HW = 3 HP DL380 G7 servers

         -8 NICs, dual 4 port (2 NICS teamed=LAN-01, 2 NICS teamed = DMZ-01, Nic 5 = mgmt, Nic 6 = Cluster communication, 2 NICS teamed = LAN-02)

         -4 onboard iscsi enhanced ports

SW = Server Core R2 Ent.

        -Roles: Hyper-V

        - Features: Failover Clustering, Multipath IO, WOW64 Support

2 of the Servers work awsome, no complaints. However the third "identical" server is giving me issues. I get it all setup and everything is working, iSCSI is good to go. When connecting to iscsicpl I can connect and disconnect at will. Once I install theFailoverCluster-Core The iSCSI goes not responding and throws the following errors:

Log Name:   System
Source:    iScsiPrt
Date:     8/25/2011 4:50:10 PM
Event ID:   49
Task Category: None
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   Server-02.bdn.ca
Description:
Target failed to respond in time to a Task Management request.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="iScsiPrt" /><EventID Qualifiers="49152">49</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" /><EventRecordID>3644</EventRecordID><Channel>System</Channel><Computer>Server-02.bdn.ca</Computer><Security /></System><EventData><Data>\Device\RaidPort1</Data><Binary>000001000100000000000000310000C000000000000000000000000000000000000000000000000007</Binary></EventData></Event>

Log Name:   System
Source:    iScsiPrt
Date:     8/25/2011 4:50:10 PM
Event ID:   7
Task Category: None
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   Server-02.bdn.ca
Description:
The initiator could not send an iSCSI PDU. Error status is given in the dump data.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="iScsiPrt" /><EventID Qualifiers="49152">7</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" /><EventRecordID>3643</EventRecordID><Channel>System</Channel><Computer>Server-02.bdn.ca</Computer><Security /></System><EventData><Data>\Device\RaidPort1</Data><Binary>000080000100000000000000070000C00000000000000000000000000000000000000000000000000D0200C0690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary></EventData></Event>

Log Name:   System
Source:    iScsiPrt
Date:     8/25/2011 4:50:10 PM
Event ID:   20
Task Category: None
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   Server-02.bdn.ca
Description:
Connection to the target was lost. The initiator will attempt to retry the connection.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="iScsiPrt" /><EventID Qualifiers="49152">20</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" /><EventRecordID>3642</EventRecordID><Channel>System</Channel><Computer>Server-02.bdn.ca</Computer><Security /></System><EventData><Data>\Device\RaidPort1</Data><Binary>00007C000100000000000000140000C0000000000000000000000000000000000000000000000000690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary></EventData></Event>

Log Name:   System
Source:    iScsiPrt
Date:     8/25/2011 4:50:10 PM
Event ID:   39
Task Category: None
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   Server-02.bdn.ca
Description:
Initiator sent a task management command to reset the target. The target name is given in the dump data.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="iScsiPrt" /><EventID Qualifiers="49152">39</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" /><EventRecordID>3641</EventRecordID><Channel>System</Channel><Computer>Server-02.bdn.ca</Computer><Security /></System><EventData><Data>\Device\RaidPort1</Data><Binary>00007C000100000000000000270000C0000000000000000000000000000000000000000000000000690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary></EventData></Event>

Things I've tried:

using only one port and cable (Testing all the physical connections)

HP actually replaced the Motherboard thinking it might bad Hardware. (Like I said I have two other identical servers that work.)

I've reloaded this unit about 5 times trying to install components in different orders.

The second FailoverCluster-Core is uninstalled the iSCSI comes back to life!

If I use the the non-onboard NICS it actaully works. Looking for any suggetions on this one.

I am looking for a method to detect the status of a cluster resource from command line. This will be used as part of a script on all cluster nodes to determine where a specific group / resource is online before issuing further resource related commands. Unfortunately I do not have access to a cluster to try some commands. Can someone please give me the outputs for following commands or recomend a better command? I prefer to use the command line.

cluster group <group name> /status

cluster resource <resource name> /status

cluster node /status

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

Hello - I'm configuring MS Failover Cluster across two datacenters with different IP Ranges using server 2016. What firewall ports are needed to setup two nodes cluster and witness file share ?

Thanks

ad

I am looking for a method to detect the status of a cluster resource from command line. This will be used as part of a script on all cluster nodes to determine where a specific group / resource is online before issuing further resource related commands. Unfortunately I do not have access to a cluster to try some commands. Can someone please give me the outputs for following commands or recomend a better command? I prefer to use the command line.

cluster group <group name> /status

cluster resource <resource name> /status

cluster node /status

Thanks

Hi,

I have the following error and need clarification on the below solution in bold:

Event Id 1206 -

The computer object associated with the cluster network name resource 'Cluster Name' could not be updated in domain 'xxxxx.xxxx'. The error code was 'Password change'. The cluster identity 'ClusterGroup1$' may lack permissions required to update the object.

1 - Move CNO back to the Computers Container

2- Give the Cluster Node Computer Accounts Change Password permission on the CNO

3 - Take the Cluster Name Resource offline

4 - Repair Cluster Name Resource

5 - Bring Cluster Name Resource back online

Firstly, is there any implication?

Secondly if ClusterGroup1$ is my CNO (Cluster Name Object) then is my cluster node computer account the server nodes in the cluster? E.g. ClusterGroup1$ is the cluster, the nodes are hyperv01 and hyperv02, do I add hyperv01 and hyperv02 to clustergroup1 -- properties -- security?

Thank you.