LLDP-EXT-DCBX-MIB
File:
LLDP-EXT-DCBX-MIB.mib (37141 bytes)
Imported modules
Imported symbols
Defined Types
LldpXdcbxPriorityGroup |
|
DCB Priority Groups. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
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) |
|
LldpXdcbxFeatureType |
|
Type code of the DCB Feature. Following is a list of defined types:
2 - Priority Groups
3 - Priority Flow Control
4 - Application Protocol |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
priorityGroup(2), priorityFlowControl(3), applicationProtocol(4) |
|
LldpXdcbxTC |
|
Traffic Classes Supported. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
0..7 |
|
LldpXdcbxPgBw |
|
Priority Group Bandwidth Range. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
0..100 |
|
LldpXdcbxTCPFC |
|
Number of TCs that can simultaneously support PFC. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
1..8 |
|
LldpXdcbxTCPeer |
|
Private Extension: Number of TCs that supported on the peer. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
0..8 |
|
LldpXdcbxAppProtos |
|
Number of Application Protocols (TLVs) supported. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
0..15 |
|
LldpXdcbxSF |
|
Selector Field to specify Application Protocol ID Type. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
l2EtherType(0), socketNumber(1), reserved2(2), reserved3(3) |
|
LldpXdcbxPortEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxPortNumber |
LldpPortNumber |
|
|
lldpXdcbxPortEnable |
TruthValue |
|
|
lldpXdcbxPortVersionOper |
LldpXdcbxVersion |
|
|
lldpXdcbxPortVersionMax |
LldpXdcbxVersion |
|
|
lldpXdcbxPortSeqNo |
Integer32 |
|
|
lldpXdcbxPortAckNo |
Integer32 |
|
LldpXdcbxFeatEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatType |
LldpXdcbxFeatureType |
|
|
lldpXdcbxFeatSubType |
LldpXdcbxFeatureSubType |
|
|
lldpXdcbxFeatVersionOper |
LldpXdcbxVersion |
|
|
lldpXdcbxFeatVersionMax |
LldpXdcbxVersion |
|
|
lldpXdcbxFeatEnable |
TruthValue |
|
|
lldpXdcbxFeatWilling |
TruthValue |
|
|
lldpXdcbxFeatError |
TruthValue |
|
|
lldpXdcbxFeatAdvertise |
TruthValue |
|
|
lldpXdcbxFeatOperMode |
TruthValue |
|
|
lldpXdcbxFeatSyncd |
TruthValue |
|
|
lldpXdcbxFeatSeqNo |
Integer32 |
|
|
lldpXdcbxFeatPeerWilling |
TruthValue |
|
|
lldpXdcbxFeatLocalParameterChange |
TruthValue |
|
|
lldpXdcbxFeatPeerEnable |
TruthValue |
|
|
lldpXdcbxFeatPeerError |
TruthValue |
|
|
lldpXdcbxFeatPeerAdvertise |
TruthValue |
|
|
lldpXdcbxFeatPeerTC |
LldpXdcbxTCPeer |
|
LldpXdcbxFeatPgPrioAllocEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatPgPrioAllocPrioId |
LldpXdcbxPriority |
|
|
lldpXdcbxFeatPgPrioAllocPgIdDesired |
LldpXdcbxPriorityGroup |
|
|
lldpXdcbxFeatPgPrioAllocPgIdOper |
LldpXdcbxPriorityGroup |
|
|
lldpXdcbxFeatPgPrioAllocPgIdPeer |
LldpXdcbxPriorityGroup |
|
LldpXdcbxFeatPgBwAllocEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatPgBwAllocPgId |
LldpXdcbxPriorityGroup |
|
|
lldpXdcbxFeatPgBwAllocBwDesired |
LldpXdcbxPgBw |
|
|
lldpXdcbxFeatPgBwAllocBwOper |
LldpXdcbxPgBw |
|
|
lldpXdcbxFeatPgBwAllocBwPeer |
LldpXdcbxPgBw |
|
LldpXdcbxFeatPfcEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatPfcPriority |
LldpXdcbxPriority |
|
|
lldpXdcbxFeatPfcEnableDesired |
TruthValue |
|
|
lldpXdcbxFeatPfcEnableOper |
TruthValue |
|
|
lldpXdcbxFeatPfcEnablePeer |
TruthValue |
|
LldpXdcbxFeatAppProtoEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatAppProtoIndex |
LldpXdcbxAppProtos |
|
|
lldpXdcbxFeatAppProtoSF |
LldpXdcbxSF |
|
|
lldpXdcbxFeatAppProtoOUI |
Integer32 |
|
|
lldpXdcbxFeatAppProtoId |
INTEGER |
|
LldpXdcbxFeatAppProtoPrioEntry |
|
SEQUENCE |
|
|
|
|
lldpXdcbxFeatAppProtoPriority |
LldpXdcbxPriority |
|
|
lldpXdcbxFeatAppProtoEnableDesired |
TruthValue |
|
|
lldpXdcbxFeatAppProtoEnableOper |
TruthValue |
|
|
lldpXdcbxFeatAppProtoEnablePeer |
TruthValue |
|
Defined Values
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. |
MODULE-IDENTITY |
|
|
|
lldpXdcbxPortEntry |
1.0.8802.1.1.2.1.5.6945.1.1.1 |
An entry containing DCBX control parameters for a particular port. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxPortEntry |
|
|
lldpXdcbxPortNumber |
1.0.8802.1.1.2.1.5.6945.1.1.1.1 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpPortNumber |
|
|
lldpXdcbxPortEnable |
1.0.8802.1.1.2.1.5.6945.1.1.1.2 |
A device capable of any DCB feature must have DCBX enabled by default
with an option for DCBX to be administratively disabled. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxPortVersionOper |
1.0.8802.1.1.2.1.5.6945.1.1.1.3 |
Operating version of the DCBX protocol. The system adjusts as needed
to operate at the highest version supported by both link partners. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxVersion |
|
|
lldpXdcbxPortVersionMax |
1.0.8802.1.1.2.1.5.6945.1.1.1.4 |
Highest DCBX protocol version supported by the system. Version numbers
start at zero. The DCBX protocol must be backward compatible with all
previous versions. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxVersion |
|
|
lldpXdcbxPortSeqNo |
1.0.8802.1.1.2.1.5.6945.1.1.1.5 |
A value that changes each time an exchanged parameter in one or more
of the DCB feature TLV's changes. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
lldpXdcbxPortAckNo |
1.0.8802.1.1.2.1.5.6945.1.1.1.6 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
lldpXdcbxFeatEntry |
1.0.8802.1.1.2.1.5.6945.2.1.1 |
A entry containing DCBX feature parameters which are common to all
features. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatEntry |
|
|
lldpXdcbxFeatType |
1.0.8802.1.1.2.1.5.6945.2.1.1.1 |
Type code of the DCB Feature. Following is a list of defined types:
2 - Priority Groups
3 - Priority Flow Control
4 - Application Protocol |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatureType |
|
|
lldpXdcbxFeatSubType |
1.0.8802.1.1.2.1.5.6945.2.1.1.2 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatureSubType |
|
|
lldpXdcbxFeatVersionOper |
1.0.8802.1.1.2.1.5.6945.2.1.1.3 |
Operating version of the feature. The system adjusts to operate at the
highest version supported by both link partners. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxVersion |
|
|
lldpXdcbxFeatVersionMax |
1.0.8802.1.1.2.1.5.6945.2.1.1.4 |
Highest feature version supported by the system. Version numbers start
at zero. The feature must be backward compatible for all previous
versions. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxVersion |
|
|
lldpXdcbxFeatEnable |
1.0.8802.1.1.2.1.5.6945.2.1.1.5 |
Locally administered parameter that indicates whether the DCB feature
is enabled or not. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatWilling |
1.0.8802.1.1.2.1.5.6945.2.1.1.6 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatError |
1.0.8802.1.1.2.1.5.6945.2.1.1.7 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatAdvertise |
1.0.8802.1.1.2.1.5.6945.2.1.1.8 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatSyncd |
1.0.8802.1.1.2.1.5.6945.2.1.1.10 |
Indicates whether the current DesiredCfg has been received by the
peer. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatSeqNo |
1.0.8802.1.1.2.1.5.6945.2.1.1.11 |
When Syncd is False, this indicates the value that SeqNo must
become equal to before Syncd can become True. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
lldpXdcbxFeatPeerWilling |
1.0.8802.1.1.2.1.5.6945.2.1.1.12 |
The Willing state of the peer as received in a DCBX TLV from the
peer. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatLocalParameterChange |
1.0.8802.1.1.2.1.5.6945.2.1.1.13 |
Indicates that a configurable DCB Feature TLV field or state variable
has been modified on the local system. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPeerEnable |
1.0.8802.1.1.2.1.5.6945.2.1.1.14 |
Private Extension: The Feature Enable state of the peer as received in a DCBX TLV from the
peer. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPeerError |
1.0.8802.1.1.2.1.5.6945.2.1.1.15 |
Private Extension: The Feature Error state of the peer as received in a DCBX TLV from the
peer. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPeerAdvertise |
1.0.8802.1.1.2.1.5.6945.2.1.1.16 |
Private Extension: The Feature Advertisment state of the peer as received in a DCBX TLV from the
peer. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPeerTC |
1.0.8802.1.1.2.1.5.6945.2.1.1.17 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxTCPeer |
|
|
lldpXdcbxFeatPgNumTCsSupported |
1.0.8802.1.1.2.1.5.6945.2.2.1 |
Number of TCs supported by device.
Number of Priority Groups supported by a device can not be more than
number of TCs supported. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxTC |
|
|
lldpXdcbxFeatPgPrioAllocEntry |
1.0.8802.1.1.2.1.5.6945.2.2.2.1 |
An entry for a priority which allows the priority to be assigned to a
priority group, or declared with no bandwidth limit. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatPgPrioAllocEntry |
|
|
lldpXdcbxFeatPgPrioAllocPgIdOper |
1.0.8802.1.1.2.1.5.6945.2.2.2.1.3 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxPriorityGroup |
|
|
lldpXdcbxFeatPgBwAllocEntry |
1.0.8802.1.1.2.1.5.6945.2.2.3.1 |
An entry for a priority group bandwidth allocation. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatPgBwAllocEntry |
|
|
lldpXdcbxFeatPgBwAllocBwOper |
1.0.8802.1.1.2.1.5.6945.2.2.3.1.3 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxPgBw |
|
|
lldpXdcbxFeatPfcEntry |
1.0.8802.1.1.2.1.5.6945.2.3.2.1 |
An entry for configuring priority flow control for each priority. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatPfcEntry |
|
|
lldpXdcbxFeatPfcEnableDesired |
1.0.8802.1.1.2.1.5.6945.2.3.2.1.2 |
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. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPfcEnableOper |
1.0.8802.1.1.2.1.5.6945.2.3.2.1.3 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatPfcEnablePeer |
1.0.8802.1.1.2.1.5.6945.2.3.2.1.4 |
The priority flow control status that the peer desires to assign to
this priority. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatAppProtoEntry |
1.0.8802.1.1.2.1.5.6945.2.4.1.1 |
An entry for configuring Application Protocol ID. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatAppProtoEntry |
|
|
lldpXdcbxFeatAppProtoSF |
1.0.8802.1.1.2.1.5.6945.2.4.1.1.2 |
The value of the Selector Field for this application protocol. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxSF |
|
|
lldpXdcbxFeatAppProtoOUI |
1.0.8802.1.1.2.1.5.6945.2.4.1.1.3 |
The value of the Application Protocol OUI for this application
protocol. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
lldpXdcbxFeatAppProtoId |
1.0.8802.1.1.2.1.5.6945.2.4.1.1.4 |
The value of the Application Protocol ID for this application
protocol. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
|
|
lldpXdcbxFeatAppProtoPrioEntry |
1.0.8802.1.1.2.1.5.6945.2.4.2.1 |
An entry for selecting priorities for the Application Protocol. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
LldpXdcbxFeatAppProtoPrioEntry |
|
|
lldpXdcbxFeatAppProtoEnableDesired |
1.0.8802.1.1.2.1.5.6945.2.4.2.1.2 |
The locally configured status of Application Protocol for this
priority.
0: Disabled
1: Enabled |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
lldpXdcbxFeatAppProtoEnableOper |
1.0.8802.1.1.2.1.5.6945.2.4.2.1.3 |
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. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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). |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
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. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|