The SNMP Trap Alert sends an SNMP Trap to the SNMP manager specified. Its function is to send the Alert text to an SNMP manager where it is analyzed by string pattern matching rules and reported, recorded, etc. by your enterprise's existing network management software.
The SNMP Trap Alert:
Use the SNMP Trap Alert to:
The Alert Parameters dialog box is used to specify the domain name or IP Address of the SNMP Manager receiving the SNMP Trap Alert, and any parameters required to connect to it.
IP Address / Domain Name
Specify the location of the SNMP Manager receiving the SNMP Trap Alert. Both IP Address and Domain Name are valid entries.
Examples of valid Domain Names are: www.xyzcompany.com and xyzcompany.com
An example of a valid IP address is: 10.200.60.3
Specify the Port Number that the target SNMP Manager listens on. By default, the standard Port Number used for SNMP Trap Listening (Port 162) is already entered.
The SNMP version used to send the Trap. The default setting (SNMP Version 1) cannot be changed.
SNMP Community strings act like passwords for SNMP information. Ensure that the value entered here matches the Community of the target SNMP Manager.
SNMP default communities are:
"From" IP Address
The SNMP Trap packet will appear to be sent from the specified IP address.
An example of a valid IP address is: 10.200.50.6
The SNMP Trap Alert can be configured to send Failure Notifications, Recovery Notifications, as well as Information Messages using text and ipMonitor Alert Tokens.
Send Failure Notifications
If enabled, ipMonitor will send an SNMP Failure Notification Trap when the Alert count matches the defined value in the Alert Range field.
Send Recovery Notifications
If enabled, ipMonitor will send an SNMP Recovery Notification Trap when the Alert count matches the defined value in the Alert Range field.
Send Information Notifications
If enabled, ipMonitor will send an SNMP Information Alert Trap when the Alert count matches the defined value in the Alert Range field. Body content is received from a Content Generator used to format captured Event Log, SNMP Trap or File Watching Monitor data for readability or layout prior to passing it to the Alert.
A number of predefined SNMPv1 Trap types can be selected from the drop-down list:
Refer to RFC 1157 for more information.
Enter the Object Identifier to identify the network management subsystem or "Enterprise" that generated the SNMP Trap
Enter a value to represent the specific kind of SNMP Trap being generated as the Alert. If used when the Trap Type field has been set to enterprise-Specific, the Specific Type value allows an SNMP Manager to correctly decipher and validate the SNMP Trap.
Message Content OID
The SNMP OID associated with the specific message content for the SNMP Trap being generated.
ipMonitor will use the values defined here to create the textual message content being sent in the SNMP Trap Failure, Recovery or Information Alert. Text, numerical data and ipMonitor Alert Tokens are all valid content entries.
Click the Token List button to place a Token between alphanumeric characters, words, or sentences. When a Token is found, it is replaced with dynamic content.
Note: Refer to Alert Tokens for more information.
To quickly configure the SNMP Trap Alert in a simple manner, enable it to send a "link down" message for failures, and a "link up" message for recoveries.
The default SNMP OID is the is the "system" object from MIB-II (RFC 1213):
Note: If you are using this Alert with HP Openview, enter the following SNMP OID into the "Message Content OID" field: 220.127.116.11.18.104.22.168.1
If you are not receiving traps, you may have to input the SNMP OID preferred by the management software.
The SNMP Trap Alert can be identified within a Profile's Alerts List by the puzzle piece icon: .
The SNMP Trap Alert can be scheduled based on a weeklong calendar. Refer to the section titled Scheduling Alerts for more information.
For information regarding escalated (ordered) alerting, refer to Alert Escalation.
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
Last Updated: March 30, 2007 | What did you think of this topic?