Download White Paper				14 of 18

Section 10: SNMP Remote Doesn't Report Alarms to the SNMP Manager

Note: You need two techs for this procedure: one at the remote site and another at the NOC.

1. At the remote site, find out what kind of local indicator you have that the remote is receiving and transmitting data - ideally this should be a software interface to monitor the device, but even a blinking Ethernet port LED will do.
2. The NOC tech should send a GetRequest from the SNMP manager and the remote site tech should watch the local indicators at his end.
3. If the remote site tech doesn't see any communication happen, the GetRequest isn't getting through. Ping the SNMP manager from the remote site to verify the IP connection.
4. If the ping is unsuccessful, double-check that the SNMP remote has the correct IP address and port for the SNMP manager and try again.
5. If the ping is still unsuccessful, you may have a network problem. Ask your network administrator for help.
6. If the communication between the remote and the SNMP manager is OK, but no traps are getting through to the manager, there may be a configuration problem.
7. Double-check the community strings databased on the SNMP remote. Community strings are case sensitive, so watch out for case mismatches.
8. Make sure that the SNMP manager has compiled the correct MIB for the SNMP remote. If the SNMP manager is using the wrong MIB, it will request invalid OIDs and the remote won't respond.

		Download White Paper				14 of 18