LLDP is an industry standard protocol designed to supplant proprietary
Link-Layer protocols such as Extreme's EDP (Extreme Discovery
Protocol) and CDP (Cisco Discovery Protocol). The goal of LLDP is to
provide an inter-vendor compatible mechanism to deliver Link-Layer
notifications to adjacent network devices. This implementation
provides LLDP sending and reception, supports VLAN and includes an
SNMP subagent that can interface to an SNMP agent through AgentX
protocol. This daemon is also able to deal with CDP, SONMP, FDP and
EDP protocol. It also handles LLDP-MED extension.
Purpose of this charm is to install and configure LLDP daemon (lldpd). LLDP
is used by network administrators to detect how machines are connected to
switches and routers.
Step by step instructions on using the charm:
juju deploy lldpd
juju add-relation lldpd application-on-physical-machine
Being a subordinate charm it needs to be related to an application running
on physical machine. It doesn't make much sense to install LLDP on a VM
or LXD container, because Linux bridge will terminate LLDP traffic.
By scaling your application, subordinate charm will get installed automatically.
LLDP is not very useful on containers and virtual machines and therefore it's
use on those is not recommended.
By default LLDPd will listen on all interfaces and pick, more or less, a random
systemid. Two given configuration options allow user to specify which interfaces
will be used to broadcast LLDP data and which will be used for systemid.
One additional option, i40e-lldp-stop, is included because some Intel NICs
block user-space LLDP generated data and instead broadcast their own. By setting
this option to True (default), NIC's built-in LLDP daemon will be disabled, if
such a NIC has been discovered on the system.