Knowledge Base >> Sending SNMP Traps from Ignite 6.5 Alerts

Sending SNMP Traps from Ignite 6.5 Alerts - Confio Article 1528

Confio Article: 1528 Published: Nov 21 2008 11:05 AM
Version: 6.5 Topic(s): Ignite Features
Product(s): Ignite
Database(s): All

Overview

Ignite Alerts can be configured to send SNMPv2c Traps to a SNMP-enabled Network Management Station (NMS) when an alert level or threshold is reached. The trap will contain them name of the monitored database, alert name, alert level, and response instructions. The NMS that will receive the trap is represented as a contact (SNMP Contact) in Ignite.

 

MIB File

Installed with Ignite is a Management Information Base (MIB) file that defines the trap and associated data that is sent with each trap. The MIB file (CONFIO-MIB) defines the following:

  • Confio Private Enterprise Number
  • One Trap Definition (NOTIFICATION-TYPE)
  • Four string objects bound to each trap (database name, alert name, alert level, response instructions)

Prior to configuring SNMP traps in Ignite, the MIB file should be provided to the person(s) responsible for importing MIB files into the NMS.

 

Required Setup for SNMP Traps

Ignite uses Java stored procedures for sending traps. Each Repository that will be using the SNMP Trap feature of Ignite is required to have the Oracle JVM installed and configured properly.  In addition, several Java class files must be loaded manually into the Repository prior to creating SNMP contacts and sending traps. The process for loading the class files is described in the file SNMP_Setup.txt which is located in the snmp directory under the Ignite installation. 

Note: Ignite uses Westhawk’s Java SNMP Stack (Copyright (C) 1998, 1999, 2000, 2001, 2002 by Westhawk Ltd (www.westhawk.co.uk))

 

SNMP Contacts

SNMP Contacts represent an NMS that will receive traps from Ignite Alerts. An SNMP Contact is created and modified through the Group/Contact Administration dialog. To create an SNMP Contact, click the New SNMP… button to display the New SNMP Contact dialog. To modify an existing SNMP contact, select the contact from the list and click Modify…

 

Sending SNMP Step 1

 

The New SNMP Contact dialog contains three tabs to configure the NMS that will receive traps from Ignite alerts. The General tab contains fields to provide a name and description for the NMS.  These values will not be included in the trap. In addition, the SNMP contact can be disabled by un-checking the Active checkbox. Disabling the SNMP contact will prevent traps from being sent to the NMS.

 

Sending SNMP Step 2

 

The Trap Receiver tab is used to configure information for the NMS. In the Trap Receiver Host field, enter the host name or IP address (preferred) of the server on which the network management application is running. Enter the port number on which the NMS host is receiving traps in the Trap Receiving Port field (default is 162). In the Community String field, enter the community string used by the NMS for traps.

 

Sending SNMP Step 3

 

The Response Instructions tab provides a text box used to enter instructions that will be sent with the trap. Enter any information that the individuals monitoring the network will need to respond appropriately to the alert. Response Instructions are set on a per-SNMP contact basis, so the information should pertain to any alerts that notify this NMS.

 

Sending SNMP Step 4

 

The SNMP contact dialog provides a means of testing traps for new or existing SNMP contacts.  By clicking the Test Trap button, Ignite will send a trap to the NMS specified in the Trap Receiver tab.  The SNMP contact dialog provides a means of testing traps for new or existing SNMP contacts.  By clicking the Test Trap button, Ignite will send a trap to the NMS specified in the Trap Receiver tab.

Tags: ignite sending Alert SNMP trap MIB snp