<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">IPDR was developed for just this use case. <br>
<br>
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. <br>
<br>
Tom.<br>
<br>
CMTShostName Name of the CMTS CMTSipAddress IP Address
of the CMTS <br>
CMTSsysUpTime SysUpTime taken from the CMTS <br>
CMTScatvIfName CATV interface name from the Interfaces
Group <br>
CMTScatvIfIndex CATV interface index <br>
CMTSupIfName Upstream interface name <br>
CMTSupIfType Upstream interface type<br>
CMTSdownIfName Downstream interface name <br>
CMmacAddress The MAC address of the Cable Modem<br>
CMdocsisMode The registration mode for this modem
(1.0, 1.1 or 2.0)<br>
CMipAddress The IP address of the Cable Modem<br>
CMCPEipAddress List of IP address assigned to CPE’s behind
the Cable Modem<br>
Rectype Interim indicating that the Service
Flow is still running. Stop indicating that it has completed<br>
RecCreationTime UTC time of record creation<br>
serviceIdenifier Service Flow ID or DOCSIS 1.0 SID<br>
GateID GateID for PacketCable initiated
service flows <br>
serviceClassName Service Class Names applied to the service
flow by the CMTS if implemented<br>
serviceDirection Upstream or Downstream<br>
serviceOctetsPassed Current or final count of octets passed by
this service flow (usage counting)<br>
servicePktsPassed Current or final count of packets passed by
this service flow<br>
serviceSlaDropPkts Number of packets dropped by the CMTS when
enforcing a QoS SLA<br>
serviceSlaDelayPkts Number of packets delayed by the CMTS when
enforcing a QoS SLA<br>
serviceTimeCreated The CMTS sysUpTime when the service was
created</font><br>
<br>
<br>
<br>
On 01/19/2011 11:59 AM, Simon Hobson wrote:
<blockquote cite="mid:p0624083fc95cc848249f@simon.thehobsons.co.uk"
type="cite">Paul Stewart wrote:
<br>
<br>
<blockquote type="cite">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..?
<br>
</blockquote>
<br>
Monitor log files to pick up changes/assignments ?
<br>
Add "on <something>" events to your DHCP config to update an
external table ?
<br>
<br>
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.
<br>
<br>
</blockquote>
</body>
</html>