On 6/18/10 5:59 AM, ganesh nikam wrote:
> Hi Friends,
>
> I am trying to make communication between FCoE targert and intiator.
>
> FCoE Initiator : this is the VMware Virtual Machine with Ubuntu 10.4 and
> kernel 2.6.32
>
> FCoE Target : this is the VMware Virtual Machine with Ubuntu 10.4 and kernel
> 2.6.34
>
> my FCoE target is unable to receive or transmit any FCoE packets.
>
> I have searched on Google and found that target should have pause priority
> support on its interface, otherwise i will not send FCoE packets. Virtual
> machine interface do not support pause priority feature.
>
> following threads gives some details to resolve this problem.
>
> http://www.open-fcoe.org/pipermail/devel/2008-February/000130.html
>
> as per this thread, if i have to put hack to ignore the pause-priority
> support check, then where do (I mean which module, fcoe libfc libfcoe or
> fcst) I put this hack. or if you have some other solution/ workaround then
> that will be very helpful to me
That is an old mail and the pause check is no longer in the kernel, it's
done by the daemon fcoemon.
I would try this on the target then the initiator:
service fcoe stop # stop fcoemon
fcc del eth0 # use actual interface name if not eth0
fcc en eth0
fcc refers to contrib/fcc.sh in the fcoe-tools distribution.
See if that works. Stopping fcoe means that fcoemon won't run and won't
do DCBX and check for pause. The fcc commands will delete and recreate
the FCoE instance and it should run with or without pause.
On point-to-point setups currently, the target first comes up as an initiator
and then changes to target mode. The initiator, if already active, will
not inform SCSI of this role change, so the LUNs aren't discovered. Starting
or restarting the initiator after the target works around this. I have fixes
for this in upcoming fcst patch sets.
Cheers,
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
