LLDP-EXT-DCBX-MIB
The LLDP Management Information Base extension module for
DCB Capability Exchage Protocol (DCBX).
In order to assure the uniqueness of the LLDP-MIB,
lldpXdcbxMIB is branched from lldpExtensions using OUI value
as the node. An OUI/'company_id' is a 24 bit globally unique
assigned number referenced by various standards.
- Source file
LLDP-EXT-DCBX-MIB- Last revised
- Identity
lldpXdcbxMIB- Base OID
1.0.8802.1.1.2.1.5.6945
Imported Objects
| LLDP-MIB | lldpExtensions LldpPortNumber |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | TEXTUAL-CONVENTION (no object page) TruthValue |
Net-SNMP examples using the rfc MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'LLDP-EXT-DCBX-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LLDP-EXT-DCBX-MIB::lldpXdcbxMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LLDP-EXT-DCBX-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LLDP-EXT-DCBX-MIB::lldpXdcbxMIB'
Objects (62)
Showing 62 of 62 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.0.8802.1.1.2.1.5.6945 |
||
.1.0.8802.1.1.2.1.5.6945.0 |
||
.1.0.8802.1.1.2.1.5.6945.1 |
||
.1.0.8802.1.1.2.1.5.6945.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.4 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.5 |
||
.1.0.8802.1.1.2.1.5.6945.1.1.1.6 |
||
.1.0.8802.1.1.2.1.5.6945.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.10 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.11 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.12 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.13 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.4 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.5 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.6 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.7 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.8 |
||
.1.0.8802.1.1.2.1.5.6945.2.1.1.9 |
||
.1.0.8802.1.1.2.1.5.6945.2.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.2.1.4 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.3.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.2.3.1.1 |
||
|
percentLldpXdcbxPgBw
|
.1.0.8802.1.1.2.1.5.6945.2.2.3.1.2 |
|
|
percentLldpXdcbxPgBw
|
.1.0.8802.1.1.2.1.5.6945.2.2.3.1.3 |
|
|
percentLldpXdcbxPgBw
|
.1.0.8802.1.1.2.1.5.6945.2.2.3.1.4 |
|
.1.0.8802.1.1.2.1.5.6945.2.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.3.2.1.4 |
||
.1.0.8802.1.1.2.1.5.6945.2.4 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.1.1.4 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2.1.1 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2.1.2 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2.1.3 |
||
.1.0.8802.1.1.2.1.5.6945.2.4.2.1.4 |
Dependencies (16) 5 direct · 11 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANA-ADDRESS-FAMILY-NUMBERS-MIBrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- LLDP-MIBrfc
- LLDP-EXT-DCBX-MIBrfcselected
Type Definitions (10)
| Integer32 |
range: 0..15 |
|
| Integer32 |
range: 0..255 |
|
| Enumeration |
priorityGroup(2)priorityFlowControl(3)applicationProtocol(4) |
|
| Integer32 |
range: 0..100 |
|
| Integer32 |
range: 0..7 |
|
| Enumeration |
priorityGroupId0(0)priorityGroupId1(1)priorityGroupId2(2)priorityGroupId3(3)priorityGroupId4(4)priorityGroupId5(5)priorityGroupId6(6)priorityGroupId7(7)reserved8(8)reserved9(9)reserved10(10)reserved11(11)reserved12(12)reserved13(13)reserved14(14)noBandwidthLimit(15) |
|
| Enumeration |
l2EtherType(0)socketNumber(1)reserved2(2)reserved3(3) |
|
| Integer32 |
range: 0..7 |
|
| Integer32 |
range: 1..8 |
|
| Integer32 |
range: 0..255 |
Notifications / Traps (10)
| Name | OID | Description |
|---|---|---|
.1.0.8802.1.1.2.1.5.6945.0.1 |
This trap is sent whenever an error occurs with DCBX control and there
is no other trap defined for the specific error condition. |
|
.1.0.8802.1.1.2.1.5.6945.0.10 |
This trap is sent when the configuration received from peer results
into partial or complete mismatch. |
|
.1.0.8802.1.1.2.1.5.6945.0.2 |
This trap is sent whenever lldpXdcbxFeatError is true and there is no
other trap defined for the specific error condition. |
|
.1.0.8802.1.1.2.1.5.6945.0.3 |
This trap is sent when multiple LLDP neighbors are detected on the
same port. DCBX is expected to operate over a point to point link. If multiple LLDP neighbors are detected, then DCBX behaves as if the peer's DCBX TLVs are not present until the multiple LLDP neighbor condition is no longer present. An LLDP neighbor is identified by its logical MAC Service Access Identifier (MSAP). The logical MSAP is a concatenation of the chassis ID and port ID values transmitted in the LLDPDU. |
|
.1.0.8802.1.1.2.1.5.6945.0.4 |
This trap is sent when the LLDP transmit has been disabled.
LLDP gives administrator control to enable/disable the protocol independently on the Rx side and Tx side. Since DCBX is an acknowledged protocol which uses LLDP, for the protocol to operate correctly both LLDP Rx and Tx must be enabled on the interface on which DCBX runs. The behavior of DCBX is as follows with respect to LLDP Rx/Tx admin state controls: - If either of Rx or Tx is in disable state, DCBX is disabled on the interface. Neither the control nor feature state machines should run. The LLDP PDU's that are generated from this interface do not have any DCBX TLVs. If the peer sends DCBX TLVs they should be ignored as far as the DCBX state machines are concerned. - When DCBX is currently running and LLDP TX is disabled, then according to the LLDP specification, a shutdown LLDPDU is sent. When the peer receives this PDU, DCBX is determined to be disabled on the peer. This is equivalent to DCBX TLV TTL expired in the Control State machine and Rx.Feature.present() = FALSE in the Feature state machine. If for some reason this frame is lost, then DCBX depends on standard rxInfoTTL expiry of the peer's LLDP TLV's. - When DCBX is currently running and LLDP Rx is disabled, then all DCBX TLV's including the control TLV should be withdrawn from the LLDP PDUs that the interface generates. The peer's behavior should be the same as discussed in the previous case. |
|
.1.0.8802.1.1.2.1.5.6945.0.5 |
This trap is sent when the LLDP receive has been disabled.
LLDP gives administrator control to enable/disable the protocol independently on the Rx side and Tx side. Since DCBX is an acknowledged protocol which uses LLDP, for the protocol to operate correctly both LLDP Rx and Tx must be enabled on the interface on which DCBX runs. The behavior of DCBX is as follows with respect to LLDP Rx/Tx admin state controls: - If either of Rx or Tx is in disable state, DCBX is disabled on the interface. Neither the control nor feature state machines should run. The LLDP PDU's that are generated from this interface do not have any DCBX TLVs. If the peer sends DCBX TLVs they should be ignored as far as the DCBX state machines are concerned. - When DCBX is currently running and LLDP TX is disabled, then according to the LLDP specification, a shutdown LLDPDU is sent. When the peer receives this PDU, DCBX is determined to be disabled on the peer. This is equivalent to DCBX TLV TTL expired in the Control State machine and Rx.Feature.present() = FALSE in the Feature state machine. If for some reason this frame is lost, then DCBX depends on standard rxInfoTTL expiry of the peer's LLDP TLV's. - When DCBX is currently running and LLDP Rx is disabled, then all DCBX TLV's including the control TLV should be withdrawn from the LLDP PDUs that the interface generates. The peer's behavior should be the same as discussed in the previous case. |
|
.1.0.8802.1.1.2.1.5.6945.0.6 |
This trap is sent when a duplicate control Sub-TLV is detected.
The DCBX Control Sub-TLV and the set of Feature Sub-TLVs can be arranged in any order within the DCBX TLV. Duplicate Sub-TLV's (such as more than one Sub-TLV for the same feature) are not allowed. A duplicate DCBX Control TLV causes an error for all features. |
|
.1.0.8802.1.1.2.1.5.6945.0.7 |
This trap is sent when a duplicate feature Sub-TLV is detected.
The DCBX Control Sub-TLV and the set of Feature Sub-TLVs can be arranged in any order within the DCBX TLV. Duplicate Sub-TLV's (such as more than one Sub-TLV for the same feature) are not allowed. Duplicates are handled as a configuration error for the feature. |
|
.1.0.8802.1.1.2.1.5.6945.0.8 |
This trap is sent when a feature is not supported on by a peer.
This condition can occur when a device does not support a feature (not really an error) or if the feature's Advertise flag is off (possible configuration error). |
|
.1.0.8802.1.1.2.1.5.6945.0.9 |
This trap is sent when the peer has stopped responding as evidenced by
an LLDP timeout event. |