We have a 2 node , majority disk, Windows 2008R2 failover cluster.   The active node is currently showing all resources and services on node A.   Node B is the inactive node.    we are about to perform a DataCenter shutdown test.   Our application manager would like us to make Node B inactive during the DataCenter Shutdown test but he believes we can make Node B active if we do it this way:

1.  power down Node B (inactive node)

2. power down Node A (active node)

3. power up Node A (active node)

4. power up Node B (inactive node)

By doing this way, he believes Node B will automatically become the Active node.

I do not believe this is correct.   I believe it has to failover to get Node B active.  So, my proposal is:

1.  power down Node A (active node)  This should cause a failover of resources and services to Node B

2. Once all resources and services are on Node B, power Node B down.   Now, both nodes are powered down and Node B is holding the cluster resources and services and is the Active node.

3.  Power up Node B (now the new Active node)

4. Power up Node A ( the new inactive node)

Which is correct?

Thanks in advance

Hello, I am experiencing random reboots on random servers during the week at random time... I did some research and I am suspecting that the "automatic recovery for application health monitoring" is what causes that but I am not sure... Can any expert make a suggestion? I am attaching a copy of the log that is being generated during the shutdown...

00001028.0000367c::2014/02/25-06:12:34.316 INFO  [RHS] Resource Virtual
Machine Configuration Computer-1 called SetResourceLockedMode.
LockedModeEnabled1, LockedModeReason0.
0000095c.00003230::2014/02/25-06:12:34.316 INFO  [RCM] HandleMonitorReply:
LOCKEDMODE for 'Virtual Machine Configuration Computer-1', gen(0)
result 0/0.
0000095c.00003230::2014/02/25-06:12:34.316 INFO  [RCM] Virtual Machine
Configuration Computer-1: Flags 1 added to StatusInformation. New
StatusInformation 1
00001028.0000367c::2014/02/25-06:12:34.316 INFO  [RHS] Resource Virtual
Machine Computer-1 called SetResourceLockedMode. LockedModeEnabled1,
LockedModeReason0.
0000095c.00003230::2014/02/25-06:12:34.316 INFO  [RCM] Computer-1:
Added Flags 1 to StatusInformation. New StatusInformation 1
0000095c.00001364::2014/02/25-06:12:34.316 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000020d0::2014/02/25-06:12:34.316 INFO  [RCM] HandleMonitorReply:
LOCKEDMODE for 'Virtual Machine Computer-1', gen(0) result 0/0.
0000095c.000020d0::2014/02/25-06:12:34.316 INFO  [RCM] Virtual Machine
Computer-1: Flags 1 added to StatusInformation. New StatusInformation 1
0000095c.00001364::2014/02/25-06:12:34.316 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000020d0::2014/02/25-06:12:34.320 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000020d0::2014/02/25-06:12:34.320 INFO  [GUM] Node 6: Processing
RequestLock 6:321
0000095c.00000f30::2014/02/25-06:12:34.321 INFO  [GUM] Node 6: Processing
GrantLock to 6 (sent by 3 gumid: 3827)
0000095c.000020d0::2014/02/25-06:12:34.321 INFO  [GUM] Node 6: executing
request locally, gumId:3828, my action: /dm/update, # of updates: 1
0000095c.000020d0::2014/02/25-06:12:34.321 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00001b00::2014/02/25-06:12:34.323 INFO  [RCM] HandleMonitorReply:
INMEMORY_NODELOCAL_PROPERTIES for 'Virtual Machine Computer-1', gen(0)
result 0/0.
0000095c.0000356c::2014/02/25-06:12:34.324 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
00001028.0000367c::2014/02/25-06:12:34.927 INFO  [RHS] Resource Virtual
Machine Configuration Computer-1 called SetResourceLockedMode.
LockedModeEnabled0, LockedModeReason0.
0000095c.0000356c::2014/02/25-06:12:34.927 INFO  [RCM] HandleMonitorReply:
LOCKEDMODE for 'Virtual Machine Configuration Computer-1', gen(0)
result 0/0.
0000095c.0000356c::2014/02/25-06:12:34.927 INFO  [RCM] Virtual Machine
Configuration Computer-1: Flags 1 removed from StatusInformation. New
StatusInformation 0
00001028.0000367c::2014/02/25-06:12:34.928 INFO  [RHS] Resource Virtual
Machine Computer-1 called SetResourceLockedMode. LockedModeEnabled0,
LockedModeReason0.
0000095c.00000140::2014/02/25-06:12:34.928 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00000c8c::2014/02/25-06:12:34.928 INFO  [RCM] HandleMonitorReply:
LOCKEDMODE for 'Virtual Machine Computer-1', gen(0) result 0/0.
00001028.0000367c::2014/02/25-06:12:34.928 INFO  [RES] Virtual Machine
<Virtual Machine Computer-1>: Current state 'Online', event 'VmStopped'
0000095c.00000c8c::2014/02/25-06:12:34.928 INFO  [RCM] Virtual Machine
Computer-1: Flags 1 removed from StatusInformation. New
StatusInformation 0
0000095c.00000c8c::2014/02/25-06:12:34.928 INFO  [RCM] Computer-1:
Removed Flags 1 from StatusInformation. New StatusInformation 0
0000095c.00000140::2014/02/25-06:12:34.928 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
00001028.0000367c::2014/02/25-06:12:34.928 INFO  [RES] Virtual Machine
<Virtual Machine Computer-1>: State change 'Online' -> 'Offline'
0000095c.00000140::2014/02/25-06:12:34.928 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000017a8::2014/02/25-06:12:34.929 INFO  [RCM]
rcm::RcmApi::OfflineResource: (Virtual Machine Computer-1, 1)
0000095c.000017a8::2014/02/25-06:12:34.929 INFO  [GUM] Node 6: executing
request locally, gumId:3829, my action: /dm/update, # of updates: 1
0000095c.000017a8::2014/02/25-06:12:34.930 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000017a8::2014/02/25-06:12:34.931 INFO  [RCM] Res Virtual Machine
Computer-1: Online -> WaitingToGoOffline( StateUnknown )
0000095c.000017a8::2014/02/25-06:12:34.931 INFO  [RCM]
TransitionToState(Virtual Machine Computer-1)
Online-->WaitingToGoOffline.
0000095c.000017a8::2014/02/25-06:12:34.931 INFO  [RCM]
rcm::RcmGroup::UpdateStateIfChanged: (Computer-1, Online --> Pending)
0000095c.000017a8::2014/02/25-06:12:34.931 INFO  [RCM] Res Virtual Machine
Computer-1: WaitingToGoOffline -> OfflineCallIssued( StateUnknown )
0000095c.000017a8::2014/02/25-06:12:34.931 INFO  [RCM]
TransitionToState(Virtual Machine Computer-1)
WaitingToGoOffline-->OfflineCallIssued.
0000095c.0000356c::2014/02/25-06:12:34.931 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00000de8::2014/02/25-06:12:34.931 INFO  [RCM] ignored non-local
state Pending for group Computer-1
0000095c.0000356c::2014/02/25-06:12:34.931 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
00001028.000025cc::2014/02/25-06:12:34.931 INFO  [RES] Virtual Machine
<Virtual Machine Computer-1>: Current state 'Offline', event 'Offline'
0000095c.0000356c::2014/02/25-06:12:34.932 INFO  [RCM] HandleMonitorReply:
OFFLINERESOURCE for 'Virtual Machine Computer-1', gen(0) result 0/0.
0000095c.0000356c::2014/02/25-06:12:34.932 INFO  [RCM] Res Virtual Machine
Computer-1: OfflineCallIssued -> OfflineSavingCheckpoints( StateUnknown
)
0000095c.0000356c::2014/02/25-06:12:34.932 INFO  [RCM]
TransitionToState(Virtual Machine Computer-1)
OfflineCallIssued-->OfflineSavingCheckpoints.
0000095c.00000c8c::2014/02/25-06:12:34.932 INFO  [RCM] Res Virtual Machine
Computer-1: OfflineSavingCheckpoints -> Offline( StateUnknown )
0000095c.00000c8c::2014/02/25-06:12:34.932 INFO  [RCM]
TransitionToState(Virtual Machine Computer-1)
OfflineSavingCheckpoints-->Offline.
0000095c.00000c8c::2014/02/25-06:12:34.932 INFO  [RCM]
rcm::RcmGroup::UpdateStateIfChanged: (Computer-1, Pending --> Offline)
0000095c.0000356c::2014/02/25-06:12:34.932 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00000c8c::2014/02/25-06:12:34.932 INFO  [RCM] moved 0 tasks from
staging set to task set.  TaskSetSize=0
0000095c.00000c8c::2014/02/25-06:12:34.932 INFO  [RCM]
rcm::RcmPriorityManager::StartGroups: [RCM] done, executed 0 tasks
0000095c.0000356c::2014/02/25-06:12:34.932 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00000de8::2014/02/25-06:12:34.932 INFO  [RCM] ignored non-local
state Offline for group Computer-1
0000095c.000017a8::2014/02/25-06:12:34.955 INFO  [GUM] Node 6: executing
request locally, gumId:3830, my action: /dm/update, # of updates: 1
0000095c.000017a8::2014/02/25-06:12:34.955 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.000017a8::2014/02/25-06:12:34.957 INFO  [RCM] HandleMonitorReply:
INMEMORY_NODELOCAL_PROPERTIES for 'Virtual Machine Computer-1', gen(0)
result 0/0.
0000095c.000017a8::2014/02/25-06:12:34.957 INFO  [GEM] Node 6: Sending 1
messages as a batched GEM message
0000095c.00000f30::2014/02/25-06:12:35.315 INFO  [GEM] Node 6: Deleting
[3:1497 , 3:1497] (both included) as it has been ack'd by every node

This is not the end of the world, but it's very annoying so I'm hoping somebody can explain what's going on or perhaps suggest some additional troubleshooting.

Here's the scenario: Server 2012 Core VM  with the file services role installed and running as a role on a Server 2012 Hyper-V failover cluster. IDE 0 is a standard VHDX in clustered storage. There are 2 pass through disks on SCSI targets 1 and 2. I proceed to attempt to add a 3rd pass-through disk:

1. Create a 750GB LUN
2. Mask the LUN to the cluster
3. Online the new disk on a cluster node
4. Initialize the disk on the node
5. Offline the disk
6. Using Failover manager, add the disk as new Available Storage in the cluster
7. Using Failover manager to modify the file server VM's settings, add the new storage to SCSI target 3
8. Using diskpart on the VM, clear the readonly flag from the disk

At this point, I was able to create a partition on the disk using new-partition with the -usemaximumsize flag, but I was unable to format it. It turns out the new partition size was 0 bytes. So I went back into diskpart and lo and behold, although the readonly flag is cleared, the "Current readonly status" on the disk is still yes.

To test the issue, I offlined the disk in the VM, removed it from the virtual SCSI chain, removed it from cluster storage and then onlined it in the owner node. I was able to partition it, format it and create an empty folder, so it is not flagged readonly at the host or SAN.

So I offlined it on the node and added it back to cluster available storage and then added it back to SCSI target 3 on the VM.

Again, I removed the readonly flag from the disk and again it cleared but the disks "current" status remained "Yes" and I was unable to manipulate the disk.

Stop/start vds did nothing and as this is a production server I could not restart it midday.

So I offlined the disk in the VM and removed it from SCSI target 3, then added it to SCSI target 4. This time, when I online it in the VM and use diskpart to clear readonly, both readonly and "current" readonly clear just fine and now the pass-through disk is operating as expected alongside the other 2 pass-through disks on the server.

Any ideas what went wrong in all this or how I can clear SCSI target 3 for another disk without having to restart the VM?

I am configuring Cluster-Aware Updating on a 5-node cluster. At this time I'm not enabling Self-Updating mode. Instead I'm going to use Remote-Updating mode. In the Cluster Aware Updating console I ran Analyze cluster updating readiness. I have two warnings that I can safely ignore (about local machine proxy and CAU clustered role not being enabled). But there is an error that I'm stuck on. Rule ID 13 gives me an error saying, "The configured CAU plug-in must be registered on all failover cluster nodes."

The resolution says to ensure that the configured CAU plug-in is inatlled on the all cluster nodes. I ran Get-CauPlugin | fl -Property * on each node and each of them returned the expected Microsoft.WindowsUpdatePlugin and Microsoft.Hotfix.Plugin listings.

Any ideas on how I can troubleshoot and get the error cleared?

As I was reading the posts it appear that ESXi 5.1 does support MSCS on W2012 server.

We are trying to setup a SQL 212 cluster (not always on bc we don't have Enterprise license) on two vm hosts running W2012 R2 server.

I assume the scenario above is supported on ESXi v5.1, but I am not sure if setting up a SQL 2012 cluster on Vmware is a good idea vs. using a physical server with direct attached disks.

Is there a good documentation for the setup?

Thanks again

----------------------------

Hi there,

I am having difficulties creating a new server 2012 R2 failover cluster in our domain.  We have a working 2008 R2 cluster that has been running fine for years now.

I have tried on different hardward with single nodes and multiple nodes when making the cluster.  I can see the new cluster account is created in AD and I have triple checked all permissions required to create the cluster.  The resulting errors are:

Any suggestions on what could be causing this?  My only current route of investigation is a currently missing domain controller account in AD as I assume this must be AD related.

I have a 2node failover cluster. When I power down a node that has the SQL server instance and resources, all the resources and service failover to the other node.   When I see that all the resources and service report "online" I then power that node.  I am being told that this is improper because failover may not have completed.  Is that correct?

Also, in our 2 node failover cluster is there a proper sequence to restarting the powered down nodes?

Hi

I am testing san controller failover. It takes around 2 mins for the second controller to come online after the first has failed.

There are some registry settings that can be configured to increase disk timeout but they don't seem to work when failover clustering is enabled.

I am testing this on a Hyper-V 2012 R2 failover cluster (regular clustered disks and CSVs - the same issue occurs on both)

I have changed the following registry settings 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk\TimeoutValue = 240

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mpio\Parameters\PDORemovePeriod = 240

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e97b-e325-11ce-bfc1-08002be10318}\0003\Parameters\LinkDownTime = 60

But as soon as the second controller comes up the cluster registers a failure of all the clustered disks and restarts the VMs. Just wondering whether the 2nd controller coming online is somehow triggering the clustered disk failure.

I am seeing the following in the event log.

Connection to the target was lost. The initiator will attempt to retry the connection.

\Device\MPIODisk3 is currently in a degraded state. One or more paths have failed, though the process is now complete.

Ownership of cluster disk 'Cluster Disk 1' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

Thanks

Daniel

Hi,

We experience some strange problem with our SQL Cluster. First I can't connect to the SQL Instance using SSMS.

Using wireshark showing a lot of TCP Retransmission. I using iperf to test the speed, and notice that with the ip address of the Cluster host, the connection is good. But using the Ip address of the Named Instance of SQL, the connection speed is very bad.

Hope somebody can help me figure this out.

I have 2 2008 R2 physical servers on the same subnet and they have been using NLB for the past 1.5 years.  We had a firewall issue and I took one of the servers out of the cluster to do testing, while the other main server (priority 1) was left serving up the virtual IPs. The main server continues to work properly.

The servers have 2 NICs, one for NLB and one just for regular traffic.  The NICs also have their own IP addresses and then there is a cluster IP and 2 virtual IPs.

Error:

When I try and add the second server to the cluster, I first connect to existing cluster which works fine.  Then I do a Add Host to Cluster, and type the name of the server and select the NLB NIC.  It sees the other server and it seems to start the process, however soon after the NLB NIC goes to having internet access to a "enabled" state and the gateway gets taken out of the settings.  I try to add it back, but as soon as I get out of the settings it disappears again.  NLB manager tells me: cluster ip address (192.#.#.#) not added to tcpip properties.  It lists this error 4 times, once for each IP (2 virtual, 1 cluster, and then once for the dedicated NLB NIC IP).  I have also tried adding all virtual IPs to the NLB NIC's settings and still same exact error.  Registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces    -even reg looks good.

Any help would be appreciated.  If I can't get any resolution my next step is going to be to delete the NLB cluster on the main server and recreate it....but this requires downtime and got to make sure it comes back up!

~I have created a 2 node cluster with server 2012 R2, each node has a 100 Gb disk but when i add this to the cluster it cant bring them online. the windows server is are located on a VM ware server. At the start of the process the disks are online, when the cluster trys to ad the disks i get this

the disks show offline and the server: file server 

if i try to get it online it says it took more than usual and still will fail

Hi,

following scenario - Migrating resources from Win2003 Cluster to Win2008 Cluster using Cluster Migration Wizard. Migrators user account added to Administrators group on both Win2003 nodes. Did the same on 5 clusters before with no issues. On last one we are getting following error:

"Failed to connect to the quorum resource"

No matter if we try to connect to Cluster name or Cluster node names.

Unable to find such an error message on the web.

Any Idea?

Thanks.

Hi,

I am not able to stop/ break the TCP/IP connection, even after stopped the cluster node configured in NLB.

Also able to see the TCP/IP connection while doing netstat though command prompt

Currently I have a Windows 2012 R2 Hyper-V Failover cluster.

When the cluster aware updating kicks in, everything works fine, except when both nodes have completed their updates, my vms are all situated on the first node that was updated, ie when the second node entered it's updating phase, it migrated all vms.

I'm sure when I was testing last year, the updating process remembered where the roles resided and put them in the correct place post update.  I know I can set Preferred Owners, but wasn't sure whether that was best practice after reading a blog about"potential" issues last year.

So in a nutshell, how can I ensure that the roles are placed correctly post cau?

Regards

One of my customers has a Windows Server 2008 R2 cluster for an Exchange 2010 Mailbox Database Availability Group.  Lately, they've been having problems with one of their nodes (the one node that is on a different subnet in a different datacenter) where their Exchange databases aren't replicating.  While looking into this issue it seems that the problem is the Network Manager isn't started because the cluster service is failing.  Since the issue seems to be with the cluster service, and not Exchange, I'm asking here. 

When the cluster service starts, it appears to start working, but within a few minutes the following is logged in the system event log.

FailoverClustering

1572

Critical

Cluster Virtual Adapter

Node 'nodename' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. ...

It seems that the problem is with the 169.254 address on the cluster virtual adapter.  An entry in the cluster.log file says: Aborting connection because NetFT route to node nodename on virtual IP 169.254.1.44:~3343~ has failed to come up. 

In my experience, you never have to mess with the cluster virtual adapter.  I'm not sure what happened here, but I doubt it has been modified.  I need the cluster to communicate with its other nodes on our routed 10. network.  I've never experienced this before and found little in my searches on the subject.  Any idea how I can fix this?

Thanks,

Joe

Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

Hi. 

I would like to configure a DCHP server failover on Windows 7.

On a part I have a windows 2008 R2 server which currently leases adresses. I recently had a crash of this server.

In order to insure avaibility of dhcp on the next crash, I whish install a DHCP server freeware and configure a script powershell to start dhcp on failover of the first one.

An other tip is to split the pool of leasing. Is it possible to do it with a windows 7 software?

Thanks a lot for your help.

I have a 3 node failover cluster that I think needs an IP address change because the current cluster IP address is on my Node Management network.

Here is my network config:

FC Internal Communication
10.24.24.0/24, Cluster Use: Internal

FC Live Migration
10.25.25.0/24, Cluster Use: Internal

iSCSI Traffic
10.23.23.0/24 Cluster Use: Disabled

Node Management
10.20.20.0/24 Cluster Use: Enabled (also allows clients to connect

The cluster IP Address is 10.20.20.200, which of course means it sits on the Node Management network.

I want to disallow cluster use of the Node Management network, but that network hold the IP Address of my failover cluster, so as soon as stop allowing cluster network communication on that network, my cluster IP Address fails

Is it best practice to have the cluster IP address set on a network dedicated to cluster communication?  If so, how can I change the address of a running cluster?

Thanks for any help you can offer,

hi

i have created fail over cluster with windows server 2012

i have a DHCP vm 

when i choose roles>> dhcp role to configure that DHCP vm it says no dhcp server found!!

so my question is isnt it possibel to make a DHCP vm as DHCP fail over role ??

but if i install DHCP role in physical machine then it shows availabel in cluster role

istiaq

I have a two-node Hyper-V 2012 Core Server cluster. Initially, the cluster was working fine and I was able to do live migrations with no problem. I first realized that something had gone wrong when I was attempting to move a VM's storage to the Cluster Disk. When I right click on the VM and select Move > Virtual Machine Storage, the bottom left area of the "move storage" screen says "Loading..." forever and never displays the cluster storage. This happened once before and I was able to correct the issue by taking the Server Name resource offline and doing More Actions > Repair. However, if I try a repair now I receive the following error messages:

"There was an error repairing the active directory object for 'Cluster Name'. Error Code: 0x800713b8. The cluster request is not valid for this object". 

I have verified that the cluster name Active Directory object (CCSDCluster) still exists and each node as well as itself has full permissions to the object. What I am not certain of is whether the object is still in the same Organizational Unit as it was originally. After the failed repair attempt, I am able to bring the Server Name resource back online successfully.

In addition, I am continually receiving cluster event errors indicating the following:

"Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server." 

Each of the two nodes has multiple NICs configured. One for management, one for guest OSs (Hyper-V virtual switch is configured to use this NIC and not allow management OS access), and two for iSCSI (for redundancy and multi-path). Live migration is set to only use the management NICs. The management NIC on both nodes is configured with valid DNS servers. The CCSDCluster DNS entry has full permissions for both nodes and itself.

Any suggestions on what to try would be greatly appreciated. Thank you!