All MIBs › LLDP-EXT-MED-MIB › lldpXMedPortConfigTLVsTxEnable
lldpXMedPortConfigTLVsTxEnable
Module: LLDP-EXT-MED-MIB
OID (symbolic): LLDP-EXT-MED-MIB::lldpXMedPortConfigTLVsTxEnable
OID (numeric): 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2
Node type: OBJECT-TYPE
Type: LldpXMedCapabilities
Access: read-write
Description: The lldpXMedPortConfigTLVsTxEnable, defined as a bitmap, includes the MED organizationally defined set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent will send the corresponding TLV if the respective capability is supported per port.
Setting a bit with in this object for a non-supported capability shall have no functional effect and will result in an inconsistent value error returned to the management application.
There are other rules and restrictions that prevent arbitrary combinations of TLVs to be enabled on LLDP-MED devices according to the device classes. These rules are defined in Section 10.2.1, Tables 5 - 9 of ANSI/TIA-1057. In case a management application attempts to set this object to a value that does not follow the rules, the set operation shall have and will result in an inconsistent value error returned to the management application.
Setting this object to an empty set is valid and effectively disables LLDP-MED on a per-port basis by disabling transmission of all MED organizational TLVs. In this case the remote tables objects in the LLDP-MED MIB corresponding to the respective port will not be populated.
The default value for lldpXMedPortConfigTLVsTxEnable object is an empty set, which means no enumerated values are set.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
What is lldpXMedPortConfigTLVsTxEnable?
A read-write bitmap letting you choose which optional LLDP-MED TLVs (network policy, location, PoE, inventory) this port actually transmits; setting a bit the port doesn't support per lldpXMedPortCapSupported returns an inconsistent-value error, and clearing all bits disables LLDP-MED on that port.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2 snmpwalk -v2c -c public <target> LLDP-EXT-MED-MIB::lldpXMedPortConfigTLVsTxEnable
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2.1 snmpget -v2c -c public <target> LLDP-EXT-MED-MIB::lldpXMedPortConfigTLVsTxEnable.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2.1 s <value>
Start monitoring Vendor-neutral TIA/IEEE standard, LLDP-MED (LAN switch/VoIP phone or media endpoint) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LLDP-EXT-MED-MIB::lldpXMedPortConfigTLVsTxEnable OID value, configure state conditions and alerts, and monitor any Vendor-neutral TIA/IEEE standard, LLDP-MED (LAN switch/VoIP phone or media endpoint) 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.4795 | lldpXMedMIB | LLDP-EXT-MED-MIB |
| 1.0.8802.1.1.2.1.5.4795.1 | lldpXMedObjects | LLDP-EXT-MED-MIB |
| 1.0.8802.1.1.2.1.5.4795.1.1 | lldpXMedConfig | LLDP-EXT-MED-MIB |
| 1.0.8802.1.1.2.1.5.4795.1.1.2 | lldpXMedPortConfigTable | LLDP-EXT-MED-MIB |
| 1.0.8802.1.1.2.1.5.4795.1.1.2.1 | lldpXMedPortConfigEntry | LLDP-EXT-MED-MIB |
| 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2 | lldpXMedPortConfigTLVsTxEnable | LLDP-EXT-MED-MIB |