All MIBs › LLDP-EXT-DCBX-MIB › lldpXdcbxLldpTxDisabled
lldpXdcbxLldpTxDisabled
Module: LLDP-EXT-DCBX-MIB
OID (symbolic): LLDP-EXT-DCBX-MIB::lldpXdcbxLldpTxDisabled
OID (numeric): 1.0.8802.1.1.2.1.5.6945.0.4
Node type: NOTIFICATION-TYPE
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.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' LLDP-EXT-DCBX-MIB::lldpXdcbxLldpTxDisabled snmptrap -v2c -c public <manager> '' 1.0.8802.1.1.2.1.5.6945.0.4
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:52054->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (359447894) 41 days, 14:27:58.94 SNMPv2-MIB::snmpTrapOID.0 = OID: LLDP-EXT-DCBX-MIB::lldpXdcbxLldpTxDisabled
Start monitoring Vendor-neutral IEEE/industry standard (data-center Ethernet switches/NICs, DCBX) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LLDP-EXT-DCBX-MIB::lldpXdcbxLldpTxDisabled OID value, configure state conditions and alerts, and monitor any Vendor-neutral IEEE/industry standard (data-center Ethernet switches/NICs, DCBX) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.0 | std | START-MIB |
| 1.0.8802 | iso8802 | START-MIB |
| 1.0.8802.1 | ieee802dot1 | START-MIB |
| 1.0.8802.1.1 | ieee802dot1mibs | START-MIB |
| 1.0.8802.1.1.2 | lldpMIB | LLDP-MIB |
| 1.0.8802.1.1.2.1 | lldpObjects | LLDP-MIB |
| 1.0.8802.1.1.2.1.5 | lldpExtensions | LLDP-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.0.8802.1.1.2.1.5.6945 | lldpXdcbxMIB | LLDP-EXT-DCBX-MIB |
| 1.0.8802.1.1.2.1.5.6945.0 | lldpXdcbxNotifications | LLDP-EXT-DCBX-MIB |
| 1.0.8802.1.1.2.1.5.6945.0.4 | lldpXdcbxLldpTxDisabled | LLDP-EXT-DCBX-MIB |