rhel4 powerlink qla2xxx HBAs not detected

[dkaplowitz1]

Hi,

I ran through a procedure script that was generated to install my Emulex QLA-2340s on a RHEL4 box (Linux rh-linx2 2.6.9-42.0.8.ELsmp #1 SMP Tue Jan 23 13:01:26 EST 2007 i686 i686 i386 GNU/Linux). Everything seems to have gone in well, I updated the HBA firmware, installed the qla2xxx-8.01.06-1dkms rpms successfully, sansurfer is installed and appears to be working, PowerPath is installed and the licenses have "Capabilties: All" set.

But cat /proc/scsi/scsi doesn't show anything other than the onboard HDDs, and the lun-scan.sh script I downloaded from emcpower gives: "ls: /sys/bus/pci/drivers/lpfc/*/host*: No such file or directory"

I see qla2xxx & qla2300 entries in lsmod as well as a bunch of emcp* entries. The PowerPath, qlremote, and naviagent are all starting from init.d.

I don't really know what I'm missing to make the connection between all this software and the hardware on the system.

Thanks for any pointers.

Dave

[dynamox]

do you have "/proc/scsi/lpfc" directory ?

[dynamox]

looks you are using Qlogic and not Emulex ..you should have /proc/scsi/qlaXXX ..or something of that nature

[dkaplowitz1]

Hi, thanks for the reply. You're right, I do have QLogic joints and I do have a /proc/scsi/qla2xxx/2 and /proc/scsi/qla2xxx/3 which have a bunch of info like:

QLogic PCI to Fibre Channel Host Adapter for QLA2340:
        Firmware version 3.03.19 IPX, Driver version 8.01.06
ISP: ISP2312, Serial# J81445
Request Queue = 0x17bc0000, Response Queue = 0x17ba0000
Request Queue count = 2048, Response Queue count = 512
Total number of active commands = 0
Total number of interrupts = 73
    Device queue depth = 0x10
Number of free request entries = 2046
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 0
Number of retries for empty slots = 0
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
Host adapter:loop state = <READY>, flags = 0x1a03
Dpc flags = 0x4000000
MBX flags = 0x0
Link down Timeout = 045
Port down retry = 045
Login retry count = 045
Commands retried with dropped frame(s) = 0
Product ID = 4953 5020 2020 0002
 
 
SCSI Device Information:
scsi-qla1-adapter-node=200000e08b8ec5f9;
scsi-qla1-adapter-port=210000e08b8ec5f9;
 
FC Port Information:
 
SCSI LUN Information:
(Id:Lun)  * - indicates lun is not registered with the OS.

I'm not sure if that last line means the Luns are not registered. Any idea how I need to register these Luns with RHEL4?

Thanks for any help.

Dave

[dynamox]

what storage array are you connecting to ?

[dkaplowitz1]

It's an EMC Clarion CX-700 OEM'ed through Dell. Our switch has these Qlogic HBA's worldwide names registered, but the SAN's connectivity status doesn't detect them, but I'm sure that rhel's not properly configured, otherwise something like `powermt display dev=all` would give something other than `Device(s) not found.`

[dynamox]

ok, so you have gone through these steps:

1) connected HBAs to the switch.
2) created new zones on the switch and activated the zoneset.

[dkaplowitz1]

Yes, to both of your questions (zoning has been done and the HBAs are connected to the FC switch) Also, I'm under the impression that regardless of whether the HBAs are connected to anything PowerPath should see and acknowledge that the HBAs are on the server on which it's installed. Am I correct?

The reason I ask is that I opened a support incident with Dell over this issue today and I was asked the same thing ---almost as if PowerPath won't see the HBAs before the zoning has been done. One of our SAN admin seems to think that it doesn't matter.

Regardless, the zoning has been done.

Thanks again.

Dave

[dynamox]

powerpath will not show HBAs until there are devices presented to them. So when you look in Navisphere under connectivity status you do not see the WWNs of your HBAs correct ?

[dkaplowitz1]

Yes, Navisphere "connectivity status" fails to show the WWNs of the HBAs. But according to the instructions for installing the QLogic Drivers and PowerPath, it should detect them if everything went well with the installation of the drivers/agents/software.