> On 02/17/2011 10:39 AM, Robert Love wrote:
> > Open-FCoE provides FCoE support for any Ethernet adapter, some have
> > offloads and some don't. You can use lldpad, from open-lldp.org, for
> the
> > lossless network, or you can use simple pause if you're not going to do
> > any converged traffic. The QUICKSTART file in fcoe-uitls should have
> > some details about lldpad. In the absence of a Fibre Channel fabric and
> > Fibre Channel Forwarders you can connect a SW initiator with a SW
> target
> > using a point-to-point connection.
> >
> > So the bottom line is that you can do FCoE with two systems connected
> > back to back.
> 
> Hi Rob, sorry to revive an old-ish thread..
> 
> Two systems back-to-back, ethtool -a needs to show TX & RX pause enabled
> for both ends?
Ethtool -a indicates only link pause, which is probably already good enough
for you to play fcoe stack in back-to-back. DCB setting has to be from the
lldpad as Rob mentioned. However, if to start you just want to see the basic
fcoe protocol stack work, i.e., getting fcid, you most probably can live w/o
any pause on back-to-back setup unless you are running ip at the same time
on the same port, but just be aware the frames are not guaranteed to be not
dropped. We started open-fcoe w/o fully support on DCB, however, the individual
cfg-ethx file has to have DCB_REQUIRED being turned off.

In the past, I had it set up not directly back-to-back but through a sw linux
bridge, then wireshark on the Bridge helps the devel/debug a lot.

> 
> I'm also interested with experiences doing fcoe development in a VM.
> Does VM--VM traffic ever result in dropped frames, I wonder?
The open-fcoe protocol stack should work just fine I think, it's just L2 frame
for vm-vm traffic. I never tried, so can't say for sure, I would think it should
work unless you have setup explicitly to drop them on the virtual switch for 
vms.
Offload for FCoE on guest or vm probably won’t work, I don't know any vf driver
has support for FCoE offload yet...

> 
> Regards -- Andy

Hope this help,
yi

> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.open-fcoe.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
[email protected]
https://lists.open-fcoe.org/mailman/listinfo/devel

Reply via email to