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 $
22 .Nd control LLDP daemon
42 When no command is specified,
44 will start an interactive shell which can be used to input arbitrary
45 commands as if they were specified on the command line. This
46 interactive shell should provide completion and history support.
48 The options are as follows:
51 Enable more debugging information. This flag can be repeated.
53 Specify the Unix-domain socket used for communication with
58 version. When repeated, show more build information.
60 Choose the output format. Currently
67 formats are available. The default is
72 but the structure of the JSON object is not affected by the number of
73 interfaces or the number of neighbors. It is therefore easier to
76 Read the given configuration file. This option may be repeated several
77 times. If a directory is provided, each file contained in it will be
80 Order is alphabetical.
86 will display detailed information about each neighbors on the
87 specified interfaces or on all interfaces if none are specified. This
88 command is mostly kept for backward compatibility with older versions.
90 The following commands are supported by
92 When there is no ambiguity, the keywords can be abbreviated. For
94 .Cd show neighbors ports eth0 summary
96 .Cd sh neigh p eth0 sum
98 .Bd -ragged -offset XX
100 .Bd -ragged -offset XXXXXX
106 .Bd -ragged -offset XXXXXX
107 Display general help or help about a command. Also, you can get help
108 using the completion or by pressing the
110 key. However, completion and inline help may be unavailable if
112 was compiled without readline support but
114 command is always available.
118 .Op ports Ar ethX Op ,...
119 .Op Cd details | summary
121 .Bd -ragged -offset XXXXXX
122 Display information about each neighbor known by
126 only the name and the port description of each remote host will be
127 displayed. On the other hand, with
129 all available information will be displayed, giving a verbose
132 also display remote ports hidden by the smart filter. When specifying
133 one or several ports, the information displayed is limited to the
138 .Op ports Ar ethX Op ,...
139 .Op Cd details | summary
141 .Bd -ragged -offset XXXXXX
142 Display information about each local interface known by
146 only the name and the port description of each local interface will be
147 displayed. On the other hand, with
149 all available information will be displayed, giving a verbose
152 also display local ports hidden by the smart filter. When specifying
153 one or several ports, the information displayed is limited to the
158 .Op Cd details | summary
159 .Bd -ragged -offset XXXXXX
160 Display information about local chassis. With
162 most details are skipped. On the other hand, with
164 all available information will be displayed, giving a verbose
169 .Op ports Ar ethX Op ,...
170 .Op Cd details | summary
173 .Bd -ragged -offset XXXXXX
174 Watch for any neighbor changes and report them as soon as they
175 happen. When specifying ports, the changes are only reported when
176 happening on the given ports.
180 have the same meaning than previously described. If
184 will exit after receiving the specified number of events.
187 .Cd show configuration
188 .Bd -ragged -offset XXXXXX
189 Display global configuration of
195 .Op ports Ar ethX Op ,...
197 .Bd -ragged -offset XXXXXX
198 Report LLDP-related statistics, like the number of LLDPDU transmitted,
199 received, discarded or unrecognized. When specifying ports, only the
200 statistics from the given port are reported. With
202 the statistics of each port is summed.
206 .Bd -ragged -offset XXXXXX
209 update its information and send new LLDP PDU on all interfaces.
213 .Cd system hostname Ar name
214 .Bd -ragged -offset XXXXXX
215 Override system hostname with the provided value. By default, the
216 system name is the FQDN found from the resolved value of
218 As a special value, use "." (dot) to use the short hostname instead of
224 .Bd -ragged -offset XXXXXX
225 Do not override system hostname and restore the use of the node name.
229 .Cd system description Ar description
230 .Bd -ragged -offset XXXXXX
231 Override chassis description with the provided value instead of using
232 kernel name, node name, kernel version, build date and architecture.
236 .Cd system description
237 .Bd -ragged -offset XXXXXX
238 Do not override chassis description and use a value computed from node
239 name, kernel name, kernel version, build date and architecture instead.
243 .Cd system chassisid Ar description
244 .Bd -ragged -offset XXXXXX
245 Override chassis ID with the provided value instead of using MAC address
246 from one interface or host name.
251 .Bd -ragged -offset XXXXXX
252 Do not override chassis ID and use a value computed from one of the interface
253 MAC address (or host name if none is found).
257 .Cd system platform Ar description
258 .Bd -ragged -offset XXXXXX
259 Override platform description with the provided value instead of using
260 kernel name. This value is currently only used for CDP.
265 .Bd -ragged -offset XXXXXX
266 Do not override platform description and use the kernel name. This
267 option undoes the previous one.
271 .Cd system capabilities enabled Ar capabilities
272 .Bd -ragged -offset XXXXXX
273 Override system capabilities with the provided value instead of using
274 kernel information. Several capabilities can be specified separated by
275 commas. Only available capabilities can be enabled. Valid capabilities are:
276 .Bl -tag -width "XXX." -compact -offset XX
286 Here is an example of use:
287 .D1 configure system capabilities enabled bridge,router
292 .Cd system capabilities enabled
293 .Bd -ragged -offset XXXXXX
294 Do not override capabilities and use the kernel information. This option
295 undoes the previous one.
299 .Cd system interface pattern Ar pattern
300 .Bd -ragged -offset XXXXXX
301 Specify which interface to listen and send LLDPDU to. Without this
304 will use all available physical interfaces. This option can use
305 wildcards. Several interfaces can be specified separated by commas.
306 It is also possible to remove an interface by prefixing it with an
307 exclamation mark. It is possible to allow an interface by
308 prefixing it with two exclamation marks. An allowed interface beats
309 a forbidden interfaces which beats a simple matched interface. For
313 will only use interfaces starting by
315 with the exception of
322 will use all interfaces, except interfaces starting by
324 with the exception of
326 When an exact match is found, it will circumvent some tests. For example, if
328 is specified, it will be accepted even if this is a VLAN interface.
332 .Cd system interface pattern
333 .Bd -ragged -offset XXXXXX
334 Remove any previously configured interface pattern and use all
335 physical interfaces. This option undoes the previous one.
339 .Cd system interface permanent Ar pattern
340 .Bd -ragged -offset XXXXXX
341 Specify interfaces whose configuration is permanently kept by
345 disregard any data about interfaces when they are removed from the
346 system (statistics, custom configuration). This option allows one to
347 specify a pattern similar to the interface pattern. If an interface
348 disappear but matches the pattern, its data is kept in memory and
349 reused if the interface reappear at some point. For example, on Linux,
350 one could use the pattern
352 which should match fixed interfaces on most systems.
356 .Cd system interface permanent
357 .Bd -ragged -offset XXXXXX
358 Remove any previously configured permanent interface pattern. Any
359 interface removed from the system will be forgotten. This option
360 undoes the previous one.
364 .Cd system interface description
365 .Bd -ragged -offset XXXXXX
366 Some OS allows the user to set a description for an interface. Setting
367 this option will enable
369 to override this description with the name of the peer neighbor if one
370 is found or with the number of neighbors found.
374 .Cd system interface description
375 .Bd -ragged -offset XXXXXX
376 Do not update interface description with the name of the peer
377 neighbor. This option undoes the previous one.
381 .Cd system interface promiscuous
382 .Bd -ragged -offset XXXXXX
383 Enable promiscuous mode on managed interfaces.
385 When the interface is not managed any more (or when quitting
387 the interface is left in promiscuous mode as it is difficult to know
388 if someone else also put the interface in promiscuous mode.
390 This option is known to be useful when the remote switch is a Cisco
391 2960 and the local network card features VLAN hardware
392 acceleration. In this case, you may not receive LLDP frames from the
393 remote switch. The most plausible explanation for this is the frame is
394 tagged with some VLAN (usually VLAN 1) and your network card is
395 filtering VLAN. This is not the only available solution to work-around
396 this problem. If you are concerned about performance issues, you can
397 also tag the VLAN 1 on each interface instead.
399 Currently, this option has no effect on anything else than Linux. On
400 other OS, either disable VLAN acceleration, tag VLAN 1 or enable
401 promiscuous mode manually on the interface.
405 .Cd system interface promiscuous
406 .Bd -ragged -offset XXXXXX
407 Do not set promiscuous mode on managed interfaces. This option does
408 not disable promiscuous mode on interfaces already using this mode.
412 .Cd system ip management pattern Ar pattern
413 .Bd -ragged -offset XXXXXX
414 Specify the management addresses of this system. As for interfaces
415 (described above), this option can use wildcards and inversions.
416 Without this option, the first IPv4 and the first IPv6 are used. If an
417 exact IP address is provided, it is used as a management address
418 without any check. If only negative patterns are provided, only one
419 IPv4 and one IPv6 addresses are chosen. Otherwise, many of them can be
420 selected. If you want to remove IPv6 addresses, you can use
422 If an interface name is matched, the first IPv4 address and the first
423 IPv6 address associated to this interface will be chosen.
427 .Cd system ip management pattern
428 .Bd -ragged -offset XXXXXX
429 Unset any specific pattern for matching management addresses. This
430 option undoes the previous one.
434 .Cd system bond-slave-src-mac-type Ar value
435 .Bd -ragged -offset XXXXXX
436 Set the type of src mac in lldp frames sent on bond slaves
439 .Bl -tag -width "XXX." -compact -offset XX
445 An arbitrary fixed value
446 .Li ( 00:60:08:69:97:ef )
448 Real mac with locally administered bit set. If the real mac already
449 has the locally administered bit set, fallback to the fixed value.
453 .Nm bond-slave-src-mac-type
456 Some switches may complain when using one of the two other possible
457 values (either because
458 .Li 00:00:00:00:00:00
459 is not a valid MAC or because the MAC address is flapping from one
460 port to another). Using
462 might lead to a duplicate MAC address on the network (but this is
467 .Cd system max-neighbors Ar neighbors
468 .Bd -ragged -offset XXXXXX
469 Change the maximum number of neighbors accepted (for each protocol) on
470 an interface. This is a global value. The default is 32. This setting
471 only applies to future neighbors.
476 .Cd nearest-bridge | nearest-non-tpmr-bridge | nearest-customer-bridge
477 .Bd -ragged -offset XXXXXX
478 The destination MAC address used to send LLDPDU allows an agent to
479 control the propagation of LLDPDUs. By default, the
480 .Li 01:80:c2:00:00:0e
481 MAC address is used and limit the propagation of the LLDPDU to the
483 .Cd ( nearest-bridge ) .
487 .Li 01:80:c2:00:00:03
488 MAC address instead, use
489 .Cd nearest-nontpmr-bridge
492 .Li 01:80:c2:00:00:00
493 MAC address instead, use
494 .Cd nearest-customer-bridge
499 .Cd lldp portidsubtype
500 .Cd ifname | macaddress
503 .Op ports Ar ethX Op ,...
504 .Cd lldp portidsubtype
506 .Bd -ragged -offset XXXXXX
507 Force port ID subtype. By default,
509 will use the MAC address as port identifier and the interface name as
510 port description, unless the interface has an alias. In this case, the
511 interface name will be used as port identifier and the description
512 will be the interface alias. With this command, you can force the port
513 identifier to be the interface name (with
515 the MAC address (with
517 or a local value (with
519 In the latest case, the local value should be provided.
523 .Op ports Ar ethX Op ,...
524 .Cd lldp portdescription
526 .Bd -ragged -offset XXXXXX
527 Force port description to the provided string.
531 .Cd lldp tx-interval Ar interval
532 .Bd -ragged -offset XXXXXX
533 Change transmit delay to the specified value in seconds. The transmit
534 delay is the delay between two transmissions of LLDP PDU. The default
535 value is 30 seconds. Note:
537 also starts another system based refresh timer on each port to detect
538 changes such as a hostname. This is the value of the tx-interval
543 value in milliseconds by appending a "ms" suffix to the figure (e.g.
544 "configure lldp tx-interval 1500ms" is 1.5s, not 1500s). In this case
545 the TTL for received and sent LLDP frames is rounded up to the next
546 second. Note: the effective interval can be limited by the operating
547 system capabilities and CPU speed.
551 .Cd lldp tx-hold Ar hold
552 .Bd -ragged -offset XXXXXX
553 Change transmit hold value to the specified value. This value is used
554 to compute the TTL of transmitted packets which is the product of this
555 value and of the transmit delay. The default value is 4 and therefore
556 the default TTL is 120 seconds.
560 .Op ports Ar ethX Op ,...
562 .Cd status Ar rx-and-tx | rx-only | tx-only | disabled
563 .Bd -ragged -offset XXXXXX
564 Configure the administrative status of the given port. By default, all
565 ports are configured to be in
567 mode. This means they can receive and transmit LLDP frames (as well as
568 other protocols if needed). In
570 mode, they won't emit any frames and in
572 mode, they won't receive any frames. In
574 mode, no frame will be sent and any incoming frame will be
575 discarded. This setting does not override the operational mode of the
576 main daemon. If it is configured in receive-only mode (with the
578 flag), setting any transmit mode won't have any effect.
582 .Op ports Ar ethX Op ,...
584 .Cd vlan-tx Ar vlan_id
585 .Op Cd prio Ar priority Op Cd dei Ar dei
586 .Bd -ragged -offset XXXXXX
587 Configure the given port to send LLDP frames over a specified VLAN. With VLAN Identifier (VID) as
589 Priority Code Point (PCP) as
591 and Drop Eligible Indicator (DEI) as
594 accepts LLDP frames on all VLANs.
598 .Op ports Ar ethX Op ,...
602 .Cd subtype Ar subtype
603 .Op Cd oui-info Ar content
604 .Bd -ragged -offset XXXXXX
605 Emit a custom TLV for OUI
609 and optionally with the bytes specified in
615 should be a comma-separated list of bytes in hex format.
617 must be exactly 3-byte long.
620 is specified then the TLV will be added. This is the default action.
623 is specified then all TLVs with the same
632 .Op ports Ar ethX Op ,...
635 .Op Cd subtype Ar subtype
636 .Bd -ragged -offset XXXXXX
637 When no oui is specified, remove all previously configured custom TLV.
642 is specified, remove specific instances of custom TLV.
645 .Cd configure med fast-start
646 .Cd enable | tx-interval Ar interval
647 .Bd -ragged -offset XXXXXX
648 Configure LLDP-MED fast start mechanism. When a new LLDP-MED-enabled
649 neighbor is detected, fast start allows
651 to shorten the interval between two LLDPDU.
653 should enable LLDP-MED fast start while
655 specifies the interval between two LLDPDU in seconds. The default
656 interval is 1 second. Once 4 LLDPDU have been sent, the fast start
657 mechanism is disabled until a new neighbor is detected.
660 .Cd unconfigure med fast-start
661 .Bd -ragged -offset XXXXXX
662 Disable LLDP-MED fast start mechanism.
666 .Op ports Ar ethX Op ,...
667 .Cd med location coordinate
668 .Cd latitude Ar latitude
669 .Cd longitude Ar longitude
670 .Cd altitude Ar altitude Ar unit
672 .Bd -ragged -offset XXXXXX
673 Advertise a coordinate based location on the given ports (or on all
674 ports if no port is specified). The format of
676 is a decimal floating point number followed either by
682 is a decimal floating point number followed either by
687 is a decimal floating point number followed either by
689 when expressed in meters or
691 when expressed in floors. A space is expected between the floating
692 point number and the unit.
694 is one of those values:
695 .Bl -bullet -compact -offset XXXXXXXX
704 A valid use of this command is:
705 .D1 configure ports eth0 med location coordinate latitude 48.85667N longitude 2.2014E altitude 117.47 m datum WGS84
709 .Op ports Ar ethX Op ,...
710 .Cd med location address
711 .Cd country Ar country
712 .Cd Op Ar type value Op ...
713 .Bd -ragged -offset XXXXXX
714 Advertise a civic address on the given ports (or on all ports if no
717 is the two-letter code representing the country. The remaining
718 arguments should be paired to form the address. The first member of
719 each pair indicates the type of the second member which is a free-form
720 text. Here is the list of valid types:
721 .Bl -bullet -compact -offset XXXXXXXX
739 trailing-street-suffix
768 A valid use of this command is:
769 .D1 configure ports eth1 med location address country US street Qo Commercial Road Qc city Qo Roseville Qc
773 .Op ports Ar ethX Op ,...
774 .Cd med location elin
776 .Bd -ragged -offset XXXXXX
777 Advertise the availability of an ELIN number. This is used for setting
778 up emergency call. If the provided number is too small, it will be
779 padded with 0. Here is an example of use:
780 .D1 configure ports eth2 med location elin 911
784 .Op ports Ar ethX Op ,...
786 .Cd application Ar application
790 .Op Cd priority Ar priority
792 .Bd -ragged -offset XXXXXX
793 Advertise a specific network policy for the given ports (or for all
794 ports if no port was provided). Only the application type is
797 should be one of the following values:
798 .Bl -bullet -compact -offset XXXXXXXX
806 guest-voice-signaling
819 flag tells that the network policy for the specified application type
820 is required by the device but is currently unknown. This is used by
821 Endpoint Devices, not by Network Connectivity Devices. If not
822 specified, the network policy for the given application type is
825 When a VLAN is specified with
827 tells which 802.1q VLAN ID has to be advertised for the network
828 policy. A valid value is between 1 and 4094.
830 tells the VLAN should be tagged for the specified application type.
833 allows one to specify IEEE 802.1d / IEEE 802.1p Layer 2 Priority, also
834 known as Class of Service (CoS), to be used for the specified
835 application type. This field is usually ignored if no VLAN is
836 specified. The names match 802.1D-2004 standard (table G-2). Some more
837 recent standards may use different labels. Only the numeric values
838 should be relied upon. The accepted labels are:
839 .Bl -tag -width "X." -compact -offset XXXX
847 critical-applications
859 represents the DSCP value to be advertised for the given network
860 policy. DiffServ/Differentiated Services Code Point (DSCP) value as
861 defined in IETF RFC 2474 for the specified application type. Value: 0
862 (default per RFC 2475) through 63. Note: The class selector DSCP
863 values are backwards compatible for devices that only support the old
864 IP precedence Type of Service (ToS) format. (See the RFCs for what
867 A valid use of this command is:
868 .D1 configure med policy application voice vlan 500 priority voice dscp 46
872 .Cd inventory hardware-revision Ar value
873 .Bd -ragged -offset XXXXXX
874 Override hardware-revision with the provided value. By default, the
875 hardware-revision is fetched from /sys/class/dmi
879 .Cd inventory hardware-revision
880 .Bd -ragged -offset XXXXXX
881 Do not override hardware-revision and restore the use of the /sys/class/dmi value.
885 .Cd inventory software-revision Ar value
886 .Bd -ragged -offset XXXXXX
887 Override software-revision with the provided value. By default, the
888 software-revision is fetched from uname
892 .Cd inventory software-revision
893 .Bd -ragged -offset XXXXXX
894 Do not override software-revision and restore the use of the uname value.
898 .Cd inventory firmware-revision Ar value
899 .Bd -ragged -offset XXXXXX
900 Override firmware-revision with the provided value. By default, the
901 firmware-revision is fetched from /sys/class/dmi
905 .Cd inventory firmware-revision
906 .Bd -ragged -offset XXXXXX
907 Do not override firmware-revision and restore the use of the /sys/class/dmi value.
911 .Cd inventory serial-number Ar value
912 .Bd -ragged -offset XXXXXX
913 Override serial-number with the provided value. By default, the
914 serial-number is fetched from /sys/class/dmi
918 .Cd inventory serial-number
919 .Bd -ragged -offset XXXXXX
920 Do not override serial-number and restore the use of the /sys/class/dmi value.
924 .Cd inventory manufacturer Ar value
925 .Bd -ragged -offset XXXXXX
926 Override manufacturer with the provided value. By default, the
927 manufacturer is fetched from /sys/class/dmi
931 .Cd inventory manufacturer
932 .Bd -ragged -offset XXXXXX
933 Do not override manufacturer and restore the use of the /sys/class/dmi value.
937 .Cd inventory model Ar value
938 .Bd -ragged -offset XXXXXX
939 Override model with the provided value. By default, the
940 model is fetched from /sys/class/dmi
945 .Bd -ragged -offset XXXXXX
946 Do not override model and restore the use of the /sys/class/dmi value.
950 .Cd inventory asset Ar value
951 .Bd -ragged -offset XXXXXX
952 Override asset with the provided value. By default, the
953 asset is fetched from /sys/class/dmi
958 .Bd -ragged -offset XXXXXX
959 Do not override asset and restore the use of the /sys/class/dmi value.
963 .Op ports Ar ethX Op ,...
964 .Cd med power pse | pd
966 .Cd priority Ar priority
968 .Bd -ragged -offset XXXXXX
969 Advertise the LLDP-MED POE-MDI TLV for the given ports or for all
970 interfaces if no port is provided. One can act as a PD (power
971 consumer) or a PSE (power provider). No check is done on the validity
972 of the parameters while LLDP-MED requires some restrictions:
975 PD shall never request more power than physical 802.3af class.
977 PD shall never draw more than the maximum power advertised by PSE.
979 PSE shall not reduce power allocated to PD when this power is in use.
981 PSE may request reduced power using conservation mode
983 Being PSE or PD is a global parameter, not a per-port parameter.
985 does not enforce this: a port can be set as PD or PSE. LLDP-MED also
986 requires for a PSE to only have one power source (primary or
989 does not enforce this. Each port can have its own power source. The
990 same applies for PD and power priority. LLDP-MED MIB does not allow
991 this kind of representation.
995 .Bl -tag -width "XXX." -compact -offset XX
997 Power Sourcing Entity (power provider)
999 Power Device (power consumer)
1003 .Bl -tag -width "XXXXXXX" -compact -offset XX
1007 For PSE, the power source is the primary power source.
1009 For PSE, the power source is the backup power source or a power
1010 conservation mode is asked (the PSE may be running on UPS for
1013 For PD, the power source is the PSE.
1015 For PD, the power source is a local source.
1017 For PD, the power source is both the PSE and a local source.
1020 Valid priorities are:
1021 .Bl -tag -width "XXXXXXXXX" -compact -offset XX
1033 should be the total power in milliwatts required by the PD device or
1034 available by the PSE device.
1036 Here is an example of use:
1037 .D1 configure med power pd source pse priority high value 5000
1041 .Op ports Ar ethX Op ,...
1042 .Cd dot3 power pse | pd
1046 .Cd powerpairs Ar powerpairs
1047 .Op Cd class Ar class
1048 .Op Cd type Ar type Cd source Ar source Cd priority Ar priority Cd requested Ar requested Cd allocated Ar allocated
1049 .Bd -ragged -offset XXXXXX
1050 Advertise Dot3 POE-MDI TLV for the given port or for all ports if none
1051 was provided. One can act as a PD (power consumer) or a PSE (power
1052 provider). This configuration is distinct of the configuration of the
1053 transmission of the LLDP-MED POE-MDI TLV but the user should ensure
1054 the coherency of those two configurations if they are used together.
1057 means that MDI power is supported on the given port while
1059 means that MDI power is enabled.
1061 is used to indicate if pair selection can be controlled. Valid values
1065 .Bl -tag -width "XXXXXX" -compact -offset XX
1067 The signal pairs only are in use.
1069 The spare pairs only are in use.
1074 is a number between 0 and 4.
1076 The remaining parameters are in conformance with 802.3at and are optional.
1078 should be either 1 or 2, indicating which if the device conforms to
1079 802.3at type 1 or 802.3at type 2. Values of
1083 are the same as for LLDP-MED POE-MDI TLV.
1087 are expressed in milliwats.
1089 Here are two valid uses of this command:
1090 .D1 configure ports eth3 dot3 power pse supported enabled paircontrol powerpairs spare class class-3
1091 .D1 configure dot3 power pd supported enabled powerpairs spare class class-3 type 1 source pse priority low requested 10000 allocated 15000
1095 .Bd -ragged -offset XXXXXX
1100 will not send any more frames or receive ones. This can be undone with
1102 command. This only works interactively as lldpd asks lldpcli to
1103 unpause after reading the configuration file.
1107 .Bd -ragged -offset XXXXXX
1112 will start to send and receive frames. This command is issued
1113 internally after processing configuration but can be used at any time
1121 .Bl -tag -width "@LLDPD_CTL_SOCKET@XX" -compact
1122 .It @LLDPD_CTL_SOCKET@
1123 Unix-domain socket used for communication with
1132 program was written by
1133 .An Vincent Bernat Aq bernat@luffy.cx .