Adding new Host to existing EVA 6000 - Platform kit? Drivers?

[Frank Andrews]

All,

This should be a very easy for one of you experienced guys to answer. Basically all I need assistance with is the correct method for installing HBAs in to a Windows 2003 host and installing the appropriate software to allow them to see storage in the SAN.

Here's what I have -

Existing/operational EVA6000 VCS HSV200, was originally v5.031
Its firmware appears to have been upgraded as on the SMA there is evidence of upgrade to 5.110 then 6000 due to some folders on the desktop with upgrade files in. When I look on CV EVA It says version "6000" with a software version of CR0D63xc3p_6000
The HBAs are brand new PCI Express HP FC2142SR 4GB PCI-e
The HBAs (predictably!) don't come with any software at all.

I'm confident with storage configuration and zoning the switches, but I haven't installed a host since I worked on an EVA3000 in 2005 and back then I had to use Platform Kit 3.0F.

So my question is, what is the correct procedure and software I need to install the HBAs so I can present storage to it? The Windows server is not built yet, its a brand new HP DL580R04. I plan to use MPIO drivers for redundant paths.

I'll do a smartstart server build to install Windows, should the HBAs be added after doing Smartstart or is it better to build the OS with the HBAs installed?

For the driver/HBA installation do I need a platform kit, if so what is the version and can I have a download link?

Help would be very appreciated, I'm working on this kit within the next 24 hours.

Thanks!

[Frank Andrews]

Just to add to this, the OS will be Windows 2003 Server Enterprise Edition, with SP1. There will be two servers running Microsoft Clustering.

I did a search around and it appears I just need the latest Storport drivers?

So does this mean I can SmartStart build the server with no HBAs and then add the HBAs afterwards using the HP Storport driver?

Many thanks for any help, I'll assign points to anyone giving me solid answers.

[Frank Andrews]

Answering my own thread (!)

I've done a search on my HBAs and got this page - <>

When looking at the docs on the HBAs I've found that -

HP StorageWorks FC2142SR with Windows 2003 SP1 requires -
firmware 2.50a6
driver SCSIPORT miniport 5.30a2
and
If you are using the Storport miniport driver with Windows Server 2003 with SP1 or later, you need the Microsoft QFE-916048. This hotfix contains updates for Microsoftâ s storport.sys driver. To obtain the QFE, see the website <>

This seems to be what I need?

[Frank Andrews]

Guys, sorry about the bad links on the last post, I've fixed them here -

Answering my own thread (!)

I've done a search on my HBAs and got this page - http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1143949&prodTypeId=12169&prodSeriesId=180983
5&swLang=8&taskId=135&swEnvOID=1005

When looking at the docs on the HBAs I've found that -

HP StorageWorks FC2142SR with Windows 2003 SP1 requires -
firmware 2.50a6
driver SCSIPORT miniport 5.30a2
and
If you are using the Storport miniport driver with Windows Server 2003 with SP1 or later, you need the Microsoft QFE-916048. This hotfix contains updates for Microsoft's storport.sys driver. To obtain the QFE, see the website http://support.microsoft.com/kb/916048

This seems to be what I need?

My own concern now is that the driver recommended is "boot from SAN", I don't need this functionality, I'm hoping this driver is suitable just to attach to storage on the EVA from a normal windows host?

[Frank Andrews]

Can anyone confirm I have the correct approach? Thanks

[Mike Bollman_1 · Accepted solution]

My build process is to install the latest HBAnywhere version, install storport HBA driver (5-1.20a7), reboot, install the storport hotfix (MS KB916048), reboot, install the latest mpio software (2.01.00) and mpio manager(2.00), reboot.

Once that is all done I then verify that my HBA's have the latest approved firmware via HBAnywhere. Then define my zones on the fabrics, define my host on the EVA, setup my vdisk and present LUN.

2142 Driver:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1143949&prodTypeId=12169&prodSeriesId=1809835&swLang=8&taskId=135&swEnvOID=1005

2142 Firmware:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1143949&prodTypeId=12169&prodSeriesId=1809835&swLang=8&taskId=135&swEnvOID=54

MPIO 2.01.00:
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

[Mike Bollman_1]

One more thing...I just noticed you said this was for a cluster.

Be sure to grab the MS KB911030 hotfix as well.

If you are going to use VSS there is a laundry list of other hotfixes you will need also.

Last I am not sure what your plans are for the NICs, but you may want to add additional for heartbeat. On my DL580 G4 clusters I am running 4 NICs in every server. 2 are teamed (failover only) for the primary interface. The other 2 are configured as primary and secondary heartbeat networks on different subnets.

One last thing, since you have multiple HBA's and have mpio installed cluster wizard is likely to give you fits. For some reason it classifies this as a "complex SAN" configuration. As a result when you go to intially setup your cluster it will put your quorum drive locally. You will then have to manually move it to your SAN volume and update the properties of that disk resource.

If you run into any problems let me know. I just finished buildig out 2 - 3 node DL580 G4 clusters about 3 months ago. All of this is still fresh in my mind.

[Frank Andrews]

Micheal,

thats a great reply, just what I was looking for. You mentioned the HBAnywhere software, is this available from HP?

Thanks

[Mike Bollman_1]

If you follow the link for the HBA driver and scroll to the bottom you will see the link for HBAnywhere.

Here is a direct link though for the download:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=1809835&prodNameId=1143949&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=co-47142-1

[Frank Andrews]

With reference to the NICs -
I'll use the onboard NICs teamed for the general network, I also have a PCI dual port card, one port for cluster heartbeat and one for management. I'll download those files and begin the build this afternoon.
Hopefully this will all go well!

[Frank Andrews]

What are the differences between the STORport and SCSIport drivers?

[Mike Bollman_1]

hmm...what do you mean by one for heartbeat and one for management?

I understand the heartbeat part, but the management? Do you mean for the cluster management? If so just assign the cluster IP to the teamed public interface. No need for a dedicated NIC on that piece. IMHO you will be better served using that second NIC port as a secondary heartbeat on a separate physical network. Also, since you are using a dual port NIC be sure you setup your public interface as a tertiary heartbeat path. Otherwise that dual port NIC "could" die someday leaving you hosed.

[Mike Bollman_1]

storport offers better performance over scsiminiport.

attached is the MS white paper on the subject

[Frank Andrews]

The heartbeat will indeed be on its own segment, possibly even a cross over cable.

The management port I believe is to be used by a third party company to gain access using their own router.

The teamed nics will be used for the local users to access the cluster/SQL

[Frank Andrews]

You advised me to use MPIO 2.01.00. Is my EVA compatible with this? I seem to recall reading some release notes stating a minimum version of firmware was needed on the EVA?

[Mike Bollman_1]

I just re-read your first post...I say 6.0 and thought you meant XCS code.

What version is your XCS code at?

[Frank Andrews]

This might be a stupid question, but can you suggest the easiest way to verify this?

[Mike Bollman_1]

launch commandview EVA
select your array
on the right side of your screen you will see a section labeled "system" under this section there will be a "version" this is your code level.

[Frank Andrews]

Thanks, to confirm I'm running version 6000

[Mike Bollman_1]

your good to go

[Frank Andrews]

I did a search on microsoft.com for KB911030 and though the article seems to refer to a hotfix (that isn't downloadable on the page) it advises that I need to install the latest Service Pack (SP2)?

[Frank Andrews]

I was reading that information from here -

http://support.microsoft.com/kb/911030/

[Mike Bollman_1]

The cluster hotfix and the storport hotfixes are both included in SP2. However, I do not believe HP has officially certified SP2 for use on SAN nodes. I could be wrong here though. I spoke to my HP BCS TAM and my internal reps for storage and servers abou this. None of them knew of any official word on support.

If you have an MS premier contract you can download the hotfix via your premier support site. Otherwise you have to call in to the support line and mention the KB article to get it.

[Frank Andrews]

The release notes for the HP driver you recommended states -

If you are using the Storport miniport driver with Windows Server 2003 with SP1 or later, you need the Microsoft QFE-916048. This hotfix contains updates for Microsoftâ s storport.sys driver. To obtain the QFE, see the website http://support.microsoft.com/kb/916048

[Mike Bollman_1]

correct, the 916048 hotfix I mentioned in my first post. It is the storport hotfix and is absolutely MANDATORY. Unless you want to trash your data in a hurry.