On 01/15/2014 12:36 PM, Robert Love wrote:
On 01/15/2014 05:23 AM, Natti Shwarts wrote:
Hello,
I'm trying to work with SCSI target over FCoE. (using fileio sample
of SCST)
I'm using Linux 3.8.13 , Intel 10G card and HP5900 switch with VSAN
10 for
Oops... Missed the kernel version here on first read, also this seems to
imply that you configured the switch.
FCoE.
I am not familiar with the SCST commands to be able to tell you if
you're using it right. I might be able to give you some pointers to
help debug though.
The problem is that the target doesn't send FLOGI to the switch.
(I have windows client that works with the same switch and configuration
and succeed to login)
The following is the operation sequence I perform:
- vconfig add eth2 10
- load scst, scst_user
- fileio_tgt disk0 file0 disk1 file1
- modprobe fcoe
- echo eth2.10 > /sys/module/libfcoe/parameters/create_vn2vn (fcoeadm -c
eth2.10 returned an error)
This is definitely a problem.
* Does eth2.10 exist? Was the VLAN configured on the switch? How did
you configure it on the host/target? Did you manually create the vlan
or did you use the 'fipvlan' application to discover/create it?
* What was the output of the 'echo' command? Why did it fail?
* What did the log files say (dmesg/messages)? You can also turn on
debug_logging for the fcoe kernel modules to get more details. I
wouldn't bother with fcoe.ko at this point as its debug_logging is
very verbose. You could try the following commands after the modprobe.
# echo 0xFFFF > /sys/module/libfcoe/parameters/debug_logging
# echo 0xFFFF > /sys/module/libfc/parameters/debug_logging
- modprobe fcst
- echo "add disk0 0" >
/sys/kernel/scst_tgt/targets/fcst/20\:01\:b8\:ca\:3a\:62\:82\:f9/luns/mgmt
- echo "add disk1 1" >
/sys/kernel/scst_tgt/targets/fcst/20\:01\:b8\:ca\:3a\:62\:82\:f9/luns/mgmt
- echo 1 >
/sys/kernel/scst_tgt/targets/fcst/20\:01\:b8\:ca\:3a\:62\:82\:f9/enabled
My questions are:
1. What is wrong with the above sequence ?
You should have stopped at the fcoeadm fail, no need to proceed with
the failure.
2. Do you have any idea why fcoeadm fails ?
No, I don't have any information about the failure to draw a conclusion.
3. Is "fcoeadm -c eth2.10" is exactly the same as "echo eth2.10 >
/sys/module/libfcoe/parameters/create_vn2vn " ?
No. 'fcoeadm -c eth2.10' with do 'Fabric Mode' and not VN2VN.
I'm not sure what kernel version you're using. For a while we did not
have VN2VN support in fcoeadm. Only in more recent kernels did we
change the sysfs interfaces to use files in /sys/bus/fcoe/. This
change allowed us to add VN2VN support to fcoeadm with the '-m|--mode'
option. The 'echo' method is how you enable VN2VN on older kernels. On
newer kernels that method will still work, but it is deprecated
because of the new interfaces.
fcoe_sysfs went into the kernel on 2012-12-14 and 3.8 was tagged on
2013-02-18, so I think you should have the new interfaces. Does
'fcoeadm' have a '-m|--mode' option?
_______________________________________________
fcoe-devel mailing list
[email protected]
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
