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.
Main OID:
lldpXdcbxMIB.1.3.6.1.4.1.3320.127.1.5.6945
76
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
76 total| Object Name |
|---|
lldpXdcbxMIBThe 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 .1.3.6.1.4.1.3320.127.1.5.6945 |
lldpXdcbxNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.0 |
lldpXdcbxMiscControlErrorThis trap is sent whenever an error occurs with DCBX control and there
is no other trap defined for the specific error condition. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.1 |
lldpXdcbxMiscFeatureErrorThis trap is sent whenever lldpXdcbxFeatError is true and there is no
other trap defined for the specific error condition. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.2 |
lldpXdcbxMultiplePeersThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.3 |
lldpXdcbxLldpTxDisabledThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.4 |
lldpXdcbxLldpRxDisabledThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.5 |
lldpXdcbxDupControlTlvThis 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-TLVs (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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.6 |
lldpXdcbxDupFeatureTlvThis 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.7 |
lldpXdcbxPeerNoFeatThis 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). NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.8 |
lldpXdcbxPeerNoRespThis trap is sent when the peer has stopped responding as evidenced by
an LLDP timeout event. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.9 |
lldpXdcbxPeerConfigMismatchThis trap is sent when the configuration received from peer results
into partial or complete mismatch. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.6945.0.10 |
lldpXdcbxObjects OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.1 |
lldpXdcbxPortTableA list of all ports capable of supporting DCBX. SEQUENCE OF LldpXdcbxPortEntry .1.3.6.1.4.1.3320.127.1.5.6945.1.1 |
lldpXdcbxPortEntryAn entry containing DCBX control parameters for a particular port. LldpXdcbxPortEntry .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1 |
lldpXdcbxPortNumberEach 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.ro LldpPortNumber (LLDP-MIB) .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.1 |
lldpXdcbxPortEnableA device capable of any DCB feature must have DCBX enabled by default
with an option for DCBX to be administratively disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.2 |
lldpXdcbxPortVersionOperOperating version of the DCBX protocol. The system adjusts as needed
to operate at the highest version supported by both link partners.ro LldpXdcbxVersion .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.3 |
lldpXdcbxPortVersionMaxHighest DCBX protocol version supported by the system. Version numbers
start at zero. The DCBX protocol must be backward compatible with all
previous versions.ro LldpXdcbxVersion .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.4 |
lldpXdcbxPortSeqNoA value that changes each time an exchanged parameter in one or more
of the DCB feature TLVs changes.ro Integer32 .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.5 |
lldpXdcbxPortAckNoThe 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.ro Integer32 .1.3.6.1.4.1.3320.127.1.5.6945.1.1.1.6 |
lldpXdcbxFeatures OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.2 |
lldpXdcbxFeatTableA list of DCBX features configured on this system. SEQUENCE OF LldpXdcbxFeatEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.1 |
lldpXdcbxFeatEntryA entry containing DCBX feature parameters which are common to all
features. LldpXdcbxFeatEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1 |
lldpXdcbxFeatTypeType code of the DCB Feature. Following is a list of defined types:
2 Priority Groups
3 Priority Flow Control
4 Application Protocolrw LldpXdcbxFeatureType .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.1 |
lldpXdcbxFeatSubTypeSome 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.rw LldpXdcbxFeatureSubType .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.2 |
lldpXdcbxFeatVersionOperOperating version of the feature. The system adjusts to operate at the
highest version supported by both link partners.ro LldpXdcbxVersion .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.3 |
lldpXdcbxFeatVersionMaxHighest feature version supported by the system. Version numbers start
at zero. The feature must be backward compatible for all previous
versions.ro LldpXdcbxVersion .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.4 |
lldpXdcbxFeatEnableLocally administered parameter that indicates whether the DCB feature
is enabled or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.5 |
lldpXdcbxFeatWillingLocally 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.6 |
lldpXdcbxFeatErrorIndicates 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 TLVs for the same Type/SubType or the DCBX Control TLV also
causes Error to be set to TRUE.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.7 |
lldpXdcbxFeatAdvertiseLocally administered parameter that indicates whether this feature is
exchanged in the DCBX TLV. When Advertise is False, received TLVs for
this feature are ignored.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.8 |
lldpXdcbxFeatOperModeOperational state of the feature.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.9 |
lldpXdcbxFeatSyncdIndicates whether the current DesiredCfg has been received by the
peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.10 |
lldpXdcbxFeatSeqNoWhen Syncd is False, this indicates the value that SeqNo must
become equal to before Syncd can become True.ro Integer32 .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.11 |
lldpXdcbxFeatPeerWillingThe Willing state of the peer as received in a DCBX TLV from the
peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.12 |
lldpXdcbxFeatLocalParameterChangeIndicates that a configurable DCB Feature TLV field or state variable
has been modified on the local system.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.13 |
lldpXdcbxFeatPeerEnablePrivate Extension: The Feature Enable state of the peer as received in a DCBX TLV from the
peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.14 |
lldpXdcbxFeatPeerErrorPrivate Extension: The Feature Error state of the peer as received in a DCBX TLV from the
peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.15 |
lldpXdcbxFeatPeerAdvertisePrivate Extension: The Feature Advertisment state of the peer as received in a DCBX TLV from the
peer.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.16 |
lldpXdcbxFeatPeerTCPrivate 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.ro LldpXdcbxTCPeer .1.3.6.1.4.1.3320.127.1.5.6945.2.1.1.17 |
lldpXdcbxFeatPg OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.2.2 |
lldpXdcbxFeatPgNumTCsSupportedNumber of TCs supported by device.
Number of Priority Groups supported by a device can not be more than
number of TCs supported.rw LldpXdcbxTC .1.3.6.1.4.1.3320.127.1.5.6945.2.2.1 |
lldpXdcbxFeatPgPrioAllocTableA list of priorities and the their priority group assignment or
declaration of no bandwidth limit. SEQUENCE OF LldpXdcbxFeatPgPrioAllocEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2 |
lldpXdcbxFeatPgPrioAllocEntryAn entry for a priority which allows the priority to be assigned to a
priority group, or declared with no bandwidth limit. LldpXdcbxFeatPgPrioAllocEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2.1 |
lldpXdcbxFeatPgPrioAllocPrioIdThe priority which is to be assigned to a priority group, or defined
with no bandwidth limit.rw LldpXdcbxPriority .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2.1.1 |
lldpXdcbxFeatPgPrioAllocPgIdDesiredThe locally configured priority group value assigned to this
priority.rw LldpXdcbxPriorityGroup .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2.1.2 |
lldpXdcbxFeatPgPrioAllocPgIdOperThe 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.ro LldpXdcbxPriorityGroup .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2.1.3 |
lldpXdcbxFeatPgPrioAllocPgIdPeerThe priority group value that the peer desires to assign to this
priority.ro LldpXdcbxPriorityGroup .1.3.6.1.4.1.3320.127.1.5.6945.2.2.2.1.4 |
lldpXdcbxFeatPgBwAllocTableA list of priority group bandwidth allocations. SEQUENCE OF LldpXdcbxFeatPgBwAllocEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3 |
lldpXdcbxFeatPgBwAllocEntryAn entry for a priority group bandwidth allocation. LldpXdcbxFeatPgBwAllocEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3.1 |
lldpXdcbxFeatPgBwAllocPgIdThe priority group for which bandwidth is allocated in this table.rw LldpXdcbxPriorityGroup .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3.1.1 |
lldpXdcbxFeatPgBwAllocBwDesiredThe locally configured bandwidth allocated to this priority group.rw LldpXdcbxPgBw UNITS "percent" .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3.1.2 |
lldpXdcbxFeatPgBwAllocBwOperThe 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.ro LldpXdcbxPgBw UNITS "percent" .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3.1.3 |
lldpXdcbxFeatPgBwAllocBwPeerThe bandwidth allocation that the peer desires to assign to this
priority group.ro LldpXdcbxPgBw UNITS "percent" .1.3.6.1.4.1.3320.127.1.5.6945.2.2.3.1.4 |
lldpXdcbxFeatPfc OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.2.3 |
lldpXdcbxFeatPfcNumTCPFCSupportedNumber of TCs that can simultaneously support PFC.rw LldpXdcbxTCPFC .1.3.6.1.4.1.3320.127.1.5.6945.2.3.1 |
lldpXdcbxFeatPfcTableA list of priority flow control configurations for each priority. SEQUENCE OF LldpXdcbxFeatPfcEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2 |
lldpXdcbxFeatPfcEntryAn entry for configuring priority flow control for each priority. LldpXdcbxFeatPfcEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2.1 |
lldpXdcbxFeatPfcPriorityThe priority for which priority flow control is being configured.rw LldpXdcbxPriority .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2.1.1 |
lldpXdcbxFeatPfcEnableDesiredThe 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2.1.2 |
lldpXdcbxFeatPfcEnableOperThe 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2.1.3 |
lldpXdcbxFeatPfcEnablePeerThe priority flow control status that the peer desires to assign to
this priority.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.3.2.1.4 |
lldpXdcbxFeatAppProto OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.6945.2.4 |
lldpXdcbxFeatAppProtoTableA list of Application Protocol configurations. SEQUENCE OF LldpXdcbxFeatAppProtoEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1 |
lldpXdcbxFeatAppProtoEntryAn entry for configuring Application Protocol ID. LldpXdcbxFeatAppProtoEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1.1 |
lldpXdcbxFeatAppProtoIndexThe index of the Application Protocol being configured in a list of
Application Protocols.rw LldpXdcbxAppProtos .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1.1.1 |
lldpXdcbxFeatAppProtoSFThe value of the Selector Field for this application protocol.rw LldpXdcbxSF .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1.1.2 |
lldpXdcbxFeatAppProtoOUIThe value of the Application Protocol OUI for this application
protocol.rw Integer32 .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1.1.3 |
lldpXdcbxFeatAppProtoIdThe value of the Application Protocol ID for this application
protocol.rw INTEGER .1.3.6.1.4.1.3320.127.1.5.6945.2.4.1.1.4 |
lldpXdcbxFeatAppProtoPrioTableA list of priority configurations for each application protocol. SEQUENCE OF LldpXdcbxFeatAppProtoPrioEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2 |
lldpXdcbxFeatAppProtoPrioEntryAn entry for selecting priorities for the Application Protocol. LldpXdcbxFeatAppProtoPrioEntry .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2.1 |
lldpXdcbxFeatAppProtoPriorityThe priority for which Application Protocol is being configured.rw LldpXdcbxPriority .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2.1.1 |
lldpXdcbxFeatAppProtoEnableDesiredThe locally configured status of Application Protocol for this
priority.
0: Disabled
1: Enabledrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2.1.2 |
lldpXdcbxFeatAppProtoEnableOperThe 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2.1.3 |
lldpXdcbxFeatAppProtoEnablePeerThe Application Protocol status that the peer desires to assign to
this priority.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.6945.2.4.2.1.4 |