[112589] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Usage-Based Billing for DIA

daemon@ATHENA.MIT.EDU (Sam Stickland)
Mon Mar 9 05:30:28 2009

Date: Mon, 09 Mar 2009 09:30:14 +0000
From: Sam Stickland <sam_mailinglists@spacething.org>
To: Jon Lewis <jlewis@lewis.org>
In-Reply-To: <Pine.LNX.4.61.0903051710040.6312@soloth.lewis.org>
Cc: "Rodriguez, Mauricio" <Mauricio.Rodriguez@fpl.com>,
	"nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

Jon Lewis wrote:
> On Thu, 5 Mar 2009, Rodriguez, Mauricio wrote:
>
>> Looking at possibilities for an implementation of usage-based 
>> billing, it seems that the same techniques and tools always come up.  
>> I'm looking for some feedback from the list on experiences with these 
>> tools and techniques as well as alternatives that may not be listed 
>> here.
>>
>> +Techniques
>>                --Flow data (Netflow, SFlow, etc) analysis to 
>> determine 95th percentile traffic levels
>>                --SNMP polling of interface counters to determine 95th 
>> percentile traffic levels
>
>
> I need to look into this in the near future as well.  The problems I'm 
> aware of are:
>
> 1) we have customers on policed ports, and the interface snmp counters 
> count packets before service-policy.  It doesn't seem right to bill 
> for packets we dropped :)...so this isn't useful data for billing 
> purposes.
>
Torrus (www.torrus.org) can use the Cisco MIBs to graph pre and 
post-policy packets.

http://www.torrus.org/plugins/tp-cisco-cbqos.pod.html

Sam


home help back first fref pref prev next nref lref last post