Forge Home


Configure OpenLLDP or lldpd, as appropriate


10,061 latest version

3.5 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.3 (latest)
  • 0.0.2
released Jul 9th 2013

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'csail-lldp', '0.0.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add csail-lldp
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install csail-lldp --version 0.0.3

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



csail/lldp — version 0.0.3 Jul 9th 2013


This module supports either of two LLDP daemons: OpenLLDP and's LLDP. The latter is superior and should be used wherever it is available. Currently only Debian (lldpd) and FreeBSD (OpenLLDP) are supported, but adding other systems should be trivial (all we need to know is the correct service and package name).

It also defines custom facts based on the LLDP neighbors of the client. These are primarily intended for storing in PuppetDB, but may also be used in manifests. Be aware, however, that LLDP information may expire on the client in the course of normal operation, so decisions should not be made on the basis of the absence of LLDP data. The particular facts defined depend on the LLDP implementation; lldpd provides a greater variety of information than OpenLLDP does. Both implementations will provide switch MAC address (chassis_mac), name, and port description (port_desc) when these variables are provided by the link partner. The fact lldp_neighbors is a comma-separated list of integers (since Puppet lacks a for loop) representing the index assigned to each LLDP neighbor; if the client has more than one interface (or more than one neighbor on a single interface), they will be numbered in an unpredictable order.

A virtual monit::monitor (tag => default) is set up for lldpd; because OpenLLDP does not write a pidfile, we can't use monit::monitor for it. This assumes that you have our version of the monit module, or else that you realize virtual monit::monitor resources in some other way. (We believe that it should be the monit module's responsibility to do this.)

N.B.: On FreeBSD, a pkgng package provider is required.


See the file LICENSE.