BRCM-CABLEDATA-PRIVATE-MIB
AI MIB Summary
The BRCM-CABLEDATA-PRIVATE-MIB provides vendor-specific extensions for monitoring and managing Broadcom-based cable data infrastructure, specifically exposing proprietary metrics for DOCSIS cable modem termination systems (CMTS) and edge routers. This module enables granular visibility into cable data plane performance, including channel utilization, modulation profiles, and proprietary error counters not covered by standard IETF MIBs.
Broadcom cabledata private MIB
Main OID:
cableDataPrivateMIB.cableDataPrivate.1
9
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
9 total| Object Name |
|---|
cableDataPrivateMIBBroadcom cabledata private MIB MODULE-IDENTITY .cableDataPrivate.1 |
cableDataPrivateMIBObjects OBJECT IDENTIFIER .cableDataPrivate.1.1 |
cableDataPrivateBase OBJECT IDENTIFIER .cableDataPrivate.1.1.1 |
cdPrivateMibEnableSetting this object to disabled(0) causes the entire cableDataPrivate
branch of the MIB to permanently disappear. Once all private
operations are complete, this object should be set to disabled(0).
Setting this object to factory(1) will expose the
cableDataPrivateFactory branch, but will hide the
cableDataPrivateEngineering branch. Setting this object to
engineering(2) will expose the cableDataPrivateEngineering branch
in addition to the cableDataPrivateFactory branch. Initial value for
this object is factory(1).rw Enumeration .cableDataPrivate.1.1.1.1 |
cdPrivateMibEnableKeyTableA table which may be used to re-enable the private MIB after
privateMibEnable is set to false. This table contains a list
of keys, all of which must be set to their current values in a single
SNMP-SET PDU in order to set privateMibEnable back to manufacturing.
If the table is empty, then this mechanism is disabled and the private
MIB cannot be re-enabled. The number of keys required to re-enable
the private MIB is controlled at configuration time by the number of
entries created in the table. Although there is no theoretical
maximum to the number of keys which may be required, a particular
device is likely to have non-volatile storage constraints which
will limit the maximum number of entries. If an attempt is made to
create more rows than the device can support, an error code of
NO CREATION will be returned. SEQUENCE OF CdPrivateMibEnableKeyEntry .cableDataPrivate.1.1.1.2 |
cdPrivateMibEnableKeyEntryAn entry identifying a single key value used to re-enable the private
MIB once it has been disabled. CdPrivateMibEnableKeyEntry .cableDataPrivate.1.1.1.2.1 |
cdPvtMibEnableKeyIndexA unique value used to identify this key instance. Note that the
indices need not be sequential, although they must be positive.
Also note that a particular device may have non-volatile storage
constraints which limit the value of this object. If an attempt is
made to create a row which has an index that is not valid for the
particular device, an error code of NO CREATION will be returned. Integer32 .cableDataPrivate.1.1.1.2.1.1 |
cdPvtMibEnableKeyValueA value used to control re-enabling of the private MIB once it has
been disabled. If the private MIB is disabled, the only value which
may be successfully set to this object is its current value. If the
MIB is enabled, then this value may be set to any value in order to
configure the table. Note that there is no theoretical limit to the
size of this string, although a particular device is likely to have
non-volatile storage constraints which will limit the size of the
value. If an attempt is made to set this value to too large of a
string, an error code of WRONG LENGTH will be returned. Also note
that this value may contain hex values as well as ASCII printable
ones.rw OCTET STRING .cableDataPrivate.1.1.1.2.1.2 |
cdPvtMibEnableKeyStatusControls and reflects the status of rows in this table. Rows in this
table may be created by either the create-and-go or create-and-wait
paradigms. There is no restriction on changing values in a row of
this table while the row is active. Setting the value of this object
to active (either directly or indirectly via create-and-go) will cause
the row to be written to non-volatile storage. Changing the value of
cdPrivateEnableKeyValue while the row is active will also cause the
row to be written to non-volatile storage.rw RowStatus (SNMPv2-TC) .cableDataPrivate.1.1.1.2.1.3 |