On 02/11/2012 22:24, Nicholas A. Bellinger wrote:
On Fri, 2012-11-02 at 13:58 +0000, Chris Boot wrote:
I have recently acquired a couple of QLE2460 HBAs in order to play
around with the FC target. I have simply strung them together with an
LC-LC fibre pair, and it appears that as soon as I plug the fibre into
both ends the link comes up: I get an entry appearing in
/sys/class/fc_remote_ports/ on both machines that contains correct
information about the node on the other end of the link (WWPNs, etc...).
You'll want to go ahead and enable ql2xextended_error_logging=0x7fffffff
at modprobe time on both sides to understand what's going on. Note this
will generate a decent amount of ring buffer output. ;)
I've got a log of the target end with that option set. I've posted it
here for now, as it's rather too large for email:
http://www.bootc.net/temp/qla-2012-11-03.log
That's with Windows as an initiator this time. Going into the SANsurfer
tools it appears that it can see the target end, but it has 0 LUNs...
On the target server, I have set up a qla2xxx target using targetcli.
This machine is running the 3.6.5 kernel from kernel.org.
Btw, just a separate heads up here. You'll also want to apply the
following one-liner patch to fix a v3.7-rc1 regression bug that managed
to make it's way into v3.6 stable:
http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git;a=commitdiff;h=dea5f0998aa82bdeca260b87c653db11e91329b2
I've added this now. It doesn't appear to have changed much at this point.
Hopefully I'll have time to enable the extended error logging under the
Linux initiator later today...
Cheers,
Chris
--
Chris Boot
bootc@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
