[ixpmanager] update-l2database.pl not updating database

[Brian Thompson]

Thanks Nick,

If I understand you correctly, I would disagree that the data would be
"wrong", I would say the data is "incomplete".  Yes what I am asking is to
define the accounting perimeter to the Juniper switch only.  Accounting is
not used for any billing purposes.

If members 1,2,3,4,5,6 were on Juniper, and 7,8,9 were on Cisco, and the
port on the Juniper trunked to the Cisco was set to new Port Type
"Core-Other".  There could be p2p graphs between any juniper member to any
juniper member.  Any graph from a Juniper member to Cisco member would only
show ingress traffic.  Although we could have a graph from a Juniper member
to "Other" that would show both egress and ingress, through the egress
would be from members [7,8,9].

We really are a small IXP 40+ members but we have changed our pricing to
free 1G ports to promote growth.  We have already tripled our traffic in
the last three months.

Getting IXP-M running with a route server would allow us to grow leaps and
bounds as we have large provider networks that will peer with a route
server but not each little member.



*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 Sun, Dec 15, 2013 at 3:33 PM, Nick Hilliard <nick at inex.ie> wrote:

> On 15/12/2013 22:41, Brian Thompson wrote:
> > Could we have a new switch port type e.g. "core-other" that could define
> > the edge of sflow data, so the data is collected and counted from all
> > non-sflow peers as an aggregate.   We very much would like to have the
> > sflow data for the other members of the exchange.
>
> Hi Brian,
>
> If you do this, your accounting perimeter will be wrong.  You'll get zero
> figures in your p2p graphs for members on that switch and completely wrong
> information in the aggregates.  The code isn't doing a whole lot with the
> aggregates at the moment, but we plan to make them visible in the UI at
> some stage and may at some stage use them in preference to the mrtg code. I
> don't want to sound unhelpful here, but using intermediate accounting
> points for sflow data collection gives wrong data in all cases so we're not
> going to write code to support this.
>
> 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/20131215/d592ff57/attachment.html>