[ovirt-users] Fwd: RE: FC QLogic question
Bill Dossett
bill.dossett at pb.com
Fri Sep 12 09:24:36 UTC 2014
Bugger, spoke to soon…. One host sees the LUNs the other doesn’t. Same builds of ovirt-node. Both dell 2950s, and both qlogic cards… but one says
Sep 9 08:12:23 localhost kernel: qla2xxx [0000:0c:00.0]-00fb:1: QLogic QLE2460 - QLogic 4GB FC Single-Port PCI-E HBA for IBM System x.
And further down the log this (this one does not find the LUNS)
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-d001:1: Firmware dump saved to temp buffer (1/ffffc90013d9e000).
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-101e:1: Mailbox cmd timeout occurred, cmd=0x69, mb[0]=0x69. Scheduling ISP abort
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-00af:1: Performing ISP error recovery - ha=ffff88086ce53000.
Sep 9 08:12:24 localhost kernel: qla2xxx 0000:0c:00.0: firmware: requesting ql2400_fw.bin
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-0063:1: Failed to load firmware image (ql2400_fw.bin).
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-0090:1: Fimware image unavailable.
Sep 9 08:12:24 localhost kernel: qla2xxx [0000:0c:00.0]-0091:1: Firmware images can be retrieved from: http://ldriver.qlogic.com/firmware/.
Sep 9 08:12:24 localhost firmware.sh[4794]: Cannot find firmware file 'ql2400_fw.bin'
Sep 9 08:12:26 localhost kernel: qla2xxx [0000:0c:00.0]-505f:1: Link is operational (4 Gbps).
Sep 9 08:12:26 localhost kernel: qla2xxx [0000:0c:00.0]-1020:1: **** Failed mbx[0]=69, mb[1]=0, mb[2]=0, mb[3]=0, cmd=69 ****.
Sep 9 08:12:32 localhost kdump: mkdumprd: failed to make kdump initrd
Sep 9 08:12:32 localhost lldpad: config file failed to load,
And the one that does find the LUNS is
Sep 11 08:33:39 localhost kernel: qla2xxx [0000:0a:00.0]-00fb:0: QLogic QLE2460 - SG-(X)PCIE1FC-QF4, Sun StorageTek 4 Gb FC Enterprise PCI-Express Single Channel.
And a little further down it discovers the LUNs
Sep 11 08:33:39 localhost kernel: qla2xxx [0000:0e:00.0]-505f:1: Link is operational (4 Gbps).
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:0: Direct-Access DGC LUNZ 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:1: Direct-Access DGC RAID 5 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:2: Direct-Access DGC RAID 5 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:3: Direct-Access DGC RAID 5 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:5: Direct-Access DGC RAID 5 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:11: Direct-Access DGC RAID 1 0216 PQ: 0 ANSI: 4
Sep 11 08:33:39 localhost kernel: scsi 1:0:0:51: Direct-Access DGC RAID 1 0216 PQ: 0 ANSI: 4
So, I am thinking maybe different firmware levels on these cards and the first one for IBM systems has different firmware? As it seems to be throwing more errors. Should I try to add the firmware? And if so I know it goes in /lib/firmware but then the boot image needs to be updated I think and I don’t know how to do that… or am I barking up the wrong tree.
Thanks again for the help.
From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On Behalf Of Bill Dossett
Sent: 12 September 2014 08:35
To: Sander Grendelman
Cc: users at ovirt.org
Subject: Re: [ovirt-users] Fwd: RE: FC QLogic question
Hmmm… I’ve just gone to add a storage domain and in the admin portal and bingo bango, all my LUNs appeared.
Just wiping out everything from my last lab now.
Thanks everyone, I am not quite sure why it started working, but knowing that the ovirt-node was seeing the LUNs prompted me to continue.
Thanks all for the help.
Bill
From: sander.grendelman at gmail.com<mailto:sander.grendelman at gmail.com> [mailto:sander.grendelman at gmail.com] On Behalf Of Sander Grendelman
Sent: 12 September 2014 08:28
To: Bill Dossett
Cc: users at ovirt.org<mailto:users at ovirt.org>
Subject: Re: [ovirt-users] Fwd: RE: FC QLogic question
This could also be an selinux issue with FC on the node, I've hit that one before.
Especially since the luns do show up with multipath -ll
Could be as simple as flipping a sanlock related selinux boolean.
A quick test would be to boot in permissive mode.
See http://www.ovirt.org/Node_Troubleshooting#SELinux for some more information.
________________________________
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140912/5fb8171f/attachment-0001.html>
More information about the Users
mailing list