BRCM-CM-MGMT-MIB: View SNMP OID List / Download MIB

Indicates the number of entries in the docsDevFilterLLCTable which can be supported on this particular device under current operating conditions. Note that this is a conservative estimate and that the device will generally be able to support more filters than this number returns. Further note that this number reflects the number of filters supported if the docsDevFilterIpTable is also simultaneously populated with the number of filters returned by cmNumIpFiltersSupported. If no IP filters are configured then the the device can be expected to support double the number of LLC filters indicated by this object.

Indicates the number of entries in the docsDevFilterIpTable which can be supported on this particular device under current operating conditions. Note that this is a conservative estimate and that the device will generally be able to support more filters than this number returns. Further note that this number reflects the number of filters supported if the docsDevFilterLLCTable is also simultaneously populated with the number of filters returned by cmNumLLCFiltersSupported. If no LLC filters are configured then the the device can be expected to support double the number of IP filters indicated by this object.

Specifies whether the CM mini-firewall will be enabled, provided the mini-firewall feature is supported. If the feature is not supported, this object will always report false(2) and an attempt to set it to true(1) will be rejected with an incosistentValue error.

Specifies the behavior of the CM with regards to retrying DSD requests when no reply is received. If set to true(1), the CM will continue to retry the request until a reply is received or roughly one hour of time has passed. If set to false(2), the CM will stop retrying after three retries as required by the DOCSIS specification. Note that this setting is not persistent across reboot.

For designs which are not capable of supporting multiple CPE interfaces simultaneously, this object specifies the interface which will be used as a CPE interface. Typical settings for such a design would include ethernet(6) and usb(160). For designs which are capable of supporting multiple CPE interfaces, this object will always return other(1).

Setting this object to true(1) will cause the device to reset all non-volatile settings to their factory default state, and the device to be rebooted. Note that only dynamic settings will be affected; permanent settings (MAC addresses, etc) will remain unchanged. When read, this object always returns false(2).

This object controls the length of time between periodic updates of system time by way of a Time of Day (ToD) refresh. If set to 0, time of day will not be refreshed. Note that in order to comply with the DOCSIS requirements for ToD periodocity, a value of 0 should be used for this object.

A table describing the characteristics of each downstream channel. An entry exists in this table for each entry in the ifTable with an ifType value of docsCableDownstream (128).

An entry describing the attributes of a single downstream channel.

Downstream Codeword Error Rate. (Errored Codewords / Total CodeWords)

Downstream Mean Square Error

Indicates the tuner to which this downstream channel is mapped. A value of 0 is a special case which indicates that this channel is not mapped to any tuner - this would generally only be the case under unusual circumstances such as very shortly after bootup before scanning has started.

Indicates which channel of the tuner identified by cmDsChanInfoTuner is mapped to this downstream channel. Values are defined as offsets from the center channel of the tuner, which is represented by a value of 0 for this object. Note that allowable values for this object are constrained by the number of channels that this tuner is capable of spanning. A value of 0 - denoting the exact center channel - is only valid if the number of channels spanned by the tuner is odd. For tuners which span an even number of channels, a value of 0 will never be reported. Single channel tuners will always report a value of 0. If cmDsChanInfoTuner has a value of 0 (not associated) then the value returned by this object has no meaning; in this case a value of 0 will be returned.

The value of this object determines the mode used by the CM for IP provisioning. If set to the default value of mdd(0), the CM will comply with the DOCSIS 3.0 specification and use the mode identified in the IP provisioning mode field of the MDD message received from the CMTS. If set to any other value, the CM will ignore the IP provisioning mode field of the MDD message and use the mode specified by this object instead. If the DOCSIS config file contains a TLV which changes the value of this object from its current value, the CM will abandon its current IP settings and restart the IP provisioning and registration process using the new mode. Setting this object using SNMP does not cause a restart; in the case of an SNMP set, the new mode will take effect the next time the CM registers with a CMTS. Note that this object may also be used to invoke IPv6 or dual-stack operation when using a pre-DOCSIS 3.0 CMTS, provided the network hosting the CM is IPv6 capable. Further note that a CM which does not support IPv6 will always report ipV4Only(1) for this object, and an attempt to set the object to any other value will be rejected with an inconsistentValue error. If this object is set to a value which is incompatible with the capabilities of the associated CMTS or network, then IP provisioning may fail. This setting is persistent across reboots.

This table describes attributes of each upstream service queue on a CM.

Describes the attributes of a single service queue. An entry exists in this table exists for each service queue. The ifIndex refers to the entry in the ifTable with an ifType value of docsCableMaclayer(127).

Identifies a service queue for upstream bandwidth. This value is equal to the SID for this service queue.

Indicates the maximum number of packets which can be enqueued on this service queue. Note that for DOCSIS 3.0 devices operating in QoS mode, max queue depth is now specified in terms of bytes, not packets. Thus, for such a configuration, this object will return 0. The maximum queue depth for such a configuration may be read from docsQosServiceFlowBufferSize.

Indicates the number of packets currently enqueued on this service queue.

Specifies whether the hardware forwarding assist engine is enabled, for devices which support such assistace. For devices which do not have hardware forwarding assist support, this object will always return false(2), and an attempt to set this object to true(1) will result in an inconsistentValue error.

This object may be used to override the max burst value specified in the burst descriptor corresponding to the long data grant IUC from the upstream channel descriptor (UCD). If set to the default value of 0, the CM will conform to the DOCSIS specification requirements and abide by the max burst values as specified in the UCD. If set to any other value, the CM will limit burst sizes to either the value specified by this object or the UCD specified value, whichever is larger. Setting this object to a value of 255 effectively means that the burst size will be unlimited. This setting will maximize upstream throughput. Note that the value of this object has no effect on burst limitations as configured by service flow parameter sets.

Specifies the maximum extended upstream transmit power of which this device is capable. A value of zero indicates that the device has no extended upstream power capability. The value specified in this object will be advertised in TLV 5.40 of the CMs modem capability message.

The table of IP filters to be applied to traffic originating from or destined to this device. The fields in this table are loosely based on a subset of the fields in the docsDevFilterIpTable as defined in the DOCS-CABLE-DEVICE-MIB. The key difference is that the filters described by the cmHostIpFilterTable are not applied to bridged traffic, but rather to traffic which is sent from or received by the cablemodem itself, acting in a role as a host. This table may be used to restrict certain IP traffic (eg SNMP, TFTP, telnet, etc.) from being accessible via the CPE and / or HFC interfaces. Note that all filters will be applied to all IP addresses associated with this host. Caution must be exercised in the use of this table. For example, it is possible to render the device unmanageable if SNMP is prohibited over both CPE and CM interfaces.

An instance of an IP filter. Entries in the cmHostIpFilterTable are created and deleted using the cmHostIpFilterStatus object. Each filter describes a set of criteria against which each IP packet will be compared. Any packet which matches the filter will be discarded. Note that these filters are not applied to bridged traffic, only to traffic which is sent from or received by the cablemodem itself.

Identifies the instance number of this conceptual row.

The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the cmHostIpFilterStatus column is notReady. In particular, a newly created row cannot be made active until the corresponding instances of cmHostIpFilterDestPortLow and cmHostIpFilterDestPortHigh have been set. Only filters with a status of active(1) will be applied.

The storage type for this conceptual row. Conceptual rows having the value permanent need not allow write-access to any columnar objects in the row.

Counts the number of times this filter was matched.

Identifies the interfaces to which this filter applies.

Determines whether the filter is applied to inbound(1) traffic, outbound(2) traffic, or traffic in both(3) directions.

The inclusive lower bound of the transport-layer destination port range that is to be matched.

The inclusive upper bound of the transport-layer destination port range that is to be matched.

Determines the channel bonding strategy used by the CM upon transition to power save mode. When set to a value of disabled(-1), there will be no channel bonding response to power save mode and the device will continue to operate in the bonding mode that was in effect at the time power save was entered. When set to the default value of cmStatus(0), the CM will conform to DOCSIS 3.0 requirements by dispatching a CM-STATUS message to the CMTS indicating a transition to battery power. The CMTS is then expected to initiate a DBC which will reduce the number of channels used by the CM. The autonomous1x1 value is obsolete. If this object is set to autonomous1x1(1), then channel bonding power save will be disabled and a subsequent read of this object will return a value of disabled(-1).

A table defining management extensions for DOCSIS 3.0 upstream channels.

An entry describing the characteristics of a single upstream channel. An entry exists in this table for each entry in the ifTable with an ifType value of docsCableUpstream(129).

This object reports an absolute power level which is the top of the dynamic range window for this upstream channel. This value is calculated by applying the value for Pload_min_set, specified by the dynamic range window upper edge TLV in the RNG-RSP or TCC encodings, to the max allowable power level (Phi) of this particular channel. This object will return zero if no dynamic range window upper edge TLV has been specified in either the RNG-RSP or TCC encodings.

This object reports an absolute power level which is the bottom of the dynamic range window for this upstream channel. This value is calculated by applying the value for Pload_min_set, specified by the dynamic range window upper edge TLV in the RNG-RSP or TCC encodings, and the fixed 12dB range of transmit power levels defined by the DRW, to the max allowable power level (Phi) of this particular channel. This object will return zero if no dynamic range window upper edge TLV has been specified in either the RNG-RSP or TCC encodings.

This object counts the number of RNG-RSP power adjustments made by the CMTS which would cause the CM to violate the constraints of the dynamic ranging window. Such adjustments (if any) will have been ignored by the CM in compliance with DOCSIS 3.0 requirements.

Setting this object to true(1) allows the CM to disregard the requirement that the packet sequence number for a newly created unicast resequencing DSID must begin at zero. This allows the CM to recover more quickly when an invalid initial PSN is received for a unicast DSID. Note that in order to comply with DOCSIS 3.0 requirements, this object MUST be set to a value of false(2).

Setting this object to true(1) causes the CM to discard the next expected sequence number for all DSIDs when a DCC-RSP (arrive) message is sent, in case the PSNs are reset by the CMTS at this time. This allows the CM to bypass the two minute out of range PSN window and reset the next expected sequence numbers immediately. Note that in order to comply with DOCSIS 3.0 requirements, this object MUST be set to a value of false(2).

A notification with the standard DOCSIS event log variable bindings. This notification may be used for vendor-specific events which do not have a suitable notification defined among the standard DOCSIS traps.

An event to report that no MDDs are being received on one or more of the secondary downstream channels.