The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
This document describes the attributes and tables of the CISCO-BRIDGE-DOMAIN-MIB, the supported operations, and related CLI commands.
A bridge domain is a means for defining an Ethernet broadcast domain on a bridging device and an alternative to 802.1D bridge groups and to 802.1Q VLAN bridging. Members of a bridge domain learn addresses and participate in Spanning-Tree Protocol (STP) and operations, administration, and maintenance (OAM) protocols. The purpose of a bridge domain MIB is to provide a Simple Network Management Protocol (SNMP) network management interface for a configured bridge domain. A bridge domain MIB also helps network management personnel learn the details of various broadcast domains configured in a network.
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
SNMP contexts must be configured before you can poll the CISCO-BRIDGE-DOMAIN-MIB.
The CISCO-BRIDGE-DOMAIN-MIB does not support notifications in Cisco IOS Release 12.2(50)SY.
Customer bridge domains (C-MACs) are not supported in Cisco IOS Release 12.2(50)SY.
The CISCO-BRIDGE-DOMAIN-MIB is delivered as an SNMP MIB and follows the general MIB architecture for the Cisco IOS software. The CISCO-BRIDGE-DOMAIN-MIB contains objects to manage multiple instances of SNMP context support for bridge domains and can be used to learn the details of various broadcast domains configured in the network.
The CISCO-BRIDGE-DOMAIN-MIB has one attribute object and one table object. Bridge domain attributes are managed using the SNMP context-aware infrastructure. Every configured bridge domain is related to an SNMP context so if you know the context, you can obtain the attributes.
The cbdMembersConfigured attribute is the only attribute defined. This attribute denotes the number of members configured on a bridge domain, and the variable used to populate the attribute is called “numb_of_bd_members.”
The cbdMembersConfigured attribute is read-only (Get operations are allowed). Set operations are not supported because bridge domain attributes are related to current bridge domain configurations on the system.
The cbdMemberInfo table is the only table defined. This table contains the bridge-domain attributes that correspond to the members configured for each bridge domain. Each row in the table is a unique entry for each interface that belongs to a specific bridge domain and a specific service.
All the objects in the cbdMemberInfoTable table are read-only. Set operations are not supported in Cisco IOS Release 12.2(50)SY. This table is indexed by ifIndex and cbdSIIndex.
The following table describes each object.
Perform this task to configure a bridge domain and a related SNMP context, which the CISCO-BRIDGE-DOMAIN-MIB can be used to manage.
1.
enable
2.
configure
terminal
3.
bridge-domain
bridge-id
4.
snmp
context
context-name
5.
end
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable
Example: Router> enable |
Enables privileged EXEC mode. |
| Step 2 |
configure
terminal
Example: Router# configure terminal |
Enters global configuration mode. |
| Step 3 |
bridge-domain
bridge-id
Example: Router(config)# bridge-domain 5 |
Configures components on bridge domain 5 and enters the bridge domain configuration mode. |
| Step 4 |
snmp
context
context-name
Example: Router(config-bdomain)# snmp context bd5 |
Creates an SNMP context for bridge domain 5. |
| Step 5 |
end
Example: Router(config-bdomain)# end |
Exits bridge domain configuration mode and returs to privleged EXEC mode. |
The following example shows how two bridge domains and their corresponding SNMP contexts are configured.
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# bridge-domain 2 Router(config-bdomain)# snmp context bd2 Router(config-bdomain)# bridge-domain 3 Router(config-bdomain)# snmp context bd3 Router(config-bdomain)# end
Contexts must be configured before you can poll the CISCO-BRIDGE-DOMAIN-MIB. The following sample output of the show snmp context mapping command shows that an SNMP context is configured for each of two bridge domains. This output reflects the configuration in the previous example, “Bridge Domain and SNMP Context Configurations.”
Router# show snmp context mapping Context: bd2 VRF Name: BD Index: 2 Context: bd3 VRF Name: BD Index: 3
|
Related Topic |
Document Title |
|---|---|
|
Ethernet CFM |
Configuring Ethernet Connectivity Fault Management in a Service Provider Network |
|
IEEE 802.3ah |
IEEE 802.3ah Ethernet in the First Mile |
|
ITU-T Y.1731 fault management functions |
Configuring ITU-T Y.1731 Fault Management Functions |
|
Delivering and filtering syslog messages |
Reliable Delivery and Filtering for Syslog |
|
Cisco IOS commands: master list of commands with complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
|
|
Cisco IOS Carrier Ethernet commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco IOS Carrier Ethernet Command Reference |
|
Standard |
Title |
|---|---|
|
IEEE P802.1ag/D1.0 |
Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks - Amendment 5: Connectivity Fault Management |
|
IETF VPLS OAM |
L2VPN OAM Requirements and Framework |
|
ITU-T |
ITU-T Y.1731 OAM Mechanisms for Ethernet-Based Networks |
|
MIB |
MIBs Link |
|---|---|
|
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
|
RFC |
Title |
|---|---|
|
RFC 3164 |
The BSD syslog Protocol |
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Bridge Domain MIB |
15.0(1)S |
The CISCO-BRIDGE-DOMAIN-MIB is delivered as an SNMP MIB and follows the general MIB architecture for Cisco IOS software. This MIB contains objects to manage multiple instances of SNMP context support for bridge domains and can be used to learn the details of various broadcast domains configured in the network. The following commands were introduced or modified: show snmp context mapping, snmp context. |