To verify that SNMP Manager is receiving trap messages

Steps

  1. On the SNMP Agent/Content Gateway machine, terminate the DownloadService process. Note that it may take several minutes from the time the trap occurs until the trap is sent to the SNMP Manager.
  2. On the SNMP Manager machine, check the SNMP trap log for an entry for DownloadService. The name and location of the log file is specified in the snmptrapd startup command (example provided above). Here is one way to find the message if it is being logged in /var/log/messages:

    cat /var/log/messages | grep DownloadService

    An entry might look like:

    Nov 25 15:09:42 localhost snmptrapd[11980]: 10.10.10.10]: Trap,
DISPAN-EV = STRING , DISMAN-EVENT-MIB::mteHotOID = OID ,
DISMAN-EVENT-IB::prErrMessage.4 = STRING: Too few DownloadService
running (# = 0)

    Grep for “snmptrapd” to see all log entries related to snmptrapd.

    Use nc (netcat) to test basic UDP connectivity between the Agent and the Manager. For example, this command could be run on either side of the connection to test the designated UDP ports.

    [root]# nc -u -v -z -w2 10.228.85.10 161-162

    Here, “-u” indicates UPD, “-v” indicates verbose output, “-z” means to scan for listening daemons, and “-w2” indicates to wait 2 seconds before timing out.

    Sample results:

    10.228.85.10: inverse host lookup failed: Unknown host (UNKNOWN) [10.228.85.10] 161 (snmp) open