DOCS-IF-MIB: View SNMP OID List / Download MIB

This is the MIB Module for DOCSIS 2.0-compliant Radio Frequency (RF) interfaces in Cable Modems and Cable Modem Termination Systems. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4546; see the RFC itself for full legal notices.

This table describes the attributes of downstream channels (frequency bands).

An entry provides a list of attributes for a single downstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128).

The Cable Modem Termination System identification of the downstream channel within this particular MAC interface. if the interface is down, the object returns the most current value. If the downstream channel ID is unknown, this object returns a value of 0.

The center of the downstream frequency associated with this channel. This object will return the current tuner frequency. If a CMTS provides IF output, this object will return 0, unless this CMTS is in control of the final downstream frequency. See the associated compliance object for a description of valid frequencies that may be written to this object.

The bandwidth of this downstream channel. Most implementations are expected to support a channel width of 6 MHz (North America) and/or 8 MHz (Europe). See the associated compliance object for a description of the valid channel widths for this object.

The modulation type associated with this downstream channel. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM), or the value of unknown(1). See the associated conformance object for write conditions and limitations. See the reference for specifics on the modulation profiles implied by qam64 and qam256. Enumeration: 'unknown': 1, 'qam256': 4, 'other': 2, 'qam64': 3.

The Forward Error Correction (FEC) interleaving used for this downstream channel. Values are defined as follows: taps8Increment16(3): protection 5.9/4.1 usec, latency .22/.15 msec taps16Increment8(4): protection 12/8.2 usec, latency .48/.33 msec taps32Increment4(5): protection 24/16 usec, latency .98/.68 msec taps64Increment2(6): protection 47/33 usec, latency 2/1.4 msec taps128Increment1(7): protection 95/66 usec, latency 4/2.8 msec taps12increment17(8): protection 18/14 usec, latency 0.43/0.32 msec The value 'taps12increment17' is supported by EuroDOCSIS cable systems only, and the others by DOCSIS cable systems. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM), or the value of unknown(1). The value of other(2) is returned if the interleave is known but not defined in the above list. See the associated conformance object for write conditions and limitations. See the reference for the FEC configuration described by the setting of this object. Enumeration: 'taps128Increment1': 7, 'unknown': 1, 'taps8Increment16': 3, 'taps12increment17': 8, 'other': 2, 'taps32Increment4': 5, 'taps64Increment2': 6, 'taps16Increment8': 4.

At the CMTS, the operational transmit power. At the CM, the received power level. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM) or the value of 0. See the associated conformance object for write conditions and limitations. See the reference for recommended and required power levels.

The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used. Enumeration: 'unknown': 1, 'annexB': 4, 'other': 2, 'annexC': 5, 'annexA': 3.

The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.

This table describes the attributes of attached upstream channels.

List of attributes for a single upstream channel. For DOCSIS 2.0 CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstreamChannel (205). For DOCSIS 1.x CM/CMTSs and DOCSIS 2.0 CMs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstream (129). For DOCSIS 2.0 CMTSs, two classes of interfaces can be defined for this table: o Upstream Physical Interfaces: The traditional DOCSIS 1.x CMTS upstream interface ifType 129 and the DOCSIS 2.0 ifType 205 that are functional. In other words, interfaces that represent upstream receivers within an RF MAC interface. Entries of physical interfaces are exposed to the management interface with their corresponding ifStack hierarchy and are not administratively created by this table. o Upstream Temporary Interfaces: A fictitious interface created for the purpose of manipulating physical interface parameters offline, then validating prior to updating the target physical interface. In case of a reinitialization of the managed system, physical interfaces values persist while the temporary interfaces are not recreated. This mechanism helps to minimize service disruptions originating in situations where a group of interface parameter values need to be consistent with each other in SET operations. A temporary buffer (temporary interface) is provided to allow the CMTS to validate the parameters offline.

The CMTS identification of the upstream channel.

The center of the frequency band associated with this upstream interface. This object returns 0 if the frequency is undefined or unknown. Minimum permitted upstream frequency is 5,000,000 Hz for current technology. See the associated conformance object for write conditions and limitations.

The bandwidth of this upstream interface. This object returns 0 if the interface width is undefined or unknown. Minimum permitted interface width is currently 200,000 Hz. See the associated conformance object for write conditions and limitations.

An entry identical to the docsIfModIndex in the docsIfCmtsModulationTable that describes this channel. This channel is further instantiated there by a grouping of interval usage codes (IUCs) that, together, fully describe the channel modulation. This object returns 0 if the docsIfCmtsModulationTable entry does not exist or is empty. See the associated conformance object for write conditions and limitations. Setting this object returns an 'inconsistentValue' error if the following conditions are not satisfied: 1. All the IUC entries in the selected modulation profile MUST have the same value of docsIfCmtsModChannelType. 2. All of the Modulation parameters in the selected modulation profile MUST be consistent with the other parameters in this docsIfUpstreamChannelEntry.

Applicable to TDMA and ATDMA channel types only. The number of 6.25 microsecond ticks in each upstream mini-slot. Returns zero if the value is undefined or unknown or in case of an SCDMA channel. See the associated conformance object for write conditions and limitations.

At the CM, a measure of the current round trip time obtained from the ranging offset (initial ranging offset + ranging offset adjustments). At the CMTS, the maximum of timing offset, among all the CMs that are/were present on the channel, taking into account all ( initial + periodic ) timing offset corrections that were sent for each of the CMs. Generally, these measurements are positive, but if the measurements are negative, the value of this object is zero. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are one 64th fraction of 6.25 microseconds.

The initial random backoff window to use when retrying Ranging Requests. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.

The final random backoff window to use when retrying Ranging Requests. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.

The initial random backoff window to use when retrying transmissions. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.

The final random backoff window to use when retrying transmissions. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.

Applicable for SCDMA channel types only. Number of active codes. Returns zero for Non-SCDMA channel types. Note that legal values from 64..128 MUST be non-prime.

Applicable for SCDMA channel types only. The number of SCDMA codes per mini-slot. Returns zero if the value is undefined or unknown or in case of a TDMA or ATDMA channel.

Applicable for SCDMA channel types only. SCDMA Frame size in units of spreading intervals. This value returns zero for non-SCDMA Profiles.

Applicable for SCDMA channel types only. 15-bit seed used for code hopping sequence initialization. Returns zero for non-SCDMA channel types. Setting this value to a value different than zero for non-SCDMA channel types returns the error 'wrongValue'.

Reflects the Upstream channel type. This object returns the value of docsIfCmtsModChannelType for the modulation profile selected in docsIfUpChannelModulationProfile for this row.

This object contains the ifIndex value of the physical interface row entry whose parameters are to be adjusted. Upon setting this object to the ifIndex value of a physical interface, the following interface objects values are copied to this entry: docsIfUpChannelFrequency, docsIfUpChannelWidth, docsIfUpChannelModulationProfile, docsIfUpChannelSlotSize, docsIfUpChannelRangingBackoffStart, docsIfUpChannelRangingBackoffEnd, docsIfUpChannelTxBackoffStart, docsIfUpChannelTxBackoffEnd, docsIfUpChannelScdmaActiveCodes, docsIfUpChannelScdmaCodesPerSlot, docsIfUpChannelScdmaFrameSize, docsIfUpChannelScdmaHoppingSeed, docsIfUpChannelType, and docsIfUpChannelPreEqEnable Setting this object to the value of a non-existent or a temporary upstream interface returns the error 'wrongValue'. This object MUST contain a value of zero for physical interfaces entries. Setting this object in row entries that correspond to physical interfaces returns the error 'wrongValue'.

Used to perform the copy of adjusted parameters from the temporary interface entry to the physical interface indicated by the docsIfUpChannelCloneFrom object. The transfer is initiated through an SNMP SET to 'true' of this object. A SET to 'true' fails and returns error 'commitFailed' if docsIfUpChannelStatus value is 'notInService', which means that the interface parameters values are not compatible with each other or have not been validated yet. Reading this object always returns 'false'.

This object is only used for the creation of a temporary upstream row with the purpose of updating the parameters of a physical upstream channel entry. The following restrictions apply to this object: 1. This object is not writable for physical interfaces. 2. Temporary interface entries are only created by a SET of this object to createandWait(5). 3. ifAdminStatus from the Interface MIB RFC 2863 is used to take a physical upstream channel offline, to be consistent with DOCSIS 1.x operation, as indicated in RFC 2670. In addition, o ifAdminStatus 'down' is reflected in this object as 'notInService'. o ifOperStatus 'down' while ifAdminStatus 'up' is reflected in this object as 'notInservice'. 4. Temporary created rows MUST be set to 'active' with the purpose of validating upstream parameter consistency prior to transferring the parameters to the physical interface. Below is a mandatory procedure for adjusting the values of a physical interface: 1. Create a temporary interface entry through an SNMP SET using 'createAndWait'. At this point, the RowStatus reports 'notReady'. The Manager entity uses an ifIndex value outside the operational range of the physical interfaces for the creation of a temporary interface. 2. Set the docsIfUpChannelCloneFrom object to the ifIndex value of the physical row to update. Now docsIfUpChannelStatus reports 'notInService'. 3. Change the upstream parameters to the desired values in the temporary row. 4. Validate that all parameters are consistent by setting docsIfUpChannelStatus to 'active'. A failure to set the RowStatus to 'active' returns the error 'commitFailed', which means the parameters are not compatible with the target physical interface. 5. With docsIfUpChannelStatus 'active', transfer the parameters to the target physical interface by setting the object docsIfUpChannelUpdate to 'true'. 6. Delete the temporary row by setting docsIfUpChannelStatus to 'destroy'.

At the CMTS, this object is used to enable or disable pre-equalization on the upstream channel represented by this table instance. At the CM, this object is read-only and reflects the status of pre-equalization as represented in the RNG-RSP. Pre-equalization is considered enabled at the CM if a RNG-RSP with pre-equalization data has been received at least once since the last mac reinitialization.

Describes the attributes for each class of service.

Describes the attributes for a single class of service. If implemented as read-create in the Cable Modem Termination System, creation of entries in this table is controlled by the value of docsIfCmtsQosProfilePermissions. If implemented as read-only, entries are created based on information in REG-REQ MAC messages received from cable modems (for Cable Modem Termination System), or based on information extracted from the TFTP option file (for Cable Modem). In the Cable Modem Termination System, read-only entries are removed if no longer referenced by docsIfCmtsServiceTable. An entry in this table MUST not be removed while it is referenced by an entry in docsIfCmServiceTable (Cable Modem) or docsIfCmtsServiceTable (Cable Modem Termination System). An entry in this table SHOULD NOT be changeable while it is referenced by an entry in docsIfCmtsServiceTable. If this table is created automatically, there SHOULD only be a single entry for each Class of Service. Multiple entries with the same Class of Service parameters are NOT RECOMMENDED.

The index value that uniquely identifies an entry in the docsIfQosProfileTable.

A relative priority assigned to this service when 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.

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.

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.

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.

The maximum number of mini-slots that may be requested for a single upstream transmission. A value of zero means there is no limit. MUST NOT be changed while this row is active. This object has been deprecated and replaced by docsIfQosProfMaxTransmitBurst, to fix a mismatch of the units and value range with respect to the DOCSIS Maximum Upstream Channel Transmit Burst Configuration Setting.

Indicates whether Baseline Privacy is enabled for this service class. MUST NOT be changed while this row is active.

This is object is used to create or delete rows in this table. This object MUST NOT be changed from active while the row is referenced by any entry in either docsIfCmServiceTable (on the CM) or docsIfCmtsServiceTable (on the CMTS).

The maximum number of bytes that may be requested for a single upstream transmission. A value of zero means there is no limit. Note: This value does not include any physical layer overhead. MUST NOT be changed while this row is active.

The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for writable objects.

At the CM, describes the PHY signal quality of downstream channels. At the CMTS, this object describes the PHY signal quality of upstream channels. At the CMTS, this table MAY exclude contention intervals.

At the CM, this object describes the PHY characteristics of a downstream channel. At the CMTS, it describes the PHY signal quality of an upstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128) for Cable Modems. For DOCSIS 1.1 Cable Modem Termination Systems, an entry exists for each ifEntry with an ifType of docsCableUpstream (129). For DOCSIS 2.0 Cable Modem Termination Systems, an entry exists for each ifEntry with an ifType of docsCableUpstreamChannel (205).

true(1) if this CMTS includes contention intervals in the counters in this table. Always false(2) for CMs.

Codewords received on this channel without error. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received on this channel with correctable errors. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received on this channel with uncorrectable errors. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Signal/Noise ratio as perceived for this channel. At the CM, this object describes the Signal/Noise of the downstream channel. At the CMTS, it describes the average Signal/Noise of the upstream channel.

Microreflections, including in-channel response as perceived on this interface, measured in dBc below the signal level. This object is not assumed to return an absolutely accurate value, but it gives a rough indication of microreflections received on this interface. It is up to the implementer to provide information as accurately as possible.

At the CM, this object returns the equalization data for the downstream channel. At the CMTS, this object is not applicable and is not instantiated. Note that previous CMTS implementations may instantiate this object in two ways: - An equalization value indicating an equalization average for the upstream channel. Those values have vendor-dependent interpretations. - Return a zero-length OCTET STRING to indicate that the value is unknown or if there is no equalization data available or defined.

Codewords received on this channel without error. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQUnerroreds. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received on this channel with correctable errors. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQCorrecteds. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received on this channel with uncorrectable errors. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQUncorrectables. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Indication of the DOCSIS capability of the device.

Describes the attributes of each CM MAC interface, extending the information available from ifEntry.

An entry containing objects describing attributes of each MAC entry, extending the information in ifEntry. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).

Identifies the CMTS that is believed to control this MAC domain. At the CM, this will be the source address from SYNC, MAP, and other MAC-layer messages. If the CMTS is unknown, returns 00-00-00-00-00-00.

Identifies the capabilities of the MAC implementation at this interface. Note that packet transmission is always supported. Therefore, there is no specific bit required to explicitly indicate this capability. Note that BITS objects are encoded most significant bit first. For example, if bit 1 is set, the value of this object is the octet string '40'H. Bits: 'concatenation': 1, 'atmCells': 0.

Waiting time for a Ranging Response packet. This object has been obsoleted and replaced by docsIfCmRangingTimeout to correct the typing to TimeInterval.

Waiting time for a Ranging Response packet. This object MUST NOT persist at reinitialization of the managed system.

This table maintains a number of status objects and counters for Cable Modems.

A set of status objects and counters for a single MAC layer instance in Cable Modem. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).

Current Cable Modem connectivity state, as specified in the RF Interface Specification. Interpretations for state values 1-12 are clearly outlined in the SP-RFI reference given below. The state value accessDenied(13) indicates the CMTS has sent a Registration Aborted message to the CM. The same state is reported as accessDenied(7) by the CMTS object docsIfCmtsCmStatusValue. Enumeration: 'ipComplete': 7, 'phySynchronized': 4, 'notSynchronized': 3, 'todEstablished': 8, 'usParametersAcquired': 5, 'operational': 12, 'notReady': 2, 'other': 1, 'paramTransferComplete': 10, 'rangingComplete': 6, 'accessDenied': 13, 'registrationComplete': 11, 'securityEstablished': 9.

Status code for a Cable Modem as defined in the OSSI Specification. The status code consists of a single character indicating error groups, followed by a two- or three-digit number indicating the status condition, followed by a decimal. An example of a returned value could be 'T101.0'. The zero-length OCTET STRING indicates no status code yet registered.

The operational transmit power for the attached upstream channel.

Number of times the CM reset or initialized this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the CM lost synchronization with the downstream channel. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the CM received invalid MAP messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the CM received invalid UCD messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the CM received invalid ranging response messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the CM received invalid registration response messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times counter T1 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times counter T2 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times counter T3 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times counter T4 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Number of times the ranging process was aborted by the CMTS. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Indication of whether the device has registered using 1.0 Class of Service or 1.1 Quality of Service. An unregistered CM SHOULD indicate 'docsis11' for a docsIfDocsisBaseCapability value of DOCSIS 1.1/2.0. An unregistered CM SHOULD indicate 'docsis10' for a docsIfDocsisBaseCapability value of DOCSIS 1.0.

Indicates modulation type status currently used by the CM. Since this object specifically identifies PHY mode, the shared upstream channel type is not permitted.

Pre-equalization data for this CM after convolution with data indicated in the RNG-RSP. This data is valid when docsIfUpChannelPreEqEnable is set to true.

The number of successful Upstream Channel Change transactions. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of failed Upstream Channel Change transactions. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Describes the attributes of each upstream service queue on a CM.

Describes the attributes of an upstream bandwidth service queue. An entry in this table exists for each Service ID. The primary index is an ifIndex with an ifType of docsCableMaclayer(127).

Identifies a service queue for upstream bandwidth. The attributes of this service queue are shared between the CM and the CMTS. The CMTS allocates upstream bandwidth to this service queue based on requests from the CM and on the class of service associated with this queue.

The index in docsIfQosProfileTable describing the quality of service attributes associated with this particular service. If no associated entry in docsIfQosProfileTable exists, this object returns a value of zero.

The number of upstream mini-slots that have been used to transmit data PDUs in immediate (contention) mode. This includes only those PDUs that are presumed to have arrived at the head-end (i.e., those that were explicitly acknowledged). It does not include retransmission attempts or mini-slots used by requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of upstream mini-slots that have been used to transmit data PDUs in dedicated mode (i.e., as a result of a unicast Data Grant). Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of attempts to transmit data PDUs containing requests for acknowledgment that did not result in acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of data PDU transmission failures due to excessive retries without acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of attempts to transmit bandwidth requests that did not result in acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of requests for bandwidth that failed due to excessive retries without acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of upstream mini-slots that have been used to transmit data PDUs in immediate (contention) mode. This includes only those PDUs that are presumed to have arrived at the head-end (i.e., those that were explicitly acknowledged). It does not include retransmission attempts or mini-slots used by requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The number of upstream mini-slots that have been used to transmit data PDUs in dedicated mode (i.e., as a result of a unicast Data Grant). Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Describes the attributes of each CMTS MAC interface, extending the information available from ifEntry. Mandatory for all CMTS devices.

An entry containing objects describing attributes of each MAC entry, extending the information in ifEntry. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).

Identifies the capabilities of the CMTS MAC implementation at this interface. Note that packet transmission is always supported. Therefore, there is no specific bit required to explicitly indicate this capability. Note that BITS objects are encoded most significant bit first. For example, if bit 1 is set, the value of this object is the octet string '40'H. Bits: 'concatenation': 1, 'atmCells': 0.

The interval between CMTS transmission of successive SYNC messages at this interface.

The interval between CMTS transmission of successive Upstream Channel Descriptor messages for each upstream channel at this interface.

The maximum number of service IDs that may be simultaneously active.

The amount of time to elapse between each broadcast initial maintenance grant. Broadcast initial maintenance grants are used to allow new cable modems to join the network. Zero indicates that a vendor-specific algorithm is used instead of a fixed time. The maximum amount of time permitted by the specification is 2 seconds. This object has been obsoleted and replaced by docsIfCmtsInsertInterval to fix a SYNTAX typing problem.

The maximum number of attempts to make on invitations for ranging requests. A value of zero means the system SHOULD attempt to range forever.

The amount of time to elapse between each broadcast initial maintenance grant. Broadcast initial maintenance grants are used to allow new cable modems to join the network. Zero indicates that a vendor-specific algorithm is used instead of a fixed time. The maximum amount of time permitted by the specification is 2 seconds.

The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.

For the MAC layer, this group maintains a number of status objects and counters.

Status entry for a single MAC layer. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).

This object counts invalid RNG-REQ messages received on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This object counts ranging attempts that were explicitly aborted by the CMTS. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This object counts invalid REG-REQ messages received on this interface; that is, syntax, out of range parameters, or erroneous requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This object counts failed registration attempts. Included are docsIfCmtsStatusInvalidRegReqs, authentication, and class of service failures. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This object counts invalid data request messages received on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This object counts the number of times counter T5 expired on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

A set of objects in the CMTS, maintained for each cable modem connected to this CMTS.

Status information for a single cable modem. An entry in this table exists for each cable modem that is connected to the CMTS implementing this table.

Index value to uniquely identify an entry in this table. For an individual cable modem, this index value SHOULD NOT change during CMTS uptime.

MAC address of the cable modem. If the cable modem has multiple MAC addresses, this is the MAC address associated with the Cable interface.

IP address of this cable modem. If the cable modem has no IP address assigned, or the IP address is unknown, this object returns a value of 0.0.0.0. If the cable modem has multiple IP addresses, this object returns the IP address associated with the Cable interface. This object has been deprecated and replaced by docsIfCmtsCmStatusInetAddressType and docsIfCmtsCmStatusInetAddress, to enable IPv6 addressing in the future.

IfIndex of the downstream channel that this CM is connected to. If the downstream channel is unknown, this object returns a value of zero.

For DOCSIS 2.0, indicates the ifIndex of the logical upstream channel (ifType 205) this CM is connected to. For DOCSIS 1.x, indicates the ifIndex of the upstream channel (ifType 129) this CM is connected to. If the upstream channel is unknown, this object returns a value of zero.

The receive power as perceived for upstream data from this cable modem. If the receive power is unknown, this object returns a value of zero.

A measure of the current round trip time for this CM. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are in terms of (6.25 microseconds/64). Returns zero if the value is unknown. For channels requiring finer resolution, please refer to object docsIfCmtsCmStatusHighResolutionTimingOffset.

Equalization data for this CM, as measured by the CMTS. Returns the zero-length OCTET STRING if the value is unknown or if there is no equalization data available or defined.

Current cable modem connectivity state, as specified in the RF Interface Specification. Returned status information is the CM status, as assumed by the CMTS, and indicates the following events: other(1) Any state other than below. ranging(2) The CMTS has received an Initial Ranging Request message from the CM, and the ranging process is not yet complete. rangingAborted(3) The CMTS has sent a Ranging Abort message to the CM. rangingComplete(4) The CMTS has sent a Ranging Complete message to the CM. ipComplete(5) The CMTS has received a DHCP reply message and forwarded it to the CM. registrationComplete(6) The CMTS has sent a Registration Response message to the CM. accessDenied(7) The CMTS has sent a Registration Aborted message to the CM. operational(8) Value 8 is considered reserved and should not be defined in future revisions of this MIB module to avoid conflict with documented implementations that support value 8 to indicate operational state after completing the BPI initialization process. registeredBPIInitializing(9) Baseline Privacy (BPI) is enabled and the CMTS is in the process of completing BPI initialization. This state MAY last for a significant length of time if failures occur during the initialization process. After completion of BPI initialization, the CMTS will report registrationComplete(6). The CMTS only needs to report states it is able to detect. Enumeration: 'registeredBPIInitializing': 9, 'rangingAborted': 3, 'ipComplete': 5, 'other': 1, 'rangingComplete': 4, 'operational': 8, 'ranging': 2, 'registrationComplete': 6, 'accessDenied': 7.

Codewords received without error from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received with correctable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received with uncorrectable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Signal/Noise ratio as perceived for upstream data from this cable modem. If the Signal/Noise is unknown, this object returns a value of zero.

Total microreflections, including in-channel response as perceived on this interface, measured in dBc below the signal level. This object is not assumed to return an absolutely accurate value, but it gives a rough indication of microreflections received on this interface. It is up to the implementer to provide information as accurately as possible. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received without error from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received with correctable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Codewords received with uncorrectable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Indication of whether the CM has registered using 1.0 Class of Service or 1.1 Quality of Service.

Indicates modulation type currently used by the CM. Since this object specifically identifies PHY mode, the shared type is not permitted. If the upstream channel is unknown, this object returns a value of zero.

The type of internet address of docsIfCmtsCmStatusInetAddress. If the cable modem internet address is unassigned or unknown, then the value of this object is unknown(0).

Internet address of this cable modem. If the Cable Modem has no Internet address assigned, or the Internet address is unknown, the value of this object is the zero-length OCTET STRING. If the cable modem has multiple Internet addresses, this object returns the Internet address associated with the Cable (i.e., RF MAC) interface.

The value of sysUpTime when docsIfCmtsCmStatusValue was last updated.

A measure of the current round trip time for this CM. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are in terms of (6.25 microseconds/(64*256)). Returns zero if the value is unknown. This is the high resolution version of object docsIfCmtsCmStatusTimingOffset, for channels requiring finer resolution.

Describes the attributes of upstream service queues in a Cable Modem Termination System.

Describes the attributes of a single upstream bandwidth service queue. Entries in this table exist for each ifEntry with an ifType of docsCableMaclayer(127), and for each service queue (Service ID) within this MAC layer. Entries in this table are created with the creation of individual Service IDs by the MAC layer and removed when a Service ID is removed.

Identifies a service queue for upstream bandwidth. The attributes of this service queue are shared between the Cable Modem and the Cable Modem Termination System. The CMTS allocates upstream bandwidth to this service queue based on requests from the CM and on the class of service associated with this queue.

Pointer to an entry in docsIfCmtsCmStatusTable identifying the cable modem using this Service Queue. If multiple cable modems are using this Service Queue, the value of this object is zero. This object has been deprecated and replaced by docsIfCmtsServiceNewCmStatusIndex, to fix a mismatch of the value range with respect to docsIfCmtsCmStatusIndex (1..2147483647).

Allows a service class for a particular modem to be suppressed, (re-)enabled, or deleted altogether. Enumeration: 'disabled': 2, 'destroyed': 3, 'enabled': 1.

The index in docsIfQosProfileTable describing the quality of service attributes associated with this particular service. If no associated docsIfQosProfileTable entry exists, this object returns a value of zero.

The value of sysUpTime when this entry was created.

The cumulative number of Packet Data octets received on this Service ID. The count does not include the size of the Cable MAC header. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The cumulative number of Packet Data packets received on this Service ID. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Pointer (via docsIfCmtsCmStatusIndex) to an entry in docsIfCmtsCmStatusTable identifying the cable modem using this Service Queue. If multiple cable modems are using this Service Queue, the value of this object is zero.

Describes a modulation profile associated with one or more upstream channels.

Describes a modulation profile for an Interval Usage Code for one or more upstream channels. Entries in this table are created by the operator. Initial default entries MAY be created at system initialization time, which could report a value of 'permanent' or 'readOnly' for docsIfCmtsModStorageType. A CMTS MAY reject the creation of additional Interval Usage Codes for a modulation profile being defined at Initialization time. No individual objects have to be specified in order to create an entry in this table. Note that some objects do not have DEFVAL clauses but do have calculated defaults and need not be specified during row creation.

An index into the Channel Modulation table representing a group of Interval Usage Codes, all associated with the same channel.

An index into the Channel Modulation table that, when grouped with other Interval Usage Codes, fully instantiates all modulation sets for a given upstream channel. Enumeration: 'initialRanging': 3, 'longData': 6, 'advPhyShortData': 9, 'request': 1, 'requestData': 2, 'advPhyLongData': 10, 'ugs': 11, 'periodicRanging': 4, 'shortData': 5.

Controls and reflects the status of rows in this table. There is no restriction on the changing of values in this table while their associated rows are active, with the exception of: 1. If a modulation profile is being referenced by one or more upstream channels, an attempt to set the value of docsIfCmtsModChannelType returns an 'inconsistentValue' error. 2. If a modulation profile is being referenced by one or more upstream channels, an attempt to set docsIfCmtsModControl to destroy(6) or notInService(2) returns an 'inconsistentValue' error.

The modulation type used on this channel. Returns other(1) if the modulation type is not qpsk, qam16, qam8, qam32, qam64, or qam128. Type qam128 is used for SCDMA channels only. See the reference for the modulation profiles implied by different modulation types. Enumeration: 'qpsk': 2, 'qam64': 6, 'qam128': 7, 'qam8': 4, 'qam32': 5, 'qam16': 3, 'other': 1.

The preamble length for this modulation profile in bits. Default value is the minimum needed by the implementation at the CMTS for the given modulation profile.

Specifies whether or not differential encoding is used on this channel.

The number of correctable errored bytes (t) used in forward error correction code. The value of 0 indicates that no correction is employed. The number of check bytes appended will be twice this value.

The number of data bytes (k) in the forward error correction codeword. This object is not used if docsIfCmtsModFECErrorCorrection is zero.

The 15-bit seed value for the scrambler polynomial.

The maximum number of mini-slots that can be transmitted during this channel's burst time. Returns zero if the burst length is bounded by the allocation MAP rather than by this profile. Default value is 0, except for shortData, where it is 8.

The number of symbol-times that MUST follow the end of this channel's burst. Default value is the minimum time needed by the implementation for this modulation profile.

Indicates whether the last FEC codeword is truncated.

Indicates whether the scrambler is employed.

ATDMA Byte Interleaver Depth (Ir). This object returns 1 for non-ATDMA profiles.

ATDMA Byte Interleaver Block size (Br). This object returns zero for non-ATDMA profiles

Preamble type for DOCSIS 2.0 bursts. The value 'unknown(0)' represents a row entry consisting only of DOCSIS 1.x bursts Enumeration: 'unknown': 0, 'qpsk0': 1, 'qpsk1': 2.

Trellis Code Modulation (TCM) On/Off. This value returns false for non-S-CDMA profiles.

S-CDMA Interleaver step size. This value returns zero for non-S-CDMA profiles.

S-CDMA spreader. This value returns false for non-S-CDMA profiles. Default value for IUC 3 and 4 is OFF; for all other IUCs it is ON.

S-CDMA sub-frame size. This value returns zero for non-S-CDMA profiles.

Describes the modulation channel type for this modulation entry. All the active entries in a modulation profile (that is all active entries that share a common docsIfCmtsModIndex) MUST have the same value of docsIfCmtsModChannelType.

The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.

This object specifies permitted methods of creating entries in docsIfQosProfileTable. createByManagement(0) is set if entries can be created using SNMP. updateByManagement(1) is set if updating entries using SNMP is permitted. createByModems(2) is set if entries can be created based on information in REG-REQ MAC messages received from cable modems. Information in this object is only applicable if docsIfQosProfileTable is implemented as read-create. Otherwise, this object is implemented as read-only and returns createByModems(2). Either createByManagement(0) or updateByManagement(1) MUST be set when writing to this object. Note that BITS objects are encoded most significant bit first. For example, if bit 2 is set, the value of this object is the octet string '20'H. Bits: 'createByModems': 2, 'updateByManagement': 1, 'createByManagement': 0.

This is a table to provide a quick access index into the docsIfCmtsCmStatusTable. There is exactly one row in this table for each row in the docsIfCmtsCmStatusTable. In general, the management station SHOULD use this table only to get a pointer into the docsIfCmtsCmStatusTable (which corresponds to the CM's RF interface MAC address) and SHOULD not iterate (e.g., GetNext through) this table.

A row in the docsIfCmtsMacToCmTable. An entry in this table exists for each cable modem that is connected to the CMTS implementing this table.

The RF side MAC address for the referenced CM (e.g., the interface on the CM that has docsCableMacLayer(127) as its ifType).

An row index into docsIfCmtsCmStatusTable. When queried with the correct instance value (e.g., a CM's MAC address), returns the index in docsIfCmtsCmStatusTable that represents that CM.

The time interval in seconds over which the channel utilization index is calculated. All upstream/downstream channels use the same docsIfCmtsChannelUtilizationInterval. Setting a value of zero disables utilization reporting. A channel utilization index is calculated over a fixed window applying to the most recent docsIfCmtsChannelUtilizationInterval. It would therefore be prudent to use a relatively short docsIfCmtsChannelUtilizationInterval. It is a vendor decision whether to reset the timer when docsIfCmtsChannelUtilizationInterval is changed during a utilization sampling period.

Reports utilization statistics for attached upstream and downstream physical channels.

Utilization statistics for a single upstream or downstream physical channel. An entry exists in this table for each ifEntry with an ifType equal to docsCableDownstream (128) or docsCableUpstream (129).

The secondary index into this table. Indicates the IANA interface type associated with this physical channel. Only docsCableDownstream (128) and docsCableUpstream (129) are valid.

The tertiary index into this table. Indicates the CMTS identifier for this physical channel.

The calculated and truncated utilization index for this physical upstream or downstream channel, accurate as of the most recent docsIfCmtsChannelUtilizationInterval. Upstream Channel Utilization Index: The upstream channel utilization index is expressed as a percentage of mini-slots utilized on the physical channel, regardless of burst type. For an Initial Maintenance region, the mini-slots for the complete region are considered utilized if the CMTS received an upstream burst within the region from any CM on the physical channel. For contention REQ and REQ/DATA regions, the mini-slots for a transmission opportunity within the region are considered utilized if the CMTS received an upstream burst within the opportunity from any CM on the physical channel. For all other regions, utilized mini-slots are those in which the CMTS granted bandwidth to any unicast SID on the physical channel. For an upstream interface that has multiple logical upstream channels enabled, the utilization index is a weighted sum of utilization indices for the logical channels. The weight for each utilization index is the percentage of upstream mini-slots allocated for the corresponding logical channel. Example: If 75% of bandwidth is allocated to the first logical channel and 25% to the second, and the utilization indices for each are 60 and 40, respectively, the utilization index for the upstream physical channel is (60 * 0.75) + (40 * 0.25) = 55. This figure applies to the most recent utilization interval. Downstream Channel Utilization Index: The downstream channel utilization index is a percentage expressing the ratio between bytes used to transmit data versus the total number of bytes transmitted in the raw bandwidth of the MPEG channel. As with the upstream utilization index, the calculated value represents the most recent utilization interval. Formula: Downstream utilization index = (100 * (data bytes / raw bytes)) Definitions: Data bytes: Number of bytes transmitted as data in the docsIfCmtsChannelUtilizationInterval. Identical to docsIfCmtsDownChannelCtrUsed Bytes measured over the utilization interval. Raw bandwidth: Total number of bytes available for transmitting data, not including bytes used for headers and other overhead. Raw bytes: (raw bandwidth * docsIfCmtsChannelUtilizationInterval). Identical to docsIfCmtsDownChannelCtrTotal Bytes measured over the utilization interval.

This table is implemented at the CMTS to collect downstream channel statistics for utilization calculations.

An entry provides a list of traffic counters for a single downstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128).

The Cable Modem Termination System identification of the downstream channel within this particular MAC interface. If the interface is down, the object returns the most current value. If the downstream channel ID is unknown, this object returns a value of 0.

At the CMTS, the total number of bytes in the Payload portion of MPEG Packets (i.e., not including MPEG header or pointer_field) transported by this downstream channel. This is the 32-bit version of docsIfCmtsDownChnlCtrExtTotalBytes, included to provide back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

At the CMTS, the total number of DOCSIS data bytes transported by this downstream channel. The number of data bytes is defined as the total number of bytes transported in DOCSIS payloads minus the number of stuff bytes transported in DOCSIS payloads. This is the 32-bit version of docsIfCmtsDownChnlCtrExtUsedBytes, included to provide back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

At the CMTS, the total number of bytes in the Payload portion of MPEG Packets (i.e., not including MPEG header or pointer_field) transported by this downstream channel. This is the 64-bit version of docsIfCmtsDownChnlCtrTotalBytes and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

At the CMTS, the total number of DOCSIS data bytes transported by this downstream channel. The number of data bytes is defined as the total number of bytes transported in DOCSIS payloads minus the number of stuff bytes transported in DOCSIS payloads. This is the 64-bit version of docsIfCmtsDownChnlCtrUsedBytes and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

This table is implemented at the CMTS to provide upstream channel statistics appropriate for channel utilization calculations.

List of traffic statistics for a single upstream channel. For DOCSIS 2.0 CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstreamChannel (205). For DOCSIS 1.x CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstream (129).

The CMTS identification of the upstream channel.

Current count, from CMTS initialization, of all mini-slots defined for this upstream logical channel. This count includes all IUCs and SIDs, even those allocated to the NULL SID for a 2.0 logical channel that is inactive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalMslots and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of unicast granted mini-slots on the upstream logical channel, regardless of burst type. Unicast granted mini-slots are those in which the CMTS assigned bandwidth to any unicast SID on the logical channel. However, this object does not include minis-lots for reserved IUCs, or grants to SIDs designated as meaning 'no CM'. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUcastGrantedMslots, and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention mini-slots defined for this upstream logical channel. This count includes all mini-slots assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnMslots, and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention mini-slots utilized on the upstream logical channel. For contention regions, utilized mini-slots are those in which the CMTS correctly received an upstream burst from any CM on the upstream logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnMslots and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of all mini-slots defined for this upstream logical channel. This count includes all IUCs and SIDs, even those allocated to the NULL SID for a 2.0 logical channel that is inactive. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of unicast granted mini-slots on the upstream logical channel, regardless of burst type. Unicast granted mini-slots are those in which the CMTS assigned bandwidth to any unicast SID on the logical channel. However, this object does not include mini-slots for reserved IUCs, or grants to SIDs designated as meaning 'no CM'. This is the 64-bit version of docsIfCmtsUpChnlCtrUcastGrantedMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention mini-slots defined for this upstream logical channel. This count includes all mini-slots assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention mini-slots utilized on the upstream logical channel. For contention regions, utilized mini-slots are those in which the CMTS correctly received an upstream burst from any CM on the upstream logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention mini-slots subjected to collisions on the upstream logical channel. For contention regions, these are the mini-slots applicable to bursts that the CMTS detected but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC1 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots utilized on this upstream logical channel. This count includes all contention mini-slots for IUC1 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC1 applicable to bursts that the CMTS detected but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC2 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention initial maintenance mini-slots defined for this upstream logical channel. This includes all mini-slots for IUC3 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention initial maintenance mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention initial maintenance mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of collision contention mini-slots on the upstream logical channel. For contention regions, these are the mini-slots applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC1 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots utilized on this upstream logical channel. This count includes all contention mini-slots for IUC1 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC1 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC2 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention request data mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of initial maintenance mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC3 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of initial maintenance mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

Current count, from CMTS initialization, of contention initial maintenance mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.

The compliance statement for devices that implement DOCSIS 1.x compliant Radio Frequency Interfaces.

The compliance statement for devices that implement DOCSIS 2.0 Radio Frequency Interfaces.

Group of objects implemented in both cable modems and cable modem termination systems.

Group of objects implemented in cable modems.

Group of objects implemented in Cable Modem Termination Systems.

Group of objects obsoleted.

Group of objects implemented in both cable modems and cable modem termination systems.

Group of objects implemented in cable modems.

Group of objects implemented in Cable Modem Termination Systems.