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

event destination create

Contributors
Suggest changes
PDFs

(DEPRECATED)-Create an event destination

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

The event destination create command creates a new event destination. An event destination is a list of addresses that receive event notifications. These addresses can be e-mail addresses, SNMP trap hosts, and syslog servers. Event destinations are used by event routes. Event routes describe which events generate notifications, and event destinations describe where to send those notifications.

When you create a destination, you can add e-mail addresses, SNMP trap hosts, and syslog hosts to the definition of the destination. Once the destination is fully defined, use the event route add-destinations command to associate the destination with event routes so that notifications of those events are sent to the recipients in the destination.

To see the current list of all destinations and their recipients, use the event destination show command.

There are several default destinations provided for your use.

  • allevents - A useful destination for all system events, though no events are routed to this destination by default.

  • asup - Events routed to this destination trigger AutoSupport(tm). Only use this destination to send notifications to technical support. See system node autosupport for more information.

  • criticals - A useful destination for critical events though no events are routed to this destination by default.

  • pager - A useful destination for all events that are urgent enough to page a system administrator, though no events are routed to this destination by default.

  • traphost - The default destination for all SNMP traps. You can also use the system snmp traphost add command to add SNMP recipients to the traphost default destination.

To add recipients to the default destinations, use the event destination modify command.

You should not create a destination that sends events to more than one type of recipient. Use separate destinations for e-mail, SNMP, and syslog activity. Also, use the traphost default destination for all SNMP activity. You must not create any other destination that sends traps to SNMP trap hosts. The traphost default destination is not required to be added to any event route.

Parameters

-name <text> - Name

This mandatory parameter specifies name of the event destination to create.

[-mail <mail address>,…​] - Mail Destination

Use this parameter to specify one or more e-mail addresses to which event notifications will be sent. For events to properly generate e-mail notifications, the event system must also be configured with an address and mail server from which to send mail. See event config modify for more information.

[-snmp <Remote IP>,…​] - SNMP Destination

To send traps to SNMP trap hosts, use this parameter with the host names or IP addresses of those trap hosts.

[-syslog <Remote IP>,…​] - Syslog Destination

Use this parameter with the host names or IP addresses of any remote syslog daemons to which syslog entries will be sent.

[-syslog-facility <Syslog Facility>] - Syslog Facility

This parameter optionally specifies a syslog facility with which the syslog is sent. Possible values for this parameter are default, local0, local1, local2, local3, local4, local5, local6, and local7. If you specify the default syslog facility, syslogs are tagged LOG_KERN or LOG_USER.

[-snmp-community <text>] - SNMP Trap Community

To specify an SNMP trap community, use this parameter with that string.

[-hide-parameters {true|false}] - Hide Parameter Values?

Use this parameter with the value "true" to hide event parameters by removing them from event notifications. This is useful to prevent sensitive information from being sent over non-secure channels.

Examples

The following example creates an event destination named support.email that e-mails events to the addresses supportmgr@example.com, techsupport@example.com, and oncall@example.com.

cluster1::> event destination create -name support.email -mail supportmgr@example.com,techsupport@example.com,oncall@example.com

This example creates an event destination named support.bucket01 that sends the notifications to a syslog host.

cluster1::> event destination create -name support.bucket01 -syslog loghost.example.com