CISCO-CABLE-METERING-MIB
This is the MIB module for Usage Based Metering for the
DOCSIS-compliant Cable Modem Termination Systems (CMTS).
Usage Based Metering is a software feature provided in the
CMTS so that cable operators can perform subscriber
account management and metering in a uniform and
consistent manner.
It involves the implementation of Subscriber Account
Management Interface Specification (SAMIS) as defined by
DOCSIS-OSSI specification. Usage-Based Metering is
essential in the processing of bills based on services
rendered to and consumed by paying subscribers. The SAMIS
specification focuses primarily on bandwidth centric
usage-based metering scenarios.
The DOCSIS 1.1 RFI specification provides a mechanism for
a Cable Modem (CM) to register with its Cable Modem
Termination System (CMTS) and to configure itself based
on external Quality of Service (QoS) parameters when it
is powered up or reset. The principal mechanism for
providing enhanced QoS is to classify packets traversing
the RF MAC interface into a Service Flow.
A Service Flow is a unidirectional flow of packets that is
provided a particular Quality of Service.
The mediation system can then rate the charges differently
for each of the Service Flow traffic counts based on
its Service Class. Thus, the mediation system obtains from
the CMTS the traffic counts for each named Service Flow
(identified by SFID) that a subscribers CM uses during
the metering data collection interval. The Usage Based
Metering requirement is that the CMTS must be able to
provide formatted Subscriber Usage
Metering Records for all subscribers attached to the CMTS,
on demand to an external collection system. Optionally,
the metering records can be stored locally so that it is
available via ftp to the external collection server.
The CMTS provides two configuration options to handle the
export of metering data.
Local :
Store the record locally on the CMTS after collection. The
metering system should then(operating at its own schedule)
take the file out of the CMTS and is also responsible for
deletion of the local file on the CMTS. The deletion of
the file is an indication to the metering collector to
start construction of the new metering record which will
then be written to the local filesystem and the cycle
continues.
Streaming:
Stream the records to an external collection system as
they get generated. The time interval in which the record
will be generated is configurable at the CMTS. A secure
and reliable stream is used to transport the metering
record out of the CMTS.
In case the connection to external metering system is
not possible, CMTS will retry establishing channel for a
max specified times.
The MIB allows for configuration of the parameters that
control the metering record collection like interval,
amount of metering information required, location or IP
address of the collection server, and metering filename.
In addition it provides for some important notificatons to
the NMS to indicate the success/failure of the
metering collection.
- Source file
CISCO-CABLE-METERING-MIB- Last revised
- Identity
ciscoCableMeteringMIB- Base OID
1.3.6.1.4.1.9.9.424
Imported Objects
| CISCO-SMI | ciscoMgmt |
| IF-MIB | InterfaceIndexOrZero |
| INET-ADDRESS-MIB | InetAddress InetAddressType InetPortNumber |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DateAndTime RowStatus TEXTUAL-CONVENTION (no object page) TruthValue |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CABLE-METERING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CABLE-METERING-MIB::ciscoCableMeteringMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-CABLE-METERING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CABLE-METERING-MIB::ciscoCableMeteringMIB'
Objects (30)
Showing 30 of 30 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.424 |
||
.1.3.6.1.4.1.9.9.424.0 |
||
.1.3.6.1.4.1.9.9.424.1 |
||
.1.3.6.1.4.1.9.9.424.1.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.424.1.1.1 |
|
|
minutesUnsigned32
|
.1.3.6.1.4.1.9.9.424.1.1.10 |
|
|
Unsigned32
|
.1.3.6.1.4.1.9.9.424.1.1.11 |
|
|
millisecondsUnsigned32
|
.1.3.6.1.4.1.9.9.424.1.1.12 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.424.1.1.2 |
|
.1.3.6.1.4.1.9.9.424.1.1.3 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1.1 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1.2 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1.3 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1.4 |
||
.1.3.6.1.4.1.9.9.424.1.1.3.1.8 |
||
|
|
minutesUnsigned32
|
.1.3.6.1.4.1.9.9.424.1.1.4 |
|
Unsigned32
|
.1.3.6.1.4.1.9.9.424.1.1.5 |
|
.1.3.6.1.4.1.9.9.424.1.1.6 |
||
.1.3.6.1.4.1.9.9.424.1.1.7 |
||
.1.3.6.1.4.1.9.9.424.1.1.8 |
||
.1.3.6.1.4.1.9.9.424.1.1.9 |
||
.1.3.6.1.4.1.9.9.424.1.2 |
||
.1.3.6.1.4.1.9.9.424.1.2.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.424.1.2.2 |
|
.1.3.6.1.4.1.9.9.424.1.2.3 |
||
.1.3.6.1.4.1.9.9.424.1.2.4 |
||
.1.3.6.1.4.1.9.9.424.3 |
||
.1.3.6.1.4.1.9.9.424.3.1 |
||
.1.3.6.1.4.1.9.9.424.3.2 |
Dependencies (9) 7 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-CABLE-METERING-MIBciscoselected
Type Definitions (2)
| Enumeration |
primary(1)secondary(2) |
|
| Enumeration |
unknown(1)success(2)deviceFull(3)writeError(4)fileNotExist(5)connectionTimeout(6)dataIncomplete(7) |
Conformance Groups (6)
|
ccmtrMeteringObjGroup
deprecated
|
ccmtrCollectionType ccmtrCollectionFilesystem ccmtrCollectionIpAddrType ccmtrCollectionIpAddress ccmtrCollectionPort ccmtrCollectionInterval ccmtrCollectionRetries ccmtrCollectionSecure ccmtrCollectionRowStatus ccmtrCollectionCpeList ccmtrCollectionAggregate ccmtrCollectionStatus ccmtrCollectionDestination ccmtrCollectionTimestamp
Group of objects implemented in CMTS
providing for usage based metering configuration and notification information. This group is deprecated by ccmtrMeteringObjGroupRev1. |
.1.3.6.1.4.1.9.9.424.3.2.1
|
|
The notification control which a
CISCO-CABLE-METERING-MIB is required to implement. |
.1.3.6.1.4.1.9.9.424.3.2.2
|
|
|
The notification which a CISCO-CABLE-METERING-MIB
is required to implement. |
.1.3.6.1.4.1.9.9.424.3.2.3
|
|
|
ccmtrCollectionType ccmtrCollectionFilesystem ccmtrCollectionIpAddrType ccmtrCollectionIpAddress ccmtrCollectionPort ccmtrCollectionRowStatus ccmtrCollectionRetries ccmtrCollectionSecure ccmtrCollectionCpeList ccmtrCollectionAggregate ccmtrCollectionRevInterval ccmtrCollectionStatus ccmtrCollectionDestination ccmtrCollectionTimestamp
Group of objects implemented in CMTS providing for usage based
metering configuration and notification information. |
.1.3.6.1.4.1.9.9.424.3.2.4
|
|
|
Group of objects implemented in CMTS to define the source
interface for the billing packets. |
.1.3.6.1.4.1.9.9.424.3.2.5
|
|
|
Group of objects implemented in CMTS to control as well as
throttle the rate of export of the service flow data. |
.1.3.6.1.4.1.9.9.424.3.2.6
|
Compliance Statements (2)
OID
.1.3.6.1.4.1.9.9.424.3.1.1The compliance statement for CMTS devices that implement
the Usage Based Metering feature.
This compliance is deprecated by
ciscoCableMeteringComplianceRev1.
the Usage Based Metering feature.
This compliance is deprecated by
ciscoCableMeteringComplianceRev1.
Required groups
| mandatory | ccmtrMeteringObjGroup | |
| mandatory | ccmtrMeteringNotifCtrlGroup | |
| mandatory | ccmtrMeteringNotifGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| ccmtrCollectionIpAddrType | Only ipv4 type of internet address is supported. | ||
| ccmtrCollectionPort | Value of 0 for port number is not supported. | ||
| ccmtrCollectionRowStatus | createAndGo, active and destroy are the only RowStatus values that will be supported for this object. |
OID
.1.3.6.1.4.1.9.9.424.3.1.2The compliance statement for CMTS devices that implement
the Usage Based Metering feature.
the Usage Based Metering feature.
Required groups
| mandatory | ccmtrMeteringNotifCtrlGroup | |
| mandatory | ccmtrMeteringNotifGroup | |
| mandatory | ccmtrMeteringObjGroupRev1 | |
| mandatory | ccmtrMeteringSrcIntfObjGroup | |
| mandatory | ccmtrMeteringRateCtrlObjGroup |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| ccmtrCollectionIpAddrType | Only ipv4 type of internet address is supported. | ||
| ccmtrCollectionPort | Value of 0 for port number is not supported. | ||
| ccmtrCollectionRowStatus | createAndGo, active and destroy are the only RowStatus values that will be supported for this object. |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.424.0.1 |
A notification that is sent to indicate the success or
failure in creating the metering record file or streaming it to the collection server. ccmtrCollectionStatus represents the success or failure of the export. ccmtrCollectionDestination and ccmtrCollectionTimestamp represent the destinaton and timestamp of the export in both the success and failure scenerios. The receipt of this notification is an indication to the collection server that the file can be accessed via ftp or any file transfer protocol in the case of local storage. |