Problem with Qlogic Failover on HS21 XM(7795G1G) and Linux RH 5.2 x86_64

[Sebastian Szewczyk]

Hello,

Install on my new Blade HS21 Linux Red Hat 5 Update 2 (Tikanga). After my installation I need install qlogic failover driver.
My Blade is boot from SAN and connected to HP EVA 5000 with Active/Passive Firmware (3028).
I read on portal site of IBM Company and Qlogic portal and HP Portal that I can use driver with failover option.
And I try drivers from Qlogic portal:
lafc-linux-8.02.08-1, qlafc-linux-8.01.07.15-2, qla2xxx-v8.01.06
From IBM portal driver: 8.01.07-15
From HP portal: hp_qla2x00-2007-10-05b, hp_qla2x00-2007-10-05a
My FC on my blade:
Product Identifier: PCI-X Combo 4Gb Fibre Channel Mezzanine HBA
Part Number: QMI2472
Serial Number: RFC0837C42595
Misc. Information: PW=10W;PCI=66MHZ;PCI-X=266MHz
Manufacturing Id: CU0210405-01 B
EFI Driver Version: 01.08
Firmware Version: 04.00.27
BIOS Version: 02.02
FCode Version: 02.00
When I install drivers from IBM portall and after that I
mkinitrd command after restart I have kernel panic.
Identical situation I have when I install drivers form Qlogic portal in diferents variants like qlinstall ora ./extras/build.sh install & mkinitrd. And identical situation I have when I install from HP drivers with option INSTALL -f
After restart something like in the attachment file and after that I have kernel panic.
What can I do in that situation please give me some advice or instructions how I can do failover on qlogic in my HS21 XM.
Where I find driver with option -fo.

Best regards
Sebastian

[Steven McCoy]

Hello Sebastian,

Have you looked at RedHat's device-mapper-multipath (dm-multipath)? We use that here with our EVAs, and it supports failover.

Here are my comments on dm-multipath from another thread:

#############################################

You could use device-mapper-multipath to assign devices via WWID and alias them to friendly names.

Check out the contents of '/dev/disk/by-id/' and see if the WWIDs are shown up there:

ls -l /dev/disk/by-id/

Then populate the '/etc/multipath.conf' file similar to below (with a separate 'multipath' entry for each WWID):

-----------------------------------------------
defaults {
user_friendly_names yes
}
blacklist {
wwid 26353900f02796769
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
}
multipaths {
multipath {
wwid 3600508b400013cf32341b00000620000
alias myname1
}
multipath {
wwid 3600508b4113013cf32341b00000620000
alias myname2
}
}
-----------------------------------------------

Restart the multipath daemon:

/etc/init.d/multipathd restart

Then try detecting the devices:

multipath -v2
multipath -ll

If your LUNs do not show up, consider taking a look at the '/usr/share/doc/device-mapper-multipath*/multipath.conf.defaults' file and adding a devices section for your SAN. Something similar to:

---------------------------------------------
devices {
device {
vendor "(COMPAQ|HP)"
product "HSV(1|2).*"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua %n"
features "0"
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
no_path_retry 60
rr_min_io 1000
path_checker tur
}

}
---------------------------------------------

Don't forget to re-run 'multipath -v2' if you make any changes to the config file.

#############################################


HTH, please reply if it doesn't.

[Sebastian Szewczyk]

I tyry device-mapper multipath and always I have problem because dosen;t work properly now I try them adn give yu my console output.
But in documentation I read that device-mapper multipath supports only Active/Active firmware nut on my EVA 5000 I have 3028 Firmwvare with Active/Passive.

Best regards
Sebastian

[Steven McCoy]

Hey Sebastian, you are using an EVA 5000? Even with active/passive, you should be able to use dm-multipath. How about adding this 'devices' section to your /etc/multipath.conf file, restarting the multipathd daemon (not really required, but would be for good measure), and re-running 'multipath -v2'?

----------------------------------------------
devices {
device {
vendor "(COMPAQ|HP)"
product "HSV(1|2).*"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua %n"
features "0"
hardware_handler "0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
no_path_retry 60
rr_min_io 1000
path_checker tur
}

}
--------------------------------------------

Please explain further what doesn't "work" with dm-multipath, the errors or problems you are receiving, and your /etc/multipath.conf file.

[Sebastian Szewczyk]

Hello,

Ok I can try tomorrow configure multipath. Now I install new clean OS like Linux Red Hat 5 Update 2 (Tikanga) x86_64.
Tomorrow on the morning I configure them and i write you what problem i have ok.
Thank you very much that you interest my problem and you give me some advice.

Best regards
Sebastian

[Sebastian Szewczyk]

Ok like I promise I isntall fresh from boxes
Linux Red Hat 5 Update 2 (Tikanga).
I configure my multipath with your suggestion configurationfile in attachment. and when I restart multipath , multipath -v2&ll I have something like that output:
[root@xyz etc]# /etc/init.d/multipathd restart
Stopping multipathd daemon: [ OK ]
Starting multipathd daemon: [ OK ]
[root@xyd etc]# multipath -v2
error calling out /sbin/mpath_prio_alua sda
error calling out /sbin/mpath_prio_alua sdb
error calling out /sbin/mpath_prio_alua sda
error calling out /sbin/mpath_prio_alua sdb
DM message failed [queue_if_no_path
]
[root@xyd etc]# multipath -ll
What can I do now.
I wait for your replay adn advices.

Best regards
Sebastian

[Jimmy Vance]

RHEL 5.2 you should be able to use the inbox QLogic drivers and device mapper MPIO.

These may help

Device Mapper Multipath enablement kit for HP StorageWorks Disk Arrays v4.1.1
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=co-67922-1&jumpid=reg_R1002_USEN

Device Mapper Migration kit v1.2 for HP StorageWorks Disk Arrays
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=co-58149-1&jumpid=reg_R1002_USEN


Release Notes for Migration from Qlogic Failover/Emulex Multipulse to HP Device Mapper Multipath
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01388427/c01388427.pdf?jumpid=reg_R1002_USEN

[Sebastian Szewczyk]

Hello Jimmy
Everythink is ok I know about that software but I have Active/Passive Firmware on my Arrays. On that soft you must have to Active/Active fimrware on Arrays.

Best regards
Sebastian