[Plugin] LLDP for UNRAID (6.10+ / Support Topic)

[Rysz]

LLDP for UNRAID (6.10+)

A plugin that integrates a Link Layer Discovery Protocol service into UNRAID systems (speaking LLDP, CDP, FDP, SONMP and EDP). LLDP allows you to know exactly on which port is a server (and reciprocally). LLDP is an industry standard protocol designed to supplant proprietary Link-Layer protocols. The goal of LLDP is to provide an inter-vendor compatible mechanism to deliver Link-Layer notifications to adjacent network devices.

 

What's the most common use case? Image: https://lldpd.github.io/

You have a managed switch with tons of cables and you're not sure which port your Unraid machine is connected to.

The plugin allows the Unraid machine to advertise itself to the switch so ideally you'll see that it's connected on port X.

 

How to install?

Community Applications. 🙂

or via Direct Link: https://raw.githubusercontent.com/desertwitch/LLDP-unRAID/main/plugin/ulldpd.plg

 

How does it work?

After installation LLDP is disabled by default and waiting for your configuration.

All necessary steps to configure and use the plugin are explained in the GUI (Settings ➔ LLDP).

 

How to contribute?

https://github.com/desertwitch/LLDP-unRAID

... and of most importantly - please do test and report back here!

 

Edited February 26 by Rysz

[sonic6]

looks like it worked with Fritzbox 7950 AX

-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 1, Time: 0 day, 00:01:09
Chassis:
ChassisID: mac xxxxxxxxxxxxx
SysName: fritzbux
SysDescr: AVM FRITZ!Box 7590 AX 259.07.80
MgmtIP: 192.168.0.1
MgmtIface: 7
Capability: Bridge, on
Capability: Router, on
Capability: Wlan, on
Port:
PortID: mac xxxxxxxxxxxx
PortDescr: LAN:1
TTL: 60
-------------------------------------------------------------------------------

 

[BVD]

Looks like the release notes are missing:

 

 

 

Checked the github and doesn't appear to be posted there either, though looking at the commits it seems like it should just be something like "verify no LLDP service is running during install/upgrade" I think?

[Rysz]

6 minutes ago, BVD said:

Looks like the release notes are missing:

 

 

 

Checked the github and doesn't appear to be posted there either, though looking at the commits it seems like it should just be something like "verify no LLDP service is running during install/upgrade" I think?

 

Yeah it was just a very minor change in the positioning of some statements in the installation and removal processes - sorry, I missed the release note. 🙂 I've added the release notes now, you probably won't see them because you've already checked for updates, but other users will see them.

 

Edited March 16 by Rysz

[AnnabellaRenee87]

Weird problem, LLDP on the server looks to only be seeing my other LAN port on the server that's unplugged, I need it to be on the other one, It's only seeing eth1, not eth0.

 

 

If that makes sense.

 

Screenshots attached of what's being detected and what the settings are.

server-diagnostics-20240430-0759.zip

 

PS,

 

Here's my Routing Table if it's needed.

Edited April 30 by AnnabellaRenee87

[Rysz]

3 hours ago, AnnabellaRenee87 said:

Weird problem, LLDP on the server looks to only be seeing my other LAN port on the server that's unplugged, I need it to be on the other one, It's only seeing eth1, not eth0.

 

 

If that makes sense.

 

Screenshots attached of what's being detected and what the settings are.

server-diagnostics-20240430-0759.zip 233.47 kB · 0 downloads

 

PS,

 

Here's my Routing Table if it's needed.

 

LLDP broadcasts on all eth* (so eth0, eth1, eth2 ...) interfaces, so both on eth0 and eth1 in your case. It seems to be advertising as the management IPs both the IPv6 IP of your eth0 interface (as you have IPv6 enabled there) and the IPv4 IP of your eth1 interface (as you have IPv6 disabled there). I think that it's doing what it should, considering you have two physical interfaces (eth0, eth1) and it's advertising both with the respective default IP of each respective interface. Would you have liked for it to advertise the IPv4 IP of eth0 (even if you're using IPv6)? I can try to add a setting to manually override the advertised management IPs, but I'll have to look how to implement that so might take a while.

 

Edited April 30 by Rysz

[AnnabellaRenee87]

19 hours ago, Rysz said:

 

LLDP broadcasts on all eth* (so eth0, eth1, eth2 ...) interfaces, so both on eth0 and eth1 in your case. It seems to be advertising as the management IPs both the IPv6 IP of your eth0 interface (as you have IPv6 enabled there) and the IPv4 IP of your eth1 interface (as you have IPv6 disabled there). I think that it's doing what it should, considering you have two physical interfaces (eth0, eth1) and it's advertising both with the respective default IP of each respective interface. Would you have liked for it to advertise the IPv4 IP of eth0 (even if you're using IPv6)? I can try to add a setting to manually override the advertised management IPs, but I'll have to look how to implement that so might take a while.

 

Yes, I would like it to advertise IPv4 on eth0.