We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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:
Oh, good catch. That makes the other issue kind of less daunting.
Sorry, something went wrong.
Resolving Issue #3085
It is possible to have the same IP address for the remote and main pollers causing synchronization issues
Okay, this is fixed now. Thanks for reporting!
No branches or pull requests