Red Hat Bugzilla – Bug 471269
[QLogic 5.3 bug] qla2xxx - No NPIV for Loop connections.
Last modified: 2009-06-20 04:07:09 EDT
FIbre channel does not support NPIV, virtual nports, for arbitrated loop connections, only for point to point connections.
This simple patch sets the value for maximum virtual ports to an acceptable value for the firmware.
This patch applies and builds cleanly with 2.6.18-122 and is observed to fix this problem on the NEC machine that reported it and also in testing at QLogic labs.
I don't think this qualifies as a blocker.. will have to defer to Tom on this.
Marcus, I don't see a patch attached as well...
The patch is on the way. When I format it for posting to the kernel list I include the BZ number etc. So I need to create the BZ first.
Without this patch machines who's HBA are set to "Loop" mode will not be able to find their storage. The NEC machines seem to fall in this category and perhaps others too.
THis problem was reported by NEC in BZ 442946, which was the firmware update BZ. It seemed appropriate each bug to have it's own BZ, but if not I can re-use the other one.
Created attachment 323377 [details]
disable vports in loopmode
Patch to disable vports in loop mode and bump the version to: 8.02.00.05.05.03-k
OK - I'll move the original bug (bug 442946) to VERIFIED then...
I confirmed the patch works well on the NEC machine which had showed the issue.
All expected LUNs are visible on both of only-4G-HBA and 2G/4G-HBA mixed condition.
Changed back to 'all platforms". THis bug was found on an IA64 system, but would effect any system whose HBA with a connection in Arbitrated Loop mode.
You can download this test kernel from http://people.redhat.com/dzickus/el5
kernel-2.6.18-124.el5 works well on NEC ia64 machine.
I confirmed both connection mode as Loop and Point-to-Point, and it's perfect.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.