Users Guide

6. In Device Association, assign the device or device groups to which you want to associate this trap forwarding alert and then
click Next.
7. By default the Trap Forward Action is always active. To limit activity, in Date Time Association, enter a date range, time range,
or days, and then click Next.
8. In Summary, review inputs and click Finish.
The severity status for any trap is set to normal and for a successful alert action, combination of severity, category, and device
has to confer with the selections in the preceding steps.
Forwarding alerts use case scenarios
This section describes scenarios about forwarding alerts using the SNMP v1 and SNMP v2 protocols. The scenarios consists of the
following components:
• Managed node with an SNMP v1 agent, referred to as MNv1
• Managed node with an SNMP v2/v2c agent, referred to as MNv2
• Managed station 1 with OpenManage Essentials, referred to as MS1
• Managed station 2 with OpenManage Essentials, referred to as MS2
• Managed station 3 with a third-party software, referred to as MS3
Scenario 1 — Forwarding Alerts in the Original Format Using SNMP v1 Protocol
In this scenario, SNMP v1 alerts are sent from MNv1 to MS1 and then forwarded from MS1 to MS2. If you try to retrieve the remote
host of the forwarded alert, it displays the name of MNv1 as the alert originates from MNv1. MNv1 is displayed because the SNMP
v1 alert standards allow you to set the agent name in the SNMP v1 alert.
Scenario 2 — Forwarding Alerts in the Original Format Using SNMP v2/v2c Protocol
In this scenario, SNMP v2 alerts are sent from MNv2 to MS1 and then forwarded from MS1 to MS3. If you try to retrieve the remote
host of the forwarded alert from MS3, it is displayed as MS1
Since there are no elds in an SNMP v2 alert to specify the agent name, the host which sends the alert is assumed as the agent.
When an SNMP v2 alert is forwarded from MS1 to MS3, MS1 is considered as the source of problem. To resolve this issue, while
forwarding SNMP v2 or v2c alerts, a varbind is added with OID as .1.3.6.1.6.3.18.1.3.0 with the variable value as Agent Address. This
has been set based on the standard OID specied in RFC2576-MIB. When you try to retrieve the Agent Address from MS3, it is
displayed as MNv2
NOTE: If the SNMP v2 alert is forwarded from MS1 to MS2, the remote host is displayed as MNv2 because MS1 parses
the extra OID along with the forwarded trap.
Scenario 3 — Forwarding Alerts in the OMEssentials Format Using Either SNMP v1/v2 Protocol
In this scenario, SNMP v1 alerts are sent from MNv1 to MS1 and then forwarded to MS2. If you try to retrieve the remote host of
the forwarded alert, it is displayed as MS1. The severity and the message of the alert is also dened by MS1 and does not display the
original severity and message dened by MNv1.
NOTE: The same behavior applies for SNMPv2 traps.
Working with sample alert action use cases
Sample alert actions are available for the Application Launch, E-mail, Ignore, and Trap Forwarding alert actions. Sample alert action
use cases are disabled by default.
To enable a sample use case, right-click the use case and select Enable.
Use cases in alert actions
Application Launch
Sample - Run Script on Server Critical Alert—Enable this use case to run a custom script when a critical alert is received.
Email
248