Hello community!
We are trying to monitor the BGP status between two mikrotik routers but the LibreNMS routing module does not appear.
We also try to monitor the BGP status between a mikrotik and a VyOS router and we cannot see it either.
Does anyone know why this could be happening?
Are the BGP Peer discovery and poller modules enabled (Device Settings>Modules)
Hi! @Heath_Barnhart
Yes, both are enabled.
I deployed a new server using the .ova image for vm ware and I see that the BGP module works better there. I can’t think of what could be causing this difference between the manual installation and the image for VM weare
It seems to be a manual installation problem. The BGP state within Routing appears as “STOP”. I reinstalled LibreNMS again manually and it continues to appear like this. However, from the .OVA image the reading is correct and the state within Rounting appears as “START”. I don’t know how to fix this problem, but it seems to be a bug in the current version.
What’s the LibreNMS version in the OVA versus manual? Could you run ./validate on both and post them?
There is version difference in the code, we need to figure out where to determine what is the cause of the problem.
Hello @Heath_Barnhart
Thank you very much for answering! 
Yes, there is a difference between the .ova and github image versions.
The manual download from github I was using was running version “24.2.0-37-gdd6ac92f1 - Fri Mar 29 2024 06:30:17 GMT-0300”, while the .ova has version "23.9.1 - Mon “September 18, 2023 22:59:06 GMT-0300.”
Yesterday I temporarily moved the manual version to the stable “release” branch with “set lnms config:set update_channel release” to wait for the next stable version, and today it was updated ( 24.3.0 - Mon Apr 01 2024 12:18:44 GMT - 0300). Unfortunately the problem does not seem to be resolved 
I share here the outputs of the ./validate script
Git version:
===========================================
Component | Version
--------- | -------
LibreNMS | 24.3.0 (2024-04-01T12:18:44-03:00)
DB Schema | 2024_02_07_151845_custom_map_additions (290)
PHP | 8.1.12-1ubuntu4.3
Python | 3.11.4
Database | MariaDB 10.11.2-MariaDB-1
RRDTool | 1.7.2
SNMP | 5.9.3
===========================================
[OK] Composer Version: 2.7.2
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQL and PHP time match
[OK] Active pollers found
[OK] Dispatcher Service is enabled
[OK] Locks are functional
[OK] Python wrapper cron entry is not present
[OK] Redis is functional
[OK] rrd_dir is writable
[OK] rrdtool version ok
OVA version:
===========================================
Component | Version
--------- | -------
LibreNMS | 23.9.1 (2023-09-19T01:59:06+00:00)
DB Schema | 2023_09_01_084057_application_new_defaults (259)
PHP | 8.1.2-1ubuntu2.14
Python | 3.10.12
Database | MariaDB 10.6.12-MariaDB-0ubuntu0.22.04.1
RRDTool | 1.7.2
SNMP | 5.9.1
===========================================
[OK] Composer Version: 2.7.2
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQl and PHP time match
[FAIL] No active polling method detected
[FAIL] No active dispatcher nodes found
[OK] Locks are functional
[FAIL] Python wrapper cron entry is not present
[OK] Redis is unavailable
[OK] rrdtool version ok
[OK] Connected to rrdcached
[FAIL] Scheduler is not running
[FIX]:
sudo cp /opt/librenms/dist/librenms-scheduler.service /opt/librenms/dist/librenms-scheduler.timer /etc/systemd/system/
sudo systemctl enable librenms-scheduler.timer
sudo systemctl start librenms-scheduler.timer
librenms@ubuntu:~$ ^C
In the .ova image you can see some errors. But it is the original form of the VM and that is where everything works well.
What I’m going to try now is to update the VM with the .ova version to the latest version available to see if the problem is replicated. What do you think?
The OVA is very of date and something has changed between September and now. We need to figure out what. Please look through the changelogs between September 2023 and now looking for changes to Mikrotik or BGP, and see what those changes were. If you need help interpreting a change, let me know the PR number after the change and I will take a look when I have time.
Something else to try. From the manual installation run the following, filling in your SNMP community string and IP address of the router. It should return your BGP mib information.
/usr/bin/snmpwalk -v2c -c -M /opt/librenms/mibs -m all -t 15 -r 3 BGP4-MIB::bgp
