lldptool(8)

✨ lldptool(8) ✨ — the LLDP-MED one, bestie 💖

okay so this is lldptool(8), the Linux manual page for the LLDP-MED stuff — aka Show / manipulate MED TLV configurations. sit down, grab a strawberry 🍓, we're doing Link Layer Discovery today and it's gonna be lowkey fun.

🌸 NAME 🌸

LLDP-MED — Show / manipulate MED TLV configurations 💅

🎀 SYNOPSIS 🎀

like, here's the whole vibe in one glance:

lldptool -t -i ethx -V [ TLV_TYPE ] enableTx

lldptool -T -i ethx -V [ TLV_TYPE ] enableTx = { yes | no }

lldptool -T -i ethx -V LLDP-MED devtype = { class1 | class2 | class3 |
none }

lldptool -t -i ethx -V LLDP-MED devtype

TLV_TYPE : = {LLDP-MED | medCap | medPolicy | medLoc | medPower | medHwRev |
       medFwRev | medSwRev | medSerNum | medManuf | medModel | medAssetID }

not me writing -t lowercase for query and -T uppercase for *set*… yes bestie, case matters, they are literally different flags 🙈

🦋 DESCRIPTION 🦋

so the LLDP-MED extensions are here to support the Link Layer Discovery Protocol for Media Endpoint Devices, which is defined in the ANSI/TIA-1057-2006 document — iconic, no notes.

Every single TLV can be configured as a class1, class2 or class3 device, and the class system goes like this:

• Class I devices are the most basic class of Endpoint Device.
• Class II devices support media stream capabilities.
• Class III devices directly support end users of the IP communication system.

want the actual clarification of class types? go read ANS-TIA-1057, periodt. (yes, that's spelled exactly like that up there, i'm just the messenger 🫶)

💜 ARGUMENTS 💜

• enableTx — Enables the TLV to be transmitted. it's giving "turn it on so it actually goes out" ✨
• devtype — Set or query the class type of the device. main character energy, honestly 👑

🌈 TLV_TYPE 🌈

the list of supported TLV specifiers that apply to Media Endpoint Devices — collect them all like pokémon:

• LLDP-MED — apply arguments to all supported MED TLVs. the "do it to everything" button, obsessed 💖
• medCAP — LLDP-MED Capabilities TLV
• medPolicy — LLDP-MED Network Policy TLV
• medLoc — LLDP-MED Location TLV
• medPower — LLDP-MED Extended Power-via-MDI TLV
• medHwRev — LLDP-MED Hardware Revision TLV
• medFwRev — LLDP-MED Firmware Revision TLV
• medSwRev — LLDP-MED Software Revision TLV
• medSerNum — LLDP-MED Serial Number TLV
• medManuf — LLDP-MED Manufacturer Name TL
• medModel — LLDP-MED Model Name TLV
• medAssetID — LLDP-MED Asset ID TLV

💀 yes medCAP up there has the capitals and the synopsis spells it medCap. and yes, medManuf says "TL" not "TLV". i am not fixing it, i am reporting it. fr fr.

🔥 EXAMPLE & USAGE 🔥

here's where it gets good. three little recipes, chef's kiss 👩‍🍳

Enable class1 MED device on eth2

lldptool -T -i eth2 -V LLDP-MED enableTx=yes devtype=class1

Query class type of MED on eth2

lldptool -t -i eth2 -V LLDP-MED -c devtype

Query transmit state of medPolicy on device eth2

lldptool -t -i eth2 -V medPolicy -c enableTx

see the pattern? -T to set, -t to peek, -c to say what you wanna peek at. ate 💅

⭐ SOURCE ⭐

• Link Layer Discovery Protocol for Media Endpoint Devices (http://www.tiaonline.org/standards/technology/voip/documents/ANSI-TIA-1057_final_for_publication.pdf)

🧚 NOTES 🧚

literally nothing here. the NOTES section is empty, bestie. it's giving "silence is a valid note". enjoy the peace and quiet 🌸

🎀 SEE ALSO 🎀

go read your siblings, they're all icons:

• lldptool(8)
• lldpad(8)

👑 AUTHOR 👑

John Fastabend

and that's the whole page, no cap 💖 this one came from open-lldp and it's dated June 2011 — yes, 2011, vintage, retro, still slaying 🦋 ty for reading bestie, go configure some TLVs, i believe in you 🫶✨