CISCO-BCP-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-BCP-MIB
Download as:   

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
 ciscoBcpMIB 1.3.6.1.4.1.9.9.275
This MIB module describes the Managed Objects for of Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474.
         ciscoBcpMIBObjects 1.3.6.1.4.1.9.9.275.1
             bcpOperTable 1.3.6.1.4.1.9.9.275.1.1 no-access
Table containing the status of the local BCP entity that is related to the operation of Bridging Control Protocol.
                 bcpOperEntry 1.3.6.1.4.1.9.9.275.1.1.1 no-access
Operational status information for a particular BCP link. For all entries in ifTable with ifType ppp(23), there will be an entry in this table.
                     bcpOperStatus 1.3.6.1.4.1.9.9.275.1.1.1.1 integer read-only
The operational status of the Bridge Control Protocol. The possible values are : open(1) - the BCP link is up and both ends are configured in the compatible manner. closed(2) - the BCP link is down and neither ends are configured. listening(3) - the local BCP entity is configured and the remote end is not configured compatibly. Enumeration: 'open': 1, 'listening': 3, 'closed': 2.
             bcpConfigTable 1.3.6.1.4.1.9.9.275.1.2 no-access
Table containing the configuration information for the local BCP entity that is related to the operation of Bridging over the PPP link.
                 bcpConfigEntry 1.3.6.1.4.1.9.9.275.1.2.1 no-access
Bridging Configuration information for a particular BCP link. For all entries in ifTable with ifType ppp(23), there will be an entry in this table.
                     bcpConfigBridgeIdControl 1.3.6.1.4.1.9.9.275.1.2.1.1 integer read-write
The Bridge-Identification configuration option is designed for use when the line is an interface between half bridges connecting virtual or physical LAN segments. When enabled the local BCP entity initiates a Bridge Identification Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigBridgeId 1.3.6.1.4.1.9.9.275.1.2.1.2 unsigned32 read-write
The bridge number of the local BCP entity. This value is meaningful only when the local BCP entity has negotiated the BridgeId Configuration option, which means the value of bcpConfigBridgeIdControl is enabled(1). The two half bridges must agree on the bridge number.
                     bcpConfigLineIdControl 1.3.6.1.4.1.9.9.275.1.2.1.3 integer read-write
The Line-Identification configuration option is designed for use when the line is assigned a LAN segment number. When enabled the local BCP entity initiates a Line Identification Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigLineId 1.3.6.1.4.1.9.9.275.1.2.1.4 unsigned32 read-write
The LAN segment number of the local BCP entity. This value is meaningful only when the local BCP entity negotiated the LineId Configuration option, which means the value of bcpConfigLineIdControl is enabled(1). The two half bridges must agree on the LAN segment number.
                     bcpConfigMacSupport 1.3.6.1.4.1.9.9.275.1.2.1.5 integer read-write
The Mac-Support configuration option is provided to permit implementations to indicate the sort of traffic they are prepared to receive. When enabled the local BCP entity initiates a Mac-Support Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigMacType 1.3.6.1.4.1.9.9.275.1.2.1.6 integer read-write
The MAC type that this local BCP entity is prepared to receive and service. This value is meaningful only when the local BCP entity has negotiated the MAC-Support Configuration option, which means the value of bcpConfigMacSupport is enabled(1). These values definition are specified in the most recent RFC1700. Enumeration: 'ieee802dot3Canonical': 1, 'ieee802dot5Canonical': 11, 'fddiCanonical': 12, 'ieee802dot4Canonical': 2, 'ieee802dot5NonCanonical': 3, 'fddiNonCanonical': 4.
                     bcpConfigTinygram 1.3.6.1.4.1.9.9.275.1.2.1.7 integer read-write
The Tinygram-Compression configuration option permits implementations to indicate support for Tinygram Compression. When enabled the local BCP Entity initiates a Tinygram-Compression Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigMacAddressControl 1.3.6.1.4.1.9.9.275.1.2.1.8 integer read-write
The Mac-Address configuration option enables the implementations to announce its MAC address or have one assigned. When enabled the local BCP Entity initiates a Mac-Address Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigMacAddress 1.3.6.1.4.1.9.9.275.1.2.1.9 displaystring read-write
This value is meaningful only when the local BCP entity has negotiated the MAC-Address configuration option, which means the value of bcpConfigMacAddressControl is enabled(1). If it is non-zero format, the local BCP get its MAC address announced. It is represented in IEEE 802.1 Canonical format. If it is in zero format, i.e. 00-00-00-00-00-00 then the implementation of the system wishes to have a MAC address assigned.
                     bcpConfigSpanTreeControl 1.3.6.1.4.1.9.9.275.1.2.1.10 integer read-write
The Spanning-Tree-Protocol configuration option enables a bridge to remain compatible with older implementations of BCP. When enabled the local BCP Entity initiates a Spanning-Tree-Protocol Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigSpanTree 1.3.6.1.4.1.9.9.275.1.2.1.11 integer read-write
The desired spanning tree protocol of the local BCP entity. The listing values of the Spanning- Tree Protocol are specified in the most recent RFC1700. This value is meaningful only when the local BCP entity has negotiated the Spanning-Tree-Protocol configuration option, which means the value of bcpConfigSpanTreeControl is enabled(1). Enumeration: 'ieee802dot1GExtended': 2, 'decLanBridge100': 4, 'ibmSourceRoute': 3, 'null': 0, 'ieee802dot1D': 1.
                     bcpConfigIeee802dot1qTagged 1.3.6.1.4.1.9.9.275.1.2.1.12 integer read-write
The IEEE-802-Tagged-Frame configuration option permits the implementation to support for IEEE 802.1q Tagged Frame. When enabled the local BCP Entity initiates a IEEE-802-Tagged-Frame Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigMgmtInline 1.3.6.1.4.1.9.9.275.1.2.1.13 integer read-write
The Management-Inline configuration option indicates that the system is willing to receive any IEEE-defined inter-bridge protocols. When enabled if the local BCP Entity initiates a Management-Inline Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
                     bcpConfigBCPacketIndicator 1.3.6.1.4.1.9.9.275.1.2.1.14 integer read-write
The Bridge Control Packet Indicator configuration option permits the implementation to indicate support for Bridge Control Packet Indicator. When enabled the local BCP Entity initiates a Bridge Control Packet Indicator Option negotiation. Enumeration: 'disabled': 2, 'enabled': 1.
         cBcpMIBConformance 1.3.6.1.4.1.9.9.275.3
             cBcpMIBCompliances 1.3.6.1.4.1.9.9.275.3.1
                 cBcpMIBCompliance 1.3.6.1.4.1.9.9.275.3.1.1
The compliance statement for entities which implement this Cisco BCP MIB.
             cBcpMIBGroups 1.3.6.1.4.1.9.9.275.3.2
                 cBcpMIBGroup 1.3.6.1.4.1.9.9.275.3.2.1
A collection of objects providing the configuration and operating status of the BCP entity.