Link Layer Discovery Protocol
LLDP shows information about connected devices. The lldpd daemon implements the IEEE802.1AB LLDP standard and starts at system boot.
LLDP in Cumulus Linux supports CDP (Cisco Discovery Protocol v1 and v2) and logs by default into /var/log/daemon.log with an lldpd prefix.
Enable or Disable LLDP
Cumulus Linux enables the lldp service by default.
You can disable LLDP globally or on an interface.
- When you disable LLDP globally, the
lldpservice, and all LLDP and CDP packet transmission stops. - When you disable LLDP on an interface, LLDP and CDP packet transmission stops on the interface.
To disable LLDP globally:
cumulus@leaf01:~$ nv set service lldp state disabled
cumulus@leaf01:~$ nv config apply
To re-enable LLDP globally, run the nv set service lldp state enabled command.
Stop the lldpd service:
cumulus@leaf01:~$ sudo systemctl stop lldpd
cumulus@leaf01:~$ sudo systemctl disable lldpd
To re-enable LLDP globally, enable and restart the lldp service:
cumulus@leaf01:~$ sudo systemctl enable lldpd
cumulus@leaf01:~$ sudo systemctl restart lldpd
To disable LLDP on an interface:
cumulus@leaf01:~$ nv set interface swp1 lldp state disabled
cumulus@leaf01:~$ nv config apply
To re-enable LLDP on an interface, run the nv set interface swp1 lldp state enabled command.
Create the /etc/lldp.d/lldp-interfaces.conf file and add the configure system interface pattern-blacklist option. The following example disables LLDP on swp1 and swp2:
cumulus@leaf01:~$ sudo nano /etc/lldpd.d/lldp-interfaces.conf
configure system interface pattern-blacklist swp1,swp2
An alternative method is to use the system interface pattern keyword to send LLDP on all interfaces except for swp1 and swp2:
cumulus@leaf01:~$ sudo nano /etc/lldpd.d/lldp-interfaces.conf
configure system interface pattern eth*,swp*,!swp1,!swp2
Restart the lldpd service for the changes to take effect:
cumulus@leaf01:~$ sudo systemctl restart lldpd
A runtime configuration does not persist when you reboot the switch; you lose all changes.
To configure active interfaces:
cumulus@leaf01:~$ sudo lldpcli configure system interface pattern "swp*"
To configure inactive interfaces:
cumulus@leaf01:~$ sudo lldpcli configure system interface pattern *,!eth0,swp*
The active interface list always overrides the inactive interface list.
To reset any interface list to none:
cumulus@leaf01:~$ sudo lldpcli configure system interface pattern ""
To show if LLDP is enabled globally or on an interface, run the nv show service lldp command.
cumulus@leaf01:~$ nv show service lldp
operational applied
---------------------- ----------- -------
tx-interval 30 30
tx-hold-multiplier 4 4
dot1-tlv off off
lldp-med-inventory-tlv off off
mode default default
state enabled disabled
The following example show that swp1 through swp4 are up and advertising LLDP between leaf01 and leaf02:
cumulus@leaf01:~$ sudo lldpctl | egrep 'Inter|Port|SysName'
Interface: eth0, via: LLDP, RID: 1, Time: 1 day, 03:07:48
SysName: oob-mgmt-switch
Port:
PortID: ifname swp2
PortDescr: swp2
Interface: swp3, via: LLDP, RID: 2, Time: 0 day, 06:52:48
SysName: leaf02
Port:
PortID: ifname swp3
PortDescr: swp3
Interface: swp4, via: LLDP, RID: 2, Time: 0 day, 00:07:38
SysName: leaf02
Port:
PortID: ifname swp4
PortDescr: swp4
The following example shows that after disabling LLDP on swp1 and swp2, only swp3 and swp4 are generating and receiving LLDP on leaf01. leaf02 is only receiving LLDP on swp3 and swp4 from leaf01:
cumulus@leaf02:~$ sudo lldpctl | egrep 'Inter|Port|SysName'
Interface: eth0, via: LLDP, RID: 2, Time: 0 day, 00:09:16
SysName: oob-mgmt-switch
Port:
PortID: ifname swp3
PortDescr: swp3
Interface: swp3, via: LLDP, RID: 1, Time: 0 day, 00:08:47
SysName: leaf01
Port:
PortID: ifname swp3
PortDescr: swp3
Interface: swp4, via: LLDP, RID: 1, Time: 0 day, 00:09:16
SysName: leaf01
Port:
PortID: ifname swp4
PortDescr: swp4
Configure LLDP Timers
You can configure the frequency of LLDP updates (between 5 and 32768 seconds) and the amount of time (between 1 and 8192 seconds) to hold the information before discarding it. The hold time interval is a multiple of the tx-interval.
The nv show commands reflect certain configuration changes in operational values only after the hold time interval.
The following example commands configure the frequency of LLDP updates to 100 and the hold time to 3.
cumulus@switch:~$ nv set service lldp tx-interval 100
cumulus@switch:~$ nv set service lldp tx-hold-multiplier 3
cumulus@switch:~$ nv config apply
Create the /etc/lldpd.conf file or create a file in the /etc/lldpd.d/ directory with a .conf suffix and add the timers:
cumulus@switch:~$ sudo nano /etc/lldpd.conf
configure lldp tx-interval 100
configure lldp tx-hold 3
...
Restart the lldpd service for the changes to take effect:
cumulus@switch:~$ sudo systemctl restart lldpd
SNMP Subagent
The SNMP subagent allows SNMP queries to retrieve LLDP information from the lldpd service.
If you enable SNMP with NVUE commands, NVUE enables the SNMP subagent automatically. To disable the SNMP subagent, disable SNMP with the NVUE nv set system snmp-server state disable command.
If you use Linux commands to configure the switch, Cumulus Linux does not enable the SNMP subagent by default. To enable the SNMP subagent, edit the /etc/default/lldpd file and add the -x option:
cumulus@switch:~$ sudo nano /etc/default/lldpd
# Add "-x" to DAEMON_ARGS to start SNMP subagent
# Enable CDP by default
DAEMON_ARGS="-c -x -M 4"
Restart the lldpd service for the changes to take effect:
cumulus@switch:~$ sudo systemctl restart lldpd
- The
-coption enables backwards compatibility with CDP. See Change CDP Settings below. - The
-M 4option sends a field in discovery packets to indicate that the switch is a network device.
Set LLDP Mode
By default, the lldpd service sends LLDP frames unless it detects a CDP peer, then it sends CDP frames. You can change this behavior and configure the lldpd service to send only CDP frames or only LLDP frames.
- You configure the
lldpdservice to send only CDP or only LLDP frames globally for all interfaces; you cannot configure these settings for specific interfaces. - If you configure the
lldpdservice to send only CDP frames (CDPv1 or CDPv2), LLDP DCBX TLV transmission for QOS ROCE is not supported.
To send only CDPv1 frames:
cumulus@switch:~$ nv set service lldp mode force-send-cdpv1
cumulus@switch:~$ nv config apply
To send only CDPv2 frames:
cumulus@switch:~$ nv set service lldp mode force-send-cdpv2
cumulus@switch:~$ nv config apply
To send only LLDP frames:
cumulus@switch:~$ nv set service lldp mode force-send-lldp
cumulus@switch:~$ nv config apply
To reset to the default setting (to send both CDP and LLDP frames):
cumulus@switch:~$ nv set service lldp mode default
cumulus@switch:~$ nv config apply
Edit the /etc/default/lldpd file and add one of the following options to the DAEMON_ARGS section:
To send only CDPv1 frames:
cumulus@switch:~$ sudo nano /etc/default/lldpd
...
DAEMON_ARGS="-cc -ll -M 4"
To send only CDPv2 frames:
cumulus@switch:~$ sudo nano /etc/default/lldpd
...
DAEMON_ARGS="-cccc -ll -M 4"
To send only LLDP frames:
cumulus@switch:~$ sudo nano /etc/default/lldpd
...
DAEMON_ARGS="-l -M 4"
To reset to the default setting (to send both CDP and LLDP frames):
cumulus@switch:~$ sudo nano /etc/default/lldpd
...
DAEMON_ARGS="-c -M 4"
You must restart the lldpd service for the changes to take effect.
cumulus@switch:~$ sudo systemctl restart lldpd
To show the current LLDP mode, run the nv show service lldp command. The following example shows that the lldpd service sends CDPv2 frames only.
cumulus@leaf02:mgmt:~$ nv show service lldp
operational applied
------------------ ---------------- ----------------
dot1-tlv off off
mode force-send-cdpv2 force-send-cdpv2
tx-hold-multiplier 4 4
tx-interval 30 30
CDP PortID Behavior
LLDP emulates CDP by default on interfaces where it detects a CDP neighbor. CDP only supports the PortID value (TLV) in the protocol; however, LLDP has a separate PortID and PortDescription field.
By default, when the switch sends a CDP packet, if there is an alias (description) on the interface, LLDP sends the alias in the CDP PortID field. When an LLDP neighbor receives a CDP packet, the receiving switch displays the CDP Port ID in both the PortID and PortDescription fields.
If you want LLDP to send the portID (ifname) value to a CDP neighbor instead of the interface alias, you can configure the following options:
- To transmit both the
PortIDandPortDescriptionin the samePortIDfield, insert the interface name in the interfacealiasfield. - To send the
ifnameinstead of the interface alias over CDP, configure theconfigure lldp portidsubtype macaddressoption in the/etc/lldpd.d/lldp_global.conffile. The default configuration isportidsubtype ifname.
The following table shows the TLVs sent for each configuration.
| LLDP Configuration | LLDP PortID Value Sent | LLDP Port Description Value Sent | CDP PortID Value Sent |
|---|---|---|---|
configure lldp portidsubtype ifname (default) |
interface ifname |
interface alias |
interface alias |
configure lldp portidsubtype macaddress MAC address |
interface mac address |
interface ifname |
interface ifname |
Use CDP only or LLDP only to get the desired behavior of PortID, Description, or MacAddress (LLDP only) across all neighbors. For more information, see LLDP Mode.
LLDP DCBX TLVs
DCBX is an extension of LLDP that supports TLVs to provide additional information in LLDP packets to peers.
Cumulus Linux supports the following LLDP DCBX TLVs:
- IEEE 802.1
- IEEE 802.3
- QoS
- LLDP-MED Inventory
- Application Priority
- You can send a maximum of 250 VLANS per switch port in one LLDP frame.
- Cumulus Linux does not support CEE DCBX TLVs.
- Cumulus Linux limits DCBX support to enabling DCBX TLVs (either with ROCE global configuration or per interface) as documented in the IEEE 802.1Q standard.
IEEE 802.1 TLVs
You can transmit the following IEEE 802.1 TLVs when exchanging LLDP messages. By default, IEEE 802.1 TLV transmission is off and the switch sends all LLDP frames without IEEE 802.1 TLVs.
| Name | Subtype | Description |
|---|---|---|
| Port VLAN ID | 1 | The port VLAN identifier. |
| VLAN Name | 3 | The name of any VLAN to which the port belongs. |
| Link Aggregation | 7 | Indicates if the port supports link aggregation and if it is on. |
To enable IEEE 802.1 TLV transmission, run the nv set service lldp dot1-tlv on command:
cumulus@switch:~$ nv set service lldp dot1-tlv on
cumulus@switch:~$ nv config apply
To disable IEEE 802.1 TLV transmission, run the nv unset service lldp dot1-tlv command.
To show if IEEE 802.1 TLV transmission is on, run the NVUE nv show service lldp command:
cumulus@leaf01:mgmt:~$ nv show service lldp
operational applied
---------------------- ----------- -------
tx-interval 30 30
tx-hold-multiplier 4 4
dot1-tlv off off
...
IEEE 802.3 TLVs
Cumulus Linux transmits the following IEEE 802.3 TLVs by default. You do not need to enable them.
| Name | Subtype | Description |
|---|---|---|
| Link Aggregation | 3 | Indicates if the port supports link aggregation and if it is on. |
| Maximum Frame Size | 4 | The MTU configuration on the port. The MTU on the port is the MFS. |
QoS TLVs
Adding QoS configuration as part of the DCBX TLVs allows automated configuration on hosts and switches that connect to the switch.
You can transmit the following QoS TLVs. By default, all QoS TLV transmission is off on all interfaces.
| Name | Subtype | Description |
|---|---|---|
| ETS Configuration | 9 | The ETS configuration settings on the switch. |
| ETS Recommendation | A | The recommended ETS settings that the switch wants the connected peer interface to use. |
| PFC Configuration | B | The PFC configuration settings on the switch. |
Adding the QoS TLVs to LLDP packets on an interface relies on PFC and ETS configuration from switchd. Refer to Quality of Service for information on configuring PFC and ETS.
When you enable ROCE on the switch:
- QoS TLV transmission (PFC Configuration, ETS Configuration, and ETS Recommendation) is on globally for all ports, which overrides any QoS TLV transmission setting on a switch port interface.
- LLDP frames for all switch port interfaces carry PFC configuration, ETS configuration, ETS recommendation, and APP Priority TLVs. The ETS configuration and PFC configuration TLV payloads are the same for all interfaces.
Enable QoS TLV Transmission
To enable PFC Configuration TLV transmission, run the nv set interface <interface> lldp dcbx-pfc-tlv on command:
cumulus@switch:~$ nv set interface swp1 lldp dcbx-pfc-tlv on
cumulus@switch:~$ nv config apply
To enable ETS Configuration TLV transmission, run the nv set interface <interface> lldp dcbx-ets-config-tlv on command:
cumulus@switch:~$ nv set interface swp1 lldp dcbx-ets-config-tlv on
cumulus@switch:~$ nv config apply
To enable ETS Recommendation TLV transmission, run the nv set interface <interface> lldp dcbx-ets-recomm-tlv on command:
cumulus@switch:~$ nv set interface swp1 lldp dcbx-ets-recomm-tlv on
cumulus@switch:~$ nv config apply
The interface must be a physical interface; you cannot enable TLVs on bonds.
Disable QoS TLV Transmission
To disable PFC Configuration TLV transmission, run the nv unset interface <interface> lldp dcbx-pfc-tlv command:
cumulus@switch:~$ nv unset interface swp1 lldp dcbx-pfc-tlv
cumulus@switch:~$ nv config apply
To disable ETS Configuration TLV transmission, run the nv unset interface <interface> lldp dcbx-ets-config-tlv command:
cumulus@switch:~$ nv unset interface swp1 lldp dcbx-ets-config-tlv
cumulus@switch:~$ nv config apply
To disable ETS Recommendation TLV transmission, run the nv unset interface <interface> lldp dcbx-ets-recomm-tlv command:
cumulus@switch:~$ nv unset interface swp1 lldp dcbx-ets-recomm-tlv
cumulus@switch:~$ nv config apply
Show QoS TLV Transmission Settings
To show if Qos TLV transmission is on for an interface, run the NVUE nv show interface <interface> command:
cumulus@leaf01:mgmt:~$ nv show interface swp1
operational applied description
------------------------ ----------------- ----------- ---------------------------------------------------
...
lldp
dcbx-ets-config-tlv on DCBX ETS config TLV flag
dcbx-ets-recomm-tlv off DCBX ETS recommendation TLV flag
dcbx-pfc-tlv on DCBX PFC TLV flag
...
LLDP-MED Inventory TLVs
LLDP-MED is an extension to LLDP that operates between endpoint devices, such as IP phones and switches. Inventory management TLV enables an endpoint to transmit detailed inventory information about itself to the switch, such as the manufacturer, model, firmware, and serial number.
To enable LLDP-MED inventory TLV transmission, run the nv set service lldp lldp-med-inventory-tlv on command:
cumulus@switch:~$ nv set service lldp lldp-med-inventory-tlv on
cumulus@switch:~$ nv config apply
To disable LLDP-MED inventory TLV transmission, run the nv unset service lldp lldp-med-inventory-tlv command.
To show if LLDP-MED Inventory TLV transmission is on, run the NVUE nv show service lldp command:
cumulus@leaf01:mgmt:~$ nv show service lldp
operational applied
---------------------- ----------- -------
tx-interval 30 30
tx-hold-multiplier 4 4
dot1-tlv off off
lldp-med-inventory-tlv on on
...
Application Priority TLVs
DCBX Application priority TLVs allow hosts to receive per-application priority values in LLDP packets.
Cumulus Linux supports application priority TLVs for:
- iSCSI using TCP port 3260.
- NVMe using TCP port 4420 and 8009.
- Applications using a specific TCP port or UDP port.
Enable Application Priority TLV Transmission
To enable application priority TLV transmission, run NVUE commands to set:
- The application, TCP port, or UDP port and the associated application priority. If you do not set an application priority, Cumulus Linux uses the default priority 0.
- The interface on which you want to enable application priority TLV transmission. LLDP starts sending PDUs with the application priority TLVs after you apply the configuration on the specified interface.
- You cannot enable application priority TLV transmission on bonds.
- You can configure a maximum of 10 application TLV priorities on the switch.
- Cumulus Linux can send a maximum of 10 application priority TLVs in an LLDP PDU.
The following example sets the application priority of iSCSI traffic to 3 in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set service lldp application-tlv app iSCSI priority 3
cumulus@switch:~$ nv set interface swp1 lldp application-tlv app iSCSI
cumulus@switch:~$ nv config apply
The following example sets the application priority of NVMe traffic using TCP port 4420 to 5 in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set service lldp application-tlv app NVME_4420 priority 5
cumulus@switch:~$ nv set interface swp1 lldp application-tlv app NVME_4420
cumulus@switch:~$ nv config apply
The following example sets the application priority of NVMe traffic using TCP port 8009 to 7 in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set service lldp application-tlv app NVME_8009 priority 7
cumulus@switch:~$ nv set interface swp1 lldp application-tlv app NVME_8009
cumulus@switch:~$ nv config apply
The following example sets the application priority for TCP traffic using port 4217 to 6 in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set service lldp application-tlv tcp-port 4217 priority 6
cumulus@switch:~$ nv set interface swp1 lldp application-tlv tcp-port 4217
cumulus@switch:~$ nv config apply
The following example sets the application priority for UDP traffic using port 4317 to 4 in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set service lldp application-tlv udp-port 4317 priority 4
cumulus@switch:~$ nv set interface swp1 lldp application-tlv udp-port 4317
cumulus@switch:~$ nv config apply
The following example sets the application priority of iSCSI traffic using port 3260 to 0 (the default priority) in the application priority TLV sent in LLDP PDUs on swp1.
cumulus@switch:~$ nv set interface swp1 lldp application-tlv app iSCSI
cumulus@switch:~$ nv config apply
Disable Application Priority TLV Transmission
To stop LLDP from sending PDUs with application priority TLVs on an interface, unset the interface configuration; for example:
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv
cumulus@switch:~$ nv config apply
The following example unsets application priority 3 for iSCSI, then disables transmission of the application priority TLVs on swp1.
cumulus@switch:~$ nv unset service lldp application-tlv app iSCSI priority 3
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv app iSCSI
cumulus@switch:~$ nv config apply
The following example unsets application priority 5 for NVMe using TCP port 4420, then disables transmission of the application priority TLVs on swp1.
cumulus@switch:~$ nv unset service lldp application-tlv app NVME_4420 priority 5
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv app NVME_4420
cumulus@switch:~$ nv config apply
The following example unsets application priority 7 for NVMe using TCP port 8009, then disables transmission of the application priority TLVs on swp1.
cumulus@switch:~$ nv unset service lldp application-tlv app NVME_8009 priority 7
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv app NVME_8009
cumulus@switch:~$ nv config apply
The following example unsets application priority 6 for the application using TCP port 4217, then disables transmission of application priority TLVs on swp1:
cumulus@switch:~$ nv unset service lldp application-tlv tcp-port 4217 priority 6
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv tcp-port 4217
cumulus@switch:~$ nv config apply
The following example unsets application priority 4 for the application using UDP port 4317, then disables transmission of application priority TLVs on swp1:
cumulus@switch:~$ nv unset service lldp application-tlv udp-port 4317 priority 4
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv udp-port 4317
cumulus@switch:~$ nv config apply
The following example unsets application priority 0 (the default priority) for iSCSI using TCP port 3260 and disables transmission of application TLVs on swp1.
cumulus@switch:~$ nv unset interface swp1 lldp application-tlv app iSCSI
cumulus@switch:~$ nv config apply
Show Application Priority TLV Settings
To show all application priority TLV configuration on the switch:
cumulus@switch:~$ nv show service lldp application-tlv
udp-port
===========
Port priority
---- --------
4317 4
tcp-port
===========
Port priority
---- --------
4217 6
app
======
AppName priority
--------- --------
NVME_4420 5
NVME_8009 7
iSCSI 3
To show all the application TLVs configured on an interface:
cumulus@switch:~$ nv show interface swp1 lldp application-tlv
operational applied
---------- ----------- ---------
[udp-port] 4317 4317
[tcp-port] 4217 4217
[app] NVME_4420 NVME_4420
[app] NVME_8009 NVME_8009
[app] iSCSI iSCSI
To show the UDP port priority mapping:
cumulus@switch:~$ nv show service lldp application-tlv udp-port
Port priority
---- --------
4317 4
To show the application priority mapping:
cumulus@switch:~$ nv show service lldp application-tlv app
AppName priority
--------- --------
NVME_4420 5
NVME_8009 7
iSCSI 3
To show the TCP port priority mapping:
cumulus@switch:~$ nv show service lldp application-tlv tcp-port
Port priority
---- --------
4217 6
To show the UDP port priority mapping for swp1:
cumulus@switch:~$ nv show interface swp1 lldp application-tlv udp-port
Ports
-----
4317
To show the application names that have application priority TLVs enabled for swp1:
cumulus@switch:~$ nv show interface swp1 lldp application-tlv app
AppName
---------
NVME_4420
NVME_8009
iSCSI
Troubleshooting
You can use the lldpcli tool to query the lldpd daemon for neighbors, statistics, and other running configuration information. See man lldpcli(8) for details.
To show all neighbors on all ports and interfaces:
cumulus@switch:~$ sudo lldpcli show neighbors
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 1, Time: 0 day, 17:38:08
Chassis:
ChassisID: mac 08:9e:01:e9:66:5a
SysName: PIONEERMS22
SysDescr: Cumulus Linux version 4.1.0 running on quanta lb9
MgmtIP: 192.168.0.22
Capability: Bridge, on
Capability: Router, on
Port:
PortID: ifname swp47
PortDescr: swp47
-------------------------------------------------------------------------------
Interface: swp1, via: LLDP, RID: 10, Time: 0 day, 17:08:27
Chassis:
ChassisID: mac 00:01:00:00:09:00
SysName: MSP-1
SysDescr: Cumulus Linux version 4.1.0 running on QEMU Standard PC (i440FX + PIIX, 1996)
MgmtIP: 192.0.2.9
MgmtIP: fe80::201:ff:fe00:900
Capability: Bridge, off
Capability: Router, on
Port:
PortID: ifname swp1
PortDescr: swp1
-------------------------------------------------------------------------------
Interface: swp2, via: LLDP, RID: 10, Time: 0 day, 17:08:27
Chassis:
ChassisID: mac 00:01:00:00:09:00
SysName: MSP-1
SysDescr: Cumulus Linux version 4.1.0 running on QEMU Standard PC (i440FX + PIIX, 1996)
MgmtIP: 192.0.2.9
MgmtIP: fe80::201:ff:fe00:900
Capability: Bridge, off
Capability: Router, on
Port:
PortID: ifname swp2
PortDescr: swp2
-------------------------------------------------------------------------------
Interface: swp3, via: LLDP, RID: 11, Time: 0 day, 17:08:27
Chassis:
ChassisID: mac 00:01:00:00:0a:00
SysName: MSP-2
SysDescr: Cumulus Linux version 4.1.0 running on QEMU Standard PC (i440FX + PIIX, 1996)
MgmtIP: 192.0.2.10
MgmtIP: fe80::201:ff:fe00:a00
Capability: Bridge, off
Capability: Router, on
Port:
PortID: ifname swp1
PortDescr: swp1
...
To show lldpd statistics for all ports:
cumulus@switch:~$ sudo lldpcli show statistics
----------------------------------------------------------------------
LLDP statistics:
----------------------------------------------------------------------
Interface: eth0
Transmitted: 9423
Received: 17634
Discarded: 0
Unrecognized: 0
Ageout: 10
Inserted: 20
Deleted: 10
--------------------------------------------------------------------
Interface: swp1
Transmitted: 9423
Received: 6264
Discarded: 0
Unrecognized: 0
Ageout: 0
Inserted: 2
Deleted: 0
---------------------------------------------------------------------
Interface: swp2
Transmitted: 9423
Received: 6264
Discarded: 0
Unrecognized: 0
Ageout: 0
Inserted: 2
Deleted: 0
---------------------------------------------------------------------
Interface: swp3
Transmitted: 9423
Received: 6265
Discarded: 0
Unrecognized: 0
Ageout: 0
Inserted: 2
Deleted: 0
----------------------------------------------------------------------
...
To show a summary of lldpd statistics for all ports:
cumulus@switch:~$ sudo lldpcli show statistics summary
---------------------------------------------------------------------
LLDP Global statistics:
---------------------------------------------------------------------
Summary of stats:
Transmitted: 648186
Received: 437557
Discarded: 0
Unrecognized: 0
Ageout: 10
Inserted: 38
Deleted: 10
To show the running LLDP configuration:
cumulus@switch:~$ sudo lldpcli show running-configuration
--------------------------------------------------------------------
Global configuration:
--------------------------------------------------------------------
Configuration:
Transmit delay: 30
Transmit hold: 4
Receive mode: no
Pattern for management addresses: (none)
Interface pattern: (none)
Interface pattern blacklist: (none)
Interface pattern for chassis ID: (none)
Override description with: (none)
Override platform with: Linux
Override system name with: (none)
Advertise version: yes
Update interface descriptions: no
Promiscuous mode on managed interfaces: no
Disable LLDP-MED inventory: yes
LLDP-MED fast start mechanism: yes
LLDP-MED fast start interval: 1
Source MAC for LLDP frames on bond slaves: local
Portid TLV Subtype for lldp frames: ifname
--------------------------------------------------------------------
Considerations
- Cumulus Linux does not support LLDP Annex E (and Annex D).
- If you configure both an eth0 IP address and a loopback IP address on the switch, LLDP advertises the loopback IP address as the management IP address. In this case, the Cumulus Linux switch behaves more like a typical Linux host than a networking appliance.