CISCO-BRIDGE-DOMAIN-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-BRIDGE-DOMAIN-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
 ciscoBridgeDomainMIB 1.3.6.1.4.1.9.9.642
A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternative to 802.1D bridge-groups and to 802.1Q VLAN bridging. Bridge domain is the service specification, and specifies the broadcast domain number on which this frame of this particular service instance must be made available on. The physical and virtual interfaces that can comprise a bridge domain are heterogeneous in nature comprising Ethernet service instances, WAN Virtual Circuit for ATM or Frame Relay and VFIs. However, the frame encapsulations for all interface types are essentially Ethernet. Without bridge-domains, VLANs would have to be globally unique per device and one would only be restricted to the theoretical maximum of 4095 VLANs for single tagged traffic. However with the introduction of bridge-domains, one can associate a service instance with a bridge-domain and all service instances in the same bridge-domain form a broadcast domain. Bridge-domain ID determines the broadcast domain and the VLAN id is merely used to match and map traffic. With bridge domain feature configured VLAN IDs would be unique per interface only and not globally. Thus bridge domains make VLAN ids have only local significance per port Differences between Bridge Domains and 802.1AD Bridges: ======================================================= 1. Scope of the VLAN technology which uses 802.1 AD is global to the box. But in case of Bridge domain, the scope of vlan is local to interface 2. Switchport 802.1AD restricts the number of broadcast domain on a box to 4095. However, with Bridge domains, we can have up to 16k broadcast domain. 3. Under a single Bridge domain service instance, there can be flexible service mapping criterion.(i.e match based on outer vlan, outer cos, inner vlan, inner cos and payload ethertype). Whereas in case of switch port 802.1AD/dot1q this is not supported. Similarities between Bridge Domains and 802.1AD Bridges: ======================================================= 1. Both use the same MAC address lookup for forwarding. 2. Both work with protocols like STP, DTP etc. 3. Both of them classify 'ports' in a system into Bridges/Bridge Domains. Ethernet service instance is the instantiation of an Ethernet virtual circuit on a given port on a given router. In other words, an Ethernet service instance is an object that holds information about the layer 2 service that is being offered on a given port of a given router as part of a given Ethernet virtual circuit. Bridge domains feature is currently supported on ethernet service instances only and can be later extented to other interfaces like ATM and Frame Relay. This MIB helps the network management personnel to find out the details of various broadcast domains configured in the network. Definition of terms and acronyms: ATM: Asynchronous Transfer mode BD: Bridge Domain C-mac: Customer MAC EVC: Ethernet Virtual Circuit FR: Frame Relay SH: Split Horizon VFI: Virtual Forwarding Instance VLAN: Virtual Local Area Network WAN: Wide Area Network
         ciscoBdMIBNotifications 1.3.6.1.4.1.9.9.642.0
             ciscoBdNotificationPrefix 1.3.6.1.4.1.9.9.642.0.0
         ciscoBdMIBObjects 1.3.6.1.4.1.9.9.642.1
             cbdSystemInfo 1.3.6.1.4.1.9.9.642.1.1
                 cbdMembersConfigured 1.3.6.1.4.1.9.9.642.1.1.1 unsigned32 read-only
This object indicates the number of bridge domain members configured on this bridge domain.
             cbdMemberInfo 1.3.6.1.4.1.9.9.642.1.2
                 cbdMemberInfoTable 1.3.6.1.4.1.9.9.642.1.2.1 no-access
This table provides the bridge domain member attributes of the members currently configured for each bridge domain.
                     cbdMemberInfoEntry 1.3.6.1.4.1.9.9.642.1.2.1.1 no-access
A conceptual row in cbdMemberInfoTable. This is indexed by ifIndex and cbdSIIndex. Each row is created when a bridge domain member is configured under a service instance.
                         cbdSIIndex 1.3.6.1.4.1.9.9.642.1.2.1.1.1 unsigned32 no-access
This object indicates an arbitary index that uniquely identifies the Service Instance to which this bridge domain member belongs to.
                         cbdMemberType 1.3.6.1.4.1.9.9.642.1.2.1.1.2 cbdtype read-only
This object identifies the type of the bridge domain member like ATM VC, Frame Relay VC, or Ethernet service.
                         cbdMemberOperState 1.3.6.1.4.1.9.9.642.1.2.1.1.3 integer read-only
This object indicates the operational state of the bridge domain Member. Operational state of the Bridge domain member is same as the operational state of the underlying service instance. Bridge domain members are configured under service instances and multiple service instances can be attached to a single physical interface defining various kinds of services. Bridge domain members have many to one relationship with interface Indexes. When ifOperStatus of the underlying interface is down, the state of cbdMemberOperState should be down. When ifOperStatus of the underlying interface is up, cbdMemberOperState can be either up or down based on the state of underlying service instance. 'unknown': the bridge domain member is an unknown state. 'up': the bridge domain member is fully operational and able to bridge the traffic. This means that both the physical interface and the underlying service instance are administratively up. 'down': the Bridge Domain member is down and not capable of bridging. This state means either the underlying service instance is down or the interface is down. Enumeration: 'down': 3, 'unknown': 1, 'up': 2.
                         cbdMemberAdminState 1.3.6.1.4.1.9.9.642.1.2.1.1.4 integer read-only
This object indicates the administrative state of the bridge domain Member. Admin state of the Bridge domain member is same as the admin state of the underlying service instance. Bridge domain members are configured under service instances and multiple service instances can be attached to a single physical interface defining various kinds of services. Bridge Domain members have many to one relationship with interface Indexes. When ifAdminStatus of the unerlying interface is down the state of cbdMemberAdminState should be down. When ifOperStatus of the underlying interface is up cbdMemberAdminState can be either up or down based on the state of underlying service instance. 'unknown': the bridge domain member is in unknown administrative state. 'up': the Bridge Domain member is administratively up. This means that both the physical interface and the underlying service instance are administratively up. 'admindown': the Bridge Domain member is down as it is administratively configured to be down and is not capable of bridging. This means that either the underlying service instance is configured as administratively down or the physical interface is configured as administratively down. Enumeration: 'down': 3, 'unknown': 1, 'up': 2.
                         cbdMemberSplitHorizon 1.3.6.1.4.1.9.9.642.1.2.1.1.5 truthvalue read-only
This object indicates whether split horizon is configured on this bridge domain member.
                         cbdMemberSplitHorizonNum 1.3.6.1.4.1.9.9.642.1.2.1.1.6 unsigned32 read-only
This object indicates the split horizon number if configured on the bridge domain member. Split horizon is used to avoid sending traffic between interfaces. Frames are not forwarded to the members belonging to the same split horizon group.
                         cbdMemberStorageType 1.3.6.1.4.1.9.9.642.1.2.1.1.7 storagetype read-only
This object specifies the storage type of this conceptual row. This object can only have a value 'nonVolatile'. Other values are not applicable for this conceptual row and are not supported.
                         cbdMemberStatus 1.3.6.1.4.1.9.9.642.1.2.1.1.8 rowstatus read-only
This object enables the SNMP agent to create, modify, and delete rows in the cbdMemberInfoTable.
                         cbdMembercMac 1.3.6.1.4.1.9.9.642.1.2.1.1.9 truthvalue read-only
This object indicates if cmac is configured on this bridge domain member. Cmac denotes if this bridge domain is configured as a customer domain.
         ciscoBdMIBConformance 1.3.6.1.4.1.9.9.642.2
             ciscoBdMIBCompliances 1.3.6.1.4.1.9.9.642.2.1
                 ciscoBdMIBComplianceRev1 1.3.6.1.4.1.9.9.642.2.1.1
The compliance statement for entities which implement the CISCO-BRIDGE-DOMAIN-MIB.
             ciscoBdMIBGroups 1.3.6.1.4.1.9.9.642.2.2
                 cbdSystemInfoGroup 1.3.6.1.4.1.9.9.642.2.2.1
This group contain information about bridge domain.
                 cbdMemberInfoGroup 1.3.6.1.4.1.9.9.642.2.2.2
This group contain information related to bridge domain members.