Tracking GB Usage
paul at paulstewart.org
Wed Jan 19 17:43:53 UTC 2011
Interesting - thanks. I'll definitely have to check that out.
From: dhcp-users-bounces+paul=paulstewart.org at lists.isc.org
[mailto:dhcp-users-bounces+paul=paulstewart.org at lists.isc.org] On Behalf Of
Sent: Wednesday, January 19, 2011 12:18 PM
To: dhcp-users at lists.isc.org
Subject: Re: Tracking GB Usage
IPDR was developed for just this use case.
In the basic DOCSIS IPDR implimentation (all CMTSs have to do IPDR to pass
cable labs, and your Cisco and Arris both do theses) the following is the
information that is tied together. All you have to do is set the CMTS to
export IPDR records and then setup a server to collect them.
CMTShostName Name of the CMTS CMTSipAddress IP Address of the
CMTSsysUpTime SysUpTime taken from the CMTS
CMTScatvIfName CATV interface name from the Interfaces Group
CMTScatvIfIndex CATV interface index
CMTSupIfName Upstream interface name
CMTSupIfType Upstream interface type
CMTSdownIfName Downstream interface name
CMmacAddress The MAC address of the Cable Modem
CMdocsisMode The registration mode for this modem (1.0, 1.1 or
CMipAddress The IP address of the Cable Modem
CMCPEipAddress List of IP address assigned to CPE's behind the Cable
Rectype Interim indicating that the Service Flow is
still running. Stop indicating that it has completed
RecCreationTime UTC time of record creation
serviceIdenifier Service Flow ID or DOCSIS 1.0 SID
GateID GateID for PacketCable initiated service flows
serviceClassName Service Class Names applied to the service flow by the
CMTS if implemented
serviceDirection Upstream or Downstream
serviceOctetsPassed Current or final count of octets passed by this
service flow (usage counting)
servicePktsPassed Current or final count of packets passed by this
serviceSlaDropPkts Number of packets dropped by the CMTS when enforcing
a QoS SLA
serviceSlaDelayPkts Number of packets delayed by the CMTS when enforcing
a QoS SLA
serviceTimeCreated The CMTS sysUpTime when the service was created
On 01/19/2011 11:59 AM, Simon Hobson wrote:
Paul Stewart wrote:
I should have elaborated a bit more though - if we used flow data as an
example we would need a way to "bind" the cable modem MAC to the usage..?
Monitor log files to pick up changes/assignments ?
Add "on <something>" events to your DHCP config to update an external table
Once you've extracted information from DCHP to relate
devices/addresses/users then it's left as an exercise for you to then
capture traffic flows. If they are your own cable modems, then potentially
you could just use SNMP to capture interface counters.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users