Start a Conversation

Unsolved

This post is more than 5 years old

48849

May 26th, 2011 12:00

Need to determine mapping between cluster shared volumes and SAN LUNS

I'm using hyper-v with cluster shared volumes. All virtual machine disks are stored on an MD3000i SAN. I need to determine which cluster disks in hyper-v map to which virtual disks (luns) on the SAN.

 For example, in Failover Cluster Manager I can view all of my cluster shared volumes which appear as "Cluster Disk 1 C:\ClusterStorage\Volume1", etc. I have 24 csv's. On my MD3000i, I have 24 virtual disks configured. These are labled as SASVOL1, SASVOL2, SATAVOL1, SATAVOL2, etc. The disks were split up proportionally so many are the same size.

There is a one to one mapping between the csv's and the virtual disks on the san, but I'm having difficulty figuring out which csv lives on which san lun. In disk management on the hostnodes all the disks are labled the same "New Volume".

We're having some performance issues with our vm's and I'm trying to determine if we have multiple high volume servers sharing drive space in the same disk group on the san.

 

Any assistance in figuring this out would be helpful.

 

Thanks in advance

5 Posts

May 26th, 2011 15:00

We actually got it figured out over here by doing the following:

On a hostnode (we run win2008R2 core), run DISKPART and select a disk. For example

DISKPART> select disk 3

Retrieve disk details

DISKPART> detail disk

this will list the Disk ID as well as the LUN ID on the SAN

Next, open PowerShell on the hostnode and import the failover cluster module

Import-Module FailoverClusters

Run the following commands for each cluster disk you have: In this example it's running agains Cluster Disk 4

$csv = Get-ClusterSharedVolume -Name "Cluster Disk 4"

next run:

Get-ClusterParameter -InputObject $csv

This will give you the Disk Signature for the cluster disk you ran the command against.

The Disk Signature is the same as the Disk ID you discovered using the DISKPART command, which also gives you the LUN that disk is on in the SAN. Now it's just a matter of matching everything up.

No Events found!

Top