Sending Trap


There are some circumstances where some Manager Applications also need to be intimated about occurrence of fault in the servers or applications being monitored. In such case, the alarms can be sent as traps to the manager applications and they can be viewed by any standard SNMP Manager such as Trap Viewer, HP Openview, IBM Tivoli etc. The supported versions of SNMP Trap are SNMPv1, SNMPv2c and SNMPv3.

To configure an alarm as a trap and send it as an action, follow these steps:

  1. Select the New Action link from the top menu.
  2. Click Send Trap under the Actions menu in the left frame. This opens the Create Action: Send Trap of SNMP action screen.
  3. Select the SNMP trap version (v1 / v2c / v3) from the combo box.
  4. Specify the following details:
    • Any display name for the action.
    • The destination or the manager application host name to which the trap has to be sent.
    • The port number, where the manager host is running.
    • The OID (Object Identifier) of the management object of a MIB.
    • The community for the trap.
    • The message, which will be sent as trap varbinds. The message can be enhanced by using Replaceable Tags.
      Note : Multiple Varbinds can be specified by having multiple ObjectIDs and their values as comma separated in "ObjectID" and " Message (Varbinds) " field respectively. For e.g., you can give ObjID1, ObjID2, ObjID3 in the ObjectID field to represent 3 Object IDs and correspondingly give ObjValue1, $RCAMESSAGE (the root cause message will be passed through the replaceable tag - $RCAMESSAGE), ObjValue3 etc., in the varbinds field to specify the values. ObjID1 and ObjValue1 will be passed as varbinds, same is the case with the other varbinds.
    • Choose the Message Format (Plain Text/HTML) for the trap.
    • For SNMP Version v3, select one of the three Security Levels:
      • No Auth, No Priv - Messages can be sent unauthenticated and unencrypted. Enter a UserName, Context Name, and Engine ID.
      • Auth, No Priv - Messages can be sent authenticated but unencrypted. Enter a UserName, Context Name, Engine ID, and an Authentication Password. You can select an Authentication Protocol (like MD5 or SHA) from the drop-down list.
      • Auth, Priv - Messages can be sent authenticated and encrypted. Enter a UserName, Context Name, Engine ID, an Authentication Password, and a Privacy Password. You can select an Authentication Protocol (like MD5 or SHA) and a Privacy Protocol (like DES or AES_128) from their respective drop-down lists.
    • Select the Generic type of trap PDU from the combo box. Specify the Enterprise OID for the trap You can also use the MIB Browser to provide the OID. In case, you want to upload a new MIB, then use the Upload Files/Binaries option. In case of SNMP v2c and v3 traps, mention the SNMP Trap OID.
  5. If you want to execute the action during specific time periods, enable the Execute Action based on Business Hours option and select the Business Hour during which the action has to be executed. The action can be configured such that it is executed during or outside the selected Business Hours. Use the drop-down menu to select your time window or click on 'Add New Business Hour' to create a new time window.
  6. Click Create Action to complete the configurations. This will list the trap action name and its details along with the other actions configured.
  7. Click Add New for creating more trap actions or Delete (on selecting the respective action's check box) to delete the action.

After creating an send trap action, you can edit or execute that action. These two tasks can be performed from the "View Actions" page.

  • To edit the action, click the Edit icon [].
  • You can also have a trial execution of the action. To do so, click the Execute icon [] of that action.
Note: You can configure alarm actions (for eg., EMails to be sent) for unsolicited traps. Refer FAQ.