1lldpad(8) System Manager's Manual lldpad(8)
2
3
4
6 lldpad - Link Layer Discovery Protocol (LLDP) agent daemon
7
9 lldpad [-h] [-v] [-V level] [-d] [-k] [-p] [-s] [-t] [-f filename]
10
12 Executes the LLDP protocol for supported network interfaces. The list
13 of TLVs currently supported are:
14
15 - IEEE 802.1AB Mandatory TLVs
16
17 - IEEE 802.1AB Basic Management TLVs
18
19 - IEEE 802.3 Organizationally Specific TLVs
20
21 - LLDP-MED Organizationally Specific TLVs
22
23 - Data Center Bridging capabilities exchange protocol (DCBX) TLVs
24
25 - Edge Virtual Bridging (EVB) TLVs
26
27 Capabilities of lldpad include:
28
29 - Transmission of LLDP PDUs containing enabled TLVs from enabled
30 ports.
31
32 - Reception of LLDP PDUs from enabled ports.
33
34 - Operation of the DCBX protocol for interfaces which support the
35 DCB rtnetlink interface. This includes operation of the DCBX
36 state machines above LLDP and corresponding configuration of the
37 DCB parameters of the network interface. Supported DCB features
38 are: Extended Transmission Selection, Priority Flow Control and
39 the FCoE application.
40
41 - Configuring the DCB settings of the network driver based on the
42 operation of DCBX.
43
44 - Provides a multi-channel interface for client applications to
45 query and configure features. Events are also generated on the
46 client interface to inform clients of changes. The lldpad pack‐
47 age includes two clients: lldptool for general LLDP agent man‐
48 agement and dcbtool for DCB management.
49
50 lldpad supports the versions of the DCB capabilities exchange (DCBX)
51 protocol listed as follows:
52
53 version 1 - also known as CIN DCBX
54 <http://download.intel.com/technology/eedc/dcb_cep_spec.pdf>
55
56 version 2 - also known as CEE DCBX
57 <http://www.ieee802.org/1/files/public/docs2008/az-wadekar-dcbx-
58 capability-exchange-discovery-protocol-1108-v1.01.pdf>
59
60 IEEE DCBX
61 See the IEEE 802.1Qaz-2011 specification for details.
62
63 IEEE DCBX is the default DCBX mode for a DCB capable interface so the
64 default and configured IEEE DCBX TLVs will be transmitted when the
65 interface comes up. lldpad can be globally configured to support one
66 of the legacy DCBX versions (CIN or CEE). If the remote LLDP agent
67 does not transmit any IEEE DCBX TLVs and does transmit a legacy DCBX
68 TLV which matches the configured legacy DCBX version, then the DCBX
69 mode will drop back to legacy DCBX mode. It will not transition back
70 to IEEE DCBX mode until the next link reset. If lldpad has dropped
71 back to legacy DCBX mode for a given interface and the daemon is
72 stopped and restarted, the legacy DCBX mode for that interface will be
73 used instead of starting out in IEEE DCBX mode. This behavior only
74 applies to the case where lldpad is restarted and is not persistent
75 across a system reboot.
76
77 See dcbtool for information on how to globally configure which legacy
78 version of DCBX lldpad executes.
79
80 See lldptool for information on how to reset the DCBX mode of an inter‐
81 face back to default (starts out in IEEE DCBX mode).
82
83 lldpad also supports edge virtual bridging as currently under specifi‐
84 cation in the IEEE 802.1Qb working group.
85 <http://www.ieee802.org/1/pages/802.1bg.html>
86
87
89 lldpad has the following command line options:
90
91 -h show usage information
92
93 -f filename
94 use the specified file as the configuration file instead of the
95 default file: /var/lib/lldpad/lldpad.conf lldpad expects the
96 directory of the configuration file to exist, but if the config‐
97 uration file does not exist, then a default configuration file
98 will be created. lldpad creates and maintains the contents of
99 the configuration file. Configuration should be performed by
100 using lldptool or dcbtool.
101
102 -d run lldpad as a daemon
103
104 -v show lldpad version
105
106 -V level
107 set lldpad debugging level. Uses syslog debug levels see sys‐
108 log.2 for details.
109
110 -k used to terminate the first instance of lldpad that was started
111 (e.g. from initrd). Once lldpad -k has been invoked and lldpad
112 has been restarted, subsequent invocations of lldpad -k will not
113 terminate lldpad.
114
115
116 -s remove lldpad state records from shared memory
117
118 -p do not create PID file /var/run/lldpad.pid on startup
119
120 -t omit timestamps from logging messages
121
123 On termination, lldpad does not undo any of the configurations that it
124 has set. This approach minimizes the risk of restarting the daemon to
125 perform a software update, or of having storage issues during shutdown.
126 Ongoing operation of network interfaces that had been controlled by
127 lldpad may result in unexpected behavior.
128
129
131 dcbtool(8), lldptool(8), lldptool-dcbx(8), lldptool-ets(8), lldptool-
132 pfc(8), lldptool-app(8), lldptool-med(8), lldptool-vdp(8), lldptool-
133 evb(8)
134
135
137 lldpad - LLDP agent daemon with DCBX support
138 Copyright(c) 2007-2012 Intel Corporation. Portions of lldpad are
139 based on:
140
141 hostapd-0.5.7
142
143 Copyright
144 (c) 2004-2008, Jouni Malinen <j@w1.fi>
145
147 This program is free software; you can redistribute it and/or modify it
148 under the terms and conditions of the GNU General Public License, ver‐
149 sion 2, as published by the Free Software Foundation.
150
151 This program is distributed in the hope it will be useful, but WITHOUT
152 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
153 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
154 for more details.
155
156 You should have received a copy of the GNU General Public License along
157 with this program; if not, write to the Free Software Foundation, Inc.,
158 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
159
160 The full GNU General Public License is included in this distribution in
161 the file called "COPYING".
162
164 Contact Information: open-lldp Mailing List <lldp-devel@open-lldp.org>
165
166
167
168 March 23, 2012 lldpad(8)