multipath -l |grep failed -->find the failed device(HBA)

/proc/scsi/qla2xxx/<failed dev> |grep port --> get the WWWN port

Check the loop state of HBA.
[root@erpdb-prd-17 qla2xxx]# cat 0 |grep -i loop
Number of loop resyncs = 0
Host adapter:loop state = <DEAD>, flags = 0x85a03
[root@erpdb-prd-17 qla2xxx]# cat 1 |grep -i loop
Number of loop resyncs = 0
Host adapter:loop state = <READY>, flags = 0x85a43

[root@erpdb-prd-17 qla2xxx]# symmask -sid 4337 list logins -wwn 2100001b320a38bf

Symmetrix ID : 000190104337
Director Identification : FA-9C
Director Port : 0
User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
2100001b320a38bf Fibre ERPDB-PRD-17 QLA0 630001 No Yes
find if Logged In is :No

________________________________________________________________________________
____
Installing HBA in 4.x
-----------------------
Run lspci | grep QLA to determine which Qlogic cards you have installed, common
values are QLA2200 or QLA2312 the corresponding driver would be either qla2200 o
r qla2300.
Once you have determined the current model, add the appropriate driver /etc/modu
les.conf similar to:
alias scsi_hostadapter1 qla2300
alias scsi_hostadapter2 qla2300
Run modprobe qla2300 where qla2300 is the driver module you added to modules.con
f. This will load the driver and should discover any already zoned storage.
Verify your storage is visible by cat /proc/scsi/qla2300/0, at the bottom of the
output is your SCSI Lun information similar to:
SCSI LUN Information:
(Id:Lun) * - indicates lun is not registered with the OS.
(0: 0): Total reqs 811, Pending reqs 0, flags 0x0, 1:0:81,
( 0: 1): Total reqs 11781944, Pending reqs 0, flags 0x0, 1:0:81,
( 0: 2): Total reqs 11709746, Pending reqs 0, flags 0x0, 1:0:81,
( 0: 3): Total reqs 5542, Pending reqs 0, flags 0x0, 1:0:81,
( 0: 4): Total reqs 5360, Pending reqs 0, flags 0x0, 1:0:81,

On a dual path system check both 0 and 1 HBA instances. If storage has not been
zoned the LUN Information section will be empty.
Create a new ramdisk image for preloading the qlogic modules:
cp /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img.nosan
 mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`
Reboot the machine with the qlogic modules preloaded and verify you can see the
storage with fdisk -l if it has been already zoned.
sudo yum groupinstall EMC-SAN-support ---> for powerpath installtion
________________________________________________________________________________
___________
Installing HBA in 5.x
-----------------------
The system administrator should use these instructions when there is no SAN stor
age at all on the host.
You must contact the Storage Team to request the proper Qlogic host bus adapters
for your server. You should also submit a storage request for your devices to b
e allocated here:Storage Request. After installing the HBA's and the devices hav
e been allocated, configure the kernel to support the new cards as follows:

Run /sbin/lspci | grep QLA to determine which Qlogic cards you have installed. T
he most common value is QLA2312 (for the QLA2340 card), and the output would loo
k something like this (for 2 1-port cards):
05:0d.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
06:0e.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
A single two-port card would look like this (note the slot and card numbers are
the same, i.e. "07" and "03", but the instance numbers are different, i.e. "0" a
nd "1"):

07:03.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
07:03.1 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
The corresponding driver would be qla2300 (which depends on another module calle
d qla2xxx with generic functionality for multiple cards).

Add Driver Name to /etc/modprobe.conf

This is only needed for RHEL4/CEL 5.0x. RHEL5/CEL5.3+ shouldn't have any mention
of HBA/FCoE drivers in modprobe.conf
Run modprobe qla2300 where qla2300 is the driver module you added to modprobe.co
nf. This will load the drivers and should discover any already zoned storage.
Add The Following where qla2300 is the driver required.
/etc/modprobe.conf
alias scsi_hostadapter1 qla2300
PLEASE NOTE: Do not run this command on a live production system that already h
as SAN storage! In at least one instance running this command has caused a reboo
t.

Verify your storage is visible by ls /sys/class/scsi_device/; output is similar

to:
0:0:0:0 0:0:0:23 0:0:0:4 0:0:1:3 1:0:0:0 1:0:0:23 1:0:0:4 1:0:1:3
0:0:0:1 0:0:0:255 0:0:0:46 0:0:1:4 1:0:0:1 1:0:0:254 1:0:0:46 1:0:1:4
0:0:0:13 0:0:0:3 0:0:0:7 0:0:2:0 1:0:0:13 1:0:0:3 1:0:0:7 1:0:2:0
0:0:0:14 0:0:0:35 0:0:0:8 0:0:2:1 1:0:0:14 1:0:0:35 1:0:0:8 1:0:2:1
0:0:0:15 0:0:0:36 0:0:1:0 0:0:2:2 1:0:0:15 1:0:0:36 1:0:1:0 1:0:2:2
0:0:0:2 0:0:0:37 0:0:1:1 0:0:2:3 1:0:0:2 1:0:0:37 1:0:1:1 1:0:2:3
0:0:0:22 0:0:0:38 0:0:1:2 0:0:2:4 1:0:0:22 1:0:0:38 1:0:1:2 1:0:2:4
The numbers mean this:

1:0:0:1
^ ^ ^ ^
| | | |
| | | + - LUN (in decimal)
| | +---- Target
| +------ Channel (always 0)
+-------- Host (HBA driver instance number); usually 0 or 1 (see NOTE).
NOTE: the HBA instance number but can vary, depending on other SCSI drivers pres
ent and the number of times the qla2300 and qla2xxx modules are reloaded.

Set HBA settings

Set the proper HBA timeout values (required for Storage Team and EMC support) by
running the the http://wwwin-kickstart-sj.cisco.com/kickstarts/scripts/set-qlog
ic-hba-timeouts.sh script. This will set the timeout values and a kernel paramet
ers as outlined in the Linux SAN standard's document