As per Relevance of the word reference, we have this rfc below:
Network Working Group M. St. Johns, Ed
Request for Comments: 2670 @Home
Category: Proposed Standard August 1999
Radio Frequency (RF) Interface Management Information
for MCNS/DOCSIS compliant RF
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines a basic set of managed objects for SNMP
based management of MCNS/DOCSIS compliant Radio Frequency (RF
interfaces
This memo specifies a MIB module in a manner that is compliant to
SNMP SMIv2 [5][6][7]. The set of objects are consistent with
SNMP framework and existing SNMP standards
This memo is a product of the IPCDN working group within the
Engineering Task Force. Comments are solicited and should
addressed to the working group's mailing list at ipcdn@terayon.
and/or the author
Table of
1 The SNMP Management Framework ................................... 3
2 Glossary ........................................................ 4
2.1 CATV .......................................................... 4
2.2 Channel ....................................................... 4
2.3 CM ............................................................ 4
2.4 CMTS .......................................................... 4
2.5 Codeword ...................................................... 4
2.6 Data Packet ................................................... 4
St. Johns Standard [Page 1]
RFC 2670 DOCSIS RF Interface MIB August 1999
2.7 dBmV .......................................................... 4
2.8 DOCSIS ........................................................ 5
2.9 Downstream .................................................... 5
2.10 Head-end ..................................................... 5
2.11 MAC Packet ................................................... 5
2.12 MCNS ......................................................... 5
2.13 Mini-slot .................................................... 5
2.14 QPSK ......................................................... 5
2.15 QAM .......................................................... 5
2.16 RF ........................................................... 5
2.17 Symbol-times ................................................. 5
2.18 Upstream ..................................................... 6
3 Overview ........................................................ 6
3.1 Structure of the MIB .......................................... 6
3.1.1 docsIfBaseObjects ........................................... 6
3.1.2 docsIfCmObjects ............................................. 7
3.1.3 docsIfCmtsObjects ........................................... 7
3.2 Relationship to the Interfaces MIB ............................ 7
3.2.1 Layering Model .............................................. 7
3.2.2 Virtual Circuits ............................................ 8
3.2.3 ifTestTable ................................................. 9
3.2.4 ifRcvAddressTable ........................................... 9
3.2.5 ifEntry ..................................................... 9
3.2.5.1 ifEntry for Downstream interfaces ......................... 9
3.2.5.1.1 ifEntry for Downstream interfaces in Cable
Termination Systems .......................................... 9
3.2.5.1.2 ifEntry for Downstream interfaces in Cable Modems ...... 11
3.2.5.2 ifEntry for Upstream interfaces .......................... 12
3.2.5.2.1 ifEntry for Upstream interfaces in Cable
Termination Systems ......................................... 12
3.2.5.2.2 ifEntry for Upstream interfaces in Cable Modems ........ 14
3.2.5.3 ifEntry for the MAC Layer ................................ 15
4 Definitions .................................................... 18
5 Acknowledgments ................................................ 69
6 References ..................................................... 69
7 Security Considerations ........................................ 70
8 Intellectual Property .......................................... 71
9 Author's Address ............................................... 71
10 Full Copyright Statement ...................................... 72
St. Johns Standard [Page 2]
RFC 2670 DOCSIS RF Interface MIB August 1999
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol,
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB MUST be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
St. Johns Standard [Page 3]
RFC 2670 DOCSIS RF Interface MIB August 1999
2.
The terms in this document are derived either from normal
system usage, or from the documents associated with the Data
Cable Service Interface Specification process
2.1.
Originally "Community Antenna Television", now used to refer to
cable or hybrid fiber and cable system used to deliver video
to a community
2.2.
A specific frequency allocation with an RF medium, specified
channel width in Hertz (cycles per second) and by center frequency
Within the US Cable Systems, upstream channels are
allocated from the 5-42MHz range while down stream channels
generally allocated from the 50-750MHz range depending on
capabilities of the given system. The typical broadcast
width in the US is 6MHz. Upstream channel widths for DOCSIS vary
2.3. CM Cable Modem
A CM acts as a "slave" station in a DOCSIS compliant cable
system
2.4. CMTS Cable Modem Termination System
A generic term covering a cable bridge or cable router in a head-end
A CMTS acts as the master station in a DOCSIS compliant cable
system. It is the only station that transmits downstream, and
controls the scheduling of upstream transmissions by its
CMs
2.5.
See [16]. A characteristic of the Foward Error Correction scheme
above the RF media layer
2.6. Data
The payload portion of the MAC Packet
2.7.
Decibel relative to one milli-volt. A measure of RF power
St. Johns Standard [Page 4]
RFC 2670 DOCSIS RF Interface MIB August 1999
2.8.
"Data Over Cable Interface Specification". A term referring to
ITU-T J.112 Annex B standard for cable modem systems [20].
2.9.
The direction from the head-end towards the subscriber
2.10. Head-
The origination point in most cable systems of the subscriber
signals
2.11. MAC
A DOCSIS PDU
2.12.
"Multimedia Cable Network System". Generally replaced in usage
DOCSIS
2.13. Mini-
See [16]. In general, an interval of time which is allocated by
CMTS to a given CM for that CM to transmit in an upstream direction
2.14. QPSK Quadrature Phase Shift Keying
A particular modulation scheme on an RF medium. See [19].
2.15. QAM Quadrature Amplitude Modulation
A particular modulation scheme on on RF medium. Usually
with a number indicating the size of the modulation
(e.g. 16 QAM). See [19], or any other book on digital
over RF for a complete explanation of this
2.16.
Radio Frequency
2.17. Symbol-
See [16]. A characteristic of the RF modulation scheme
St. Johns Standard [Page 5]
RFC 2670 DOCSIS RF Interface MIB August 1999
2.18.
The direction from the subscriber towards the head-end
3.
This MIB provides a set of objects required for the management
MCNS/DOCSIS compliant Cable Modem (CM) and Cable Modem
System (CMTS) RF interfaces. The specification is derived in
from the parameters and protocols described in DOCSIS Radio
Interface Specification [16].
3.1. Structure of the
This MIB is structured as three groups
o Management information pertinent to both Cable Modems (CM)
Cable Modem Termination Systems (CMTS) (docsIfBaseObjects).
o Management information pertinent to Cable Modems
(docsIfCmObjects).
o Management information pertinent to Cable Modem
Systems only (docsIfCmtsObjects).
Tables within each of these groups group objects functionally - e.g
Quality of Service, Channel characteristics, MAC layer management
etc. Rows created automatically (e.g. by the device according to
hardware configuration) may and generally will have a mixture
configuration and status objects within them. Rows that are meant
be created by the management station are generally restricted
configuration (read-create) objects
3.1.1.
docsIfDownstreamChannelTable - This table describes the
downstream channels for a CMTS and the received downstream
for a CM
docsIfUpstreamChannelTable - This table describes the active
channels for a a CMTS and the current upstream transmission
for a CM
docsIfQosProfileTable - This table describes the valid Quality
Service service profiles for the cable data system
docsIfSignalQualityTable - This table is used to monitor RF
quality characteristics of received signals
St. Johns Standard [Page 6]
RFC 2670 DOCSIS RF Interface MIB August 1999
3.1.2.
docsIfCmMacTable - This table is used to monitor the DOCSIS
interface and can be considered an extension to the ifEntry
docsIfCmServiceTable - This table describes the upstream
queues available at this CM. There is a comparable table at
CMTS, docsIfCmtsServiceEntry, which describes the service queues
the point of view of the CMTS
3.1.3.
docsIfCmtsStatusTable - This table provides a set of
counters which roll-up values and events that occur on the
sub-interfaces
docsIfCmtsCmStatusTable - This table is used to hold
about known (e.g. registered) cable modems on the system serviced
this CMTS
docsIfCmtsServiceEntry - This table provides access to
information related to upstream service queues
docsIfCmtsModulationTable - This table allows control over
modulation profiles for RF channels associated with this CMTS
docsIfCmtsMacToCmTable - This table allows fast access into
docsIfCmtsCmTable via a MAC address (of the CM) interface
3.2. Relationship to the Interfaces
This section clarifies the relationship of this MIB to the
MIB [17]. Several areas of correlation are addressed in
following subsections. The implementor is referred to the
MIB document in order to understand the general intent of
areas
3.2.1. Layering
An instance of ifEntry exists for each RF Downstream interface,
each RF Upstream interface, and for each RF MAC layer.
ifStackTable [17] MUST be implemented to identify relationships
sub-interfaces
St. Johns Standard [Page 7]
RFC 2670 DOCSIS RF Interface MIB August 1999
The following example illustrates a MAC interface with one
and two upstream channels
| <== to network
+-------------+--------------+
| RF MAC |
+----+---------+-----------+-+
| | |
+---------+---+ +---+-------+ +-+---------+
| Downstream1 | | Upstream1 | | Upstream2 |
+-------------+ +-----------+ +-----------+
As can be seen from this example, the RF MAC interface is layered
top of the downstream and upstream interfaces
In this example, the assignment of index values could be as follows
ifIndex ifType
1 docsCableMaclayer(127) CATV MAC
2 docsCableDownstream(128) CATV Downstream
3 docsCableUpstream(129) CATV Upstream
4 docsCableUpstream(129) CATV Upstream
The corresponding ifStack entries would then be
| IfStackHigherLayer | ifStackLowerLayer |
| 0 | 1 |
| 1 | 2 |
| 1 | 3 |
| 1 | 4 |
| 2 | 0 |
| 3 | 0 |
| 4 | 0 |
The same interface model can also be used in Telephony or
Return systems. A pure Telco Return system (Cable Modem as well
Cable Modem Termination System) would not have upstream, but
downstream cable channels. Systems supporting both Telco Return
cable upstream channels can use the above model without modification
Telco Return Upstream channel(s) are handled by the appropriate MIBs
such as PPP or Modem MIBs
3.2.2. Virtual
This medium does not support virtual circuits and this area is
applicable to this MIB
St. Johns Standard [Page 8]
RFC 2670 DOCSIS RF Interface MIB August 1999
3.2.3.
The ifTestTable is not supported by this MIB
3.2.4.
The ifRcvAddressTable is not supported by this MIB
3.2.5.
This section documents only the differences from the
specified in the Interfaces MIB. See that MIB for columns
from the descriptions below
3.2.5.1. ifEntry for Downstream
The ifEntry for Downstream interfaces supports
ifGeneralInformationGroup and the ifPacketGroup of the
MIB. This is an output only interface at the CMTS and all
status counters - ifIn* - will return zero. This is an input
interface at the CM and all output status counters - ifOut* -
return zero
3.2.5.1.1. ifEntry for Downstream interfaces in Cable Modem
ifTable
============== ===========================================
ifIndex Each RF Cable Downstream interface is
by an ifEntry
ifType The IANA value of docsCableDownstream(128).
ifSpeed Return the speed of this downstream channel
The returned value the raw bandwidth in bits/
of this interface. This is the symbol
multiplied with the number of bits per symbol
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of this interface
ifMtu The size of the largest frame which can
sent on this interface, specified in octets
The value includes the length of the MAC header
St. Johns Standard [Page 9]
RFC 2670 DOCSIS RF Interface MIB August 1999
ifInOctets Return zero
ifInUcastPkts Return zero
ifInMulticastPkts Return zero
ifInBroadcastPkts Return zero
ifInDiscards Return zero
ifInErrors Return zero
ifInUnknownProtos Return zero
ifOutOctets The total number of octets transmitted on
interface. This includes MAC packets as well
data packets, and includes the length of the
header
ifOutUcastPkts The number of Unicast packets transmitted on
interface. This includes MAC packets as well
data packets
Return the number of Multicast packets
on this interface
This includes MAC packets as well as data packets
Return the number of broadcast packets
on this interface
This includes MAC packets as well as data packets
ifOutDiscards The total number of outbound packets
were discarded. Possible reasons are
buffer shortage
ifOutErrors The number of packets which could not
transmitted due to errors
ifPromiscuousMode Return false
St. Johns Standard [Page 10]
RFC 2670 DOCSIS RF Interface MIB August 1999
3.2.5.1.2. ifEntry for Downstream interfaces in Cable
ifTable
============== ===========================================
ifIndex Each RF Cable Downstream interface is
by an ifEntry
ifType The IANA value of docsCableDownstream(128).
ifSpeed Return the speed of this downstream channel
The returned value the raw bandwidth in bits/
of this interface. This is the symbol
multiplied with the number of bits per symbol
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of this interface
ifMtu The size of the largest frame which can
received from this interface, specified in octets
The value includes the length of the MAC header
ifInOctets The total number of octets received on
interface. This includes data packets as well
MAC layer packets, and includes the length of
MAC header
ifInUcastPkts The number of Unicast packets received on
interface. This includes data packets as well
MAC layer packets
ifInMulticastPkts Return the number of Multicast packets
on this interface. This includes data packets
well as MAC layer packets
ifInBroadcastPkts Return the number of Broadcast packets
on this interface. This includes data
as well as MAC layer packets
ifInDiscards The total number of received packets which
been discarded
The possible reasons are: buffer shortage
ifInErrors The number of inbound packets that
errors preventing them from being
to higher layers
St. Johns Standard [Page 11]
RFC 2670 DOCSIS RF Interface MIB August 1999
Possible reasons are: MAC FCS error
ifInUnknownProtos The number of frames with an unknown packet type
These are MAC frames with an unknown packet type
ifOutOctets Return zero
ifOutUcastPkts Return zero
Return zero
Return zero
ifOutDiscards Return zero
ifOutErrors Return zero
ifPromiscuousMode Refer to the Interfaces MIB
3.2.5.2. ifEntry for Upstream
The ifEntry for Upstream interfaces supports
ifGeneralInformationGroup and the ifPacketGroup of the
MIB. This is an input only interface at the CMTS and all
status counters - ifOut* - will return zero. This is an output
interface at the CM and all input status counters - ifIn* -
return zero
3.2.5.2.1. ifEntry for Upstream interfaces in Cable Modem
ifTable
============== ===========================================
ifIndex Each RF Cable Upstream interface is
by an ifEntry
ifType The IANA value of docsCableUpstream(129).
ifSpeed Return the speed of this upstream channel
The returned value is the raw
in bits/s of this interface, regarding
highest speed modulation profile that
defined. This is the symbol rate
with the number of bits per symbol for
modulation profile
St. Johns Standard [Page 12]
RFC 2670 DOCSIS RF Interface MIB August 1999
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of this interface
ifMtu The size of the largest frame which can
received on this interface, specified in octets
The value includes the length of the MAC header
ifInOctets The total number of octets received on
interface. This includes data packets as well
MAC layer packets, and includes the length of
MAC header
ifInUcastPkts The number of Unicast packets received on
interface. This includes data packets as well
MAC layer packets
ifInMulticastPkts Return the number of Multicast packets
on this interface. This includes data packets
well as MAC layer packets
ifInBroadcastPkts Return the number of Broadcast packets
on this interface. This includes data
as well as MAC layer packets
ifInDiscards The total number of received packets which
been discarded
The possible reasons are: buffer shortage
ifInErrors The number of inbound packets that
errors preventing them from being
to higher layers
Possible reasons are: MAC FCS error
ifInUnknownProtos The number of frames with an unknown packet type
This are MAC frames with an unknown packet type
ifOutOctets Return zero
ifOutUcastPkts Return zero
Return zero
Return zero
St. Johns Standard [Page 13]
RFC 2670 DOCSIS RF Interface MIB August 1999
ifOutDiscards Return zero
ifOutErrors Return zero
3.2.5.2.2. ifEntry for Upstream interfaces in Cable
ifTable
============== ===========================================
ifIndex Each RF Cable Upstream interface is
by an ifEntry
ifType The IANA value of docsCableUpstream(129).
ifSpeed Return the speed of this upstream channel
The returned value is the raw
in bits/s of this interface, regarding
highest speed modulation profile that
defined. This is the symbol rate
with the number of bits per symbol for
modulation profile
ifPhysAddress Return an empty string
ifAdminStatus The administrative status of this interface
ifOperStatus The current operational status of this interface
ifMtu The size of the largest frame which can
transmitted on this interface, specified in octets
The value includes the length of the MAC header
ifInOctets Return zero
ifInUcastPkts Return zero
ifInMulticastPkts Return zero
ifInBroadcastPkts Return zero
ifInDiscards Return zero
ifInErrors Return zero
ifInUnknownProtos Return zero
St. Johns Standard [Page 14]
RFC 2670 DOCSIS RF Interface MIB August 1999
ifOutOctets The total number of octets transmitted on
interface. This includes MAC packets as well
data packets, and includes the length of the
header
ifOutUcastPkts The number of Unicast packets transmitted on
interface. This includes MAC packets as well
data packets
Return the number of Multicast packets
on this interface
This includes MAC packets as well as data packets
Return the number of broadcast packets
on this interface
This includes MAC packets as well as data packets
ifOutDiscards The total number of outbound packets
were discarded. Possible reasons are
buffer shortage
ifOutErrors The number of packets which could not
transmitted due to errors
ifPromiscuousMode Return false
3.2.5.3. ifEntry for the MAC
The ifEntry for the MAC Layer supports the
and the ifPacketGroup of the Interfaces MIB. This interface
an aggregate view of status for the lower level Downstream
Upstream interfaces
ifTable
============== ===========================================
ifIndex Each RF Cable MAC layer entity is
by an ifEntry
ifType The IANA value of docsCableMaclayer(127).
ifSpeed Return zero
ifPhysAddress Return the physical address of this interface
ifAdminStatus The administrative status of this interface
St. Johns Standard [Page 15]
RFC 2670 DOCSIS RF Interface MIB August 1999
ifOperStatus The current operational status of the
layer interface
ifHighSpeed Return zero
ifMtu Return 1500.
ifInOctets The total number of data octets received on
interface, targeted for upper protocol layers
ifInUcastPkts The number of Unicast packets received on
interface, targeted for upper protocol layers
ifInMulticastPkts Return the number of Multicast packets
on this interface, targeted for upper
layers
ifInBroadcastPkts Return the number of Broadcast packets
on this interface, targeted for upper
layers
ifInDiscards The total number of received packets which
been discarded
The possible reasons are: buffer shortage
ifInErrors The number of inbound packets that
errors preventing them from being
to higher layers
Possible reasons are: data packet FCS error
invalid MAC header
ifInUnknownProtos The number of frames with an unknown packet type
This is the number of data packets targeted
upper protocol layers with an unknown packet type
ifOutOctets The total number of octets, received from
protocol layers and transmitted on this interface
ifOutUcastPkts The number of Unicast packets, received from
protocol layers and transmitted on this interface
Return the number of Multicast packets
from upper protocol layers and transmitted on
interface
St. Johns Standard [Page 16]
RFC 2670 DOCSIS RF Interface MIB August 1999
Return the number of broadcast packets
from upper protocol layers and transmitted on
interface
ifOutDiscards The total number of outbound packets
were discarded. Possible reasons are
buffer shortage
ifOutErrors The number of packets which could not
transmitted due to errors
ifPromiscuousMode Refer to the Interfaces MIB
St. Johns Standard [Page 17]
RFC 2670 DOCSIS RF Interface MIB August 1999
4.
DOCS-IF-MIB DEFINITIONS ::=
MODULE-IDENTITY
OBJECT-TYPE
-- do not import BITS
Unsigned32,
Integer32,
Counter32,
TimeTicks
IpAddress
FROM SNMPv2-
TEXTUAL-CONVENTION
MacAddress
RowStatus
TruthValue
TimeInterval
FROM SNMPv2-
OBJECT-GROUP
MODULE-
FROM SNMPv2-
ifIndex,
FROM IF-MIB
docsIfMib MODULE-
LAST-UPDATED "9908190000Z" -- August 19, 1999
ORGANIZATION "IETF IPCDN Working Group
CONTACT-
" Michael
Postal: @Home
425
Redwood City,
U.S.A
Phone: +1 650 569 5368
E-mail: stjohns@corp.home.net
"This is the MIB Module for MCNS/DOCSIS compliant
Frequency (RF) interfaces in Cable Modems (CM)
Cable Modem Termination Systems (CMTS)."
REVISION "9908190000Z
"Initial Version, published as RFC 2670.
Modified by Mike StJohns to fix problems identified
St. Johns Standard [Page 18]
RFC 2670 DOCSIS RF Interface MIB August 1999
the first pass of the MIB doctor. Of special note
docsIfRangingResp and docsIfCmtsInsertionInterval
obsoleted and replaced by other objects with the
functionality, but more appropriate SYNTAX."
::= { transmission 127 }
-- Textual
TenthdBmV ::= TEXTUAL-
DISPLAY-HINT "d-1"
STATUS
"This data type represents power levels that are
expressed in dBmV. Units are in tenths of a dBmV
for example, 5.1 dBmV will be represented as 51."
SYNTAX Integer32
TenthdB ::= TEXTUAL-
DISPLAY-HINT "d-1"
STATUS
"This data type represents power levels that are
expressed in dB. Units are in tenths of a dB
for example, 5.1 dB will be represented as 51."
SYNTAX Integer32
docsIfMibObjects OBJECT IDENTIFIER ::= { docsIfMib 1 }
docsIfBaseObjects OBJECT IDENTIFIER ::= { docsIfMibObjects 1 }
docsIfCmObjects OBJECT IDENTIFIER ::= { docsIfMibObjects 2 }
docsIfCmtsObjects OBJECT IDENTIFIER ::= { docsIfMibObjects 3 }
--
-- BASE
--
--
-- The following table is implemented on both the Cable Modem (CM
-- and the Cable Modem Termination System (CMTS).
--
docsIfDownstreamChannelTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table describes the attributes of
channels (frequency bands)."
St. Johns Standard [Page 19]
RFC 2670 DOCSIS RF Interface MIB August 1999
"DOCSIS Radio Frequency Interface Specification
Table 4-12 and Table 4-13."
::= { docsIfBaseObjects 1 }
docsIfDownstreamChannelEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry provides a list of attributes for a
Downstream channel
An entry in this table exists for each ifEntry with
ifType of docsCableDownstream(128)."
INDEX { ifIndex }
::= { docsIfDownstreamChannelTable 1 }
DocsIfDownstreamChannelEntry ::= SEQUENCE {
docsIfDownChannelId Integer32,
docsIfDownChannelFrequency Integer32,
docsIfDownChannelWidth Integer32,
docsIfDownChannelModulation INTEGER
docsIfDownChannelInterleave INTEGER
docsIfDownChannelPower
}
docsIfDownChannelId OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"The Cable Modem Termination System (CMTS)
of the downstream channel within this particular
interface. If the interface is down, the object
the most current value. If the downstream channel ID
unknown, this object returns a value of 0."
::= { docsIfDownstreamChannelEntry 1 }
docsIfDownChannelFrequency OBJECT-
SYNTAX Integer32 (0..1000000000)
UNITS "hertz
MAX-ACCESS read-
STATUS
"The center of the downstream frequency associated
this channel. This object will return the current
frequency. If a CMTS provides IF output, this
will return 0, unless this CMTS is in control of
final downstream RF frequency. See the
St. Johns Standard [Page 20]
RFC 2670 DOCSIS RF Interface MIB August 1999
compliance object for a description of valid
that may be written to this object."
"DOCSIS Radio Frequency Interface Specification
Section 4.3.3."
::= { docsIfDownstreamChannelEntry 2 }
docsIfDownChannelWidth OBJECT-
SYNTAX Integer32 (0..16000000)
UNITS "hertz
MAX-ACCESS read-
STATUS
"The bandwidth of this downstream channel.
implementations are expected to support a channel
of 6 MHz (North America) and/or 8 MHz (Europe). See
associated compliance object for a description of
valid channel widths for this object."
"DOCSIS Radio Frequency Interface Specification
Table 4-12 and Table 4-13."
::= { docsIfDownstreamChannelEntry 3 }
docsIfDownChannelModulation OBJECT-
SYNTAX INTEGER {
unknown(1),
other(2),
qam64(3),
qam256(4)
}
MAX-ACCESS read-
STATUS
"The modulation type associated with this
channel. If the interface is down, this object
returns the configured value (CMTS), the most
value (CM), or the value of unknown(1). See
associated conformance object for write conditions
limitations. See the reference for specifics on
modulation profiles implied by qam64 and qam256."
"DOCSIS Radio Frequency Interface Specification
Section 3.6.2."
::= { docsIfDownstreamChannelEntry 4 }
docsIfDownChannelInterleave OBJECT-
SYNTAX INTEGER {
unknown(1),
St. Johns Standard [Page 21]
RFC 2670 DOCSIS RF Interface MIB August 1999
other(2),
taps8Increment16(3),
taps16Increment8(4),
taps32Increment4(5),
taps64Increment2(6),
taps128Increment1(7)
}
MAX-ACCESS read-
STATUS
"The Forward Error Correction (FEC) interleaving
for this downstream channel
Values are defined as follows
taps8Increment16(3): protection 5.9/4.1 usec
latency .22/.15
taps16Increment8(4): protection 12/8.2 usec
latency .48/.33
taps32Increment4(5): protection 24/16 usec
latency .98/.68
taps64Increment2(6): protection 47/33 usec
latency 2/1.4
taps128Increment1(7): protection 95/66 usec
latency 4/2.8
If the interface is down, this object either
the configured value (CMTS), the most current value (CM),
or the value of unknown(1).
The value of other(2) is returned if the
is known but not defined in the above list
See the associated conformance object for
conditions and limitations. See the reference for the
configuration described by the setting of this object."
"DOCSIS Radio Frequency Interface Specification
Section 4.3.2."
::= { docsIfDownstreamChannelEntry 5 }
docsIfDownChannelPower OBJECT-
SYNTAX
UNITS "dBmV
MAX-ACCESS read-
STATUS
"At the CMTS, the operational transmit power. At the CM
the received power level. May be set to zero at the
if power level measurement is not supported
If the interface is down, this object either
the configured value (CMTS), the most current value (CM
or the value of 0. See the associated conformance
St. Johns Standard [Page 22]
RFC 2670 DOCSIS RF Interface MIB August 1999
for write conditions and limitations. See the
for recommended and required power levels."
"DOCSIS Radio Frequency Interface Specification
Table 4-12 and Table 4-13."
::= { docsIfDownstreamChannelEntry 6 }
--
-- The following table is implemented on both the CM and the CMTS
-- For the CM, only attached channels appear in the table. For
-- CM, this table is read only as well
--
docsIfUpstreamChannelTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table describes the attributes of attached
channels (frequency bands)."
::= { docsIfBaseObjects 2 }
docsIfUpstreamChannelEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"List of attributes for a single upstream channel
An entry in this table exists for each ifEntry with
ifType of docsCableUpstream(129)."
INDEX { ifIndex }
::= { docsIfUpstreamChannelTable 1 }
DocsIfUpstreamChannelEntry ::= SEQUENCE {
docsIfUpChannelId Integer32,
docsIfUpChannelFrequency Integer32,
docsIfUpChannelWidth Integer32,
docsIfUpChannelModulationProfile Unsigned32,
docsIfUpChannelSlotSize Unsigned32,
docsIfUpChannelTxTimingOffset Unsigned32,
docsIfUpChannelRangingBackoffStart Integer32,
docsIfUpChannelRangingBackoffEnd Integer32,
docsIfUpChannelTxBackoffStart Integer32,
docsIfUpChannelTxBackoffEnd Integer32
}
docsIfUpChannelId OBJECT-
SYNTAX Integer32 (0..255)
St. Johns Standard [Page 23]
RFC 2670 DOCSIS RF Interface MIB August 1999
MAX-ACCESS read-
STATUS
"The CMTS identification of the upstream channel."
::= { docsIfUpstreamChannelEntry 1 }
docsIfUpChannelFrequency OBJECT-
SYNTAX Integer32 (0..1000000000)
UNITS "hertz
MAX-ACCESS read-
STATUS
"The center of the frequency band associated with
upstream channel. This object returns 0 if the
is undefined or unknown. Minimum permitted
frequency is 5,000,000 Hz for current technology.
the associated conformance object for write
and limitations."
"DOCSIS Radio Frequency Interface Specification
Table 2-2."
::= { docsIfUpstreamChannelEntry 2 }
docsIfUpChannelWidth OBJECT-
SYNTAX Integer32 (0..20000000)
UNITS "hertz
MAX-ACCESS read-
STATUS
"The bandwidth of this upstream channel. This
returns 0 if the channel width is undefined or unknown
Minimum permitted channel width is 200,000 Hz currently
See the associated conformance object for write
and limitations."
"DOCSIS Radio Frequency Interface Specification
Table 4-3."
::= { docsIfUpstreamChannelEntry 3 }
docsIfUpChannelModulationProfile OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"An entry identical to the docsIfModIndex in
docsIfCmtsModulationTable that describes this channel
This channel is further instantiated there by a
of interval usage codes which together fully describe
St. Johns Standard [Page 24]
RFC 2670 DOCSIS RF Interface MIB August 1999
channel modulation. This object returns 0 if
docsIfCmtsModulationTable entry does not exist
docsIfCmtsModulationTable is empty.
the associated conformance object for write
and limitations."
::= { docsIfUpstreamChannelEntry 4 }
docsIfUpChannelSlotSize OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"The number of 6.25 microsecond ticks in each upstream mini
slot. Returns zero if the value is undefined or unknown
See the associated conformance object for
conditions and limitations."
"DOCSIS Radio Frequency Interface Specification
Section 6.1.2.4."
::= { docsIfUpstreamChannelEntry 5 }
docsIfUpChannelTxTimingOffset OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"A measure of the current round trip time at the CM, or
maximum round trip time seen by the CMTS. Used for
of CM upstream transmissions to ensure
arrivals at the CMTS. Units are in terms
(6.25 microseconds/64)."
"DOCSIS Radio Frequency Interface Specification
Section 6.5."
::= { docsIfUpstreamChannelEntry 6 }
docsIfUpChannelRangingBackoffStart OBJECT-
SYNTAX Integer32 (0..16)
MAX-ACCESS read-
STATUS
"The initial random backoff window to use when
Ranging Requests. Expressed as a power of 2. A value of 16
at the CMTS indicates that a proprietary adaptive
mechanism is to be used. See the associated
object for write conditions and limitations."
"DOCSIS Radio Frequency Interface Specification
St. Johns Standard [Page 25]
RFC 2670 DOCSIS RF Interface MIB August 1999
Section 6.4.4."
::= { docsIfUpstreamChannelEntry 7 }
docsIfUpChannelRangingBackoffEnd OBJECT-
SYNTAX Integer32 (0..16)
MAX-ACCESS read-
STATUS
"The final random backoff window to use when
Ranging Requests. Expressed as a power of 2. A value of 16
at the CMTS indicates that a proprietary adaptive
mechanism is to be used. See the associated
object for write conditions and limitations."
"DOCSIS Radio Frequency Interface Specification
Section 6.4.4."
::= { docsIfUpstreamChannelEntry 8 }
docsIfUpChannelTxBackoffStart OBJECT-
SYNTAX Integer32 (0..16)
MAX-ACCESS read-
STATUS
"The initial random backoff window to use when
transmissions. Expressed as a power of 2. A value of 16
at the CMTS indicates that a proprietary adaptive
mechanism is to be used. See the associated
object for write conditions and limitations."
"DOCSIS Radio Frequency Interface Specification
Section 6.4.4."
::= { docsIfUpstreamChannelEntry 9 }
docsIfUpChannelTxBackoffEnd OBJECT-
SYNTAX Integer32 (0..16)
MAX-ACCESS read-
STATUS
"The final random backoff window to use when
transmissions. Expressed as a power of 2. A value of 16
at the CMTS indicates that a proprietary adaptive
mechanism is to be used. See the associated
object for write conditions and limitations."
"DOCSIS Radio Frequency Interface Specification
Section 6.4.4."
::= { docsIfUpstreamChannelEntry 10 }
St. Johns Standard [Page 26]
RFC 2670 DOCSIS RF Interface MIB August 1999
-- The following table describes the attributes of each class
-- service. The entries in this table are referenced from
-- docsIfServiceEntries. They exist as a separate table in order
-- reduce redundant information in docsIfServiceTable
--
-- This table is implemented at both the CM and the CMTS
-- The CM need only maintain entries for the classes of
-- referenced by its docsIfServiceTable
--
docsIfQosProfileTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Describes the attributes for each class of service."
::= { docsIfBaseObjects 3 }
docsIfQosProfileEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Describes the attributes for a single class of service
If implemented as read-create in the Cable
Termination System, creation of entries in this table
controlled by the value of docsIfCmtsQosProfilePermissions
If implemented as read-only, entries are created
on information in REG-REQ MAC messages received
Cable Modems (Cable Modem Termination
implementation), or based on information extracted
the TFTP option file (Cable Modem implementation).
In the Cable Modem Termination system, read-only
are removed if no longer referenced
docsIfCmtsServiceTable
An entry in this table must not be removed while it
referenced by an entry in docsIfCmServiceTable (Cable Modem
or docsIfCmtsServiceTable (Cable Modem Termination System).
An entry in this table should not be changeable
it is referenced by an entry in docsIfCmtsServiceTable
If this table is created automatically, there should
be a single entry for each Class of Service.
entries with the same Class of Service parameters are
St. Johns Standard [Page 27]
RFC 2670 DOCSIS RF Interface MIB August 1999
recommended."
INDEX { docsIfQosProfIndex }
::= { docsIfQosProfileTable 1 }
DocsIfQosProfileEntry ::= SEQUENCE {
docsIfQosProfIndex Integer32,
docsIfQosProfPriority Integer32,
docsIfQosProfMaxUpBandwidth Integer32,
docsIfQosProfGuarUpBandwidth Integer32,
docsIfQosProfMaxDownBandwidth Integer32,
docsIfQosProfMaxTxBurst Integer32,
docsIfQosProfBaselinePrivacy TruthValue
docsIfQosProfStatus
}
docsIfQosProfIndex OBJECT-
SYNTAX Integer32 (1..16383)
MAX-ACCESS not-
STATUS
"The index value which uniquely identifies an
in the docsIfQosProfileTable."
::= { docsIfQosProfileEntry 1 }
docsIfQosProfPriority OBJECT-
SYNTAX Integer32 (0..7)
MAX-ACCESS read-
STATUS
"A relative priority assigned to this service
allocating bandwidth. Zero indicates lowest priority
and seven indicates highest priority
Interpretation of priority is device-specific
MUST NOT be changed while this row is active."
DEFVAL { 0 }
::= { docsIfQosProfileEntry 2 }
docsIfQosProfMaxUpBandwidth OBJECT-
SYNTAX Integer32 (0..100000000)
MAX-ACCESS read-
STATUS
"The maximum upstream bandwidth, in bits per second
allowed for a service with this service class
Zero if there is no restriction of upstream bandwidth
MUST NOT be changed while this row is active."
DEFVAL { 0 }
::= { docsIfQosProfileEntry 3 }
St. Johns Standard [Page 28]
RFC 2670 DOCSIS RF Interface MIB August 1999
docsIfQosProfGuarUpBandwidth OBJECT-
SYNTAX Integer32 (0..100000000)
MAX-ACCESS read-
STATUS
"Minimum guaranteed upstream bandwidth, in bits per second
allowed for a service with this service class
MUST NOT be changed while this row is active."
DEFVAL { 0 }
::= { docsIfQosProfileEntry 4 }
docsIfQosProfMaxDownBandwidth OBJECT-
SYNTAX Integer32 (0..100000000)
MAX-ACCESS read-
STATUS
"The maximum downstream bandwidth, in bits per second
allowed for a service with this service class
Zero if there is no restriction of downstream bandwidth
MUST NOT be changed while this row is active."
DEFVAL { 0 }
::= { docsIfQosProfileEntry 5 }
docsIfQosProfMaxTxBurst OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"The maximum number of mini-slots that may be
for a single upstream transmission
A value of zero means there is no limit
MUST NOT be changed while this row is active."
DEFVAL { 0 }
::= { docsIfQosProfileEntry 6 }
docsIfQosProfBaselinePrivacy OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indicates whether Baseline Privacy is enabled for
service class
MUST NOT be changed while this row is active."
DEFVAL { false }
::= { docsIfQosProfileEntry 7 }
docsIfQosProfStatus OBJECT-
SYNTAX
St. Johns Standard [Page 29]
RFC 2670 DOCSIS RF Interface MIB August 1999
MAX-ACCESS read-
STATUS
"This is object is to used to create or delete rows
this table. This object MUST NOT be changed from
while the row is referenced by the any entry in
docsIfCmServiceTable (on the CM), or
docsIfCmtsServiceTable (on the CMTS)."
::= { docsIfQosProfileEntry 8 }
docsIfSignalQualityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"At the CM, describes the PHY signal quality of
channels. At the CMTS, describes the PHY signal quality
upstream channels. At the CMTS, this table may
contention intervals."
::= { docsIfBaseObjects 4 }
docsIfSignalQualityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"At the CM, describes the PHY characteristics of
downstream channel. At the CMTS, describes the PHY
quality of an upstream channel
An entry in this table exists for each ifEntry with
ifType of docsCableUpstream(129) for Cable Modem
Systems and docsCableDownstream(128) for Cable Modems."
INDEX { ifIndex }
::= { docsIfSignalQualityTable 1 }
DocsIfSignalQualityEntry ::= SEQUENCE {
docsIfSigQIncludesContention TruthValue
docsIfSigQUnerroreds Counter32,
docsIfSigQCorrecteds Counter32,
docsIfSigQUncorrectables Counter32,
docsIfSigQSignalNoise TenthdB
docsIfSigQMicroreflections Integer32,
docsIfSigQEqualizationData OCTET
}
docsIfSigQIncludesContention OBJECT-
SYNTAX
St. Johns Standard [Page 30]
RFC 2670 DOCSIS RF Interface MIB August 1999
MAX-ACCESS read-
STATUS
"true(1) if this CMTS includes contention intervals
the counters in this table. Always false(2) for CMs."
"DOCSIS Radio Frequency Interface specification
Section 6.4.4"
::= { docsIfSignalQualityEntry 1 }
docsIfSigQUnerroreds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Codewords received on this channel without error
This includes all codewords, whether or not
were part of frames destined for this device."
"DOCSIS Radio Frequency Interface specification
Section 4.2.3 and 4.3.6"
::= { docsIfSignalQualityEntry 2 }
docsIfSigQCorrecteds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Codewords received on this channel with
errors. This includes all codewords, whether or
they were part of frames destined for this device."
"DOCSIS Radio Frequency Interface specification
Section 4.2.3 and 4.3.6"
::= { docsIfSignalQualityEntry 3 }
docsIfSigQUncorrectables OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Codewords received on this channel with
errors. This includes all codewords, whether or
they were part of frames destined for this device."
"DOCSIS Radio Frequency Interface specification
Section 4.2.3 and 4.3.6"
::= { docsIfSignalQualityEntry 4 }
St. Johns Standard [Page 31]
RFC 2670 DOCSIS RF Interface MIB August 1999
docsIfSigQSignalNoise OBJECT-
SYNTAX
UNITS "dB
MAX-ACCESS read-
STATUS
"Signal/Noise ratio as perceived for this channel
At the CM, describes the Signal/Noise of the
channel. At the CMTS, describes the average Signal/
of the upstream channel."
"DOCSIS Radio Frequency Interface specification
Table 2-1 and 2-2"
::= { docsIfSignalQualityEntry 5 }
docsIfSigQMicroreflections OBJECT-
SYNTAX Integer32 (0..255)
UNITS "dBc
MAX-ACCESS read-
STATUS
"Total microreflections including in-channel
as perceived on this interface, measured in dBc
the signal level
This object is not assumed to return an
accurate value, but should give a rough
of microreflections received on this interface
It is up to the implementor to provide
as accurate as possible."
"DOCSIS Radio Frequency Interface specification
Table 2-1 and 2-2"
::= { docsIfSignalQualityEntry 6 }
docsIfSigQEqualizationData OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"At the CM, returns the equalization data for the
channel. At the CMTS, returns the average
data for the upstream channel. Returns an empty
if the value is unknown or if there is no
data available or defined."
"DOCSIS Radio Frequency Interface Specification
Figure 6-23."
::= { docsIfSignalQualityEntry 7 }
St. Johns Standard [Page 32]
RFC 2670 DOCSIS RF Interface MIB August 1999
--
-- CABLE MODEM
--
-- #######
--
-- The CM MAC
--
docsIfCmMacTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Describes the attributes of each CM MAC interface
extending the information available from ifEntry."
::= { docsIfCmObjects 1 }
docsIfCmMacEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing objects describing attributes
each MAC entry, extending the information in ifEntry
An entry in this table exists for each ifEntry with
ifType of docsCableMaclayer(127)."
INDEX { ifIndex }
::= { docsIfCmMacTable 1 }
DocsIfCmMacEntry ::= SEQUENCE {
docsIfCmCmtsAddress MacAddress
docsIfCmCapabilities BITS
docsIfCmRangingRespTimeout TimeTicks
docsIfCmRangingTimeout
}
docsIfCmCmtsAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Identifies the CMTS that is believed to control this
domain. At the CM, this will be the source address
SYNC, MAP, and other MAC-layer messages. If the CMTS
unknown, returns 00-00-00-00-00-00."
::= { docsIfCmMacEntry 1 }
St. Johns Standard [Page 33]
RFC 2670 DOCSIS RF Interface MIB August 1999
docsIfCmCapabilities OBJECT-
SYNTAX BITS {
atmCells(0),
concatenation(1)
}
MAX-ACCESS read-
STATUS
"Identifies the capabilities of the MAC
at this interface. Note that packet transmission
always supported. Therefore, there is no specific
required to explicitely indicate this capability."
::= { docsIfCmMacEntry 2 }
-- This object has been obsoleted and replaced
-- docsIfCmRangingTimeout to correct the typing to TimeInterval.
-- implementations of the MIB should use docsIfCmRangingTimeout instead
docsIfCmRangingRespTimeout OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Waiting time for a Ranging Response packet."
"DOCSIS Radio Frequency Interface specification
Figure 7-6 and 7-7, timer T3."
DEFVAL { 20 }
::= { docsIfCmMacEntry 3 }
docsIfCmRangingTimeout OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Waiting time for a Ranging Response packet."
"DOCSIS Radio Frequency Interface specification
Figure 7-6 and 7-7, timer T3."
DEFVAL { 20 }
::= { docsIfCmMacEntry 4 }
--
-- CM status table
-- This table is implemented only at the CM
--
docsIfCmStatusTable OBJECT-
St. Johns Standard [Page 34]
RFC 2670 DOCSIS RF Interface MIB August 1999
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table maintains a number of status
and counters for Cable Modems."
::= { docsIfCmObjects 2 }
docsIfCmStatusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of status objects and counters for a single
layer instance in a Cable Modem
An entry in this table exists for each ifEntry with
ifType of docsCableMaclayer(127)."
INDEX { ifIndex }
::= { docsIfCmStatusTable 1 }
DocsIfCmStatusEntry ::= SEQUENCE {
docsIfCmStatusValue INTEGER
docsIfCmStatusCode OCTET STRING
docsIfCmStatusTxPower TenthdBmV
docsIfCmStatusResets Counter32,
docsIfCmStatusLostSyncs Counter32,
docsIfCmStatusInvalidMaps Counter32,
docsIfCmStatusInvalidUcds Counter32,
-- docsIfCmStatusInvalidRangingResp Counter32,
docsIfCmStatusInvalidRangingResponses Counter32,
-- docsIfCmStatusInvalidRegistrationResp Counter32,
docsIfCmStatusInvalidRegistrationResponses Counter32,
docsIfCmStatusT1Timeouts Counter32,
docsIfCmStatusT2Timeouts Counter32,
docsIfCmStatusT3Timeouts Counter32,
docsIfCmStatusT4Timeouts Counter32,
docsIfCmStatusRangingAborteds Counter32
}
docsIfCmStatusValue OBJECT-
SYNTAX INTEGER {
other(1),
notReady(2),
notSynchronized(3),
phySynchronized(4),
usParametersAcquired(5),
rangingComplete(6),
ipComplete(7),
St. Johns Standard [Page 35]
RFC 2670 DOCSIS RF Interface MIB August 1999
todEstablished(8),
securityEstablished(9),
paramTransferComplete(10),
registrationComplete(11),
operational(12),
accessDenied(13)
}
MAX-ACCESS read-
STATUS
"Current Cable Modem connectivity state, as
in the RF Interface Specification."
"DOCSIS Radio Frequency Interface Specification
Chapter 7.2."
::= { docsIfCmStatusEntry 1 }
docsIfCmStatusCode OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"Status code for this Cable Modem as defined in
RF Interface Specification. The status code
of a single character indicating error groups,
by a two- or three-digit number indicating the
condition."
"DOCSIS Radio Frequency Interface Specification
Cable Modem status codes."
::= { docsIfCmStatusEntry 2 }
docsIfCmStatusTxPower OBJECT-
SYNTAX
UNITS "dBmV
MAX-ACCESS read-
STATUS
"The operational transmit power for the attached
channel."
"DOCSIS Radio Frequency Interface specification
Section 4.2.8."
::= { docsIfCmStatusEntry 3 }
docsIfCmStatusResets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
St. Johns Standard [Page 36]
RFC 2670 DOCSIS RF Interface MIB August 1999
STATUS
"Number of times the CM reset or
this interface."
::= { docsIfCmStatusEntry 4 }
docsIfCmStatusLostSyncs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times the CM lost synchronization
the downstream channel."
"DOCSIS Radio Frequency Interface specification
Section 6.5."
::= { docsIfCmStatusEntry 5 }
docsIfCmStatusInvalidMaps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times the CM received invalid MAP messages."
"DOCSIS Radio Frequency Interface specification
Section 6.3.2.3 and 6.4.2."
::= { docsIfCmStatusEntry 6 }
docsIfCmStatusInvalidUcds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times the CM received invalid UCD messages."
"DOCSIS Radio Frequency Interface specification
Section 6.3.2.2."
::= { docsIfCmStatusEntry 7 }
-- docsIfCmStatusInvalidRangingResp replaced for Counter32
-- naming
docsIfCmStatusInvalidRangingResponses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
St. Johns Standard [Page 37]
RFC 2670 DOCSIS RF Interface MIB August 1999
"Number of times the CM received invalid ranging
messages."
::= { docsIfCmStatusEntry 8 }
-- docsIfCmStatusInvalidRegistrationResp replaced
-- Counter32 naming
docsIfCmStatusInvalidRegistrationResponses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times the CM received invalid
response messages."
::= { docsIfCmStatusEntry 9 }
docsIfCmStatusT1Timeouts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times counter T1 expired in the CM."
"DOCSIS Radio Frequency Interface specification
Figure 7-3."
::= { docsIfCmStatusEntry 10 }
docsIfCmStatusT2Timeouts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times counter T2 expired in the CM."
"DOCSIS Radio Frequency Interface specification
Figure 7-6."
::= { docsIfCmStatusEntry 11 }
docsIfCmStatusT3Timeouts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times counter T3 expired in the CM."
"DOCSIS Radio Frequency Interface specification
Figure 7-6 and 7-7."
::= { docsIfCmStatusEntry 12 }
St. Johns Standard [Page 38]
RFC 2670 DOCSIS RF Interface MIB August 1999
docsIfCmStatusT4Timeouts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times counter T4 expired in the CM."
"DOCSIS Radio Frequency Interface specification
Figure 7-7."
::= { docsIfCmStatusEntry 13 }
docsIfCmStatusRangingAborteds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of times the ranging process was
by the CMTS."
::= { docsIfCmStatusEntry 14 }
--
-- The Cable Modem Service
--
docsIfCmServiceTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Describes the attributes of each upstream service
on a CM."
::= { docsIfCmObjects 3 }
docsIfCmServiceEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Describes the attributes of an upstream bandwidth
queue
An entry in this table exists for each Service ID
The primary index is an ifIndex with an ifType
docsCableMaclayer(127)."
INDEX { ifIndex, docsIfCmServiceId }
::= { docsIfCmServiceTable 1 }
DocsIfCmServiceEntry ::= SEQUENCE {
docsIfCmServiceId Integer32,
St. Johns Standard [Page 39]
RFC 2670 DOCSIS RF Interface MIB August 1999
docsIfCmServiceQosProfile Integer32,
docsIfCmServiceTxSlotsImmed Counter32,
docsIfCmServiceTxSlotsDed Counter32,
docsIfCmServiceTxRetries Counter32,
-- docsIfCmServiceTxExceeded Counter32,
docsIfCmServiceTxExceededs Counter32,
docsIfCmServiceRqRetries Counter32,
-- docsIfCmServiceRqExceeded Counter32
docsIfCmServiceRqExceededs Counter32
}
docsIfCmServiceId OBJECT-
SYNTAX Integer32 (1..16383)
MAX-ACCESS not-
STATUS
"Identifies a service queue for upstream bandwidth.
attributes of this service queue are shared between
CM and the CMTS. The CMTS allocates upstream
to this service queue based on requests from the CM
on the class of service associated with this queue."
::= { docsIfCmServiceEntry 1 }
docsIfCmServiceQosProfile OBJECT-
SYNTAX Integer32 (0..16383)
MAX-ACCESS read-
STATUS
"The index in docsIfQosProfileTable describing the
of service attributes associated with this
service. If no associated entry in
exists, this object returns a value of zero."
::= { docsIfCmServiceEntry 2 }
docsIfCmServiceTxSlotsImmed OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of upstream mini-slots which have been used
transmit data PDUs in immediate (contention) mode.
includes only those PDUs which are presumed to
arrived at the headend (i.e., those which were
acknowledged.) It does not include retransmission
or mini-slots used by Requests."
"DOCSIS Radio Frequency Interface specification
St. Johns 