MIBs Depot

CISCO-BCP-MIB

Registered at
1.3.6.1.4.1.9.9.275
Last updated
2004-08-31 00:00
Organization
Cisco Systems, Inc.
Revisions
2004-08-31 00:00, 2002-08-02 00:00
Namespace
cisco
Source file
CISCO-BCP-MIB
Digest
sha256:403854339e425cdc3e66ceb979b4bdaf3db89fc9a45d9c6a7396f10eee01c31c

Description

This MIB module describes the Managed Objects for of Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474.

Contact

Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: osm-wan-snmp@cisco.com

Imports

FromSymbols
CISCO-SMIciscoMgmt
IF-MIBifIndex
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

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

Objects

NameOIDSyntaxAccessStatus
ciscoBcpMIBObjects
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.275.1
bcpOperTable
OBJECT-TYPE
Table containing the status of the local BCP entity that is related to the operation of Bridging Control Protocol.
1.3.6.1.4.1.9.9.275.1.1not-accessiblecurrent
bcpOperEntry
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.1.1not-accessiblecurrent
bcpOperStatus
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.1.1.1INTEGER {open(1), closed(2), listening(3)}read-onlycurrent
bcpConfigTable
OBJECT-TYPE
Table containing the configuration information for the local BCP entity that is related to the operation of Bridging over the PPP link.
1.3.6.1.4.1.9.9.275.1.2not-accessiblecurrent
bcpConfigEntry
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1not-accessiblecurrent
bcpConfigBridgeIdControl
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.1INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigBridgeId
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.2Unsigned32 (0..15)read-writecurrent
bcpConfigLineIdControl
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.3INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigLineId
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.4Unsigned32 (0..4095)read-writecurrent
bcpConfigMacSupport
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.5INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigMacType
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.6INTEGER {ieee802dot3Canonical(1), ieee802dot4Canonical(2), ieee802dot5NonCanonical(3), fddiNonCanonical(4), ieee802dot5Canonical(11), fddiCanonical(12)}read-writecurrent
bcpConfigTinygram
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.7INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigMacAddressControl
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.8INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigMacAddress
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.9DisplayString (SIZE(1..20))read-writecurrent
bcpConfigSpanTreeControl
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.10INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigSpanTree
OBJECT-TYPE
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).
1.3.6.1.4.1.9.9.275.1.2.1.11INTEGER {null(0), ieee802dot1D(1), ieee802dot1GExtended(2), ibmSourceRoute(3), decLanBridge100(4)}read-writecurrent
bcpConfigIeee802dot1qTagged
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.12INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigMgmtInline
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.13INTEGER {enabled(1), disabled(2)}read-writecurrent
bcpConfigBCPacketIndicator
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.275.1.2.1.14INTEGER {enabled(1), disabled(2)}read-writecurrent
cBcpMIBConformance
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.275.3
cBcpMIBCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.275.3.1
cBcpMIBGroups
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.275.3.2

Conformance

NameOIDStatus
cBcpMIBCompliance
MODULE-COMPLIANCE
The compliance statement for entities which implement this Cisco BCP MIB.
1.3.6.1.4.1.9.9.275.3.1.1current
cBcpMIBGroup
OBJECT-GROUP
A collection of objects providing the configuration and operating status of the BCP entity.
1.3.6.1.4.1.9.9.275.3.2.1current