event notification destination create
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Create an event notification destination
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The event notification destination create
command creates a new event notification destination of either email or syslog type.
The following system-defined notification destination is configured for your use:
-
snmp-traphost - This destination reflects the configuration in "system snmp traphost".
Parameters
-name <text>
- Destination Name-
Use this mandatory parameter to specify the name of the notification destination that is to be created. An event notification destination name must be 2 to 64 characters long. Valid characters are the following ASCII characters: A-Z, a-z, 0-9, "_", and "-". The name must start and end with: A-Z, a-z, or 0-9.
- {
-email <mail address>
- Email Destination -
Use this parameter to specify the email address to which event notifications will be sent. For events to properly generate email notifications, the event system must also be configured with an address and mail server from which the mail will be sent. See event config modify command for more information.
- |
-syslog <text>
- Syslog Destination -
Use this parameter to specify syslog server host name or IP address to which syslog entries will be sent.
- |
-rest-api-url <text>
- REST API Server URL -
Use this parameter to specify REST API server URL to which event notifications will be sent. Enter the full URL, which must start either with an http:// or https:// prefix. To specify a URL that contains a question mark, press ESC followed by the "?". + If an https:// URL is specified, then Data ONTAP verifies the identity of the destination host by validating its certificate. If the Online Certificate Status Protocol (OCSP) is enabled for EMS, then Data ONTAP uses that protocol to determine the certificate's revocation status. Use the
security config oscp show -application ems
command to determine if the OCSP-based certificate revocation status check is enabled for EMS. [-certificate-authority <text>]
- Client Certificate Issuing CA-
Use this parameter to specify the name of the certificate authority (CA) that signed the client certificate that will be sent in case mutual authentication with the REST API server is required. + There can be multiple client certificates installed for the admin vserver in the cluster, and this parameter, along with the
certificate-serial
parameter, uniquely identifies which one. + Use the security certificate show command to see the list of certificates installed in the cluster. [-certificate-serial <text>]
- Client Certificate Serial Number }-
Use this parameter to specify the serial number of the client certificate that will be sent in case mutual authentication with the REST API server is required.
Examples
The following example shows the creation of a new event notification destination of type email called "StorageAdminEmail":
cluster1::> event notification destination create -name StorageAdminEmail -email StorageAdmin@example.com cluster1::> event notification destination show Name Type Destination -------------- ---------- --------------------- StorageAdminEmail email StorageAdmin@example.com snmp-traphost snmp 10.30.40.10 (from "system snmp traphost") 2 entries were displayed.
The following example shows the creation of a new event notification destination of type rest-api called "RestApi":
cluster1::> event notification destination create -name RestApi -rest-api-url https://rest.example.com/rest -certificate-authority cluster1-root-ca -certificate-serial 052213E60B7088 cluster1::> event notification destination show -name RestApi -instance Destination Name: RestApi Type of Destination: rest-api Destination Values: https://rest.example.com/rest Client Certificate Issuing CA: cluster1-root-ca Client Certificate Serial Number: 052213E60B7088