rosederekj
asked on
Troubleshooting SNMP Alerts with Solarwinds IP Monitor 8.5
I just moved our IP Monitor 8.5 instance from an old Windows 2000 physical machine to a Windows 2003 Virtual Machine running on ESX. The migration went good for the most part, and the only remaining issue is getting the SNMP alerts to work right. The SNMP Cold Starts seem ok, but the straight SNMP alerts are all down with a status of "The remote device failed to respond"
I don't have the luxury of knowing if these were 100% before the migration since the old machine is off and the license removed (parked). There are only two SNMP alerts that work - they all use one of two communities, which are called "CommunityA" and "CommunitB" (not real names). They all use port 161 and the OID is the same for system uptime.
I don't know a lot about SNMP and am wondering if I have to troubleshoot the communities somehow, but can't find them in any of the pages of IP Monitor. Any help is greatly appreciated.
I don't have the luxury of knowing if these were 100% before the migration since the old machine is off and the license removed (parked). There are only two SNMP alerts that work - they all use one of two communities, which are called "CommunityA" and "CommunitB" (not real names). They all use port 161 and the OID is the same for system uptime.
I don't know a lot about SNMP and am wondering if I have to troubleshoot the communities somehow, but can't find them in any of the pages of IP Monitor. Any help is greatly appreciated.
ASKER
the IP Monitor can connect, as the PING alerts for the same host are working fine. For example, let's say MACHINEA has a PING alert and a SNMP alert. The PING alert is working and online, but the SNMP alert shows the error above.
The only thing I could figure was it had something to do with the community setting?
The only thing I could figure was it had something to do with the community setting?
Yes could be. Do you have a common community string on all machines. You can verify the community string on each machine if it is correct and co-relate it to the community strings you have put in your IP Monitor.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That was it - the machines were hard coded to accept SNMP monitoring from a specific IP. When I changed the new machine to the IP of our old monitoring machine, it worked. Thanks!
The error "The remote device failed to respond" suggests that your IP Monitor is unable to connect to the device. Have you tried to manually ping any of the devices on which you are getting alert errors?