lldptool(8)
π lldptool(8) β APP π
okay bestie, welcome to the lldptool girlies' guide to the APP TLV β¨ this one lives in the Linux manual pages and it's literally all about showing off and manipulating your APP TLV configuration π
πΈ NAME πΈ
APP β show / manipulate APP TLV configuration π¦
β¨ SYNOPSIS β¨
lldptool -t -i ethx -V APP [-c app]
lldptool -T -i ethx -V APP [-d] app=prio,sel,pid
like. that's the whole vibe. two modes, that's it π
π DESCRIPTION π
okay so the APP TLV is an informational TLV β it's giving "just here to share the news", no cap. It advertises the current configured application table π’
and here's the tea: if the peer APP TLV and a local APP TLV both match on the same selector and protocol field, then the local parameter is used. local wins, periodt. π
π ARGUMENTS π
appβ sets up a local application data field using three lil parameters: priority (prio), selector (sel), and protocol (pid). and if you pass the-doption too? it removes the entry that matches all three of those parameters ποΈβ¨
π§ Theory of Operations π§
so for most end stations, the APP TLV is an informational TLV. it is not expected that setting APP data should be required β like, chill, you probably don't need to touch it π«Ά
by default, peer data gets processed and added to the application data table automatically, assuming there isn't already a local entry with matching selector and priority fields. (key word: assuming π)
and why do we even care? because once APP data is in the application table, it's available for applications β eg iscsid β to query π those applications query for a specific protocol and selector, and they can use that data to map traffic to the corresponding traffic class. it's giving matchmaker energy honestly π
π EXAMPLE & USAGE π
Configure ISCSI application for priority 4 on eth2
lldptool -T -i eth2 -V APP app=4,2,3260
Configure FCoE application for priority 3 on eth2
lldptool -T -i eth2 -V APP app=3,1,35078
Remove FCoE application for priority 3 on eth2
lldptool -T -i eth2 -V APP -d app=3,1,35078
Display locally configured application table on eth2
lldptool -t -i eth2 -V APP -c app
Display last transmitted APP TLV on eth2
lldptool -t -i eth2 -V APP
see? iconic. ate and left no crumbs π
β SOURCE β
- IEEE 802.1Qaz (http://www.ieee802.org/1/pages/dcbridges.html)
π SEE ALSO π
π AUTHOR π
John Fastabend
fr fr, that's the whole page. go configure some application tables, bestie, you've got this πͺπ¦
open-lldp Β· February 2010 β yeah she's vintage, but she's still serving π mwah π
π¦ where this page comes from
- alpine 3.22: open-lldp-doc 1.1-r2 Β· GPL-2.0-only
- alpine 3.23: open-lldp-doc 1.1-r3 Β· GPL-2.0-only
- alpine 3.24: open-lldp-doc 1.1-r3 Β· GPL-2.0-only
- centos-stream 10: lldpad 1.1.1-4.gitf1dd9eb.el10 Β· GPL-2.0-only
- centos-stream 9: lldpad 1.1.1-5.gitf1dd9eb.el9 Β· GPL-2.0-only
- centos-stream 9: lldpad 1.1.1-5.gitf1dd9eb.el9 Β· GPL-2.0-only
- debian bookworm: lldpad 1.1+git20221028.aa18720-1 Β· GPL-2.0-only
- debian trixie: lldpad 1.1.1-1+b1 Β· GPL-2.0-only
- fedora 43: lldpad 1.1.0-14.git85e5583.fc43 Β· GPL-2.0-only
- fedora 43: lldpad 1.1.0-14.git85e5583.fc43 Β· GPL-2.0-only
- fedora 44: lldpad 1.1.0-16.git85e5583.fc44 Β· GPL-2.0-only
- fedora 44: lldpad 1.1.0-16.git85e5583.fc44 Β· GPL-2.0-only
- opensuse-leap 16.0: open-lldp 1.1+110.f16f944-160000.1.1 Β· GPL-2.0-only
- opensuse-leap 16.0: open-lldp 1.1+110.f16f944-160000.1.1 Β· GPL-2.0-only
- opensuse-leap 16.0: open-lldp 1.1+110.f16f944-160000.1.1 Β· GPL-2.0-only
- opensuse-leap 16.0: open-lldp 1.1+110.f16f944-160000.1.1 Β· GPL-2.0-only
- ubuntu jammy: lldpad 1.1-1 Β· GPL-2.0-only
- ubuntu noble: lldpad 1.1+git20221028.aa18720-2 Β· GPL-2.0-only
- ubuntu questing: lldpad 1.1.1-1build1
- ubuntu resolute: lldpad 1.1.1-1build2 Β· GPL-2.0-only
- ubuntu stonking: lldpad 1.1.1-1build2 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms