Distributed polling with overlapping IP ranges?

Help
1

Does LibreNMS support distributed polling for devices with overlapping IPs?

E.g., can one poller monitor a “host.foo” (10.8.5.11/32) whilst another poller monitors “host.bar” (also 10.8.5.11/32)?

2

IF u add by domain name, yes also on solo poller works also.

Rrds created are then 2 diffrent,
Host.foo and host.bar voor the rrd map.

Myself had multiple devices over same host.
Sw01.host.foo
Sw02.host.foo
Ect.
OFC port camping at host.foo if its wan polling. (And set on other port map)

3

Thanks SniperVegeta, but you may get me wrong. host.foo and host.bar are not the same device, nor are they residing in the same network. It’s two devices in two different customer networks, but with the same IP addressing.

How should this work with one poller? From the perspective of the poller (or the default gateway of the poller) there can only be one active route towards a network e.g. 10.8.5.0/24.

My question is: Can every poller have it’s routing towards a target host done from the perspective of the poller?

This is what I want to achive:

+--------------+
|   MSP MGMT   |         VPN         Poller1@Customer1             HOST-TO-BE-MONITORED@CUSTOMER-A
|   Network    |    +--------------+ 10.10.5.0/24 +--------------+ 10.5.8.11/24
+--------------+    |
||  LibreNMS  ||    |
||WebUI/DB/API|-----+
||10.10.4.0/24||    |    VPN         Poller2@Customer2             HOST-TO-BE-MONITORED@CUSTOMER-B
|--------------|    +--------------+ 10.10.6.0/24 +--------------+ 10.5.8.11/24
+--------------+
4

As long the poler1 DNS points to there IP and poller2 DNS points to there (same) IP it will be fine
dont forget the rra’s database (else other database) to be same

Poller 1 dont know poller 2, as long its not serving the same group, else it will be fucked.

So u need to force add whitout check on the main, set to poller 1 ( as name not as IP bc, main can not know IP and check)

so add sw01.comp1.com to poller 1 ( what will result in RRD map sw01.comp1.com mapped to 10.5.8.11)
and add sw01.comp2.com to poller 2 (what will result in RRD map sw01.comp2.com mapped to 10.5.8.11)

So your libre can get seperate data for same IP
but poller 1 could never take over poller 2. bc its comp1 or comp2 dedicated poller for there infra

5

This is great news! In combination with policy based routing this will enable us to monitor customers with overlapping IP address ranges using a single LibreNMS “plane”.

Thank you very much!