CISCO-BCP-MIB

File: CISCO-BCP-MIB.mib (18352 bytes)

Imported modules

SNMPv2-SMI IF-MIB SNMPv2-TC
CISCO-SMI SNMPv2-CONF

Imported symbols

MODULE-IDENTITY OBJECT-TYPE Unsigned32
ifIndex DisplayString ciscoMgmt
MODULE-COMPLIANCE OBJECT-GROUP

Defined Types

BcpOperEntry  
SEQUENCE    
  bcpOperStatus INTEGER

BcpConfigEntry  
SEQUENCE    
  bcpConfigBridgeIdControl INTEGER
  bcpConfigBridgeId Unsigned32
  bcpConfigLineIdControl INTEGER
  bcpConfigLineId Unsigned32
  bcpConfigMacSupport INTEGER
  bcpConfigMacType INTEGER
  bcpConfigTinygram INTEGER
  bcpConfigMacAddressControl INTEGER
  bcpConfigMacAddress DisplayString
  bcpConfigSpanTreeControl INTEGER
  bcpConfigSpanTree INTEGER
  bcpConfigIeee802dot1qTagged INTEGER
  bcpConfigMgmtInline INTEGER
  bcpConfigBCPacketIndicator INTEGER

Defined Values

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.
MODULE-IDENTITY    

ciscoBcpMIBObjects 1.3.6.1.4.1.9.9.275.1
OBJECT IDENTIFIER    

bcpOperTable 1.3.6.1.4.1.9.9.275.1.1
Table containing the status of the local BCP entity that is related to the operation of Bridging Control Protocol.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    BcpOperEntry

bcpOperEntry 1.3.6.1.4.1.9.9.275.1.1.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  BcpOperEntry  

bcpOperStatus 1.3.6.1.4.1.9.9.275.1.1.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER open(1), closed(2), listening(3)  

bcpConfigTable 1.3.6.1.4.1.9.9.275.1.2
Table containing the configuration information for the local BCP entity that is related to the operation of Bridging over the PPP link.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    BcpConfigEntry

bcpConfigEntry 1.3.6.1.4.1.9.9.275.1.2.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  BcpConfigEntry  

bcpConfigBridgeIdControl 1.3.6.1.4.1.9.9.275.1.2.1.1
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigBridgeId 1.3.6.1.4.1.9.9.275.1.2.1.2
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.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32 0..15  

bcpConfigLineIdControl 1.3.6.1.4.1.9.9.275.1.2.1.3
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigLineId 1.3.6.1.4.1.9.9.275.1.2.1.4
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.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32 0..4095  

bcpConfigMacSupport 1.3.6.1.4.1.9.9.275.1.2.1.5
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigMacType 1.3.6.1.4.1.9.9.275.1.2.1.6
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER ieee802dot3Canonical(1), ieee802dot4Canonical(2), ieee802dot5NonCanonical(3), fddiNonCanonical(4), ieee802dot5Canonical(11), fddiCanonical(12)  

bcpConfigTinygram 1.3.6.1.4.1.9.9.275.1.2.1.7
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigMacAddressControl 1.3.6.1.4.1.9.9.275.1.2.1.8
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigMacAddress 1.3.6.1.4.1.9.9.275.1.2.1.9
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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString Size(1..20)  

bcpConfigSpanTreeControl 1.3.6.1.4.1.9.9.275.1.2.1.10
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigSpanTree 1.3.6.1.4.1.9.9.275.1.2.1.11
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).
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER null(0), ieee802dot1D(1), ieee802dot1GExtended(2), ibmSourceRoute(3), decLanBridge100(4)  

bcpConfigIeee802dot1qTagged 1.3.6.1.4.1.9.9.275.1.2.1.12
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigMgmtInline 1.3.6.1.4.1.9.9.275.1.2.1.13
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

bcpConfigBCPacketIndicator 1.3.6.1.4.1.9.9.275.1.2.1.14
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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

cBcpMIBConformance 1.3.6.1.4.1.9.9.275.3
OBJECT IDENTIFIER    

cBcpMIBCompliances 1.3.6.1.4.1.9.9.275.3.1
OBJECT IDENTIFIER    

cBcpMIBGroups 1.3.6.1.4.1.9.9.275.3.2
OBJECT IDENTIFIER    

cBcpMIBCompliance 1.3.6.1.4.1.9.9.275.3.1.1
The compliance statement for entities which implement this Cisco BCP MIB.
Status: current Access: read-write
MODULE-COMPLIANCE    

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.
Status: current Access: read-write
OBJECT-GROUP