1 .\" Copyright (c) 2006 Pierre-Yves Ritschard <pyr@openbsd.org>
2 .\" Copyright (c) 2008 Vincent Bernat <bernat@luffy.cx>
4 .\" Permission to use, copy, modify, and/or distribute this software for any
5 .\" purpose with or without fee is hereby granted, provided that the above
6 .\" copyright notice and this permission notice appear in all copies.
8 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
9 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
10 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
11 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
12 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
13 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
14 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16 .Dd $Mdocdate: July 16 2008 $
21 .Nd control LLDP daemon
37 When no specific option is given,
39 displays the list of discovered neighbors along with
40 some of their advertised capabilities. If some interfaces are given,
41 only those interfaces will be displayed.
43 The options are as follows:
46 Enable more debugging information.
52 Display all remote ports, including those hidden by the smart filter.
54 Choose the output format. Currently
59 formats are available. The default is
62 Enable the transmission of LLDP-MED location TLV for the given
63 interfaces. This option can be repeated several times to enable the
64 transmission of the location in several formats. Several formats are
67 .It Em Coordinate based location
71 .Ar 1:48.85667N:2.2014E:117.47:m:1
72 The first digit is always
74 It is followed by the latitude, a letter for the direction (
78 for East or West), the longitude and a letter for the direction (
82 ). The next figure is the altitude. It can be expressed in meters (the
85 ) or in floors (the letter should be
87 ). The last digit is the datum. It can either be
95 The location can be expressed as an address. The format of the
97 .Ar 2:FR:6:Commercial Rd:3:Roseville:19:4
98 The first digit is always
100 The next two letters are the country code. Then, arguments are paired
101 to form the address. The first member of the pair is a digit
102 indicating the type of the second member. Here is the list of
104 .Bl -tag -width "XXXX." -compact
108 National subdivisions
110 County, parish, district
114 City division, borough, ward
120 Leading street direction
122 Trailing street suffix
130 Landmark or vanity address
132 Additional location info
151 This is a numerical string using for setting up emergency call. The
152 format of the location is then the following:
154 where the first digit should be
156 and the second argument is the ELIN number.
159 When setting a location for a given port, all previous locations are
160 erased. To erase all location, just use the empty string. There is
161 currently no way to get the location from the command line.
164 Enable the transmission of LLDP-MED Network Policy TLVs for the given
165 interfaces. This option can be repeated several times to specify
166 different policies. Format (without spaces!):
181 Valid application types (see ANSI/TIA-1057 table 12):
182 .Bl -tag -width "X." -compact
190 Guest Voice Signaling
202 .Bl -tag -width "X." -compact
204 Network policy for the specified application type is defined.
206 Network policy for the specified application type is required by
207 the device but is currently unknown. This is used by Endpoint
208 Devices, not by Network Connectivity Devices.
212 .Bl -tag -width "X." -compact
214 Untagged VLAN. In this case the VLAN ID and the Layer 2 Priority
215 are ignored and only the DSCP value has relevance.
220 IEEE 802.1q VLAN ID (VID). A value of 1 through 4094 defines a
221 VLAN ID. A value of 0 means that only the priority level is
224 IEEE 802.1d / IEEE 802.1p Layer 2 Priority, also known as Class of Service
225 (CoS), to be used for the specified application type.
226 .Bl -tag -width "X." -compact
232 Best Effort (default)
245 DiffServ/Differentiated Services Code Point (DSCP) value as defined
246 in IETF RFC 2474 for the specified application type. Value: 0 (default
247 per RFC 2475) through 63. Note: The class selector DSCP values are
248 backwards compatible for devices that only support the old IP
249 precedence Type of Service (ToS) format. (See the RFCs for what
252 .Bl -tag -width "X." -compact
253 .It Sy 1:0:1:500:6:46
254 Voice (1): not unknown (0), tagged (1), VLAN-ID 500, l2 prio Voice (6), DSCP 46 (EF, Expedited Forwarding)
255 .It Sy 2:0:1:500:3:24
256 Voice Signaling (2): not unknown (0), tagged (1), VLAN-ID 500, l2 prio
257 Excellent Effort (3), DSCP 24 (CS3, Class Selector 3)
262 Enable the transmission of LLDP-MED POE-MDI TLV for the given
263 interfaces. One can act as a PD (power consumer) or a PSE (power
264 provider). No check is done on the validity of the parameters while
265 LLDP-MED requires some restrictions:
268 PD shall never request more power than physical 802.3af class.
270 PD shall never draw more than the maximum power advertised by PSE.
272 PSE shall not reduce power allocated to PD when this power is in use.
274 PSE may request reduced power using conservation mode
276 Being PSE or PD is a global paremeter, not a per-port parameter.
278 does not enforce this: a port can be set as PD or PSE. LLDP-MED also
279 requires for a PSE to only have one power source (primary or
282 does not enforce this. Each port can have its own power source. The
283 same applies for PD and power priority. LLDP-MED MIB does not allow
284 this kind of representation.
287 This option is distinct of
289 option. You may want to use both options at the same time.
291 The format of this option is (without spaces):
303 .Bl -tag -width "XXX." -compact
305 Power Sourcing Entity (power provider)
307 Power Device (power consumer)
311 .Bl -tag -width "X." -compact
315 For PSE, the power source is the primary power source.
317 For PSE, the power source is the backup power source or a power
318 conservation mode is asked (the PSE may be running on UPS for
321 For PD, the power source is the PSE.
323 For PD, the power source is a local source.
325 For PD, the power source is both the PSE and a local source.
328 Four priorities are available:
329 .Bl -tag -width "X." -compact
340 For PD, the power value is the total power in milliwatts required
341 by a PD device from the PSE device.
344 Enable the transmission of Dot3 POE-MDI TLV for the given
345 interfaces. One can act as a PD (power consumer) or a PSE (power
346 provider). This option is distinct of the
348 option. You might want to use both. Contrary to LLDP-MED POE-MDI TLV,
349 Dot3 POE-MDI TLV are strictly per-port values.
351 The format of this option is (without spaces):
378 .Bl -tag -width "XXX." -compact
380 Power Sourcing Entity (power provider)
382 Power Device (power consumer)
386 .Bl -tag -width "X." -compact
388 The signal pairs only are in use.
390 The spare pairs only are in use.
393 Five classes are available:
394 .Bl -tag -width "X." -compact
414 can be set to to 0 or 1.
416 means that MDI power is supported on the given port.
418 means that MDI power is enabled on the given port.
420 is used to indicate if the pair selection can be controlled on the
426 (and remaining values) are optional. They are only requested in
427 conformance with 802.3at.
429 should be either 1 or 2. For source, use one of the following values:
431 .Bl -tag -width "X." -compact
435 For PD, the power source is the PSE. For PSE, the power source is the
436 primary power source.
438 For PD, the power source is a local source. For PSE, the power source
439 is the backup power source or a power conservation mode is asked (the
440 PSE may be running on UPS for example).
442 For PD, the power source is both the PSE and a local source. For PSE,
443 this value should not be used.
447 see what is done for LLDP-MED MDI/POE.
451 are respectively the PD requested power value and the PSE allocated
452 power value. This should be expressed in milliwatts.
455 .Bl -tag -width "/var/run/lldpd.socketXX" -compact
456 .It /var/run/lldpd.socket
457 Unix-domain socket used for communication with
466 program was written by
467 .An Vincent Bernat Aq bernat@luffy.cx .