Status in source: current.
Names: lldpXdcbxLldpTxDisabled
Technical details
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"lldpXdcbxLldpTxDisabled",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"lldpXdcbxPortNumber",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"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.\"",
"::=",
"{",
"lldpXdcbxNotifications",
"4",
"}"
],
"syntax_tree": [
[
"Objects",
[
"lldpXdcbxPortNumber"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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."
],
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: LLDP-EXT-DCBX-MIB
See published definition above
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages:
- NETGEAR official product and EOL MIB downloads
· Publisher's source file: Source package: MS510TX_TXPP_MIBS_V6.7.0.43.zip
Module: LLDP-EXT-DCBX-MIB
See published definition above
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages:
Same file in MX510TX_MS510TXPP_MIBS_ODM_V6.7.0.42.zip.
Same file in MS510TX_TXPP_V6.7.0.37_MIB_V6.7.0.37.zip.
- Common and standard MIB copies (LibreNMS/Observium Community)
· Publisher's source file: LLDP-EXT-DCBX-MIB
Vendor MIB copy from the LibreNMS archive.
Module: LLDP-EXT-DCBX-MIB
See published definition above
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages: