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.
|
Imported Objects
| lldpExtensions, LldpPortNumber | LLDP-MIB |
| SnmpAdminString | SNMP-FRAMEWORK-MIB |
| MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
| MODULE-IDENTITY, OBJECT-TYPE, Integer32, NOTIFICATION-TYPE | SNMPv2-SMI |
| TEXTUAL-CONVENTION, TruthValue | SNMPv2-TC |
Type Definitions (10)
| Name | Base Type | Values/Constraints |
|---|---|---|
 LldpXdcbxAppProtos | range: 0..15 | |
| LldpXdcbxFeatureSubType | range: 0..255 | |
| LldpXdcbxFeatureType | priorityGroup(2), priorityFlowControl(3), applicationProtocol(4) | |
| LldpXdcbxPgBw | range: 0..100 | |
| LldpXdcbxPriority | range: 0..7 | |
| LldpXdcbxPriorityGroup | 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) | |
| LldpXdcbxSF | l2EtherType(0), socketNumber(1), reserved2(2), reserved3(3) | |
| LldpXdcbxTC | range: 0..7 | |
| LldpXdcbxTCPFC | range: 1..8 | |
| LldpXdcbxVersion | range: 0..255 |
Objects
  lldpXdcbxMIB  | .1.0.8802.1.1.2.1.5.6945 | |
| lldpXdcbxNotifications | .1.0.8802.1.1.2.1.5.6945.0 | |
| lldpXdcbxObjects | .1.0.8802.1.1.2.1.5.6945.1 | |
 lldpXdcbxPortTable | .1.0.8802.1.1.2.1.5.6945.1.1 | |
 lldpXdcbxPortEntry | .1.0.8802.1.1.2.1.5.6945.1.1.1 | |
 lldpXdcbxPortNumber | .1.0.8802.1.1.2.1.5.6945.1.1.1.1 | |
| lldpXdcbxPortEnable | .1.0.8802.1.1.2.1.5.6945.1.1.1.2 | |
| lldpXdcbxPortVersionOper | .1.0.8802.1.1.2.1.5.6945.1.1.1.3 | |
| lldpXdcbxPortVersionMax | .1.0.8802.1.1.2.1.5.6945.1.1.1.4 | |
| lldpXdcbxPortSeqNo | .1.0.8802.1.1.2.1.5.6945.1.1.1.5 | |
| lldpXdcbxPortAckNo | .1.0.8802.1.1.2.1.5.6945.1.1.1.6 | |
| lldpXdcbxFeatures | .1.0.8802.1.1.2.1.5.6945.2 | |
| lldpXdcbxFeatTable | .1.0.8802.1.1.2.1.5.6945.2.1 | |
| lldpXdcbxFeatEntry | .1.0.8802.1.1.2.1.5.6945.2.1.1 | |
| lldpXdcbxFeatType | .1.0.8802.1.1.2.1.5.6945.2.1.1.1 | |
| lldpXdcbxFeatSyncd | .1.0.8802.1.1.2.1.5.6945.2.1.1.10 | |
| lldpXdcbxFeatSeqNo | .1.0.8802.1.1.2.1.5.6945.2.1.1.11 | |
| lldpXdcbxFeatPeerWilling | .1.0.8802.1.1.2.1.5.6945.2.1.1.12 | |
| lldpXdcbxFeatLocalParameterChange | .1.0.8802.1.1.2.1.5.6945.2.1.1.13 | |
| lldpXdcbxFeatSubType | .1.0.8802.1.1.2.1.5.6945.2.1.1.2 | |
| lldpXdcbxFeatVersionOper | .1.0.8802.1.1.2.1.5.6945.2.1.1.3 | |
| lldpXdcbxFeatVersionMax | .1.0.8802.1.1.2.1.5.6945.2.1.1.4 | |
| lldpXdcbxFeatEnable | .1.0.8802.1.1.2.1.5.6945.2.1.1.5 | |
| lldpXdcbxFeatWilling | .1.0.8802.1.1.2.1.5.6945.2.1.1.6 | |
| lldpXdcbxFeatError | .1.0.8802.1.1.2.1.5.6945.2.1.1.7 | |
| lldpXdcbxFeatAdvertise | .1.0.8802.1.1.2.1.5.6945.2.1.1.8 | |
| lldpXdcbxFeatOperMode | .1.0.8802.1.1.2.1.5.6945.2.1.1.9 | |
| lldpXdcbxFeatPg | .1.0.8802.1.1.2.1.5.6945.2.2 | |
 lldpXdcbxFeatPgNumTCsSupported | .1.0.8802.1.1.2.1.5.6945.2.2.1 | |
| lldpXdcbxFeatPgPrioAllocTable | .1.0.8802.1.1.2.1.5.6945.2.2.2 | |
| lldpXdcbxFeatPgPrioAllocEntry | .1.0.8802.1.1.2.1.5.6945.2.2.2.1 | |
| lldpXdcbxFeatPgPrioAllocPrioId | .1.0.8802.1.1.2.1.5.6945.2.2.2.1.1 | |
| lldpXdcbxFeatPgPrioAllocPgIdDesired | .1.0.8802.1.1.2.1.5.6945.2.2.2.1.2 | |
| lldpXdcbxFeatPgPrioAllocPgIdOper | .1.0.8802.1.1.2.1.5.6945.2.2.2.1.3 | |
| lldpXdcbxFeatPgPrioAllocPgIdPeer | .1.0.8802.1.1.2.1.5.6945.2.2.2.1.4 | |
| lldpXdcbxFeatPgBwAllocTable | .1.0.8802.1.1.2.1.5.6945.2.2.3 | |
| lldpXdcbxFeatPgBwAllocEntry | .1.0.8802.1.1.2.1.5.6945.2.2.3.1 | |
| lldpXdcbxFeatPgBwAllocPgId | .1.0.8802.1.1.2.1.5.6945.2.2.3.1.1 | |
| lldpXdcbxFeatPgBwAllocBwDesired | .1.0.8802.1.1.2.1.5.6945.2.2.3.1.2 | |
| lldpXdcbxFeatPgBwAllocBwOper | .1.0.8802.1.1.2.1.5.6945.2.2.3.1.3 | |
| lldpXdcbxFeatPgBwAllocBwPeer | .1.0.8802.1.1.2.1.5.6945.2.2.3.1.4 | |
| lldpXdcbxFeatPfc | .1.0.8802.1.1.2.1.5.6945.2.3 | |
| lldpXdcbxFeatPfcNumTCPFCSupported | .1.0.8802.1.1.2.1.5.6945.2.3.1 | |
| lldpXdcbxFeatPfcTable | .1.0.8802.1.1.2.1.5.6945.2.3.2 | |
| lldpXdcbxFeatPfcEntry | .1.0.8802.1.1.2.1.5.6945.2.3.2.1 | |
| lldpXdcbxFeatPfcPriority | .1.0.8802.1.1.2.1.5.6945.2.3.2.1.1 | |
| lldpXdcbxFeatPfcEnableDesired | .1.0.8802.1.1.2.1.5.6945.2.3.2.1.2 | |
| lldpXdcbxFeatPfcEnableOper | .1.0.8802.1.1.2.1.5.6945.2.3.2.1.3 | |
| lldpXdcbxFeatPfcEnablePeer | .1.0.8802.1.1.2.1.5.6945.2.3.2.1.4 | |
| lldpXdcbxFeatAppProto | .1.0.8802.1.1.2.1.5.6945.2.4 | |
| lldpXdcbxFeatAppProtoTable | .1.0.8802.1.1.2.1.5.6945.2.4.1 | |
| lldpXdcbxFeatAppProtoEntry | .1.0.8802.1.1.2.1.5.6945.2.4.1.1 | |
| lldpXdcbxFeatAppProtoIndex | .1.0.8802.1.1.2.1.5.6945.2.4.1.1.1 | |
| lldpXdcbxFeatAppProtoSF | .1.0.8802.1.1.2.1.5.6945.2.4.1.1.2 | |
| lldpXdcbxFeatAppProtoOUI | .1.0.8802.1.1.2.1.5.6945.2.4.1.1.3 | |
| lldpXdcbxFeatAppProtoId | .1.0.8802.1.1.2.1.5.6945.2.4.1.1.4 | |
| lldpXdcbxFeatAppProtoPrioTable | .1.0.8802.1.1.2.1.5.6945.2.4.2 | |
| lldpXdcbxFeatAppProtoPrioEntry | .1.0.8802.1.1.2.1.5.6945.2.4.2.1 | |
| lldpXdcbxFeatAppProtoPriority | .1.0.8802.1.1.2.1.5.6945.2.4.2.1.1 | |
| lldpXdcbxFeatAppProtoEnableDesired | .1.0.8802.1.1.2.1.5.6945.2.4.2.1.2 | |
| lldpXdcbxFeatAppProtoEnableOper | .1.0.8802.1.1.2.1.5.6945.2.4.2.1.3 | |
| lldpXdcbxFeatAppProtoEnablePeer | .1.0.8802.1.1.2.1.5.6945.2.4.2.1.4 |
Notifications/Traps
| Name | OID | Description |
|---|---|---|
 lldpXdcbxMiscControlError | .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. |
| lldpXdcbxPeerConfigMismatch | .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. |
| lldpXdcbxMiscFeatureError | .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. |
| lldpXdcbxMultiplePeers | .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. |
| lldpXdcbxLldpTxDisabled | .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. |
| lldpXdcbxLldpRxDisabled | .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. |
| lldpXdcbxDupControlTlv | .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. |
| lldpXdcbxDupFeatureTlv | .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. |
| lldpXdcbxPeerNoFeat | .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). |
| lldpXdcbxPeerNoResp | .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. |