[Open-FCoE] Setup question

charles zhuang charlesz at opengridcomputing.com
Thu Sep 11 21:26:29 UTC 2008


Hi,
I am new to the community and just built the environment yesterday
(following the quick start guide on target and initiator). Here's couple
of questions and issues that I will greatly appreciate if I can get some
help from you. I have read all the open-fcoe web site and arch mail. 
1. Once I start the initiator and the target, 
>From initiator side I saw dmesg like following:
Sep 11 08:50:39 linux kernel: SCSI subsystem initialized
Sep 11 08:51:17 linux kernel: scsi0 : FCoE Driver
 
>From target side I saw dmesg like following:
Sep 11 10:58:43 vic17 kernel: [29440]: scst:
scst_cmd_thread:3296:Processing thread started, PID 29440
Sep 11 10:58:43 vic17 kernel: [29441]: scst:
scst_cmd_thread:3296:Processing thread started, PID 29441
Sep 11 10:58:43 vic17 kernel: [29443]: scst:
scst_init_cmd_thread:3076:Init thread started, PID 29443
Sep 11 10:58:43 vic17 kernel: [29445]: scst:
scst_mgmt_cmd_thread:4636:Task management thread started, PID 29445
Sep 11 10:58:43 vic17 kernel: [29432]: scst: init_scst:1784:SCST version
1.0.1 loaded successfully (max mem for commands 252MB, per device 100MB)
Sep 11 10:58:43 vic17 kernel: [29432]: scst:
scst_print_config:1589:Enabled features: EXTRACHECKS, DEBUG
Sep 11 10:58:43 vic17 kernel: [29446]: scst:
scst_mgmt_thread:5127:Management thread started, PID 29446
Sep 11 10:58:43 vic17 kernel: [29432]: scst:
__scst_register_target_template:235:Target template openfct registered
successfully
Sep 11 10:58:44 vic17 kernel: device eth0 entered promiscuous mode
Sep 11 10:58:44 vic17 kernel:  mtu 1478
Sep 11 10:58:44 vic17 kernel: fc_local_port_recv_flogi_req: FLOGI from
port WWPN 20000002b3d90d26
Sep 11 10:58:44 vic17 kernel: [29464]:
scst_suspend_activity:477:suspend_count 0
Sep 11 10:58:44 vic17 kernel: [29464]: scst_susp_wait:456:wait_event()
returned 0
Sep 11 10:58:44 vic17 kernel: [29464]: scst_suspend_activity:516:Waiting
for 0 active commands finally to complete
Sep 11 10:58:44 vic17 kernel: [29464]: scst_susp_wait:456:wait_event()
returned 0
Sep 11 10:58:44 vic17 kernel: [29464]:
__scst_resume_activity:546:suspend_count 0 left
Sep 11 10:58:44 vic17 kernel: [29464]: scst: scst_register:357:Target
<NULL> (f733f980) for template openfct registered successfully
Sep 11 10:58:46 vic17 kernel: fc_local_port_recv_flogi_req: FLOGI from
port WWPN 20000002b3d90d26
Sep 11 10:59:18 vic17 last message repeated 16 times
 
>From the wireshark, I saw constant FLOGI command packet send out from
initiator to ethernet destination address 0e:fc:00:ff:ff:fe. That's the
only fcoe packet I saw.
My initiator ethernet addr is 00:02:B3:D9:0D:26, so from the target log,
looks like it correctly receive the flogi request but fail to generate
the response. I assume I will get a trace in initiator like
"fc_local_port_flogi_resp point-to-point mode ..." if indeed the target
send out the response. So does that means the problem is on the target
side?
 
>From the note in target quick start, "Note that the target doesn't know
it's a target and attempts FLOGIs. If you're not seeing FLOGIs from the
target you have a problem." Once I do "fcconf eth0 enable", I should see
FLOGI packet send out from target even at that time there's no initiator
exist, correct?
 
For my target setup, I don't have a scsi disk, only ide disk ("lsscsi"
come out empty). Does that cause this problem? I saw some post that use
vdisk, is that workable now? If so, can someone post a detail
instruction on how to do that? Basically I just try to run from my
current ide disk instead of adding a new scsi disk to the system.
 
Also, on the initiator, I don't have openfc.ko, I only have fcoe.ko,
libfc.ko, scsi_transport_fc.ko, and scsi_mod.ko. Did I miss anything?
 
2. By following the quick start on initiator, my initiator system
doesn't have fcconf. I guess I can use the same procedure on the target
quick start guide to build/install fcconf and hbaapi. I don't need
openfctgt and scst. Is it correct?
 
Thanks very much for your help.
 
charles
 
 



More information about the devel mailing list