Version info:
Commit SHA: bd5e692dc778ff7e7e05e5765baa2ad584154589
Commit Date: 1543783698
DB Schema: 274
PHP: 7.2.12
MySQL: 10.3.11-MariaDB
RRDTool: 1.7.0
SNMP: NET-SNMP 5.7.2
I added the localhost device, and a single remote switch to the librenms webui, then enabled a /28 network in config.php to restrict discovery (before I go adding my entire network again)
After discovery it found the cambium devices I had allowed, but oddly the network map shows them connecting back to the monitoring server that librenms runs on, and doesnât show the extremexos switch at all even though it discovered them through the lldp on the extremexos switch, nor the extremexos switches between the cambiumâs and the monitoring switchâŠ
The librenms discovered a total of 5 switches, 7 or so cambiums and itself, yet the network map still only shows 7 cambiums connected back to the monitoring switch none of the XOS switches are showing up.
Pastebin of the discovery of the switch that was used for autodiscovery: pastebin.com/X51wzPgJ
In the âneighborsâ on the original switch i see all of the switches and cambiums, on the cambiums i donât see anything (i donât think they implement lldp-mib)
Edit:
I think i know why the cambiums shows up next to the monitoring server not because of lldp but because they have an interface on the same network as the monitoring server⊠whats funny though is if thats the case the xos switches should have also been next to monitoring as they also have a network interface on the same network as monitoring.
That said if i disable in config.php the use of mac addresses and leave it as only xdp (lldp) the map is blank saying i need to add or discover devices
$config[ânetwork_map_itemsâ] = array(âxdpâ);
I did some checking in mysql, and iâm seeing for example that when i check, so it would appear that for some reason remote_port_idâs arenât set
MariaDB [librenms]> SELECT local_port_id, remote_port, remote_port_id from ports AS I, links AS L WHERE I.device_id = 12 AND L.local_port_id = I.port_id ORDER BY L.remote_hostname;
±--------------±------------±---------------+
| local_port_id | remote_port | remote_port_id |
±--------------±------------±---------------+
| 460 | 46 | NULL |
| 461 | 46 | NULL |
| 462 | 47 | NULL |
| 463 | 48 | NULL |
| 459 | 46 | NULL |
±--------------±------------±---------------+
Probably you have ARP discovery enable. ARP doesnât really give us good info⊠I just says. Hey this device is somewhere out this port and someone has resolved it recently.
nope, stock autodiscovery settings (beyond having a $config[net set to restrict the autodiscovery from adding all my devices till i get the first few working)
The network map and auto discovery are two different things. With different settings for each.
Yes but if autodiscovery is limited to discovering only certain ip ranges the network map canât map things that the entire system donât know about.
I worked a bit with murrant before the holidays but even he seemed to be a bit lost on where the mapping was going haywire.
Network map using devices that are already in librenms using CDP and LLDP.
Hello,
Sorry for bringing up an old thread but we have this exact problem.
For some devices âremote_port_idâ show us âNULLâ and seems to me like the only thing different from those working with âmappingâ.
Did you have any progress or solution to this?
//Cristian
Do you have the remote device also monitored?
Didnât make any more progress got busy at work and havenât had time to really try to figure out with murrant and the team whats going on. Whatâs odd is that i thought it was because the cambium radios donât support lldp-mib, so maybe it was because both sides werenât seeing each other, but i also have 2 extreme switches that were autodiscovered (well 1 was the first unit manually added to librenms) and the second was autodiscovered, but even that doesnât show up in network map
No map to display, this may be because you arenât running autodiscovery or no devices are linked by mac address. And in the case of the extremes they show up as lldp neighbors in each other neighbor tab.
Yes both devices are monitored using librenms.
They also find each other via lldp but the link between them doesnât work in gui.
The only difference i found between working and none working is when looking at âlinksâ table:
working links: âremote_port_idâ = XXXX
none working links: âremote_port_idâ = âNULLâ
Would it help if i posted some kind of output/config file?
//Cristian
Ok we solved LLDP XOS and links in librenms.
I will post sample config for you to look at.
In this example we have a simple topology
oh-exro-gi01-02 P3 => P47 oh-exro-vett01-01
#oh-exro-gi01-02
enable lldp ports 3
configure lldp port 3 advertise port-description
configure lldp port 3 advertise system-name
configure lldp port 3 advertise system-capabilities
configure lldp port 3 advertise management-address
!
configure ports 3 display-string 3_OH-EXRO-VETT01-01
configure ports 3 description-string â3â
#oh-exro-vett01-01
enable lldp ports 47
configure lldp port 47 advertise port-description
configure lldp port 47 advertise system-name
configure lldp port 47 advertise system-capabilities
configure lldp port 47 advertise management-address
!
configure ports 47 display-string 47_OH-EXRO-GI01-02
configure ports 47 description-string â47â
As you can see the key was âdescription-stringâ.
If not configured it would be sent as something like âX450a-24x Port 6â wich will not work for Librenms (maybe a change in place to look at some regex string instead?).
I hope this is helpful for you or anyone finding this post.
//Cristian
1 Like