event route show

(DEPRECATED)-Display event routes

Availability: This command is available to cluster administrators at the admin privilege level.

Description

Note: This command has been deprecated. It may be removed from a future release of Data ONTAP. Instead, use the "event catalog" command set.
This command displays information about event routes. Event routes describe which events generate notifications. A route specifies what to watch for, whom to notify, and what to do should a particular event occur. By default, the command displays the following information:

To display detailed information about a specific event route, run the command with the -message-name parameter, and specify the name of the message. The detailed view adds the following information:

You can specify additional parameters to limit output to the information that matches those parameters. For example, to display information only about events with a message name that begins with "raid", run the command with the -message-name raid* parameter. You can enter either a specific text string or a wildcard pattern.

Parameters

{ [-fields <fieldname>, ...]
If you specify the -fields <fieldname>, ... parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.
| [-instance ]}
If you specify the -instance parameter, the command displays detailed information about all fields.
[-message-name <Message Name>] - Message Name
Selects the event routes that match this parameter value.
[-severity {EMERGENCY|ALERT|ERROR|NOTICE|INFORMATIONAL|DEBUG}] - Severity
Selects the event routes that match this parameter value. Valid values:
  • EMERGENCY - Disruption
  • ALERT - Single point of failure
  • ERROR - Degradation
  • NOTICE - Infromation
  • INFORMATIONAL - Information
  • DEBUG - Debug information
[-action <text>] - Corrective Action
Selects the events that match this parameter value. This parameter is most useful when entered with wildcards. The "action" field describes what steps, if any, you must take to remedy the situation.
[-description <text>] - Description
Selects the events that match this parameter value. This parameter is most useful when entered with wildcards. The "description" field describes why the event was encountered and what it means.
[-snmp-support {true|false}] - Supports SNMP trap
Selects the event routes that match this parameter value.
[-destinations <Event Destination>, ...] - Destinations
Selects the event routes that match this parameter value. A destination is a list of email addresses, SNMP clients, and syslogs.
[-frequencythreshold <integer>] - Number of Drops Between Transmissions
Selects the event routes that match this parameter value (number of events since previous notification).
[-timethreshold <integer>] - Dropping Interval (Seconds) Between Transmissions
Selects the event routes that match this parameter value.

Examples

The following example displays information about all event routes:
cluster1::> event route show
                                                  Freq    Time
Message               Severity  Destinations   Threshd Threshd
--------------------- --------- -------------- ------- -------
admin.config.backup.
push.fail             ERROR     allevents,pager      5     120
admin.config.changed  INFO      allevents            0       0
admin.file.deleted    INFO      allevents            0       0
admin.login.failure   INFO      allevents            0       0
admin.software.
commit.failure        ERROR     criticals,allevents  0       0
admin.software.
commit.success        INFO      allevents            0       0
admin.software.
committing            INFO      allevents            0       0
admin.software.
installed             INFO      allevents            0       0
aggrcopy.dst.
autoRestrictMsg       NOTICE    allevents            0       0
aggrcopy.dst.
noMemory              ERROR     pager,admin          4     300
...