I might add, the IP addresses were 172.16.1.11 and 172.16.1.1 … I don’t know why that would have anything to do with it though.
~ Laz Peterson Paravis, LLC
On Feb 16, 2016, at 4:04 PM, Laz C. Peterson laz@paravis.net wrote:
The SNMP credentials are the same, in this case, but none of the IP addresses or hostnames changed. They are all static addresses set in the router or VM, as well as static DNS.
It was very odd.
If it happens again, is there a way of debugging or getting more information why this might be happening?
~ Laz Peterson Paravis, LLC
On Feb 16, 2016, at 3:49 PM, Colin Stubbs <colin.stubbs@equatetechnologies.com.au mailto:colin.stubbs@equatetechnologies.com.au> wrote:
Only when the IP for a monitored device has been “taken over” by a different device that accepts the same SNMP credentials.
e.g. when swapping in replacement devices
e.g. in your network outage situation the KVM VS may have wound up on the same IP somehow (DHCP, SLAAC or something else)
On 17 February 2016 at 09:42, Laz C. Peterson <laz@paravis.net mailto:laz@paravis.net> wrote: So, weird thing happened today …
We had a network outage that lasted for maybe 45 minutes that kept Observium from monitoring one site. When Observium resumed its normal monitoring activities, it somehow added a whole bunch of inventory items for a Cisco router to a KVM virtual server. About 10 minutes ago, it deleted all of the Cisco items, and is now back to normal.
Has anyone seen anything like this before? Does anyone know what might have caused this?
~ Laz Peterson Paravis, LLC
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium