LLDP-EXT-DCBX-MIB
- Registered at
- 1.0.8802.1.1.2.1.5.6945
- Last updated
- 2008-11-20 00:00
- Organization
- IEEE ??? Working Group
- Namespace
- standard
- Source file
LLDP-EXT-DCBX-MIB- Digest
sha256:cf000478dc39d4785c090dff67f3e6396c13c410fc8186b23c2e28fc12213856
Description
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.
Contact
WG-URL: ??? WG-EMail: ??? Contact: Robert Cowart Postal: IBM 6303 Barfield Road NE Atlanta, GA 30328-4233 USA Tel: +1-404-935-6841 E-mail: rcowart@us.ibm.com Contact: Nagaraj Govindaiah Postal: EMULEX 2560 N First St. Ste.300 San Jose, CA 95131 USA Tel: +1-408-904-4150 E-mail: nagaraj.govindaiah@emulex.com
Imports
| From | Symbols |
|---|---|
| LLDP-MIB | LldpPortNumber, lldpExtensions |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION, TruthValue |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
IANA-ADDRESS-FAMILY-NUMBERS-MIB IANAifType-MIB IF-MIB LLDP-EXT-DCBX-MIB LLDP-MIB RFC1158-MIB RFC1271-MIB RMON-MIB RMON2-MIB SNMP-FRAMEWORK-MIB SNMPv2-CONF SNMPv2-MIB SNMPv2-SMI SNMPv2-TC TOKEN-RING-RMON-MIB
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| LldpXdcbxAppProtos TEXTUAL-CONVENTION Number of Application Protocols (TLVs) supported. | current | |||
| LldpXdcbxFeatureSubType TEXTUAL-CONVENTION LLDP DCBX Feature Sub Type. | current | |||
| LldpXdcbxFeatureType TEXTUAL-CONVENTION Type code of the DCB Feature. Following is a list of defined types: 2 – Priority Groups 3 – Priority Flow Control 4 - Application Protocol | current | |||
| LldpXdcbxPgBw TEXTUAL-CONVENTION Priority Group Bandwidth Range. | current | |||
| LldpXdcbxPriority TEXTUAL-CONVENTION IEEE 802.1p Priorities. | current | |||
| LldpXdcbxPriorityGroup TEXTUAL-CONVENTION DCB Priority Groups. | current | |||
| LldpXdcbxSF TEXTUAL-CONVENTION Selector Field to specify Application Protocol ID Type. | current | |||
| LldpXdcbxTC TEXTUAL-CONVENTION Traffic Classes Supported. | current | |||
| LldpXdcbxTCPFC TEXTUAL-CONVENTION Number of TCs that can simultaneously support PFC. | current | |||
| LldpXdcbxTCPeer TEXTUAL-CONVENTION Private Extension: Number of TCs that supported on the peer. | current | |||
| LldpXdcbxVersion TEXTUAL-CONVENTION LLDP DCBX Version. | current |
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| lldpXdcbxNotifications OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.0 | |||
| lldpXdcbxObjects OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.1 | |||
| lldpXdcbxPortTable OBJECT-TYPE A list of all ports capable of supporting DCBX. | 1.0.8802.1.1.2.1.5.6945.1.1 | not-accessible | current | |
| lldpXdcbxPortEntry OBJECT-TYPE An entry containing DCBX control parameters for a particular port. | 1.0.8802.1.1.2.1.5.6945.1.1.1 | not-accessible | current | |
| lldpXdcbxPortNumber OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.1.1.1.1 | LldpPortNumber | read-only | current |
| lldpXdcbxPortEnable OBJECT-TYPE A device capable of any DCB feature must have DCBX enabled by default with an option for DCBX to be administratively disabled. | 1.0.8802.1.1.2.1.5.6945.1.1.1.2 | TruthValue | read-write | current |
| lldpXdcbxPortVersionOper OBJECT-TYPE Operating version of the DCBX protocol. The system adjusts as needed to operate at the highest version supported by both link partners. | 1.0.8802.1.1.2.1.5.6945.1.1.1.3 | LldpXdcbxVersion | read-only | current |
| lldpXdcbxPortVersionMax OBJECT-TYPE Highest DCBX protocol version supported by the system. Version numbers start at zero. The DCBX protocol must be backward compatible with all previous versions. | 1.0.8802.1.1.2.1.5.6945.1.1.1.4 | LldpXdcbxVersion | read-only | current |
| lldpXdcbxPortSeqNo OBJECT-TYPE A value that changes each time an exchanged parameter in one or more of the DCB feature TLV’s changes. | 1.0.8802.1.1.2.1.5.6945.1.1.1.5 | Integer32 | read-only | current |
| lldpXdcbxPortAckNo OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.1.1.1.6 | Integer32 | read-only | current |
| lldpXdcbxFeatures OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.2 | |||
| lldpXdcbxFeatTable OBJECT-TYPE A list of DCBX features configured on this system. | 1.0.8802.1.1.2.1.5.6945.2.1 | not-accessible | current | |
| lldpXdcbxFeatEntry OBJECT-TYPE A entry containing DCBX feature parameters which are common to all features. | 1.0.8802.1.1.2.1.5.6945.2.1.1 | not-accessible | current | |
| lldpXdcbxFeatType OBJECT-TYPE Type code of the DCB Feature. Following is a list of defined types: 2 – Priority Groups 3 – Priority Flow Control 4 – Application Protocol | 1.0.8802.1.1.2.1.5.6945.2.1.1.1 | LldpXdcbxFeatureType | read-write | current |
| lldpXdcbxFeatSubType OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.1.1.2 | LldpXdcbxFeatureSubType | read-write | current |
| lldpXdcbxFeatVersionOper OBJECT-TYPE Operating version of the feature. The system adjusts to operate at the highest version supported by both link partners. | 1.0.8802.1.1.2.1.5.6945.2.1.1.3 | LldpXdcbxVersion | read-only | current |
| lldpXdcbxFeatVersionMax OBJECT-TYPE Highest feature version supported by the system. Version numbers start at zero. The feature must be backward compatible for all previous versions. | 1.0.8802.1.1.2.1.5.6945.2.1.1.4 | LldpXdcbxVersion | read-only | current |
| lldpXdcbxFeatEnable OBJECT-TYPE Locally administered parameter that indicates whether the DCB feature is enabled or not. | 1.0.8802.1.1.2.1.5.6945.2.1.1.5 | TruthValue | read-write | current |
| lldpXdcbxFeatWilling OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.1.1.6 | TruthValue | read-write | current |
| lldpXdcbxFeatError OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.1.1.7 | TruthValue | read-only | current |
| lldpXdcbxFeatAdvertise OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.1.1.8 | TruthValue | read-write | current |
| lldpXdcbxFeatOperMode OBJECT-TYPE Operational state of the feature. | 1.0.8802.1.1.2.1.5.6945.2.1.1.9 | TruthValue | read-only | current |
| lldpXdcbxFeatSyncd OBJECT-TYPE Indicates whether the current DesiredCfg has been received by the peer. | 1.0.8802.1.1.2.1.5.6945.2.1.1.10 | TruthValue | read-only | current |
| lldpXdcbxFeatSeqNo OBJECT-TYPE When Syncd is False, this indicates the value that SeqNo must become equal to before Syncd can become True. | 1.0.8802.1.1.2.1.5.6945.2.1.1.11 | Integer32 | read-only | current |
| lldpXdcbxFeatPeerWilling OBJECT-TYPE The Willing state of the peer as received in a DCBX TLV from the peer. | 1.0.8802.1.1.2.1.5.6945.2.1.1.12 | TruthValue | read-only | current |
| lldpXdcbxFeatLocalParameterChange OBJECT-TYPE Indicates that a configurable DCB Feature TLV field or state variable has been modified on the local system. | 1.0.8802.1.1.2.1.5.6945.2.1.1.13 | TruthValue | read-only | current |
| lldpXdcbxFeatPeerEnable OBJECT-TYPE Private Extension: The Feature Enable state of the peer as received in a DCBX TLV from the peer. | 1.0.8802.1.1.2.1.5.6945.2.1.1.14 | TruthValue | read-only | current |
| lldpXdcbxFeatPeerError OBJECT-TYPE Private Extension: The Feature Error state of the peer as received in a DCBX TLV from the peer. | 1.0.8802.1.1.2.1.5.6945.2.1.1.15 | TruthValue | read-only | current |
| lldpXdcbxFeatPeerAdvertise OBJECT-TYPE Private Extension: The Feature Advertisment state of the peer as received in a DCBX TLV from the peer. | 1.0.8802.1.1.2.1.5.6945.2.1.1.16 | TruthValue | read-write | current |
| lldpXdcbxFeatPeerTC OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.1.1.17 | LldpXdcbxTCPeer | read-only | current |
| lldpXdcbxFeatPg OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.2.2 | |||
| lldpXdcbxFeatPgNumTCsSupported OBJECT-TYPE Number of TCs supported by device. Number of Priority Groups supported by a device can not be more than number of TCs supported. | 1.0.8802.1.1.2.1.5.6945.2.2.1 | LldpXdcbxTC | read-write | current |
| lldpXdcbxFeatPgPrioAllocTable OBJECT-TYPE A list of priorities and the their priority group assignment or declaration of no bandwidth limit. | 1.0.8802.1.1.2.1.5.6945.2.2.2 | not-accessible | current | |
| lldpXdcbxFeatPgPrioAllocEntry OBJECT-TYPE An entry for a priority which allows the priority to be assigned to a priority group, or declared with no bandwidth limit. | 1.0.8802.1.1.2.1.5.6945.2.2.2.1 | not-accessible | current | |
| lldpXdcbxFeatPgPrioAllocPrioId OBJECT-TYPE The priority which is to be assigned to a priority group, or defined with no bandwidth limit. | 1.0.8802.1.1.2.1.5.6945.2.2.2.1.1 | LldpXdcbxPriority | read-write | current |
| lldpXdcbxFeatPgPrioAllocPgIdDesired OBJECT-TYPE The locally configured priority group value assigned to this priority. | 1.0.8802.1.1.2.1.5.6945.2.2.2.1.2 | LldpXdcbxPriorityGroup | read-write | current |
| lldpXdcbxFeatPgPrioAllocPgIdOper OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.2.2.1.3 | LldpXdcbxPriorityGroup | read-only | current |
| lldpXdcbxFeatPgPrioAllocPgIdPeer OBJECT-TYPE The priority group value that the peer desires to assign to this priority. | 1.0.8802.1.1.2.1.5.6945.2.2.2.1.4 | LldpXdcbxPriorityGroup | read-only | current |
| lldpXdcbxFeatPgBwAllocTable OBJECT-TYPE A list of priority group bandwidth allocations. | 1.0.8802.1.1.2.1.5.6945.2.2.3 | not-accessible | current | |
| lldpXdcbxFeatPgBwAllocEntry OBJECT-TYPE An entry for a priority group bandwidth allocation. | 1.0.8802.1.1.2.1.5.6945.2.2.3.1 | not-accessible | current | |
| lldpXdcbxFeatPgBwAllocPgId OBJECT-TYPE The priority group for which bandwidth is allocated in this table. | 1.0.8802.1.1.2.1.5.6945.2.2.3.1.1 | LldpXdcbxPriorityGroup | read-write | current |
| lldpXdcbxFeatPgBwAllocBwDesired OBJECT-TYPE The locally configured bandwidth allocated to this priority group. | 1.0.8802.1.1.2.1.5.6945.2.2.3.1.2 | LldpXdcbxPgBw | read-write | current |
| lldpXdcbxFeatPgBwAllocBwOper OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.2.3.1.3 | LldpXdcbxPgBw | read-only | current |
| lldpXdcbxFeatPgBwAllocBwPeer OBJECT-TYPE The bandwidth allocation that the peer desires to assign to this priority group. | 1.0.8802.1.1.2.1.5.6945.2.2.3.1.4 | LldpXdcbxPgBw | read-only | current |
| lldpXdcbxFeatPfc OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.2.3 | |||
| lldpXdcbxFeatPfcNumTCPFCSupported OBJECT-TYPE Number of TCs that can simultaneously support PFC. | 1.0.8802.1.1.2.1.5.6945.2.3.1 | LldpXdcbxTCPFC | read-write | current |
| lldpXdcbxFeatPfcTable OBJECT-TYPE A list of priority flow control configurations for each priority. | 1.0.8802.1.1.2.1.5.6945.2.3.2 | not-accessible | current | |
| lldpXdcbxFeatPfcEntry OBJECT-TYPE An entry for configuring priority flow control for each priority. | 1.0.8802.1.1.2.1.5.6945.2.3.2.1 | not-accessible | current | |
| lldpXdcbxFeatPfcPriority OBJECT-TYPE The priority for which priority flow control is being configured. | 1.0.8802.1.1.2.1.5.6945.2.3.2.1.1 | LldpXdcbxPriority | read-write | current |
| lldpXdcbxFeatPfcEnableDesired OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.3.2.1.2 | TruthValue | read-write | current |
| lldpXdcbxFeatPfcEnableOper OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.3.2.1.3 | TruthValue | read-only | current |
| lldpXdcbxFeatPfcEnablePeer OBJECT-TYPE The priority flow control status that the peer desires to assign to this priority. | 1.0.8802.1.1.2.1.5.6945.2.3.2.1.4 | TruthValue | read-only | current |
| lldpXdcbxFeatAppProto OBJECT-IDENTITY | 1.0.8802.1.1.2.1.5.6945.2.4 | |||
| lldpXdcbxFeatAppProtoTable OBJECT-TYPE A list of Application Protocol configurations. | 1.0.8802.1.1.2.1.5.6945.2.4.1 | not-accessible | current | |
| lldpXdcbxFeatAppProtoEntry OBJECT-TYPE An entry for configuring Application Protocol ID. | 1.0.8802.1.1.2.1.5.6945.2.4.1.1 | not-accessible | current | |
| lldpXdcbxFeatAppProtoIndex OBJECT-TYPE The index of the Application Protocol being configured in a list of Application Protocols. | 1.0.8802.1.1.2.1.5.6945.2.4.1.1.1 | LldpXdcbxAppProtos | read-write | current |
| lldpXdcbxFeatAppProtoSF OBJECT-TYPE The value of the Selector Field for this application protocol. | 1.0.8802.1.1.2.1.5.6945.2.4.1.1.2 | LldpXdcbxSF | read-write | current |
| lldpXdcbxFeatAppProtoOUI OBJECT-TYPE The value of the Application Protocol OUI for this application protocol. | 1.0.8802.1.1.2.1.5.6945.2.4.1.1.3 | Integer32 | read-write | current |
| lldpXdcbxFeatAppProtoId OBJECT-TYPE The value of the Application Protocol ID for this application protocol. | 1.0.8802.1.1.2.1.5.6945.2.4.1.1.4 | INTEGER | read-write | current |
| lldpXdcbxFeatAppProtoPrioTable OBJECT-TYPE A list of priority configurations for each application protocol. | 1.0.8802.1.1.2.1.5.6945.2.4.2 | not-accessible | current | |
| lldpXdcbxFeatAppProtoPrioEntry OBJECT-TYPE An entry for selecting priorities for the Application Protocol. | 1.0.8802.1.1.2.1.5.6945.2.4.2.1 | not-accessible | current | |
| lldpXdcbxFeatAppProtoPriority OBJECT-TYPE The priority for which Application Protocol is being configured. | 1.0.8802.1.1.2.1.5.6945.2.4.2.1.1 | LldpXdcbxPriority | read-write | current |
| lldpXdcbxFeatAppProtoEnableDesired OBJECT-TYPE The locally configured status of Application Protocol for this priority. 0: Disabled 1: Enabled | 1.0.8802.1.1.2.1.5.6945.2.4.2.1.2 | TruthValue | read-write | current |
| lldpXdcbxFeatAppProtoEnableOper OBJECT-TYPE 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. | 1.0.8802.1.1.2.1.5.6945.2.4.2.1.3 | TruthValue | read-only | current |
| lldpXdcbxFeatAppProtoEnablePeer OBJECT-TYPE The Application Protocol status that the peer desires to assign to this priority. | 1.0.8802.1.1.2.1.5.6945.2.4.2.1.4 | TruthValue | read-only | current |
Notifications
| Name | OID | Status |
|---|---|---|
| lldpXdcbxMiscControlError NOTIFICATION-TYPE 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.1 | current |
| lldpXdcbxMiscFeatureError NOTIFICATION-TYPE 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.2 | current |
| lldpXdcbxMultiplePeers NOTIFICATION-TYPE 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.3 | current |
| lldpXdcbxLldpTxDisabled NOTIFICATION-TYPE 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.4 | current |
| lldpXdcbxLldpRxDisabled NOTIFICATION-TYPE 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.5 | current |
| lldpXdcbxDupControlTlv NOTIFICATION-TYPE 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.6 | current |
| lldpXdcbxDupFeatureTlv NOTIFICATION-TYPE 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.7 | current |
| lldpXdcbxPeerNoFeat NOTIFICATION-TYPE 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.8 | current |
| lldpXdcbxPeerNoResp NOTIFICATION-TYPE This trap is sent when the peer has stopped responding as evidenced by an LLDP timeout event. | 1.0.8802.1.1.2.1.5.6945.0.9 | current |
| lldpXdcbxPeerConfigMismatch NOTIFICATION-TYPE 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.10 | current |