Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > Send SNMP traps from DPA 7.0 alerts

Send SNMP traps from DPA 7.0 alerts

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 78 Votes: 0 Revisions: 10

This article applies to all versions of DPA and Ignite 7.0 and later.

Overview


DPA alerts can be configured to send SNMPv2c traps to an SNMP-enabled Network Management Station (NMS) when an alert level or threshold is reached. The trap contains the name of the monitored database, alert name, alert level, and response instructions. The NMS receiving the trap is represented as an SNMP contact in DPA.

MIB File


DPA contains 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:

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


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

SNMP contacts

SNMP contacts represent an NMS that will receive traps from DPA alerts. An SNMP contact is created and modified in Options > Administration > Contacts and Contact Groups. Click Create SNMP Contact, or select a contact and click Edit.

Sending SNMP Step 1


The SNMP Contact dialog contains three sections to configure the NMS that will receive traps from DPA alerts. The first section contains fields for name and description for the NMS.  These values will not be included in the trap. The SNMP contact can be enabled or disabled by checking Active or Inactive. If you disable the SNMP contact, traps are not sent to the NMS.

snmp_step1.jpg

Sending SNMP Step 2


Use the second section to configure information for the NMS. In the Trap Receiver Host field, enter the hostname or IP address of the server where the network management application is running. Enter the port number where the NMS host is receiving traps in the Trap Receiver Port field. The default is 162. In the Community String field, enter the community string used by the NMS for traps.

snmp_step2.jpg

Sending SNMP Step 3


Enter instructions to send with the trap in the Response Instructions section. Enter information that the individuals monitoring the network need to respond to the alert. Response Instructions are set for  each SNMP contact, so the information should pertain to alerts that notify this NMS.

snmp_step3.jpg

Sending SNMP Step 4


Click Send Test to send a trap to the NMS. Ensure the NMS receives the trap, indicating a successful test.

snmp_step4.jpg

Sending SNMP Step 5 (optional)

An SNMP contact can 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 and send an SNMP trap to the NMS. In this case, add the SNMP contact to the On Call group.

snmp_step5.jpg

Last modified
19:17, 22 Jun 2016

Tags

Classifications

Public