topic Re: RHEL 5 U 2 and above in Operating System - Linux

RHEL 5 U 2 and above

ossupport55 — Sun, 16 Aug 2009 10:41:53 GMT

Dear all,

This is a rephrased question. With RHEL 5 U2 should I install the HP drivers for the HBAs or should I try to live with the drivers that come with the distro?
These servers would be using device-mapper multipathing instead of the 3rd party multipathing software. What approach do you folks recommend?.
We are into HP blades and some bricks.

Ps: When I get the lspci output. How can I know which hHP driver would suite the HBA being used.

Thanks in advance.

Re: RHEL 5 U 2 and above

Steven E. Protter — Sun, 16 Aug 2009 16:19:19 GMT

Shalom,

With RHEL 5, update 2, I had to install the HBA drivers that shipped with PSP 8.25 in order to get normal multipathing functionality.

Before installation, my systems could not see the SAN, in spite of using qlogic HBA cards that worked out of the box with RHEL 4.x

SEP
hpuxconsulting on yahoo messenger

Re: RHEL 5 U 2 and above

ossupport55 — Mon, 17 Aug 2009 02:50:15 GMT

Thanks for the reply SEP. What about the identification of the proper driver for mez adapter by looking at the lspci output.
What RPMs do you folks recommend to have with respect to SAN.

Re: RHEL 5 U 2 and above

Jimmy Vance — Mon, 17 Aug 2009 11:53:04 GMT

You should be able to use the inbox HBA drivers.

You can look at this, it gives you the hp_rescan utility which comes in handy.

Linux Inbox Driver kits

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=co-69719-1&jumpid=reg_R1002_USEN

Re: RHEL 5 U 2 and above

ossupport55 — Mon, 17 Aug 2009 18:57:38 GMT

Jimmy thanks for the reply mate. But please tell me what this "inbox driver" means. Well i installed the driver that came along with the PSP.
After installing that RHEL 5 U2 storage detection and reporting goes back to /proc/scsi, which i read was outdated as of the RHEL 5 release.
When i install the inbox driver which U have given does it also refer to the /proc/scsi FSs or does stay with the /sys/class
What is the best aproach when using device-mapper ?.

Please folks..

Re: RHEL 5 U 2 and above

Jimmy Vance — Mon, 17 Aug 2009 20:37:31 GMT

The "inbox" driver is the version of the driver that is packaged in the OS

Re: RHEL 5 U 2 and above

Jimmy Vance — Mon, 17 Aug 2009 20:38:19 GMT

the hp-fc-enablement package use /sys instead of /proc

Re: RHEL 5 U 2 and above

ossupport55 — Mon, 17 Aug 2009 20:52:59 GMT

Ok Jimmy. Thanks for the reply. Let me install that and give it a shot.
Folks, any special configuration needed for the HDS USP V and USP 1100 arrays. We might use command devices for replication as well.

Thanks for all the sup/

Re: RHEL 5 U 2 and above

ossupport55 — Wed, 19 Aug 2009 04:37:16 GMT

Jimmy, i installed the inbox driver. It was for RHEL 5.3. But looks OK.
I'm still in search to know how to map the lspci output to the card actually installed.,

cheers

Re: RHEL 5 U 2 and above

Jimmy Vance — Wed, 19 Aug 2009 11:31:28 GMT

I'm not sure exactly what your asking for. On a test system I have, with a dual port QLogic card, lspci shows this

06:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)
06:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)

The output of hp_rescan -l displays this

QLogic adapters:

/sys/class/scsi_host/2
/sys/class/scsi_host/3

Emulex adapters:

--------------

One can then figure that

06:00.0 = /sys/class/scsi_host/2
06:00.1 = /sys/class/scsi_host/3