OSPF routes are fetched during the polling process so if you have very big ospf clouds this can happen. Other routing info is done during the discovery instead of polling.
Not sure if you can set the data to be purged better or adjust the ospf polling separately.
BGP peers are within the poller reach but BGP routes should only be pulled during discovery, are you running the discovery process with the default 6h interval? If you look at your global config in the gui, what value do you have for route_purge?
I do remember someone else having the same issue with the table growing like crazy on cisco devices, I have only non-cisco devices and my routes table is 1.5MB so I don’t see this issue. OSPF and BGP are both enabled.
$config[‘syslog_purge’] = 30;
$config[‘eventlog_purge’] = 30;
$config[‘authlog_purge’] = 30;
$config[‘perf_times_purge’] = 30;
$config[‘device_perf_purge’] = 7;
$config[‘rrd_purge’] = 90;// Not set by default
$config[‘ports_purge’] = true;// Set to false by default
Hi ! I already tested this but no effect after i start dail.sh script ! Could it be possible that this feature is very new ? because we doesnt update our librenms daily ?! Thanks kristoferus75
The route table discovery feature is less than one month old. And the route table discovery is limited to 1000 routes with most of the devices, unless you change manually this value. So if you have a different behaviour, please let us know more:
number of routes per device
frequency of discovery
stability of your routes
and any other thing that might help.
we will update the librenms version next week -> hope that this solve the issue !
the problem ist that millions of lines with the same route are installed ->always a new line but same route ( i dont know after a polling or after a discovery freqency )
bgp and also ospf !
our devices have from full bgp table to only 100 Routes and that very stable
@kristoferus75
Yes, you are still running the old code. The new code will wipe the existing “route” table, so the 130G of data will be deleted.
Then, during each discovery, the routes will be polled and should not get duplicated anymore (this was tested with Cisco devices successfully).
Bye