Since we've been using InterMapper 5.2.2 (now upgraded to 5.2.3) we've noticed some intermittent network behavior that has us confused.
We're polling more than 500 devices, for SNMP or ICMP, generally at 30 second intervals. Intermittently, IM will report a random device(s) as being "down". A console ping session from the IM server confirms the IM status...that the device is unavailable. Traceroute from the IM server stops ONE HOP AWAY from the device reported as down. During the time that IM reports the device to be down we can verify that the device is indeed alive by pinging from another PC. The device may stay "down" anywhere from a few seconds to several minutes...long enough to set off alerts to our pagers/cell phones. We can clean up the maps by simply restarting the IM process on the server. A ping session running from the IM server while we restart the process confirms the result. At first we thought that we had a flaky IM server, running Windows Server 2008R2. We moved IM to our blade server running CentOS Linux and we have seen exactly the same behavior, so we know it's not related to the OS, nor the physical hardware. We've been using InterMapper for years and have never seen this sort of behavior. We're rapidly getting tired of a big batch of bogus alerts that disturbs our daily routine and gets us out of bed at night. Anybody else seen this problem? ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
