Skip to content
This repository has been archived by the owner on Mar 16, 2023. It is now read-only.

CanonicalLtd/charm-lldpd-1

This branch is 34 commits behind canonical/charm-lldpd:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

e64816a · Sep 16, 2022

History

39 Commits
May 6, 2020
Apr 23, 2020
Apr 23, 2020
Apr 23, 2020
Apr 23, 2020
Jun 8, 2020
Apr 23, 2020
Apr 30, 2020
Apr 23, 2020
Apr 23, 2020
Apr 30, 2020
Oct 4, 2019
Apr 23, 2020
Sep 14, 2016
Sep 14, 2016
Apr 23, 2020
Sep 16, 2022
Apr 7, 2020
Apr 23, 2020

Repository files navigation

Overview

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.

Usage

Start by installing the lldpd charm and relating it to another application:

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.

Scale out Usage

By scaling your application, subordinate charm will get installed automatically.

Known Limitations and Issues

LLDP is not very useful on containers and virtual machines and therefore it's use on those is not recommended.

Configuration

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.

Releases

No releases published

Packages

No packages published

Languages

  • Python 87.3%
  • Makefile 12.7%