Multipath support for EVA 6000

[stefano colombo_1]

We have a customer with an EVA 3000 which has to be migrated to an EVA 6000.
Connected to the eva 3000 are several windows 2K/2K3 clusters with secure path 4.0c/4.0csp2.

Reading the latest securepath RN I have found on the web site I 've read the HSV200( EVA 6000) is not supported .
Is that true ?
Is MPIO the only supported multipath software for EVA 4/6/8K ?

Thanks a lot
Stefano

[Luk Vandenbussche]

Hi Stefano

Yes, you need to replace securepath by MPIO

[stefano colombo_1]

Hello ,
thanks for the reply . I was wondering about this link http://h18006.www1.hp.com/storage/evasoftware.html
Shouldn't HP correct the statement at the half of the page , which I report below ?

HP StorageWorks Secure Path Software


Challenge: Data availability and performance
Ideal use: Automatic failover, automatic load balancing
Supported on: HP StorageWorks EVA4000/6000/8000, EVA3000, EVA5000, MSA1000, EMA16000, EMA12000, and MA8000 disk arrays

[stefano colombo_1]

I've also another question .
As we have to migrate the data from the 3k to the 6k storage the hosts should accesse both at the same time .

I've looked at the MPIO BASIC ( the only supported by EVA 3k with vcs 3.x ) but it doesn support EVA4/6/8 K .

Will I have to install two MPIO versions ? Where can I find the MPIO for 4/6/8K ? The following link is only for 3/5K
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=421494&prodTypeId=18964&prodSeriesId=421492&swLang=8&taskId=135&swEnvOID=1005

Thanks

[Luk Vandenbussche]

Stefano,

I advise you to work in a single path solution during migration

- NO SP
- NO MPIO
- Modify your zoning on the san switches to single path

[Ashley Clark]

Stefano

I believe for the duration of the migration, both pieces of software will work concurrently, one only seeing the 3000 and the other only seeing the 6000. Unfortunately my co-worker who has done this is not in the office but we had a similar issue with EVA6000's and 5000's being presented to the same machine.

[stefano colombo_1]

HI ,
thanks all for the advices .
Regarding the MPIO software . I've only found the one for 3000/5000 even following the link from the eva 6000 page
Is it the same ?

[Uwe Zessin]

Watch out! There is now a full-featured MPIO (V1.00.00) for the EVA3000/5000, but it requires VCS V4 firmware. Do not upgrade to V4 without serious planning.

[stefano colombo_1]

Yes , I know it . Thanks for point it out anyway.
The question is still valid .Is there a different version of MPIO software to support EVA 3000/5000 nd eva 4/6/8K ?

The release notes of the MPIO I've downloaded talks only about 3/5K

thanks
Stefano

[Uwe Zessin]

After browsing some notes I think the situation is this:
- EVA3/5000 - VCS V3
-- basic MPIO 1.01
--- not compatible with Secure Path
--- compatible with EVA4/6/8000 MPIO
-- Secure Path V4.0C SP2
--- compatible with EVA4/6/8000 MPIO

[Stephen Kebbell]

Hi,

you should be able to use SecurePath 4.0C, SP2-1 for your EVA3000 and MPIO Full-Featured 1.00.02 for the EVA6000, both software packages running on the same hosts and accessing the storage systems via the same HBAs. The latest versions of SecurePath and MPIO can co-exist with one another. You don't need MPIO for your EVA3000. SecurePath will not do anything with EVA6000 LUNs.

MPIO for EVA6000 is here:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=421494&prodTypeId=12169&prodSeriesId=421492&swLang=8&taskId=135&swEnvOID=1005

You want the third and fourth downloads (3.5MB and 33.6MB, respectively) for the MPIO DSM and the DSM Manager MMC Plug-in.

You may want to update your HBA drivers so that the EVA6000 Command Console LUNs are correctly recognised by device manager, and so that you're at an officially supported driver version.

Regards,
Stephen

[stefano colombo_1]

Hi Stephen,
I've installed a server to test the configuration.
- First I installed securepath 4.0c sp2-1 and presented a LUN from the eva 3000 ( to simulate our actual condition.
- Then I presented the EVA6000 storage ( no lun presented to the host ) . The eva controllers are recognized as HP HSV200... with a question mark .
- I skipped the driver installation.
- Installed the MPIO FF 1.002
- rebooted

The eva 6000 controller are still not correctly recognized

[Del_3]

Stefano, A couple of thoughts: I always present the first lun on a new host with no multipathing software. On Windows you should see four paths and four unpartitioned Windows disks (assuming 2 FCA's,etc). This ensures you have your zoning correct and hosts properly defined in the EVA. Otherwise its not so easy to see an error. Then install the multipathing software, reboot and you will see only one disk partition.

That said the PnP yellow question marks can be ignored as the EVA contollers dont need a "driver" per se. So if you see the HSV200 under Dev Manager the host "sees" the EVA 6000.

If Disk Manager doesnt show the EVA 6000 lun, and you have rebooted - I would zone out the EVA 3000 and check it again. Next I would uninstall all multipath and verify the EVA6000 partition is displayed four times or maybe only two in your case with only one HBA connected to the 6K.

I have seen rare cases where SP and MPIO get whacked and a reinstall fixes it.

Good Luck

[stefano colombo_1]

Hello ,
it's true that I could ignore the unrecognized EVA controllers , in fact I can see the presented LUNs , but I'd rather complete the installation the correct way.
I've always installed the EVA making their controllers being recognized and I'd like to be able to do the same with the EVA 6000.
The problem is that even installing only the MPIO software the EVA 6000 controller isn't recognized ( as it should be ) .

I wonder if anyone which has installed an EVA 6000 has had my same problems
Thanks

[stefano colombo_1]

Hello ,
here my findings.
If SP 4.0c is already installed on the Host when the EVA 6K is been presented the controller is not correctly recognized even when the MPIO is installed , but the multipath works perfectly.
If MPIO is installed on a host where SP has never been installed the EVA 6K controller is correctly identified and multipath works well.
If the EVA6K has been presented to a host with SP4.0csp2 its controllers are not correctly recognized even uninstalling the SP software and reinstalling MPIO .

Stefano

[Del_3]

Stefano, I am not clear now what you mean by unrecognized controllers. If you are talking only about the Windows PnP yellow question marks then the issue is only cosmetic. If you see 4 HSV200 controllers under device manager as Unknown Devices then the host recognizes the controllers fine! If you want to make the question marks go away then do a driver update and manually select SCSI Controllers and then Unknown Manufacturer. This will register the device with Windows. MPIO or Secure Path have nothing to do with recognizing the controller on the hardware level or providing psuedo drivers for Windows.

I have not tried to apply Sec Path and MPIO to the same host. Sounds like a support call is in order.

Let us know how it works out.

[stefano colombo_1]

Hi ,
yes I meant the yellow question mark.
The problem might seems cosmetic but each time the system reboot the new hardware wizard pops up , even if I check the " don't ask .." option.
I understand that SP and MPIO shouldn't be related with the problem , however only when I install them the controllers are cleared out from the question mark.

I didn't try the workaround of configuring them as unknown manufacturer , I'll do as soon as I can .

Installing SP40cSp2 and MPIO worked for me
Thanks
Stefano

[Del_3]

Interesting, I now understand. I have seen this behavior before but never had time to really dig into it. It has happened on ocassion for several generations of EVA and VCS . I suspect its a Windows "issue" related to ???? perhaps a SP or hotfix. Is this 32 or 64 bit Windows? I have seen this on HP NSR (tape routers) when they change the firmware and the fix is to get the updated inf file.

Did you mean that SP and MPIO work when installed in that order but not MPIO 1st and SP 2nd?

[Del_3]

Stefano, Is this server an HP and was it built with the latest Smartstart? If not this could explain your PnP issue.

[Farid Abizeid]

Hi,

I would like to mention that ? for HSV in dev manager may be caused by wrong securepath 4.0c; there use to be SP4.0c workgroup edition (for MSA) and SP4.0c enterprise edition (for MSA & EVA)
I have once used the workgroup edition by mistake for an EVA3000 and got these interrogation mark in dev manager once i reinstalled the enterprise edition, the HSV were recognized

Regards,
Farid

[Stephen Kebbell]

Hi,

all you really need to get rid of the question marks in device manager is the inf file from the newest HBA drivers (or just update your HBA drivers to the latest version). The inf file has information on how to recognise HSV200/210 Command Console LUNs.

Regards,
Stephen

[Del_3]

Stephen can you support your statement?

[Stephen Kebbell · Accepted solution]

Hi Del,

in HBA Driver Packages from HP:
cp004709.exe (Contains Emulex SCSIport 5.5.10a10 Driver). This package has a file HSGCCL.inf, where only HSG60/80 and HSV100/110 descriptions are present (you won't find HSV200 in this file, or any other inf file in the package)

cp005600.exe (Contains Emulex SCSport 5.5.10a11 Driver). There is no HSGCCL.inf, but an inf called SACD.inf. This has information on HSG60/80, HSV100/110, and HSV200/210 CCLs.

At the end of each of these files is a [Strings] section, all the descriptions are there you can see for yourself if you have the 2 versions available to you. I've attached a text file with extracts from both files.

Also, I installed an DL380 G4 storage server and did not have updated HBA drivers. When I allowed it to see an EVA4000 the CCLs showed up as unknown devices. I updated the HBA drivers and then it was recognised correctly.

Hope that helps.

Regards,
Stephen

[Del_3]

That is very interesting. I never took time to examine the driver kit. Thanks!

Del

[stefano colombo_1]

thanks to all answers. the solution was to use hp drivers for the hba