LLDP-EXT-DCBX-MIB

All MIBs › LLDP-EXT-DCBX-MIB

Organization: IEEE ??? Working Group

Last Updated: 2008-11-20

Category: Protocol: LLDP, Standard: IEEE 802

Description: IEEE LLDP extension MIB for Data Center Bridging Exchange (DCBX) protocol, enabling negotiation of DCB features like PFC and ETS via LLDP.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is LLDP-EXT-DCBX-MIB?

LLDP-EXT-DCBX-MIB is a vendor-neutral IEEE/industry-standard LLDP extension MIB implementing the Data Center Bridging Exchange Protocol (DCBX), which lets adjacent switches negotiate Data Center Bridging features such as Priority Flow Control (PFC) and Enhanced Transmission Selection (ETS) over LLDP. Its data covers per-port DCBX protocol state (enable status, operational and maximum protocol version, sequence and acknowledgment numbers) along with per-feature negotiation records (feature type and subtype). It reveals the software/protocol health of DCB negotiation: lldpXdcbxPortEnable and lldpXdcbxPortVersionOper confirm DCBX is running and which version is active on a port, while a growing gap between lldpXdcbxPortSeqNo and lldpXdcbxPortAckNo lets an operator detect a stalled or failing DCBX handshake between two data-center switches, directly relevant to diagnosing lossless Ethernet or FCoE fabric problems. It extends the IEEE 802.1AB LLDP-MIB framework (lldpExtensions branch), and the features it negotiates (PFC, ETS) tie into the IEEE 802.1Qbb/802.1Qaz standards. It is deployed on converged data-center Ethernet switches and NICs supporting FCoE or lossless Ethernet fabrics, regardless of vendor. Engineers implementing or auditing this functionality typically reference the LLDP-EXT-DCBX-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in LLDP-EXT-DCBX-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
data-center Ethernet switches/NICs supporting Data Center Bridging (DCB/FCoE)

Monitoring Examples

An operator polls lldpXdcbxPortTable/lldpXdcbxPortEntry (indexed by lldpXdcbxPortNumber) to check lldpXdcbxPortEnable and compare lldpXdcbxPortVersionOper against lldpXdcbxPortVersionMax, confirming DCBX is active and running the expected protocol version on an inter-switch link, while a growing gap between lldpXdcbxPortSeqNo and lldpXdcbxPortAckNo signals a stuck DCBX negotiation. lldpXdcbxFeatTable/lldpXdcbxFeatEntry (lldpXdcbxFeatType, lldpXdcbxFeatSubType) would be checked to confirm PFC or ETS was successfully negotiated between two ports before enabling a lossless FCoE fabric over that link.

What Can Be Monitored

DCBX enable status per port
DCBX operational/max protocol version
DCBX handshake sequence/ack numbers
negotiated DCB feature type (PFC, ETS)

Imported Objects

From LLDP-MIB

LldpPortNumber
lldpExtensions	OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
lldpXdcbxMIB	1.0.8802.1.1.2.1.5.6945			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.
lldpXdcbxNotifications	1.0.8802.1.1.2.1.5.6945.0
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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).
NTF 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.
NTF 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.
lldpXdcbxObjects	1.0.8802.1.1.2.1.5.6945.1
lldpXdcbxPortTable	1.0.8802.1.1.2.1.5.6945.1.1		not-accessible	A list of all ports capable of supporting DCBX.
lldpXdcbxPortEntry	1.0.8802.1.1.2.1.5.6945.1.1.1		not-accessible	An entry containing DCBX control parameters for a particular port.
LLD lldpXdcbxPortNumber	1.0.8802.1.1.2.1.5.6945.1.1.1.1	LldpPortNumber	read-only	Each port contained in the chassis (that is known to the LLDP agent) is uniquely identified by a port number. A port number has no mandatory relationship to an InterfaceIndex object (of the interfaces MIB, IETF RFC 2863). If the LLDP agent is a IEEE 802.1D, IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the dot1dBasePort object (defined in IETF RFC 1493) associated corresponding bridge port. If the system hosting LLDP agent is not an IEEE 802.1D or an IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the corresponding interface's InterfaceIndex object. Port numbers should be in the range of 1 and 4096 since a particular port is also represented by the corresponding port number bit in LldpPortList.
T/F lldpXdcbxPortEnable	1.0.8802.1.1.2.1.5.6945.1.1.1.2	TruthValue	read-write	A device capable of any DCB feature must have DCBX enabled by default with an option for DCBX to be administratively disabled.
LLD lldpXdcbxPortVersionOper	1.0.8802.1.1.2.1.5.6945.1.1.1.3	LldpXdcbxVersion	read-only	Operating version of the DCBX protocol. The system adjusts as needed to operate at the highest version supported by both link partners.
LLD lldpXdcbxPortVersionMax	1.0.8802.1.1.2.1.5.6945.1.1.1.4	LldpXdcbxVersion	read-only	Highest DCBX protocol version supported by the system. Version numbers start at zero. The DCBX protocol must be backward compatible with all previous versions.
I32 lldpXdcbxPortSeqNo	1.0.8802.1.1.2.1.5.6945.1.1.1.5	Integer32	read-only	A value that changes each time an exchanged parameter in one or more of the DCB feature TLV�s changes.
I32 lldpXdcbxPortAckNo	1.0.8802.1.1.2.1.5.6945.1.1.1.6	Integer32	read-only	The SeqNo value from the most recent peer DCBX TLV that has been handled. This acknowledges to the peer that a specific SeqNo has been received.
lldpXdcbxFeatures	1.0.8802.1.1.2.1.5.6945.2
lldpXdcbxFeatTable	1.0.8802.1.1.2.1.5.6945.2.1		not-accessible	A list of DCBX features configured on this system.
lldpXdcbxFeatEntry	1.0.8802.1.1.2.1.5.6945.2.1.1		not-accessible	A entry containing DCBX feature parameters which are common to all features.
LLD lldpXdcbxFeatType	1.0.8802.1.1.2.1.5.6945.2.1.1.1	LldpXdcbxFeatureType	read-write	Type code of the DCB Feature. Following is a list of defined types: 2 � Priority Groups 3 � Priority Flow Control 4 � Application Protocol
LLD lldpXdcbxFeatSubType	1.0.8802.1.1.2.1.5.6945.2.1.1.2	LldpXdcbxFeatureSubType	read-write	Some Feature TLVs may define subtypes that are specific to that feature. When subtypes are not defined by a specific feature, subtype field should be set to zero. In general, the Type and SubType, taken together, identify a unique feature that is managed by an instance of the DCB Feature State Machine.
LLD lldpXdcbxFeatVersionOper	1.0.8802.1.1.2.1.5.6945.2.1.1.3	LldpXdcbxVersion	read-only	Operating version of the feature. The system adjusts to operate at the highest version supported by both link partners.
LLD lldpXdcbxFeatVersionMax	1.0.8802.1.1.2.1.5.6945.2.1.1.4	LldpXdcbxVersion	read-only	Highest feature version supported by the system. Version numbers start at zero. The feature must be backward compatible for all previous versions.
T/F lldpXdcbxFeatEnable	1.0.8802.1.1.2.1.5.6945.2.1.1.5	TruthValue	read-write	Locally administered parameter that indicates whether the DCB feature is enabled or not.
T/F lldpXdcbxFeatWilling	1.0.8802.1.1.2.1.5.6945.2.1.1.6	TruthValue	read-write	Locally administered parameter that indicates whether this feature accepts its configuration from the peer or not. When set to TRUE, the system uses the DesiredCfg supplied by a not Willing peer as the OperCfg. A system set to Willing must be capable of accepting any valid DesiredCfg for the feature from the peer. If both local and remote systems have the same value for the Willing flag, then the local DesiredCfg is used and the operational outcome of the exchange is determined by the Compatible method of the feature.
T/F lldpXdcbxFeatError	1.0.8802.1.1.2.1.5.6945.2.1.1.7	TruthValue	read-only	Indicates that an error has occurred during the configuration exchange with the peer. Error is set TRUE when the OperCfg and OperMode of a feature cannot be set as the protocol requires. Error is also set to TRUE when the Compatible method for the feature fails. The Feature turns OperMode to FALSE if either the local or remote Error flag is set to TRUE. Duplicate TLV�s for the same Type/SubType or the DCBX Control TLV also causes Error to be set to TRUE.
T/F lldpXdcbxFeatAdvertise	1.0.8802.1.1.2.1.5.6945.2.1.1.8	TruthValue	read-write	Locally administered parameter that indicates whether this feature is exchanged in the DCBX TLV. When Advertise is False, received TLVs for this feature are ignored.
T/F lldpXdcbxFeatOperMode	1.0.8802.1.1.2.1.5.6945.2.1.1.9	TruthValue	read-only	Operational state of the feature.
T/F lldpXdcbxFeatSyncd	1.0.8802.1.1.2.1.5.6945.2.1.1.10	TruthValue	read-only	Indicates whether the current DesiredCfg has been received by the peer.
I32 lldpXdcbxFeatSeqNo	1.0.8802.1.1.2.1.5.6945.2.1.1.11	Integer32	read-only	When Syncd is False, this indicates the value that SeqNo must become equal to before Syncd can become True.
T/F lldpXdcbxFeatPeerWilling	1.0.8802.1.1.2.1.5.6945.2.1.1.12	TruthValue	read-only	The Willing state of the peer as received in a DCBX TLV from the peer.
T/F lldpXdcbxFeatLocalParameterChange	1.0.8802.1.1.2.1.5.6945.2.1.1.13	TruthValue	read-only	Indicates that a configurable DCB Feature TLV field or state variable has been modified on the local system.
T/F lldpXdcbxFeatPeerEnable	1.0.8802.1.1.2.1.5.6945.2.1.1.14	TruthValue	read-only	Private Extension: The Feature Enable state of the peer as received in a DCBX TLV from the peer.
T/F lldpXdcbxFeatPeerError	1.0.8802.1.1.2.1.5.6945.2.1.1.15	TruthValue	read-only	Private Extension: The Feature Error state of the peer as received in a DCBX TLV from the peer.
T/F lldpXdcbxFeatPeerAdvertise	1.0.8802.1.1.2.1.5.6945.2.1.1.16	TruthValue	read-write	Private Extension: The Feature Advertisment state of the peer as received in a DCBX TLV from the peer.
LLD lldpXdcbxFeatPeerTC	1.0.8802.1.1.2.1.5.6945.2.1.1.17	LldpXdcbxTCPeer	read-only	Private Extension: Number of TCs that supported on the peer. Relevan for PG and PFC features. If not relevant (as for App feat), will be set to 0.
lldpXdcbxFeatPg	1.0.8802.1.1.2.1.5.6945.2.2
LLD lldpXdcbxFeatPgNumTCsSupported	1.0.8802.1.1.2.1.5.6945.2.2.1	LldpXdcbxTC	read-write	Number of TCs supported by device. Number of Priority Groups supported by a device can not be more than number of TCs supported.
lldpXdcbxFeatPgPrioAllocTable	1.0.8802.1.1.2.1.5.6945.2.2.2		not-accessible	A list of priorities and the their priority group assignment or declaration of no bandwidth limit.
lldpXdcbxFeatPgPrioAllocEntry	1.0.8802.1.1.2.1.5.6945.2.2.2.1		not-accessible	An entry for a priority which allows the priority to be assigned to a priority group, or declared with no bandwidth limit.
LLD lldpXdcbxFeatPgPrioAllocPrioId	1.0.8802.1.1.2.1.5.6945.2.2.2.1.1	LldpXdcbxPriority	read-write	The priority which is to be assigned to a priority group, or defined with no bandwidth limit.
LLD lldpXdcbxFeatPgPrioAllocPgIdDesired	1.0.8802.1.1.2.1.5.6945.2.2.2.1.2	LldpXdcbxPriorityGroup	read-write	The locally configured priority group value assigned to this priority.
LLD lldpXdcbxFeatPgPrioAllocPgIdOper	1.0.8802.1.1.2.1.5.6945.2.2.2.1.3	LldpXdcbxPriorityGroup	read-only	The operating priority group value assigned to this priority. NOTE: This value may be different than the locally desired value depending on whether or not this feature is 'willing' to accept the peer's desired configuration. The operating configuration MUST match either the locally desired configuration or the peer's desired configuration if the feature is operational.
LLD lldpXdcbxFeatPgPrioAllocPgIdPeer	1.0.8802.1.1.2.1.5.6945.2.2.2.1.4	LldpXdcbxPriorityGroup	read-only	The priority group value that the peer desires to assign to this priority.
lldpXdcbxFeatPgBwAllocTable	1.0.8802.1.1.2.1.5.6945.2.2.3		not-accessible	A list of priority group bandwidth allocations.
lldpXdcbxFeatPgBwAllocEntry	1.0.8802.1.1.2.1.5.6945.2.2.3.1		not-accessible	An entry for a priority group bandwidth allocation.
LLD lldpXdcbxFeatPgBwAllocPgId	1.0.8802.1.1.2.1.5.6945.2.2.3.1.1	LldpXdcbxPriorityGroup	read-write	The priority group for which bandwidth is allocated in this table.
LLD lldpXdcbxFeatPgBwAllocBwDesired	1.0.8802.1.1.2.1.5.6945.2.2.3.1.2	LldpXdcbxPgBw	read-write	The locally configured bandwidth allocated to this priority group.
LLD lldpXdcbxFeatPgBwAllocBwOper	1.0.8802.1.1.2.1.5.6945.2.2.3.1.3	LldpXdcbxPgBw	read-only	The operating bandwidth allocated to this priority group. NOTE: This value may be different than the locally desired value depending on whether or not this feature is 'willing' to accept the peer's desired configuration. The operating configuration MUST match either the locally desired configuration or the peer's desired configuration if the feature is operational.
LLD lldpXdcbxFeatPgBwAllocBwPeer	1.0.8802.1.1.2.1.5.6945.2.2.3.1.4	LldpXdcbxPgBw	read-only	The bandwidth allocation that the peer desires to assign to this priority group.
lldpXdcbxFeatPfc	1.0.8802.1.1.2.1.5.6945.2.3
LLD lldpXdcbxFeatPfcNumTCPFCSupported	1.0.8802.1.1.2.1.5.6945.2.3.1	LldpXdcbxTCPFC	read-write	Number of TCs that can simultaneously support PFC.
lldpXdcbxFeatPfcTable	1.0.8802.1.1.2.1.5.6945.2.3.2		not-accessible	A list of priority flow control configurations for each priority.
lldpXdcbxFeatPfcEntry	1.0.8802.1.1.2.1.5.6945.2.3.2.1		not-accessible	An entry for configuring priority flow control for each priority.
LLD lldpXdcbxFeatPfcPriority	1.0.8802.1.1.2.1.5.6945.2.3.2.1.1	LldpXdcbxPriority	read-write	The priority for which priority flow control is being configured.
T/F lldpXdcbxFeatPfcEnableDesired	1.0.8802.1.1.2.1.5.6945.2.3.2.1.2	TruthValue	read-write	The locally configured status of priority flow control for this priority. 0: Disabled 1: Enabled PFC Enabled means that flow control in both directions (Rx and Tx) is enabled.
T/F lldpXdcbxFeatPfcEnableOper	1.0.8802.1.1.2.1.5.6945.2.3.2.1.3	TruthValue	read-only	The operating status of priority flow control for this priority. NOTE: This value may be different than the locally desired value depending on whether or not this feature is 'willing' to accept the peer's desired configuration. The operating configuration MUST match either the locally desired configuration or the peer's desired configuration if the feature is operational.
T/F lldpXdcbxFeatPfcEnablePeer	1.0.8802.1.1.2.1.5.6945.2.3.2.1.4	TruthValue	read-only	The priority flow control status that the peer desires to assign to this priority.
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		not-accessible	A list of Application Protocol configurations.
lldpXdcbxFeatAppProtoEntry	1.0.8802.1.1.2.1.5.6945.2.4.1.1		not-accessible	An entry for configuring Application Protocol ID.
LLD lldpXdcbxFeatAppProtoIndex	1.0.8802.1.1.2.1.5.6945.2.4.1.1.1	LldpXdcbxAppProtos	read-write	The index of the Application Protocol being configured in a list of Application Protocols.
LLD lldpXdcbxFeatAppProtoSF	1.0.8802.1.1.2.1.5.6945.2.4.1.1.2	LldpXdcbxSF	read-write	The value of the Selector Field for this application protocol.
I32 lldpXdcbxFeatAppProtoOUI	1.0.8802.1.1.2.1.5.6945.2.4.1.1.3	Integer32	read-write	The value of the Application Protocol OUI for this application protocol.
INT lldpXdcbxFeatAppProtoId	1.0.8802.1.1.2.1.5.6945.2.4.1.1.4	INTEGER	read-write	The value of the Application Protocol ID for this application protocol.
lldpXdcbxFeatAppProtoPrioTable	1.0.8802.1.1.2.1.5.6945.2.4.2		not-accessible	A list of priority configurations for each application protocol.
lldpXdcbxFeatAppProtoPrioEntry	1.0.8802.1.1.2.1.5.6945.2.4.2.1		not-accessible	An entry for selecting priorities for the Application Protocol.
LLD lldpXdcbxFeatAppProtoPriority	1.0.8802.1.1.2.1.5.6945.2.4.2.1.1	LldpXdcbxPriority	read-write	The priority for which Application Protocol is being configured.
T/F lldpXdcbxFeatAppProtoEnableDesired	1.0.8802.1.1.2.1.5.6945.2.4.2.1.2	TruthValue	read-write	The locally configured status of Application Protocol for this priority. 0: Disabled 1: Enabled
T/F lldpXdcbxFeatAppProtoEnableOper	1.0.8802.1.1.2.1.5.6945.2.4.2.1.3	TruthValue	read-only	The operating status of Application Protocol for this priority. NOTE: This value may be different than the locally desired value depending on whether or not this feature is 'willing' to accept the peer's desired configuration. The operating configuration MUST match either the locally desired configuration or the peer's desired configuration if the feature is operational.
T/F lldpXdcbxFeatAppProtoEnablePeer	1.0.8802.1.1.2.1.5.6945.2.4.2.1.4	TruthValue	read-only	The Application Protocol status that the peer desires to assign to this priority.

RFC description

LLDP extension module for Data Center Bridging (DCB) Capability Exchange Protocol, enabling standardized QoS negotiation over Ethernet.

Start monitoring Vendor-neutral IEEE/industry standard (data-center Ethernet switches/NICs, DCBX) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download LLDP-EXT-DCBX-MIB

What Is LLDP-EXT-DCBX-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description