Previous Page: Checklist: 5 Steps You Can Take Today to Start Your SNMP Monitoring Project
PDFDownload White Paper

SNMP Troubleshooting Guide

Not getting Traps from your SNMP RTU? Here's some quick troubleshooting steps to isolate the problem:

  • Check RTU configuration
    • Is the Trap address set to the correct IP address for the SNMP manager?
    • Is the RTU configured to send Traps to Port 162? (Port 162 is the standard port for receiving SNMP Traps - if your SNMP manager uses a different port, make sure all devices are configured for the same port)
  • Are all alarm points on the RTU configured to send Traps?
    • Does the Trap community string on the RTU match the Trap community string on the SNMP manager?
  • Use packet sniffer at RTU end to make sure Trap PDUs are sent.
    If no packet sniffer is available, proceed to the next step. If your RTU is a DPS Telecom unit, use the Analyze mode of your included configuration software.
  • If RTU configuration is correct, check network communication between the SNMP manager and the RTU
    • Ping the RTU from the SNMP manager
      If the ping is unsuccessful, check the firewall configuration. Reconfigure firewall to allow UDP traffic at Port 162 (or port used by your SNMP manager)
    • Use packet sniffer at SNMP manager end to make sure Trap PDUs are arriving at the manager.
  • If Trap packets are arriving, check SNMP manager configuration
    • Double-check Trap community string settings
    • Make sure that the right MIB file for the RTU has been compiled on the SNMP manager.
  • If no Trap packets are arriving at the SNMP manager, there is an error in the network settings. Consult your network administrator.
Next Page: SNMP Glossary
PDFDownload White Paper
Sitemap