Skip to main content
A newer release of this product is available.

event route add-destinations

Contributors
Suggest changes
PDFs

(DEPRECATED)-Add destination(s) to an event definition

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 notification" command set.

The event route add-destinations command adds destinations to an event route. Any existing destinations assigned to the route are not removed.

The destinations you add must already exist. See the documentation for the event destination create command for information about creating destinations. To show all existing destinations and their attributes, use the event destination show command. To remove destinations from an event route, use the event route remove-destinations command.

You can use extended queries with such parameters as -severity and -snmp-support to specify multiple events that meet certain criteria. See examples below that show how to use extended queries.

Parameters

-message-name <Message Name> - Message Name

Specify the message name of the event you are modifying. You can use wildcards to specify a family of events or type of event.

[-severity {EMERGENCY|ALERT|ERROR|NOTICE|INFORMATIONAL|DEBUG}] - Severity

Use this optional parameter to specify a set of events that match this parameter value. You must use the -message-name parameter with wildcards to specify the family of events or type of events.

-destinations <Event Destination>,…​ - Destinations

Specify a comma-separated list of destinations to which notifications for the named event are sent. These destinations will be added to any existing destinations assigned to this event route.

Examples

The following example specifies that all RAID events go to the destinations named support.email, mgr.email, and sreng.pager:

cluster1::> event route add-destinations -message-name raid* -destinations support.email,mgr.email,sreng.pager

The following example specifies that all alert, and emergency events go to the destination named test_dest:

cluster1::> event route add-destinations -message-name * -severity <=ALERT -destinations test_dest

The following example specifies that all alert events that support a SNMP trap go to the destination named traphost. In this example, because the -snmp-support parameter is specified as part of extended queries, the -severity parameter must also be specified in the extended queries:

cluster1::> event route add-destinations {-snmp-support true -severity ALERT} -destinations traphost