CISCO-CABLE-METERING-MIB.mib object view, vendor Cisco
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-CABLE-METERING-MIB and use it to monitor vendor specific OID's.
CISCO-CABLE-METERING-MIB file content
Object view of CISCO-CABLE-METERING-MIB:
| Scalar Object |
| ccmtrCollectionType |
.1.3.6.1.4.1.9.9.424.1.1.1 |
|
Current method of export for metering data.
The enumerations are:
none(1) : Metering collection has not been enabled.
local(2) : Store the collected metering records locally
on the CMTS.
stream(3) : Stream the metering records to an external
collection or mediation server.
|
| ccmtrCollectionFilesystem |
.1.3.6.1.4.1.9.9.424.1.1.2 |
|
The filesystem where metering records are to be stored.
This object makes sense only if ccmtrCollectionType object
is local which indicates that the metering records are
to be stored in the local filesystem.
When ccmtrCollectionType is 'stream' this object will
retain its set value though it will not be used.
|
| ccmtrCollectionEntry |
.1.3.6.1.4.1.9.9.424.1.1.3.1 |
|
A set of IP attributes of the mediation or
collection server and configuration parameters for
streaming the metering records.
An entry in this table exists for each configured
mediation or collection server.
|
| ccmtrCollectionInterval |
.1.3.6.1.4.1.9.9.424.1.1.4 |
|
The interval in which the metering information is
collected.
This object makes sense only if ccmtrCollectionType object
is stream which indicates that the metering records
are to be streamed to an external collection server.
|
| ccmtrCollectionRetries |
.1.3.6.1.4.1.9.9.424.1.1.5 |
|
The number of retries to stream the metering records to
the external collection server before an error is flagged.
This object makes sense only if ccmtrCollectionType object
is stream which indicates that the metering records
are to be streamed to an external collection server.
|
| ccmtrCollectionSecure |
.1.3.6.1.4.1.9.9.424.1.1.6 |
|
An indication of whether the streaming to the collection
server should be secure or not. The value of true
indicates that the streaming will be secure and false
indicates non-secure.
However the secure option is available only if the image
on the CMTS allows for security.
This object makes sense only if ccmtrCollectionType object
is stream which indicates that the metering records
are to be streamed to an external collection server.
|
| ccmtrCollectionCpeList |
.1.3.6.1.4.1.9.9.424.1.1.7 |
|
An indication if one would like the metering records to
contain the CPE(Customer premises equipment) IP addresses.
This option is provided to improve performance.
By default, this object is true which means the CPE
information will always be present.
|
| ccmtrCollectionAggregate |
.1.3.6.1.4.1.9.9.424.1.1.8 |
|
An indication if one would like only aggregate Service Flow
information per Cable Modem to be recorded. In this case
the record will have a SFID of 0 and a blank Service Class
Name. The distinction between upstream and downstream will
however be maintained. The counters present in the metering
records in this case will be the aggregate. i.e., sum of all
upstream/downstream service flows. By default, this object
is false which means that the metering records will
contain service flow counter information for all service
flows per CM.
|
| ccmtrCollectionStatus |
.1.3.6.1.4.1.9.9.424.1.2.1 |
|
The status of the last metering data export. It indicates
the success or failure of writing the metering record file
or streaming the record to the collection server.
|
| ccmtrCollectionDestination |
.1.3.6.1.4.1.9.9.424.1.2.2 |
|
It represents the name of the file that is created to
store the metering record or the IP address and port
number to which the metering information was streamed in
both the success and failure scenerios.
In the case of local storage it is the filename generated
as the CMTS host name followed by the timestamp when the
file was created.
The file will be stored in the filesystem as specified in
ccmtrCollectionFilesystem.
In the case of streaming it is the IP address and port
number in the format IPADDRESS:PORT# to which the last
streaming took place.
|
| ccmtrCollectionTimestamp |
.1.3.6.1.4.1.9.9.424.1.2.3 |
|
The time when the last metering record was exported
successfully or with some failure.
|
| ccmtrMeteringNotifEnable |
.1.3.6.1.4.1.9.9.424.1.2.4 |
|
An indication of whether the notifications associated
with metering are enabled or disabled.
true indicates the notification is enabled and
false indicates the notification is disabled.
|
| Tabular Object |
| ccmtrCollectionID |
.1.3.6.1.4.1.9.9.424.1.1.3.1.1 |
|
Identification of a IP address and port number
associated with the mediation or collection server.
The ccmtrCollectionID is used in determining the order
of the IP address, port number to which the streaming will
take place. The primary represents the first
collection server and secondary represents the
second collection server if streaming to the primary
failed for any reason. Thus primary entry
must be created before the secondary.
|
| ccmtrCollectionIpAddrType |
.1.3.6.1.4.1.9.9.424.1.1.3.1.2 |
|
The type of internet address of ccmtrCollectionIpAddress.
|
| ccmtrCollectionIpAddress |
.1.3.6.1.4.1.9.9.424.1.1.3.1.3 |
|
The IP address of the collection server. It will be of
type as referred by ccmtrCollectionIpAddrType.
The ccmtrCollectionPort should be also valid along with
ccmtrCollectionIpAddress for a row to be created. The
primary collection server IP address represented by
ccmtrCollectionID equal to 1 must be created before the
secondary collection server IP address.
|
| ccmtrCollectionPort |
.1.3.6.1.4.1.9.9.424.1.1.3.1.4 |
|
The port number of the collection server. This port number
chosen should not be any of the well defined ports.
The ccmtrCollectionIpAddress should be also valid along
with ccmtrCollectionPort for a row to be created. The
primary collection server port represented by
ccmtrCollectionID equal to 1 must be created before the
secondary collection server port.
|
| ccmtrCollectionRowStatus |
.1.3.6.1.4.1.9.9.424.1.1.3.1.8 |
|
Controls and reflects the status of rows in this table.
It can use used for creation, modifying and deleting
entries in this table.
The ccmtrCollectionPort should also be valid along with
ccmtrCollectionIpAddress for a row to be created.
The ccmtrCollectionID 1 represents the primary
collection server and ccmtrCollectionID 2 represents the
secondary collection server. Thus ccmtrCollectionID of 1
must be created before the ccmtrCollectionID of 2.
|
| Table |
| ccmtrCollectionTable |
.1.3.6.1.4.1.9.9.424.1.1.3 |
|
This table is used only if ccmtrCollectionType object is
stream which indicates that the metering records are to
be streamed to an external collection server.
It contains IP address information of the collection
server. In addition it contains other configurable
parameters like interval, retries etc needed for
streaming the metering records.
|
| Trap |
| ccmtrCollectionNotification |
.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.
|
| Object Identifier |
| ciscoCableMeteringMIB |
.1.3.6.1.4.1.9.9.424 |
|
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.
|
| ciscoCableMeteringMIBNotifs |
.1.3.6.1.4.1.9.9.424.0 |
| ciscoCableMeteringMIBObjects |
.1.3.6.1.4.1.9.9.424.1 |
| ccmtrMeteringConfig |
.1.3.6.1.4.1.9.9.424.1.1 |
| ccmtrMetering |
.1.3.6.1.4.1.9.9.424.1.2 |
| ciscoCableMeteringMIBConformance |
.1.3.6.1.4.1.9.9.424.3 |
| ciscoCableMeteringMIBCompliances |
.1.3.6.1.4.1.9.9.424.3.1 |
| ciscoCableMeteringMIBGroups |
.1.3.6.1.4.1.9.9.424.3.2 |
| Group |
| ccmtrMeteringObjGroup |
.1.3.6.1.4.1.9.9.424.3.2.1 |
|
Group of objects implemented in CMTS
providing for usage based metering configuration
and notification information.
|
| ccmtrMeteringNotifCtrlGroup |
.1.3.6.1.4.1.9.9.424.3.2.2 |
|
The notification control which a
CISCO-CABLE-METERING-MIB
is required to implement.
|
| ccmtrMeteringNotifGroup |
.1.3.6.1.4.1.9.9.424.3.2.3 |
|
The notification which a CISCO-CABLE-METERING-MIB
is required to implement.
|
