Thanks! I’ll give the hierarchical setting a try to see how it looks.
Yes, I see the same weird loops and incorrect topology if I enable mac. With xdp alone the topology is correct provided all the switches support LLDP, however we have quite a few switches which don’t - not only do those not show up in an xdp only graph (as you would expect) you get really weird topology errors and loops if there is a switch which doesn’t support LLDP (and thus forwards LLDP on all ports) which is connecting multiple other switches which do. (As each one of those other LLDP switches is unaware of the intervening switch)
LibreNMS’s network drawing algorithm seems to get confused if a switch reports multiple LLDP partners on a single port, which happens if an intervening switch does not support LLDP.
I’ve noticed that for an LLDP link to appear in the network map, BOTH devices at each end of the link must report LLDP data via SNMP.
All our Meraki wireless access ports support LLDP, thus if I look at LLDP remote link partners directly on a switch which has an access point is connected, I can see the Name, IP address, etc of the Access point listed, and via the interface for the access point I can see the name/ip/port of the switch reported, so there is definitely bi-directional LLDP going on between the switch and Access point.
However the access points don’t show up in the xdp network map despite the access points being devices in LibreNMS and being polled with SNMP - presumably the reason is that while the AP’s report interface statistics via LLDP they don’t report LLDP via SNMP, so LibreNMS does not “connect the dots” and display the link.
They also aren’t listed under “ports” in the switch which is a shame. It’s a shame there isn’t a configuration setting to allow all LLDP remote partner information to be listed in the ports for a switch, not just devices that are also monitored via LibreNMS and report their LLDP state via SNMP.