Sending Alerts through SNMP Traps

This feature enables the management tools on a system to use the alert information that Operations Sentinel receives through alert policy.

Each action list belonging to alert policy raises an alert with the alert ID as the action list name. Operations Sentinel allows selective enabling and disabling of sending alert information through SNMP traps. These traps are issued on the system (localhost) on which Operations Sentinel is installed. The other management tools installed on the system can capture these SNMP traps and make use of the alert information.

The alert information consists of Object Name, Application Name, Alert Text, Alert Identifier, Severity, Alarm Sender Time, and Alarm Server Time.

Specifying SNMP Trap Listeners

To configure the SNMP service

The Windows SNMP service must be running on the system from where the SNMP traps are generated. Refer to Operations Sentinel Administration and Configuration Guide for more information on how to configure the Windows SNMP service.

To add the Object Identifier (OID) Information

The OID used for Operations Sentinel alerts as designated by the Internet Assigned Numbers Authority (IANA) is 1.3.6.1.4.1.45552. Entities intending to receive the Alert-SNMP trap information can add the OID information to their Management Information Base (MIB).

To configure the alert policy

  1. In the navigation pane, under the Alert Policies node, expand the desired alert policy.

  2. Select and expand the Action Lists subnode. The action lists appear in the display pane.

  3. In the display pane, select the desired action list.

  4. In the properties pane, set the Enable SNMP alert parameter to True and then save the alert policy.

  5. Activate the alert policy. In case the policy is already activated, reactivate the policy after saving the changes.

Note: The alert policy must be in activated state in order to send out alerts.

To receive the alert information

Configure the third-party program receiving the Alert-SNMP trap information to listen for SNMP traps. You might need to make changes to accommodate the proprietary OID.

Note: The configurations vary depending on the choice of the third-party program.