Posts tagged Hyper-V

In an HP Storage Works EVA Best Practices document published in February 2010, we were advised not to use the HP MPIO DSM with Cluster Shared Volumes, but as an alternative to use Microsoft Native MPIO only. This was unfortunate because the HP MPIO Full Featured DSM allows for better visibility and control of the multiple paths between Hyper-V R2 host and its storage.

During a storage change in one of our datacenters, we noticed that not all nodes were able to see all CSV disks. The Hyper-V R2 cluster we were working on has eight cluster nodes. On another occasion, one of my cluster MVP colleagues, Edwin van Mierlo, had explained to me that in a Hyper-V R2 cluster with CSV, the number of SCSI registrations can add up very quickly.

In our case we work with an 8-node Hyper-V R2 cluster with HP BL490c blades and HP EVA6400 storage array with 20 LUNs.

Each CSV LUN counts as one SCSI Reservation. The coordinator node makes a persistent reservation for each LUN it owns in the cluster. Because all other nodes in the cluster must be able to read/write to that same LUN (CSV with Direct I/O), they must register all possible paths to that LUN, dependent on one of the following two registration methods:

1. Storage that require a registration per path
2. Storage that require a registration per Initiator

The software on the host will send a registration over all of the paths. So the Storage will receive a registration REGISTER_ IGNORE_EXISTING_KEY on all paths. It is then up to the storage to do the correct thing.
http://www.freepatentsonline.com/EP1246060.html

In a two node cluster this would mean:

Example: 2 node cluster, 2 Initiators per node, 4 paths per Initiator, 1 Disk (CSV) :

For Storage "class" A, per path registration, you get:

• 16 registrations (4 paths x 2 initiators x 2 nodes x 1 disk)
• 1 reservation (from 1 node in the cluster that owns the disk)
  

For Storage "class" B, per Initiator registration, you get:

• 4 registrations (2 nodes x 2 initiators)
• 1 reservation (from 1 node in the cluster that owns the disk)

In an 8-node cluster with 20 CSV disks, the number of registrations go up quite significantly:

For Storage "class" A, per path registration, you get:

• 1280 registrations (4 paths x 2 initiators x 8 nodes & 20 disks)
• 20 reservations (from all nodes owning an online disk)

For Storage "class" B, per Initiator registration, you get:

• 16 registrations (8 nodes with 2 initiators)
• 20 reservations (from all nodes owning an online disk)

I am not sure what method HP uses for HP EVA, but I hope it is “class” B. If anyone knows, please let me know!

While searching for other cases with CSV problems in HP EVA environments I struck on this important piece of news:

The author of the blog refers to a newly released version of HP MPIO Full Featured DSM v4.01 which fully supports Cluster Shared Volumes with Windows Server 2008 R2

See the original blog: http://blogs.technet.com/b/hugofe/archive/2010/06/18/hp-dsm-support-with-csv.aspx

Important parts:

“if there is a stray reservation on a disk device, the device becomes inaccessible to the host systems connected to it. This is because the strong reservation type (persistent reservations) supports load balancing in clusters. You can use the persistent reservations clear utility that comes with HP MPIO EVA DSM package to remove the stray reservations.”

“Note: For Microsoft Windows Server 2008 and Windows Server 2008 R2 Failover cluster to work properly, set the array host mode on the HP CommandView EVA to ‘Microsoft Windows LH’ or set custom host mode to “00000004198009A8”.

In the CommandView we use (v9.2.1) we don’t have the Microsoft Windows LH host mode option.

If you issue the hpprutil devices command you can see this:

You can clear the reservation with hpprutil clear devices

We finally seem to have some light at the end of the tunnel about Hyper-V R2 clusters and mysteriously disappearing cluster shared volumes.