Table of ContentsView in Frames

Setting up the Event Management System

You can configure EMS to reduce the number of event messages that you receive, and to set up the event destinations and the event routes for a particular event severity.


  1. Display the mail server settings: event config show
    cluster1::> event config show
      Mail From: admin@localhost
    Mail Server: localhost
  2. Optional: If necessary, change the mail server settings to meet your requirements: event config modify -mailserver name -mailfrom email address
    The following example shows how to change the mail server and display the results:
    cluster1::> event config modify -mailserver
    cluster1::> event config show
      Mail From:
    Mail Server:
  3. Create the destination for events by using the event destination create command.
    You can send events to email addresses, SNMP trap hosts, and syslog servers.
    The following command creates an email destination, sends all important events to the specified email address, and displays the results:
    cluster1::> event destination create -name test_dest -mail
    cluster1::> event destination show
    Name      Mail Dest.      SNMP Dest.  Syslog Dest.  Params
    --------  --------------- ----------- ------------- ------
    allevents -               -           -             false
    asup      -               -           -             false
    criticals -               -           -             false
    pager     -               -           -             false
    test_dest  -           -             false
    traphost  -               -           -             false
  4. Use the event route add-destinations command to define the severity level of messages to receive.
    You should set up event routes for critical and above events.
    The following example sends all critical, alert, and emergency events to the test_dest event destination:
    cluster1::> event route add-destinations -messagename * -severity <=CRITICAL -destinations test_dest
  5. To display all critical and above events, enter the following command: event route show -severity <=CRITICAL
    The following example shows the events with critical and above severity levels:
    cluster1::> event route show -severity <=CRITICAL
                                                         Freq        Time
    Message                 Severity    Destinations     Threshd     Threshd
    adminapi.time.zoneDiff  ALERT       test_dest        0           3600
    api.engine.killed       CRITICAL    test_dest        0           0
    app.log.alert           ALERT       test_dest        0           0
    app.log.crit            CRITICAL    test_dest        0           0
    app.log.emerg           EMERGENCY   test_dest        0           0
  6. If you are still getting too many event messages, use the -timethreshold parameter to specify how often events are sent to the destination.
    For example, the following event is sent to the destinations no more than once per hour:
    cluster1::> event route modify -messagename adminapi.time.zoneDiff
    -timethreshold 3600


When you have completed these steps, all events with a severity of critical or above are automatically sent to the destination specified in the event route.