Knowledge Base >> Sending SNMP Traps from Ignite 7.0+ Alerts

Sending SNMP Traps from Ignite 7.0+ Alerts - Confio Article 1572

Confio Article: 1572 Published: Oct 29 2009 11:32 AM
Version: >=7.0 Topic(s): Install and Setup Ignite Management Ignite Features
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.

 

 

SNMP Contacts

 

SNMP Contacts represent an NMS that will receive traps from Ignite Alerts. An SNMP Contact is created and modified through the Contacts and Contact Groups dialog found under the Ignite Administration section in the main Options menu.  To create an SNMP Contact, click the Create SNMP Contact button to display the New SNMP Contact dialog. To modify an existing SNMP contact, select the contact from the list of SNMP Contacts and click the Edit link.

 

Sending SNMP Step 1


The New SNMP Contact dialog contains 3 sections to configure the NMS that will receive traps from Ignite alerts. The upper section 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 enabled/disabled by checking the appropriate radio button. Disabling the SNMP contact will prevent traps from being sent to the NMS.

 

 

Sending SNMP Step 2


Section 2 is used to configure information for the NMS. In the Trap Receiver Host field, enter the host name or IP address 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 Receiver 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 section 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 Send Test button, Ignite will send a trap to the NMS specified in the Trap Receiver tab.  Ensure the NMS receives the trap indicating a successful test.

 

 

Sending SNMP Step 5 (optional)

 

An SNMP contact can optionally be added to an existing Contact Group.  For example, if an alert meets a specific threshold you may want to page the on call personnel as well as send an SNMP trap to the NMS.  In this case, add the SNMP contact to the On Call group.

Tags: ignite Alert SNMP trap MIB snp nm network management system hp openview tivoli