topic Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0 in Operating System - Linux

Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

Chris_557 — Wed, 10 Aug 2005 14:32:35 GMT

I have a pair of Qlogic 2300 series HBAs installed on a Proliant with RHEL 3.0 AS.
I can see and use the LUNs with these HBAs fine.
Persistent binding is in use.
I can not get automatic failover to work, it claims I am missing a failover driver.
I have 6 LUNs total, but the system sees them as 12 LUNs, and if you try to access the twin of the other it obviously writes to the first.
I installed all the qlogic stuff I had, and I am not sure what I am lacking.
Could anyone point this out for me?

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

Vitaly Karasik_1 — Thu, 11 Aug 2005 03:53:50 GMT

You should download & install hp_qla2x00 driver from HP site.

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

JAVAUX — Thu, 11 Aug 2005 04:49:42 GMT

You must install the package hp_qla2x00src-7.05.00-9...
In the installation procedure you must to choose the mode "Qlogic Failover"...
And If you have one EVA for the san you must present the LUN "FAILOVER only" path A ou Path B...
In last your host on the EVA must be declared "SUN SOLARIS" for O.S.

Normaly you have in the file /etc/modules.conf :
alias scsi_hostadapter2 qla2200
alias scsi_hostadapter3 qla2300_conf
alias scsi_hostadapter4 qla2300
alias scsi_hostadapter5 sg
options qla2200 ql2xmaxqdepth=16 qlport_down_retry=3 qlogin_retry_count=16 ql2xfailover=1
options qla2300 ql2xmaxqdepth=16 qlport_down_retry=3 qlogin_retry_count=16 ql2xfailover=1
post-remove qla2300 rmmod qla2300_conf

And in the file /etc/hp_qla2x00.conf :
qdepth = 16
port_down_retry_count = 3
login_retry_count = 16
failover = 1

After the reboot you cat see your disk with the command "cat /proc/partitions"

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

David Spencer_1 — Thu, 11 Aug 2005 06:25:35 GMT

I had the same problem and here is what fixed it.
Hopefully you have already downloaded the hp_fibreutils. If not, go to the HP website and download them.
After getting the utilities, run the following script:
/opt/hp/src/hp_qla2x00src/set_parms
Choose option 1 for "XP/MSA/EVA failover"
then "y" to rebuild the initrd file.
After a reboot the system should be in the failover mode and the paths properly filtered.

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

Chris_557 — Thu, 11 Aug 2005 13:51:34 GMT

Ok, quick question then.
I am using an IBM Shark for the SAN disks.
Will this affect things at all?
The hp qla rpm file said it didn't like seeing the IBM there, so I am figuring it must matter, but it also tells me how to force the install.

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

David Spencer_1 — Thu, 11 Aug 2005 14:24:12 GMT

Chis, the hp_fibreutils are for the Qlogic interface. The script:
/opt/hp/src/hp_qla2x00src/set_parms should resolve your 12 LUN problem. The system needs to see it only as 6 LUNS for everything to be correct with the failover.

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

JAVAUX — Fri, 12 Aug 2005 02:09:27 GMT

Chris,

Your Qlogic card is provided by HP... The best driver for this cards is from fp_fibreutils...

You can chosse :
1) Uninstall driver and reinstall driver with option "Qlogic failover" (I think this is the best way..)
2) Execute the shell /opt/hp/src/hp_qla2x00src/set_prms and set option "failover"

If you driver is already installed you must uninstall this.. I have this problem and I have remove the driver and reinstall this driver... for use the qlogic failover...

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

Chris_557 — Thu, 08 Sep 2005 16:15:00 GMT

As far as I can tell, thigns are working as exected after installing the HP drivers.
There were a few odd messages here and there, but I now have 6 LUNs and they aren't moving around on me. Thanks for the help.

Re: Finding 'failover drivers' for Qlogic 2300 on RHEL 3.0

Chris_557 — Thu, 08 Sep 2005 16:15:40 GMT

Installing HP Drivers as suggested seemed to do the trick.