Tony,
Take a look at pmacct, it will be able to handle your needs with a number of
modifications. The section I linked below should give you a good starting
point. Change the traffic dump to a MySQL database, add some indexes, craft
some SQL queries, then you're off to the races. As for billing
Tony,
You might find the following article useful in identifying features to
consider when evaluating sFlow analyzers:
https://blog.sflow.com/2009/05/choosing-sflow-analyzer.html
The following white paper discusses accuracy of packet sampling for usage
accounting:
https://inmon.com/pdf/sFlowBilli
I’m curious what the service is that 50Mbps avg over a 24 hr window is an
investigative threshold.
On Sat, Apr 13, 2019 at 17:57 Peter Phaal wrote:
> Tony,
>
> You might find the following article useful in identifying features to
> consider when evaluating sFlow analyzers:
> https://blog.sflow.
?
Please keep the suggestions coming.
Tony
From: Tom Beecher [mailto:beec...@beecher.cc]
Sent: Sunday, April 14, 2019 9:24 AM
To: Peter Phaal
Cc: Tony C ; nanog
Subject: Re: Sflow billing or usage calculation software
I’m curious what the service is that 50Mbps avg over a 24
On 14. Apr 2019, at 13:28, Tony C wrote:
>
> Please keep the suggestions coming.
I’ve had good results using Traffic Sentinel from Inmon. It’s got a nice
queriable database backend and you don’t have to do much manual setup to get
good results. The UI feels a bit 1995, but it works, and the AP
Sflow being IP/protocol/etc aware.
thanks in advance,
Deepak
-Original Message-
From: NANOG [mailto:nanog-bounces+deepak=ai@nanog.org] On Behalf Of Nick
Morrison
Sent: Sunday, April 14, 2019 8:09 AM
To: Tony C
Cc: nanog
Subject: Re: Sflow billing or usage calculation software
On 1
> On 16. Apr 2019, at 00:21, Deepak Jain wrote:
>
> I'm only aware of Sflow being IP/protocol/etc aware.
Actually the sflow standard is flexible, and there are many fields widely
available, including input interface and output interface, vlan/vxlan/mpls
headers, etc. The sending device just n
>On Tue, Apr 16, 2019 at 2:14 AM Nick Morrison wrote:
>
> Actually the sflow standard is flexible, and there are many fields widely
> available, including input interface and output interface, vlan/vxlan/mpls
> headers, etc. The sending device just needs to support the fields.
Vendor support f
Thanks for the pointers and suggestions!
Now I know I'm pushing my luck... but do certain vendors more fully
embrace sFlow than others? maybe one of the whitebox vendors if not one
of the majors?
Hacking support into something isn't the worse thing in the world, but
if there is any experienc
On Tue, Apr 16, 2019 at 8:35 PM Deepak Jain wrote:
> Now I know I'm pushing my luck... but do certain vendors more fully
> embrace sFlow than others? maybe one of the whitebox vendors if not one
> of the majors?
>
> Hacking support into something isn't the worse thing in the world, but
> if there
10 matches
Mail list logo