Consulta de temas

Configuring Alert Actions in OpenManage Essentials


Introduction

OpenManage Essentials provides a powerful framework for monitoring and alerting which can be built upon to automate a variety of common tasks. This white paper illustrates several examples and provides complete steps on how to accomplish this. This white paper also describes the following supported alerts action in OpenManage Essentials and provides information on how an IT administrator can leverage them:

  • Alert Email Action
  • Alert Trap Forward Action
  • Alert Application Launch Action
  • Alert Ignore Action

Alert Email Action

The Alert Email Action feature helps you know the device status as soon as the device goes into critical state without you having to log on to the OpenManage Essentials console. You can customize alert severity, type, date, device, and days for Alert Email Action.
For the IT administrator to receive emails through the support desk, an SMTP server is required. The SMTP settings can be configured when an email alert action task is created. For SMTP settings. By default, port 25 is selected. You can customize the port according to your environment. For secured communication, you can enable ‘SSL’. Fill out all the fields.
You can enable Logging to help you troubleshoot when there are issues in sending emails to the SMTP server. The logs can be viewed under the Logs tab in the OpenManage Essentials console. It is not recommended to enable logging unless it is required as it will consume a large amount of storage space.Configuring Alert Actions in OpenManage Essentials 5

Creating An Alert Email Action

1. Click New Alert Email Action, provide a name and proceed.
2. In the Email Configuration window, provide a valid To and From email address.
3. Customize the Subject and Message of the email based on your preference.
4. To receive emails for the alerts with critical severity, select Critical in the Severity Association window.
5. To restrict the emails to a specific category, select one or more alert categories or sources.
6. A specific device(s) that needs to be monitored can only be selected through a query or from the device tree.
7. Emails can be configured to be sent during a specific date/range. If none of the options are selected in this wizard, emails will be sent without any time restriction.
8. On receiving an alert that matches all the conditions configured in the Alert Email Action task, an email is sent from OpenManage Essentials.

Alert Trap Forward Action

OpenManage Essential receives alerts from various SNMP agents and platform event traps (PETs) configured on the network. These traps may be required by another OpenManage Essentials instance or other network management systems (NMS) such as Microsoft SCOM, Dell ITA, Dell DMC, and so on. In this scenario, OpenManage Essentials can reproduce the traps and send them to other NMS for consolidation of the traps.
The system administrator can set the rules to define which traps will be forwarded based on the traps severity, traps categories, and devices/device groups.
When there are multiple instances of OpenManage Essentials configured where each instance is monitoring a subset of devices in a data center, a system administrator may want to consolidate the alerts from multiple OpenManage Essential instances for tiered management. Otherwise, the system administrator will have to individually check all the OpenManage Essentials servers for monitoring the devices. Instead a system administrator can configure a master OpenManage Essentials server to which all the other OpenManage Essentials instances will forward the alerts/traps. It will then provide the system administrator a consolidated view of all the alerts and enable the system administrator to manage the data center from a single master OpenManage Essentials server.

NOTE: Only SNMPv1 traps can be forwarded in the original format. OpenManage Essentials does not support forwarding SNMP v2 alerts generated by devices such as PDU, KVM, and so on in the original format. SNMP v3 alerts are not supported by OpenManage Essentials.



Creating An Alert Trap Forward Action

1. Click New Alert Trap Forward Action,, provide a name and proceed.
2. Provide the trap destination to which the alerts need to be forwarded. The community string provided should be the same as that of the destination system.
− Forward Trap in Original Format (if enabled): The destination console will receive the alerts in the same format as the original alert that was received in the OpenManage Essentials console. The alert will have proper severity, enterprise, specific and generic OIDs as the original alert received by OpenManage Essentials.
− Forward Trap in Original Format (if disabled): The destination console will receive the alert with ‘other’ category and source as ‘OMEalertforwardedalert’. The Enterprise OID alert will always be 1.3.6.1.4.1.674.11000.1000.100.1 irrespective of the original alert.
3. Severity, Category, Device, date and time can be customized according to the requirement as described for Alert Email Action.
4. The alert is forwarded to the destination OpenManage Essentials console if all the conditions configured in the task match.

Alert Application Launch Action

On receiving an alert in the OpenManage Essentials console, an IT administrator can automate to run scripts. Scripts can be used to log a trouble ticket or run any diagnostic tool. An executable VBScript or a batch file can be configured to run when an alert is received.
Creating An Alert Application Launch Action
1. Click New Application Launch Action, provide a name and proceed.
2. Configure the task by providing the correct path and the name of the script in the Executable Name field. The arguments are all configurable.
3. Severity, Category, Device, date and time can be customized according to the requirement as described for Alert Email Action.

Alert Ignore Action

An IT administrator can choose to ignore alerts for different reasons.

  • If a maintenance task is scheduled in a data center, alerts are received in bulk and the alert log is flooded in OpenManage Essentials. These alerts are known and can be ignored instead of flooding the database.
  • When you are aware that there are a few fault devices in the data center that keep generating alerts frequently. Alerts from those devices can be ignored.
  • In case of devices sending similar alerts continuously, you can choose to avoid receiving duplicate alerts in the console.

    Creating An Alert Ignore Action

    1. Click New Alert Ignore Action, provide a name and proceed.
    2. Select the alert severity in the Name and Severity Association wizard.
    3. Alert category, source, date/Range and time can be customized as described for Alert Email Action.
    4. In order to avoid duplication of alerts, select Yes in the Duplicate Alert Correlation wizard. Duplicate alerts received will be discarded within the specified time interval. If you select No, the duplicate alerts will be received in the console.
    Alerts that match the ignore alerts criteria will neither be stored in DB nor be displayed in the console, as they are discarded. By default, ‘Default duplicate alert filter’ is enabled to avoid getting duplicate alerts within 15 seconds.




  • Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips.

    Identificación del artículo: SLN285557

    Última fecha de modificación: 08/22/2014 02:09 PM


    Califique este artículo

    Preciso
    Útil
    Fácil de comprender
    ¿Este artículo fue útil?
    No
    Envíenos sus comentarios
    Los comentarios no pueden contener estos caracteres especiales: <>"(", ")", "\"
    Disculpe, nuestro sistema de comentarios está actualmente inactivo. Vuelva a intentarlo más tarde.

    Muchas gracias por sus comentarios.