How to configure Microsoft MultipathIO Configuration Tool for Compellent SAN attached storage

I have a HP Proliant DL380 G6 Server with x2 HP FC1142SR 4GB PCI-e FC cards installed running Windows Server 2008 R2.  Compellent SAN attached storage has been successfully presented to the server and test data copied to the SAN attached disks within Windows.  For FC resiliency I've installed the feature Microsoft MultipathIO onto the server.  I've configured MultipathIO as per MS Technet article http://technet.microsoft.com/en-us/library/ee619778(WS.10).aspx.  In the MPIO properties dialog box I've added the device hardware ID's "COMPELNTCompellent Vol" & "COMPELNTCompellent Vol1" after a reboot the MPIO tab has appeared within the SAN attached disks in windows disk management.  Within the MPIO tab the device is only showing 1 path and not 2 as I would expect.  I've attempted testing resiliency by removing one of the fibre cables and the failover does not work as some of the SAN external attached disks disappear from Windows.  I've tried MPIO policies Round Robin and Fail Over only both without success.

Does anyone know how to configure Microsoft MultipathIO using compellent storage?  Any help will be much appreciated.
LG_ITAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
LG_ITConnect With a Mentor Author Commented:
Issue was escalated to Compellent who confirmed that a change to the server object to be MPIO aware on the Compellent SAN was necessary.  Once this change was made the issue was resolved.
0
 
DavidPresidentCommented:
Were you aware that not all Compellent systems support MSFT's MPIO stack?

You didn't mention the specific model you have, so I can't give you a link to the setup guide, but if you just click o this link, you will find howto docs for whatever model you have.

http://www.compellent.com/search-results.aspx?searchtext=multipath

In general, setting this up properly requires qualified HBAs, registry settings, and NVRAM changes to your HBA which may not be default.  If you are using QLOGIC or EMULEX, in particular, you probably have to use their Java-based utility to make some changes to expose both paths, and remove the default qlogic/emulex MPIO software.    Also, the drivers, firmware, and BIOS typically need to be at certain revisions.

Back in early 2000s I worked with some vendors trying to get mpio working with a few HBAs, and there is a LOT that has to be done for anything other than dual-ported FC JBOD disks.  The subsystem itself needs firmware that supports it because MPIO sends some low-level commands that may not be supported by your hardware.
0
 
LG_ITAuthor Commented:
Issue was escalated to Compellent who confirmed that a change to the server object to be MPIO aware on the Compellent SAN was necessary.  Once this change was made the issue was resolved.
0
All Courses

From novice to tech pro — start learning today.