When no specific option is given,
displays the list of discovered neighbors along with
some of their advertised capabilities. If some interfaces are given,
only those interfaces will be displayed.
The options are as follows:
Enable more debugging information.
Choose the output format. Currently
formats are available. The default is
Enable the transmission of LLDP-MED location TLV for the given
interfaces. This option can be repeated several times to enable the
transmission of the location in several formats. Several formats are
Coordinate based location
The format of
The first digit is always
It is followed by the latitude, a letter for the direction (
for East or West), the longitude and a letter for the direction (
). The next figure is the altitude. It can be expressed in meters (the
next letter is then
) or in floors (the letter should be
). The last digit is the datum. It can either be
The location can be expressed as an address. The format of the
location is then
The first digit is always
The next two letters are the country code. Then, arguments are paired
to form the address. The first member of the pair is a digit
indicating the type of the second member. Here is the list of
County, parish, district
City division, borough, ward
Leading street direction
Trailing street suffix
House number suffix
Landmark or vanity address
Additional location info
This is a numerical string using for setting up emergency call. The
format of the location is then the following:
where the first digit should be
and the second argument is the ELIN number.
When setting a location for a given port, all previous locations are
erased. To erase all location, just use the empty string. There is
currently no way to get the location from the command line.
Enable the transmission of LLDP-MED Network Policy TLVs for the given
interfaces. This option can be repeated several times to specify
different policies. Format (without spaces!):
Valid application types (see ANSI/TIA-1057 table 12):
Guest Voice Signaling
Unknown Policy Flag.
Network policy for the specified application type is defined.
Network policy for the specified application type is required by
the device but is currently unknown. This is used by Endpoint
Devices, not by Network Connectivity Devices.
Untagged VLAN. In this case the VLAN ID and the Layer 2 Priority
are ignored and only the DSCP value has relevance.
IEEE 802.1q VLAN ID (VID). A value of 1 through 4094 defines a
VLAN ID. A value of 0 means that only the priority level is
IEEE 802.1d / IEEE 802.1p Layer 2 Priority, also known as Class of Service
(CoS), to be used for the specified application type.
Best Effort (default)
DiffServ/Differentiated Services Code Point (DSCP) value as defined
in IETF RFC 2474 for the specified application type. Value: 0 (default
per RFC 2475) through 63. Note: The class selector DSCP values are
backwards compatible for devices that only support the old IP
precedence Type of Service (ToS) format. (See the RFCs for what
these values mean.)
Enable the transmission of LLDP-MED POE-MDI TLV for the given
interfaces. One can act as a PD (power consumer) or a PSE (power
provider). No check is done on the validity of the parameters while
LLDP-MED requires some restrictions:
PD shall never request more power than physical 802.3af class.
PD shall never draw more than the maximum power advertised by PSE.
PSE shall not reduce power allocated to PD when this power is in use.
PSE may request reduced power using conservation mode
Being PSE or PD is a global paremeter, not a per-port parameter.
does not enforce this: a port can be set as PD or PSE. LLDP-MED also
requires for a PSE to only have one power source (primary or
does not enforce this. Each port can have its own power source. The
same applies for PD and power priority. LLDP-MED MIB does not allow
this kind of representation.
The format of this option is (without spaces):
Valid types are:
Power Sourcing Entity (power provider)
Power Device (power consumer)
Valid sources are:
For PD, the power source is the PSE. For PSE, the power source is the
primary power source.
For PD, the power source is a local source. For PSE, the power source
is the backup power source or a power conservation mode is asked (the
PSE may be running on UPS for example).
For PD, the power source is both the PSE and a local source. For PSE,
this value should not be used.
Four priorities are available:
For PD, the power value is the total power in tenth of watts required
by a PD device from the PSE device. This value should range from 0 to
1023 tenth of watts.
Unix-domain socket used for communication with