Avadhoot Punde wrote:
> I did some research and found that few devs are working on fcst, which
> bridges the gap between scst and fcoe. Using the instructions given in
> README, I could successfully install scst and fcst. However, I would like to
> export the disks without installing any initiator on the same machine. Is
> this possible ?
Not currently. I have some fixes where the initiator is enabled explicitly
but there's no config method to tell fcoe not to enable the initiator.
However, it should be OK to register both as an initiator and a target.
Long term, I think we'll have that ability.
> Once I export a scsi disk on the target, I should be able to export it over
> fcoe, so that remote initiator can login and directly see scsi device in its
> /dev directory.
Yes.
> Regarding the same, how do I start fcoe target on a specific ethX ? What are
> the configuration steps after exporting scsi disk to
> /proc/scst_tgt/groups/Default/devices ?
You start fcoe target the same way you start the initiator.
fcoeadm -c ethX
For fcst, you need
to use the /sys method of configuration for scst, though. To do that you need
to build scst using
make disable_proc
and then remake scst (and probably fcst).
Once you have the /sys/kernel/scst_tgt tree, you will see a group for the
ethX WWPN under
cd /sys/kernel/scst_tgt/targets/fcst/<WWPN>/ini_group
you can add each initiator port to that by cd-ing there and doing
echo create group-name > mgmt
echo add <initiator-wwpn> > group-name/initiators/mgmt
If the initiator is already logged in at this point, you may need
to reset it so it sees the target features.
This is due to a flaw that I also have patches in the works for, which
make the target re-register with the fabric once it is enabled as a target.
You're one of the first people to try fcst, so, thanks for being a pioneer.
Joe
> On Sat, May 22, 2010 at 8:36 AM, Avadhoot Punde
> <[email protected]>wrote:
>
>> Hi
>>
>> The document
>> http://www.mail-archive.com/[email protected]/msg03299.htmlcontains good
>> information on setting up FCOE initiator and target. Do we
>> have a similar document when both initiator and target are using > 2.6.29
>> kernel ?
>>
>> I could build and install scst and libhbaapi, however, how do I install
>> openfc and fcoe at target side in the 2.6.30 kernel ? Do I need to compile
>> the vanilla kernel code ?
>>
>> Initiator seems pretty straightforward. Simply $modprobe fcoe and $echo
>> "ethX" >/sys/module/fcoe/create works.
>>
>> Regards,
>> Avadhoot
>>
>>
> _______________________________________________
> 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
