BRCM-CABLEDATA-PRIVATE-MIB: View SNMP OID List / Download MIB

VENDOR: BROADCOM LIMITED


 Home MIB: BRCM-CABLEDATA-PRIVATE-MIB
Download as:   
SNMPv2-SMI, SNMPv2-TC, BRCM-CABLEDATA-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 cableDataPrivateMIB 1.3.6.1.4.1.4413.2.99.1
     cableDataPrivateMIBObjects 1.3.6.1.4.1.4413.2.99.1.1
         cableDataPrivateBase 1.3.6.1.4.1.4413.2.99.1.1.1
             cdPrivateMibEnable 1.3.6.1.4.1.4413.2.99.1.1.1.1
Setting 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).
             cdPrivateMibEnableKeyTable 1.3.6.1.4.1.4413.2.99.1.1.1.2
A 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.
                 cdPrivateMibEnableKeyEntry 1.3.6.1.4.1.4413.2.99.1.1.1.2.1
An entry identifying a single key value used to re-enable the private MIB once it has been disabled.
                     cdPvtMibEnableKeyIndex 1.3.6.1.4.1.4413.2.99.1.1.1.2.1.1
A 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.
                     cdPvtMibEnableKeyValue 1.3.6.1.4.1.4413.2.99.1.1.1.2.1.2
A 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.
                     cdPvtMibEnableKeyStatus 1.3.6.1.4.1.4413.2.99.1.1.1.2.1.3
Controls 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.