[30302] in North American Network Operators' Group
Re: bw usage?
daemon@ATHENA.MIT.EDU (Dana Hudes)
Wed Jul 26 11:23:30 2000
Message-ID: <015301bff715$252ad080$3d5cdcd1@hudes.org>
From: "Dana Hudes" <dhudes@hudes.org>
To: "Jeremy Brandt" <JBrandt@scient.com>,
"David M. Ramsey" <dmr@webserve.net>, <nanog@merit.edu>
Date: Wed, 26 Jul 2000 11:21:17 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: owner-nanog-outgoing@merit.edu
You can use Cisco NetFlow Export as a basis for billing.
Capture the data with cflowd.
I've done some work in this area for traffic engineering. It could be =
adapted to a billing solution as well.
Interested parties please contact me off-list
----- Original Message -----=20
From: "Jeremy Brandt" <JBrandt@scient.com>
To: "David M. Ramsey" <dmr@webserve.net>; <nanog@merit.edu>
Sent: Wednesday, July 26, 2000 11:09 AM
Subject: RE: bw usage?
>=20
> If you are using Cisco 6500 switches you an use Private VLANS. They =
do
> exactly what you want without wasting IP addresses.
>=20
> Jeremy Brandt
> Infrastructure Architect
> Scient
>=20
> -----Original Message-----
> From: David M. Ramsey [mailto:dmr@webserve.net]
> Sent: Wednesday, July 26, 2000 9:54 AM
> To: nanog@merit.edu
> Subject: bw usage?
>=20
>=20
>=20
> Folks,
>=20
> I'm interested in learning which tools other people are using to =
measure
> bandwidth usage for co-located client machines on Ethernet switches.
>=20
> For now I've cobbled together some crude software to regularly=20
> read SNMP port byte in/out counters from our switches, stashing=20
> the deltas in a DB for later reporting/analysis.
>=20
> I'm concerned that the data is misleading, though, in that it will
> include LAN broadcast traffic. Also, customers end up paying=20
> for other bandwidth that they did not want or induce, like network=20
> scans, etc. (tough luck?).
>=20
> We've considered implementing unique customer VLANS to separate
> customer broadcast domains, but it seems like that'd be a pain,
> would eat up IP addresses, and possibly tax our routers with all of
> the ISL/VLAN stuff?
>=20
> Thanks in advance for any help/hints/pointers/advice you can offer.
>=20
> Regards, --dmr
>=20
> David Ramsey
> Charlotte, NC
