Table of ContentsView in Frames

Getting notified of dashboard alarms

You can view dashboard alarms by using the dashboard alarm show command. You can also subscribe to specific Event Management System (EMS) messages to receive notifications of dashboard alarms.

Before you begin

You must have used the dashboard alarm thresholds modify command to specify that the EMS sends a message when an alarm is generated.

About this task

The EMS generates messages for dashboard alarms when the threshold value is equal or greater than the critical threshold (rising) and when the threshold value is less than the warning value (falling). You need to route EMS messages for the object type for which you want alarm notifications:

aggregate-used
The following EMS messages are related to this object type:
  • mgmtgwd.aggregate.used.rising
  • mgmtgwd.aggregate.used.falling
cpu-busy
The following EMS messages are related to this object type:
  • mgmtgwd.cpu.busy.rising
  • mgmtgwd.cpu.busy.falling
op-latency
The following EMS messages are related to this object type:
  • mgmtgwd.op.latency.rising
  • mgmtgwd.op.latency.falling
port-problems
The following EMS messages are related to this object type:
  • mgmtgwd.port.problems.rising
  • mgmtgwd.port.problems.falling
port-util
The following EMS messages are related to this object type:
  • mgmtgwd.port.util.rising
  • mgmtgwd.port.util.falling

Steps

  1. Use the event destination create command to define the destination to which you want to send the EMS messages.
    Example
    cluster1::> event destination create -name dashboard_alarms -mail admin@example.com
  2. Use the event route add-destinations command to route EMS messages to a destination.
    Example
    The following example specifies that aggregate utilization messages go to the destination named dashboard_alarms.
    cluster1::> event route add-destinations -messagename mgmtgwd.aggregate.used* -destinations dashboard_alarms
    Example
    The following example specifies that all dashboard alarm messages go to the destination named dashboard_alarms.
    cluster1::> event route add-destinations -messagename mgmtgwd.aggregate.used*,mgmtgwd.port.problems*,mgmtgwd.op.latency*,
    mgmtgwd.port.util*,mgmtgwd.cpu.busy* -destinations dashboard_alarms