Hello, Few last message are:
fcoe:hold driver module e1000 for eth0 fcoe_transport_match:fcoesw:0:ffff -- eth0:8086:1076 fcoe_transport_lookup:use default transport for eth0 fcoe_transport_device_add:device eth0 added to transport fcoesw fcoe_sw_create:interface on eth0 scsi4 : FCoE Driver fcoe_transport_attach:transport fcoesw for eth0 I am not using any userspace tools and just compiled kernel to use it as standalone initiator. I don't have any switch connected too. I'll compile the kernel with debug logging too. Cheers, -Praveen > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Love, Robert W > Sent: Monday, June 01, 2009 10:25 PM > To: Morab, Praveen; [email protected] > Subject: Re: [Open-FCoE] New disk on FCoE initiator > > [email protected] wrote: > > Hello Everyone, > > I got 2.6.29 kernel compiled and trying to configure as fcoe > > initiator. I did follow the quick guide for initiator on the fcow > > wiki. > > > > I am not able to see the new disk on the initiator, so > wondering if I > > have missed something apart from whats there on wiki. > > > > [r...@rhel ~]# lsmod | grep fcoe > > fcoe 21320 0 > > libfc 66364 1 fcoe > > scsi_transport_fc 35232 3 fcoe,libfc,qla2xxx > > scsi_mod 134292 9 > > > fcoe,libfc,sg,qla2xxx,scsi_transport_fc,mptspi,mptscsih,scsi_t > ransport_s > > pi,sd_mod. > > > I'd need much more information to debug the problem, but > here's a bit of > a brain-dump that might help. > > Does dmesg show anything interesting? You should at least see > something like > > May 28 17:04:06 itchy.jf.intel.com [ 9272.632517] scsi55 : FCoE Driver > > this would indicate that we've registered with SCSI. > > Probably the best thing to look at would be wireshark. You want to see > that FLOGIs are going out, that you're getting a response and > that PLOGIs, > GPN_FT, etc... are occuring. > > If you're getting FLOGIs and whatnot, but still don't see > LUNs you can try- > setting the debug logging in the source files, for example, change > > static int fc_lport_debug; > > to, > > static int fc_lport_debug = 1; > > Each of the source files will have this ability. This will just give > you additional log statements in dmesg. > > If you're sending out FLOGIs and not getting responses you > might want to > check your switch settings. > > Are you running with DCB? Are you using the userspace tools > at all or are > you just compiling kernel code? You may need to use the > userspace tools if > your switch is setup to use DCB. When DCB is enabled on the > switch we have > fcoemon and fcoeadm to setup the QoS filters and monitor the link. > The wiki doesn't cover any of that and actually completely ignores the > userspace tools (fcoemon & fcoeadm)- it needs to be updated. > > In open-fcoe.git under the debug/ directory there are some > scripts that > might help. dcbcheck.sh might help you if DCB is misconfigured. > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel > > _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
