[ixpmanager] LAG and SFLOW workaround

[Brian Thompson]

Nick,  Yes I understand OSS.  I did fork IXP and massaged @Rowanthorpe code
in to my own and submitted a pull request.

I was really just asking the community that someone must have some private
code to make theirs work.  I am surprised that other IX don't have this
issue.  Or they created a private workaround.

Could you describe "foundation work" and how I might leverage that, to make
sure I am moving the ball in the right direction?  I also am
not familiar with 'kit' could you send me a reference so I can put more
context around your comments.

Thanks,
Brian

*Brian Thompson*
Senior Infrastructure Engineer // Senior Second Guesser

Direct: 503.943.6779
Mobile: 503.707.9018 // Twitter: iovation
*www.iovation.com <http://www.iovation.com/>*



On Wed, Feb 5, 2014 at 2:19 PM, Nick Hilliard <nick at inex.ie> wrote:

> On 05/02/2014 18:00, Brian Thompson wrote:
> > After 3 months working on https://github.com/inex/IXP-Manager/issues/104to
> > find out LAG is not supported.
> >
> > Is there any workarounds?  We are a small IX but we already have one
> member
> > with two 10gig ports in a lag, and all of our other members want to know
> > how much of their traffic is going to that member.
> >
> > Who else has LAG ports and P2P graphs?
>
> Brian,
>
> sflow LAG graphs work fine on kit which assign lags directly on the
> ethernet interfaces (e.g. brocade and extreme boxes).
>
> As INEX doesn't use kit which implements virtual-interface style LAGs,
> implementing it for other systems is down a bit on our priority list,
> particularly as Dell's sflow implementation doesn't work correctly (the
> flows are measured in the wrong direction) and Cisco doesn't implement
> sflow at all. This leaves only juniper boxes as a target platform.
>
> We've put in some of the foundation work to handle the virtual interface
> approach, but getting from there to a working implementation will take some
> work.
>
> I know it's nice feature of IXP Manager, but bear it in mind that we didn't
> sflow graphs at INEX until about 18 months ago, even though we've been
> working on IXP Manager since 2006.
>
> There are two options:
>
> - live with it for the time being until we get to fixing it
> - contribute code
>
> This is the nature of open source software.  It may not always do what you
> want, but you always have the option of fixing it.
>
> Nick
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20140205/0f0ce3f2/attachment.html>