The Deployment Bunny

OS Deployment, Virtualization, Microsoft based Infrastructure…

  • Archives

  • Meta

Cluster Shared Volumes and iSCSI could be a problem

Posted by Mikael Nystrom on October 26, 2009

So you have decided to run Windows Server 2008 R2, using the new Clustered Shared Volumes features and you are going to have a SAN based on iSCSI. Good for you, then you will properly also want to set it up according to best practices, hmm lets see…

Two physical servers, with 4 NIC’s that is perfect. I use one NIC for management, one NIC as the Hyper-V network switch and the other two NIC’s as iSCSI NIC’s and as a best practices you bind off everything except for IP on the iSCSI NIC’s

THAT WILL MAKE Cluster Shared Volumes to FAIL !!!

Microsoft require you to enable the “Microsoft Network Client” and “File and Printer Sharing for Microsoft Networks” on all network that takes part of the cluster, in other words you have two choices here.

1. Do not use the iSCSI NIC’s as “cluster NIC’s”, in other word make sure that they are listed as disabled for cluster use (You cannot use them for Internal or Client use). Bad thing about this is that in that case they cannot be used as heartbeat either.

2. Enable “Microsoft Network Client” and “File and Printer Sharing for Microsoft Networks” on the iSCSI NIC’s, (All NIC’s) bad thing about that is that you will have some traffic on the iSCSI network that is “unwanted”.

For some reason there is no KB article that I have found on this little issue, the problem is that it works perfect as long as you do not use the clustered shared volumes and Live Migration, if you just use Quick Migration it works. It is easy to see if there is anything wrong with the configuration, just open c:\clusterstorage\volume1 on one of the nodes, then try to open the same path on the other node. If it freezes up, you know what the problem is. Option one or option two. I usually take option number two

There are two other articles about this issue, sorry to say, not in English.

Hungarian – http://www.microsoft.com/hun/technet/article/?id=a20a6494-645d-4ee6-993b-f0e341cfdffc 

German http://www.server-talk.eu/2009/07/10/error-cluster-shared-volume-is-no-longer-available-mit-hyper-v-failover-cluster/

If you open the event log, you will find this:

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Event ID: 5120
Task Category: Cluster Shared Volume
Level: Error
Description: Cluster Shared Volume ‘Volume1′ (’Cluster Disk 1′) is no longer available on this node because of ‘STATUS_BAD_NETWORK_PATH(c00000be)’. All I/O will temporarily be queued until a path to the volume is reestablished.

One Response to “Cluster Shared Volumes and iSCSI could be a problem”

  1. […] znalazłem ciekawy art, w którym jest opisane podobne zachowanie – nie mój scenariusz ale warto się zapoznać […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: