You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just came across a scenario we might want to check for
On my remote poller lab I mistakenly entered the main poller Ip as the remote DB ip on the remote poller
This led to devices going bye bye when syncing the pollers see below
My Lab is setup as following
192.168.1.227 is the main poller
192.168.1.228 is the remote
below I had entered 192.168.1.227 as the remote DB and as you can see above this caused the device to disappear this could be very bad in production
The text was updated successfully, but these errors were encountered:
cigamit
changed the title
|Feature request| check if IP for main poller is entered as remote poller remote db IP
It is possible to have the same IP address for the remote and main pollers causing synchronization issues
Nov 11, 2019
netniV
changed the title
It is possible to have the same IP address for the remote and main pollers causing synchronization issues
When editing a poller, ensure each IP is unique
Dec 7, 2019
netniV
changed the title
When editing a poller, ensure each IP is unique
When editing a poller, ensure each listening IP is unique
Dec 7, 2019
Hey Guys
I just came across a scenario we might want to check for
On my remote poller lab I mistakenly entered the main poller Ip as the remote DB ip on the remote poller
This led to devices going bye bye when syncing the pollers see below
My Lab is setup as following
192.168.1.227 is the main poller
192.168.1.228 is the remote
below I had entered 192.168.1.227 as the remote DB and as you can see above this caused the device to disappear this could be very bad in production
The text was updated successfully, but these errors were encountered: