On Wed, 2010-07-14 at 00:20 -0700, Ramaraju Yelavarthy wrote:
> Hi,
>
> I am new to FCoE and was in the process of learning FCoE
> and setting up FCoE target. I had couple of queries on FCoE which are
> as below,
>
>
>
> 1. I had setup FCoE target by following the steps from this link
> (http://www.mail-archive.com/[email protected]/msg03299.html).
> Initially I tried to setup the target on 2.6.30 kernel but was unable to
> do so. From the same link, under the Issues section, it is mentioned
> that Open FCoE target can be setup only on 2.6.23 kernel. This is
> because of the scatterlist structure issue. From one of the mail
> archives,
> (http://www.open-fcoe.org/pipermail/devel/2008-August/000526.html), it
> was known that there is no plan to support SW target on newer kernels.
> Also, during my interaction with one of the open fcoe developer, the
> older target which works with 2.6.23 is non-FIP mode, but the
> development in progress is with FIP mode. The older target may or may
> not work with the current generation switches since they might not
> support FCoE FLOGI with non-FIP.
>
>
>
> Meaning, practically, if switch does not support non-FIP with FCoE
> FLOGI, open fcoe target cannot be setup. Is my understanding correct?
> Is there no open source fcoe target that works with newer kernel?
>
>
Current initiator supports both FIP and non-FIP modes and Joe added
target support on initiator as add-on using transport providers hooks to
libfc, he added FCST as fcoe target for SCST core and also enabled FCoE
target using LIO target core, these both fcoe target flavors supports
both FIP and non-FIP modes as same initiator login code is used in these
targets.
However as both are not upstream, therefore not sure if these works with
upstream kernel and perhaps needs another update. I tried r1527 tag of
FCST and that worked fine with 2.6.33-rc8 kernel, see FCST instructions
from SCST source trunk for that.
Not sure if above answers your newer kernel working question for fcoe
target but 2.6.33-rc8 is also not so old.
>
>
>
> 2. If FC port on a FCoE switch is disabled and FCoE target(say for
> example, open fcoe sw target on 2.6.23) is setup and connected to the
> FCoE port, then there would be no FIP advertisements and FCoE FLOGI
> might not work. Is this correct? If so, why would a FCoE target not do
> FLOGI if FC ports are disabled?
>
>
If FCoE is disabled then switch may not work for either mode but you can
check with your switch vendor on this question for more details, the
trace you sent me offlist had correct FCoE FLOGI from target but no
response from switch, therefore you need to look into your switch
settings and switch tech support can be helpful here.
>
> You can have 2 fcoe switch connected to each other through the fcoe
> ports (E port) with one switch hosting the fcoe target and other having
> fcoe Initiator. In this case, how does it matter if the FC ports are
> enabled or disabled?
>
>
If you want switch to be unaware of fcoe and two hosts on connected
ports could see eth traffic having initiator and target then these
should work fine as if in point to point mode.
Vasu
>
>
>
> Thanks and Regards,
>
> Rama Raju Y.C.
>
> _______________________________________________
> 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
