Step 7
|
In the Configure Notification window, configure the following values:
-
If you choose an EMAIL notification channel, configure the following in the Email Settings window:
-
Click the link to access the Email GUI window and configure a new email server.
Note
|
-
Notification type can be set for either REST API endpoint (webhook), PAGERDUTY, SNMP, SYSLOG, WEBEX, and EMAIL. If you choose EMAIL, but have not yet configured the email settings, you are prompted to access the GUI window where you can perform this task.
Email settings are configured in the Email tab.
(Optional) To access the Email tab, click the menu icon () and choose .
Expand External Services, choose , and click the Email tab.
-
Up to 20 email addresses per endpoint can be configured to receive email notifications. To add multiple email addresses, you
need to add each email address separately and press Enter (on your keyboard) after each addition. Cisco DNA Center validates the email addresses and notifies you if the syntax is incorrect.
-
If you need to configure more than 20 email addresses per endpoint, you can use a group email alias.
-
When using email destinations for event subscriptions, the emails that are sent show events with a UTC timestamp.
|
-
Click either Select Existing Instance to use the existing email instance or Create New Instance to create a new email instance.
-
If you click Select Existing Instance, from the Select Instance drop-down list, choose an email instance.
-
Enter the email addresses in the From and To fields and a subject for the Subject header in the email.
-
If you choose a SYSLOG notification, configure the following values in the Syslog Settings window:
-
Click the link to access the Syslog GUI window and configure a new syslog endpoint (syslog server hostname and port number).
Note
|
Notification type can be set for either REST API endpoint (webhook), PAGERDUTY, SNMP, SYSLOG, WEBEX, and EMAIL. If you choose SYSLOG, but have not yet configured the syslog server settings, you are prompted to access the GUI window where you can perform
this task. Syslog server settings are configured in the Syslog tab.
(Optional) To access the Syslog tab, click the menu icon () and choose .
Expand External Services, choose , and click the Syslog tab.
|
-
In the Protocol field, enter either TCP or UDP.
-
In the Port field, enter the port number of the syslog server.
-
In the Hostname/IP field, enter the hostname or IP address of the syslog server.
-
From the Select Instance drop-down list, choose the syslog instance.
-
If you choose a REST notification, configure the following values in the REST Settings window:
-
Click the link to access the REST Webhook GUI window and configure a new webhook endpoint.
Note
|
Notification type can be set for either REST API endpoint (webhook), PAGERDUTY, SNMP, SYSLOG, WEBEX, and EMAIL. If you select REST, but have not yet configured the webhook settings, you are prompted to access the GUI window where you can perform this task.
Webhook settings are configured in the Webhook tab.
(Optional) To access the Webhook tab, choose .
Expand External Services, choose , and click the Webhook tab.
|
-
From the Webhook Instance drop-down list, choose a notification endpoint and URL.
-
In the URL field, enter the URL address of the REST API endpoint that the event will be sent to.
Trust certificate: Whether a trust certificate is required for REST API endpoint notification.
Method: Either the PUT or POST method.
-
Basic: Authentication where the client sends HTTP requests with the word Basic in the authorization header, followed by a space and a base64-encoded string username:password. If you choose Basic in the GUI, the Headers field is automatically populated with the Authorization value.
-
Token: Authentication where users are authenticated using a security token provided by the server. If you choose Token, the Headers field is automatically populated with the X-Auth-Token value.
-
No Authentication: No authentication needed.
-
Headers: The Header Name and Header Value.
Note
|
The Headers fields may be automatically populated depending on your Authentication selection.
|
-
If you choose SNMP notification channel, configure the following values in the SNMP Settings window:
-
Click the link to access the SNMP GUI window and configure a new SNMP endpoint.
Note
|
Notification type can be set for either REST API endpoint (webhook), PAGERDUTY, SNMP, SYSLOG, WEBEX, and EMAIL. If you select SNMP, but have not yet configured the SNMP settings, you are prompted to access the GUI window where you can perform this task.
SNMP settings are configured in the SNMP tab.
(Optional) To access the SNMP tab, click the menu icon () and choose .
Expand External Services, choose , and click the SNMP tab.
The SNMP trap notification is only available for a system hardware event. When the health state of hardware components changes,
a system hardware event triggers notifications to subscribers. Hardware components monitored for changes include CPU, memory,
disk, NIC, fan, power supply, and RAID controller.
|
-
From the SNMP Instance drop-down list, choose the notification endpoint.
-
Create a new endpoint: Enter a new endpoint name and description.
-
In the Hostname/IP Address field, enter the hostname or IP address for the SNMP trap receiver (server).
-
In the Port field, enter the port number for the SNMP trap receiver (server).
-
If you choose PAGERDUTY notification channel, configure the following in the PAGERDUTY settings window:
-
In the SERVICE CONFIGURATION area, click either Select Existing Instance to use the existing PagerDuty instance or Create New Instance to create a new PagerDuty instance.
-
From the Select Instance drop-down list, choose a PagerDuty instance.
-
In the PagerDuty Events API URL field, enter a PagerDuty event API URL.
-
In the PagerDuty Integration Key field, enter a PagerDuty integration key.
-
If you choose WEBEX notification channel, configure the following values in the WEBEX Settings window:
-
From the Select Instance drop-down list, choose a Webex instance.
-
In the Webex URL field, enter the Webex URL.
-
In the Webex Room ID field, enter the Webex room ID.
-
In the Webex Bot Access Token field, enter the Webex bot access token.
|