[30317] in North American Network Operators' Group
Re: bw usage?
daemon@ATHENA.MIT.EDU (Paul Froutan)
Wed Jul 26 16:48:43 2000
Message-Id: <4.2.2.20000726153505.04f07610@pop3.rackspace.com>
Date: Wed, 26 Jul 2000 15:36:56 -0500
To: Alex <alex@nac.net>, "David M. Ramsey" <dmr@webserve.net>
From: Paul Froutan <pfroutan@rackspace.com>
Cc: nanog@merit.edu
In-Reply-To: <Pine.WNT.4.21.0007261120580.836-100000@EXPLOSION>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_16359475==_.ALT"
Errors-To: owner-nanog-outgoing@merit.edu
--=====================_16359475==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 7/26/00 -0400, Alex wrote:
>On Wed, 26 Jul 2000, David M. Ramsey wrote:
>
> > For now I've cobbled together some crude software to regularly
> > read SNMP port byte in/out counters from our switches, stashing
> > the deltas in a DB for later reporting/analysis.
>
>We do about the same thing, but we store absolute byte counts, relative
>byte counts from the last measurement, and figure the kb/s; we also store
>AdminStatus and OperStatus for SLA purposes.
>
>
> > I'm concerned that the data is misleading, though, in that it will
> > include LAN broadcast traffic. Also, customers end up paying
> > for other bandwidth that they did not want or induce, like network
> > scans, etc. (tough luck?).
>
>Exactly, tough. If they use the bandwidth, then they should pay for the
>bandwidth.
Depending on which switch you're using, you can also poll the switch for
broadcast and multicast on the port and subtract that from the total so you
don't bill for that.
----------------------------------------------------------------------
Paul Froutan Email: pfroutan@rackspace.com
Rackspace Managed Hosting <http://www.rackspace.com>
--=====================_16359475==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
At 7/26/00 -0400, Alex wrote:<br>
<br>
<blockquote type=cite cite>On Wed, 26 Jul 2000, David M. Ramsey
wrote:<br>
<br>
> For now I've cobbled together some crude software to regularly
<br>
> read SNMP port byte in/out counters from our switches, stashing
<br>
> the deltas in a DB for later reporting/analysis.<br>
<br>
We do about the same thing, but we store absolute byte counts,
relative<br>
byte counts from the last measurement, and figure the kb/s; we also
store<br>
AdminStatus and OperStatus for SLA purposes. <br>
<br>
<br>
> I'm concerned that the data is misleading, though, in that it
will<br>
> include LAN broadcast traffic. Also, customers end up paying
<br>
> for other bandwidth that they did not want or induce, like network
<br>
> scans, etc. (tough luck?).<br>
<br>
Exactly, tough. If they use the bandwidth, then they should pay for
the<br>
bandwidth.</blockquote><br>
<br>
Depending on which switch you're using, you can also poll the switch for
broadcast and multicast on the port and subtract that from the total so
you don't bill for that.<br>
<br>
<font face="Fixedsys">----------------------------------------------------------------------<br>
Paul Froutan
<x-tab> </x-tab><x-tab> </x-tab><x-tab> </x-tab><x-tab> </x-tab>
Email: pfroutan@rackspace.com <br>
Rackspace Managed
Hosting<x-tab> </x-tab><x-tab> </x-tab>
<</font><a href="http://www.rackspace.com/" eudora="autourl"><font face="Fixedsys" color="#0000FF"><u>http://www.rackspace.com</a></font></u><font face="Fixedsys">><x-tab> </x-tab>
<br>
</font></html>
--=====================_16359475==_.ALT--
