When mapping a volume from my SAN to a Server 2008 R2 Host, it appears twice, Multipath is configured and installed, what am i doing wrong?

Hiya Everyone,

Just looking for some advice.  Its been an issue for a while, and although i have a workaround, i want to know the opinion of someone who knows a little more about this.

I have some HS22 Blades, in a BladeCenter E Chasis, which connect to a V7000 IBM SAN.  

My problem is, i have 2 Fibre cards in each Blade.  These have two viewable mac addresses in the Storage Explorer.  If i map both MAC's to a host, the volume will show up twice.  I have the Multipath I/O installed and the HBA drivers setup.  

Im not sure if this is a failover feature im looking for outside of the functionality of this system, or if i am doing something wrong.  

We had a technical consultant come in, and only map 1 MAC address to the Host, meaning it was showing once, but multipath doesnt appear to work.  Because if you pull out a fibre connection, the systems go offline.

Any advice on this would be very much appreciated.

Software:

Windows Server 2008 R2 SP1
demon90kAsked:
Who is Participating?
 
serchlopConnect With a Mentor Commented:
I mixed the info in the past post, please ignore it.

Installing on Windows Server 2008 R2
Microsoft has deprecated the servermanagercmd command for Windows Server 2008 R2, so use the
ocsetup command instead.
1. open a command prompt window and run the following command:
ocsetup MultipathIo /norestart
mpclaim -n -i -a
NOTE: The mpclaim -n option avoids rebooting.
The MPIO software is installed.
If you plan on using MPIO with a large number of LUNs, configure your Windows Server Registry to
use a larger PDORemovePeriod setting.
If you are using a Fibre Channel connection to a Windows server running MPIO, use a value of 90
seconds.
If you are using an iSCSI connection to a Windows server running MPIO, use a value of 300 seconds.
See “Long Failover Times When Using MPIO with Large Numbers of LUNs” on page 20 for details.
Once the MPIO DSM is installed, no further configuration is required; however, after initial installation,
you should use Windows Server 2008 Device Manager to ensure that the MPIO DSM has installed
correctly as described in “Managing MPIO LUNs”.

The Windows Server 2008 Device Manager enables you to display or change devices, paths, and load
balance policies, and enables you to diagnose and troubleshoot the DSM. After initial installation of the
MPIO DSM, use Device Manager to verify that it has installed correctly.
If the MPIO DSM was installed correctly, each SAN storage volume visible to the
host will be listed as a multi-path disk drive.

To verify that there are multiple, redundant paths to a volume, right-click the Multi-Path Disk Device and
select Properties.

Click the MPIO tab to view the MPIO property sheet, which enables you to view or change the load
balance policy and view the number of paths and their status.

Full PDF is in http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02520790/c02520790.pdf



0
 
serchlopCommented:
This happend to me on HP blade server and I discover that the problem was the driver that I was using. You have to use the windows integrated multipath driver in windows 2008, not the drivers from HP.
0
 
serchlopCommented:
The next page (http://h18000.www1.hp.com/products/quickspecs/13551_div/13551_div.html) has some information for P2000 G3 SAN for HP has it says:

Path failover (MPIO)       

MPIO for Windows provides a single multi-path solution for HP P2000 G3 Modular Smart Array on HP servers.
Support for Windows 2003 and Windows 2003 R2 operating systems is provided by HP MPIO Full Featured DSM. For the P2000 G3 this version is 2.6.1.7 or greater.
Support for Microsoft Windows 2008 is bundled within the operating system
Support for Linux distributions is with Device Mapper 4.4.0 or greater.
Support for HPUX is native multipathing in HP-UX v3 and PV-Links in HP-UX v2.
        



Maybe this link could help.
http://technet.microsoft.com/en-us/library/ee619778%28WS.10%29.aspx
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
demon90kAuthor Commented:
So it isn't a limitation?  I can have 2 fibre nodes mapped to the host, and it "should" use only one connection, and the other as a failover, as long as the driver and configuration in windows is done correctly?
0
 
serchlopCommented:
Actually you can use MPIO for your SAN, but you have to set up with Windows 2008 R2, not with MPIO driver for the manufacturer. This apply to MSA P2000, but I think that should apply to your SAN too.

Uninstall the drivers for the manufacturer MPIO.

Installing on Windows Server 2008 R2
Microsoft has deprecated the servermanagercmd command for Windows Server 2008 R2, so use the
ocsetup command instead.
servermanagercmd -install multipath-io
mpclaim -r -i -d "HP P2"
HP StorageWorks MSA System MPIO DSM Installation Guide 7
1. open a command prompt window and run the following command:
ocsetup MultipathIo /norestart
mpclaim -n -i -a
NOTE: The mpclaim -n option avoids rebooting.
The MPIO software is installed.
2. If you plan on using MPIO with a large number of LUNs, configure your Windows Server Registry to
use a larger PDORemovePeriod setting.
• If you are using a Fibre Channel connection to a Windows server running MPIO, use a value of 90
seconds.
• If you are using an iSCSI connection to a Windows server running MPIO, use a value of 300 seconds.
See “Long Failover Times When Using MPIO with Large Numbers of LUNs” on page 20 for details.
Once the MPIO DSM is installed, no further configuration is required; however, after initial installation,
you should use Windows Server 2008 Device Manager to ensure that the MPIO DSM has installed
correctly as described in “Managing MPIO LUNs” on page 8.

Maybe you need to restart the server twice to function.
0
 
demon90kAuthor Commented:
I will try this and let you know how i get on.  Thanks so much :)
0
 
demon90kAuthor Commented:
Brilliant, all working now.  I ended up using the IBM UpdateXpress software to update the FC firmware and drivers.  Because even using Windows ones weren't working.  But all appears fine.  I suggest using the UpdateXpress package to make sure you get all the latest editions of software :)

Thanks once again Serchlop for pointing me in the right direction.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.