So the missing priority flow control is the only limitation?

Is the LUID Exchange not necessary in FCoE VN2VN mode?
- Probe Request (#1) (Multicast: All_VN2VN_Enode_MACs)
- Claim Notification (Multicast: All_VN2VN_Enode_MACs, inc. FC-4
attributes)
- Beacon  (Multicast:  Send every Beacon_Period)
 
On the target side (open fcoe) I just need to start the following services
without any lldpad and further dcbtool settings?

lldpad -k # terminate curreny running lldpad
service lldpad stop # just in case if it's started
service fcoe restart
echo eth2.569 > /sys/module/libfcoe/parameters/create_vn2vn
echo eth2.569 > /sys/module/libfcoe/parameters/enable
dcbtool sc eth2 dcb off # switch dcb off

Thanks,
Gerald

-----Original Message-----
From: Neil Horman [mailto:[email protected]] 
Sent: Monday, August 26, 2013 12:50 PM
To: Gerald Stanje
Cc: [email protected]
Subject: Re: [Open-FCoE] DCBTool fails on tap0

On Mon, Aug 26, 2013 at 12:04:28PM -0700, Gerald Stanje wrote:
> Hello Neil,
> 
> What's the workaround?
> 
> Thanks,
> Gerald
> 
To the best of my knoweldge, just don't set dcb settings on the adapter.
IIRC if your adapter doesn't support dcb, then you just send vlan
encapsulated fcoe frames on the same output queue as any other traffic.
You  loose the ability to do hardware priority classification of course,
but theres no way around that Neil

> -----Original Message-----
> From: Neil Horman [mailto:[email protected]]
> Sent: Monday, August 26, 2013 11:28 AM
> To: Gerald Stanje
> Cc: [email protected]
> Subject: Re: [Open-FCoE] DCBTool fails on tap0
> 
> On Mon, Aug 26, 2013 at 10:50:55AM -0700, Gerald Stanje wrote:
> > Hello,
> > 
> >  
> > 
> > I use VN2VN mode and tried to create the following topology:
> > 
> >  
> > 
> > eth2.569 (ixgbe)                             tap0.569------ fcoe
target
> > 
> >        |                                                            |
> > 
> >         --------------- virbr1---------------
> > 
> >  
> > 
> > I attached my script including output and the syslog at the end.
> > 
> > Why does the call dcbtool fail with this message: Device not found, 
> > link down or DCB not enabled???
> > 
> Because the tap0 interface, being a software defined virtual interface 
> has no hardware to enable DCB on.
> 
> Neil
> 
_______________________________________________
fcoe-devel mailing list
[email protected]
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel

Reply via email to