[175255] in North American Network Operators' Group
Re: Keeping Track of Data Usage in GB Per Port
daemon@ATHENA.MIT.EDU (Michael Loftis)
Wed Oct 15 21:20:26 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <CAMDdSzNDYW17o-a4nXuO1-i5QdDptaxnkjWziLQhgqGbELaXDg@mail.gmail.com>
Date: Wed, 15 Oct 2014 18:20:18 -0700
From: Michael Loftis <mloftis@wgops.com>
To: Colton Conor <colton.conor@gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
IPDR under DOCSIS and generally RADIUS or TACACS(+) for DSL. Unclear
personally about fiber/FiOS deployments (never been near enough to know)
Flow (sflow, nflow, ipfix, etc) generally doesn't scale and is woefully
inaccurate.
On Wednesday, October 15, 2014, Colton Conor <colton.conor@gmail.com> wrote:
> I see in past news articles that cable companies are inaccurately
> calculating customers data usage for their online GB of usage per month. My
> question is how do you properly determine how much traffic in bytes a port
> passes per month? Is it different if we are talking about an ethernet port
> on a cisco switch vs a DSL port on a DSLAM for example? I would think these
> access switches would have some sort of stat you can count similar to a
> utility meter reader on a house. See what it was at last month, see what is
> is at this month, subtract last months from this months, and the difference
> is the total amount used for that month.
>
> Why are the cable companies having such a hard time? Is it hard to
> calculate data usage per port? Is it done with SNMP or some other method?
>
> What is the best way to monitor a 48 port switch for example, and know how
> much traffic they used?
>
>
> https://gigaom.com/2013/02/07/more-bad-news-about-broadband-caps-many-meters-are-inaccurate/
>
--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
