A customer with a gateway connected to a device on gigabitethernet 0/0/3 configures an Asset...

In Aruba gateways/switches, LLDP decodes and displays standard LLDP TLVs by default. LLDP-MED inventory TLVs (including Asset ID) are shown only when LLDP-MED is enabled.

When LLDP-MED is not enabled, received MED TLVs are counted as Unknown TLVs and are not decoded in the neighbor detail output.

In the exhibit, show lldp statistics shows “Unknown TLVs: 2” and show lldp neighbor ... detail displays only basic LLDP fields (Chassis ID, Mgmt Address, Port Description, MTU), with no MED inventory fields such as Asset ID. This is the expected symptom of LLDP-MED being disabled.

LLDP TX is not required to receive and display neighbor TLVs; the missing Asset ID is unrelated to transmit state. MTU is also not relevant to TLV decoding.

References (HPE Aruba official materials): Aruba AOS-CX LLDP/LLDP-MED configuration—MED must be enabled to advertise/parse MED inventory TLVs (Asset ID, Serial, HW/FW/SW, etc.).