topic Path Failover failure when I use FCA2214 driver self failover function instead of securepath in Operating System - Linux

Path Failover failure when I use FCA2214 driver self failover function instead of securepath

richeal75 — Thu, 02 Jun 2005 05:11:09 GMT

HW: 380G4 with 2xFCA2214
MSA1000 with 2xcontroller and hub 2/3
OS : redhat AS3.0 update4
driver: MSA1000 support software CD 6.51-02

1.I installed msa1000 driver on
/mnt/cdrom/RDP/Linux/INSTALL -f

2.and then reboot server.

3. can find msa1000 lun as /dev/sda

4. i disconnect active fiber cable

5. but standby fiber cable can't takeover msa100 lun /dev/sda, i can't open it .

why ?

Re: Path Failover failure when I use FCA2214 driver self failover function instead of securepath

Bryan Swanson_1 — Thu, 09 Jun 2005 09:15:52 GMT

You should probably double check the dmesg output from when the (FC) driver loads.
Look for the driver version, it should say something like "Driver version 7.01.01-fo"

Note the '-fo' indicating the driver was built with failover support.

You can also do a 'modinfo qla2200' and look for ql2xfailover option.

Additionally you should have a module option
ql2xfailover=1 in either /etc/modules.conf or /etc/hp_qla2x00.conf (or both).

regards,
-b

Re: Path Failover failure when I use FCA2214 driver self failover function instead of securepath

Simon P. — Fri, 01 Jul 2005 09:09:47 GMT

cd to /etc/init.d then vi the rawdevices file and the following two lines to the top of the file

rmmod qla2300
insmod qla2300 ql2xfailover=1

wq (write quit) the file and reboot the server.

You know it's working when you don't the same disk presented many times to server.