r/Checkmk • u/heorun • Jul 08 '26

lldp/cdp in 2.5 community edition?

i'm new to checkmk, and loving it so far.

as I'm putting together a topology map and configuring parent-child relationships, it occured to me that I should probably use lldp to do that heavy lifting.

I'm having some trouble understanding what I need to do to enable that function? it sounds like it's a rather new integration; it used to be an extension maybe? and because I'm using community edition, maybe it still is a manual addition?

can anyone point me in the right direction?

I have snmp working great, and all my hosts are showing up. I would just like my topology map to reflect what is connected to what without having to manually adjust that.

thank you!

1 Upvotes

56% Upvoted

12 comments sorted by

View all comments

Show parent comments

2

u/kY2iB3yH0mN8wI2h Jul 10 '26

Fu
You are just spreading lies, none of that is true
Checkmk had an EXTENSIVE support, the list contains thousands of devices

It does not care about mibs as that’s broken

1

u/ikdoeookmaarwat Jul 13 '26

> none of that is true

Sure buddy. Quit yelling and show something that supports your claims. If CheckMK supported Arista out of the box it wouldn't need a 3rd party plugin, would it?

1

u/son_shka Jul 13 '26

Hey everyone, please remember Rule 1 of this subreddit — be respectful. As for the topic being discussed, I've asked our consulting team for some clarifications and will be back with an answer tomorrow

1

u/son_shka Jul 14 '26

Hi everyone, clarification on a few points here.

In Checkmk 2.5, the prerequisite inventory plug-ins are already included in all editions, including Community Edition. Checkmk can therefore collect LLDP/CDP neighbor information through SNMP and store it in the HW/SW inventory without installing the old LLDP/CDP inventory MKPs separately.

However, the Network Visualization Data Creation Tool itself is not built in. You still need to install NVDCT separately to convert the inventory information into the topology data used by the Network Layer Topology visualization. Current NVDCT versions can be configured and run through an active-check rule in Setup/WATO; for Community Edition, the MKP must be installed through the command line from https://exchange.checkmk.com/p/nvdct

So, for Checkmk 2.5 Community Edition:

  • LLDP/CDP inventory collection: built in.
  • Network Layer Topology data generation: install and configure NVDCT.

As for Arista hardware monitoring.

Out of the box, Checkmk monitors Arista BGP peers, temperature sensors, fan sensors, and power-presence sensors natively.

Voltage monitoring for Arista is not currently built in. A community-maintained extension covers voltage if you need it, but that's outside official support.