Audience: IT Support Staff

When Used: If a client wants to use SNMP traps as part of their notification system.


Notes


Testing SNMP traps

There is a daemon called snmptrapd that can be run to handle incoming SNMP traps. This can be run on a node such as cablegnw or any other Linux machine that has a public IP address.

From the command line run the following command to start the daemon.

The log file will contain the snmp traps that are received.

Follow the same setup as above using the IP address of the machine that will be running the snmptrapd daemon.

The machine receiving the traps will either need to have the firewall temporarily disabled while the testing is being done or have a rule added to allow the SNMP traffic through. (Port 162 is the default SNMP port.)


Setup (historical)

NOTE: This setup information is no longer needed. SNMP is now configured through the Notification Center. This setup information is kept for historical reasons.

First add a new email address in the Notification Center for that clients account. Example: test@globalnetwatch.com (The actual address isn't important since it will be changed below to an IP address - just ensure that it is not already in use on that account.)

After creating the new email entry, make the following changes to the new address in the database:

  1. In database, update notification table to change the value for notifyid. Example:

     SQL> update notification set notifyid=2 where subid=2342 and notifyinfo='echambers@globalnetwatch.com';
     

    The following values are available for notifyid:

      NOTIFYID DESCRIPTION
    ---------- --------------------------------------------------
             0 email
             1 TCP snmp trap
             2 UDP snmp trap
     
  2. Update notification table in database - change notifyinfo to an ipaddress instead of an email address.

     SQL> update notification set notifyinfo='70.168.37.72' where subid=10061 and notifyinfo='echambers@cox.net';
     
  3. Update notification table in database - change notlevel to 0 (The default is -1)

     SQL> update notification set notlevel=0 where subid=10061 and notifyinfo='70.168.37.72';
     
  4. Set other flags to N. This is the setup for Allstate (A known working implementation)

     SQL> update notification set error_msg_type='N' where subid=10061 and notifyinfo='70.168.37.72';
     
     Allstate Example:
     SQL> select * from notification where subid=754;
          SUBID NOTIFYINFO
    ---------- ------------------------------------------------------
      NOTIFYID A B S E S   NOTLEVEL
    ---------- - - - - - ----------
           754 167.127.14.38
             2 N N N N A          0
    
           754 68.15.235.75
             2 N N N N A          0
    
         
    

    Note: The status flag should remain set to A to indicate that the address is active.


Message Format

The Object ID (OID) is custom generated by the GNW notification server.

The OID 1.3.6.1.2.1.2.3.{37-40} can be broken down to the following 1.3.6.1.2.1.2.<gnw>.<serviceCnt>.<status>

1.3.6.1.2.1.2 - SNMP MIB-2 Interfaces, aka iso.org.dod.internet.mgmt.mib-2

.3 - GNW

.37 – Service Count as seen on GNW Subscriber Home page

.0, .1, .2 – Status: 1 first notification, 2 second notification, 0 OK

SNMP Traps (last edited 2012-04-17 20:54:19 by Eric)