This release supports audit log export to multiple syslog servers. This feature becomes important if the primary syslog server data becomes corrupted or irretrievable. There are two parallel syslogs streams going to two different syslog servers for redundancy.

To configure syslog servers using the Cisco DNA Center GUI, click the Menu icon > System > Settings > External Services > Destinations > Syslog. For information about the syslog server configuration, see the Cisco DNA Center Platform User Guide.

To subscribe an audit log to a syslog server, click the Menu icon > Activity > Audit Logs > Subscribe. Check one or more of the preconfigured syslog servers and Save.

This release supports new email features for Cisco DNA Center platform events. An event email is no longer in plain text, but now utilizes HTML formatting and images. The new event (HTML) email displays the following information:

• Email Header: Descriptive email header that may include problem description and location.

• Event Name: Descriptive text and link to event in the Cisco DNA Center GUI.

• Event Type: Event type (Network, App, System, Security, or Integrations type of event.)

• Event Time: Time of event's occurrence.

• Device Name: Name of the device

• Device IP: Device IP address

• Device Type: Device type (Switch, Router, AP, and so on.)

• Details: Details for the event.

• Status: Active, inactive, and so forth.

• View Device: Click the button to view device in Cisco DNA Center GUI.

The Cisco DNA Center platform GUI has been updated to support IPv6 for the following configuration settings:

• Webhook configuration: Updated the Cisco DNA Center platform GUI to support IPv6 format validation (the URL text field when adding a webhook).

  To access this field, click the Menu icon > System > Settings > External Services > Destinations > Webhook. Click the Add button to add a webhook.

• Email configuration: Updated the Cisco DNA Center platform GUI to support IPv6 format validation (the Primary SMTP Server Hostname/IP and Secondary SMTP Server Hostname/IP text fields).

  To access these fields, click the Menu icon > System > Settings > External Services > Destinations > Email.

• Syslog configuration: Updated the Cisco DNA Center platform GUI to support IPv6 format validation (the Hostname/IP text field).

  To access this field, click the Menu icon > System > Settings > External Services > Destinations > Syslog.

• SNMP notification trap receiver: Updated the Cisco DNA Center platform GUI to support IPv6 format validation (the Hostname/IP address text field).

  To access this field, click the Menu icon > System > Settings > External Services > Destinations > Trap > Add.

• Integration Settings: Updated the Cisco DNA Center platform GUI to support IPv6 format validation (the Callback URL hostname or IP address text field).

  To access this field, click the Menu icon > System > Settings > System Configuration > Integration Settings.

For this release, the SNMP trap configuration has moved from individual events to System Settings in the Cisco DNA Center GUI. Use the SNMP trap configuration to forward audit logs and event notifications.

To access the SNMP trap configuration, click the Menu icon and choose System > Settings > External Services > Destination > Trap.

For information about the SNMP trap configuration, see the Cisco DNA Center Platform User Guide.

For this release, an ITSM integration configuration window has been added to System Settings in the Cisco DNA Center GUI. Use this new window to configure ITSM (ServiceNow) access settings.

To access the ITSM integration configuration, click the Menu icon and choose System > Settings > External Services > Destination > ITSM.

For detailed information about the ITSM integration configuration and its options, see the Cisco DNA Center Platform User Guide.

For this Cisco DNA Center Platform release, the following new bundle event notifications are supported:

• On Active (Enable)

• On Disable (Disable)

• On Update

To perform the above actions on a bundle, click the Menu icon > Platform > Manage > Bundles. For detailed information about the bundles, see the Cisco DNA Center Platform User Guide.

This release supports the ability to create generic REST API endpoints for the following bundles:

• SWIM Events for ITSM (ServiceNow)

• Network Issue Monitor and Enrichment for ITSM (ServiceNow)

Note	Previously, you could only use predetermined endpoints as defined in the Cisco DNA App.

To access the bundles, click the Menu icon > Platform > Manage > Bundles.

For detailed information about creating generic REST API endpoints for bundles, see the Cisco DNA Center ITSM Integration Guide.

This release supports multiple Cisco DNA Centers to a single ServiceNow configuration.

The following event updates are now supported:

• Events are aware of the Cisco DNA Center instance.

  For example, when a specific Cisco DNA Center cluster generates an event to be sent out to ServiceNow, the event now has the Cisco DNA Center IP or hostname information within itself.

• When an event in the previous scenario is sent to ServiceNow, the extra field containing the Cisco DNA Center IP or hostname is now populated as a separate field in the incident, RFC, or problem.

• Any responses to the incident, RFC or problem coming from ServiceNow, identifies the correct event in the correct Cisco DNA Center instance.

  Note

  Responses reach the specific Cisco DNA Center only when the ServiceNow MID Server is configured and added to the Cisco DNA Controller Properties table. This table is located within the Cisco DNA App. All callbacks from ServiceNow to Cisco DNA Center require that the Cisco DNA Controller Properties table be configured with the correct MID Server details. This table should contain a list of all of the Cisco DNA Centers configured for ServiceNow integration. See the Scope Certified Application Installation and Configuration Guide on the ServiceNow Store website for MID server configuration information: https://store.servicenow.com/sn_appstore_store.do#!/store/application/03eb0f4ddbf6ba00f27978b5ae96197b/1.1.1

• For earlier releases, it was assumed that events were being sent to an external system from a single Cisco DNA Center cluster. In the event header for this release (with multiple Cisco DNA Center clusters), each of the events will have the corresponding Cisco DNA Center IP address. This will be the virtual IP address (VIP) for the Cisco DNA Center cluster.

The Cisco DNA Center CMDB synchronization is now multi-Cisco DNA Center aware:

• For a list of attributes that were synchronized from a particular Cisco DNA Center instance, each attribute is tagged with a Cisco DNA Center IP address.

• On the ServiceNow side, we are able to maintain as to which Cisco DNA Center instance the attribute came from. An extra attribute for the CI has been added to hold the Cisco DNA Center IP or hostname information.

For detailed information about the Cisco DNA Center to ServiceNow integration, see the Cisco DNA Center ITSM Integration Guide.

This release supports new and improved Cisco DNA Center platform messages for ServiceNow errors in the Runtime Dashboard

For detailed information about the Cisco DNA Center-to-ServiceNow integration, see the Cisco DNA Center ITSM Integration Guide. For information about the Runtime Dashboard, see the Cisco DNA Center Platform User Guide.

To access the Runtime Dashboard in the Cisco DNA Center GUI, click the Menu icon > Platform > Runtime Dashboard.

Table 2. Cisco DNA Center-to-ServiceNow Error Messages

ServiceNow Error Code	ServiceNow Error Description	Exception Category	Retry Without Corrective Action	Runtime Dashboard Message
400	Bad Request	Business	No	Invalid Input payload to ITSM. Contact administrator.
401	Unauthorized	Business	No	Invalid credentials or permission issues. Check with ITSM administrator.
403	Forbidden	Business	No	Access restricted. Check with ITSM administrator.
404	Request URL not found	Business	No	Service or URL not found. Contact respective support group.
408	Request Timeout	Technical	Yes	Connection timed out. Please retry. If issue persists, contact system administrator.
409	Conflict	Business	No	Duplicate Insert. Contact support group.
429	Too many requests	Technical	Yes	Network busy. Please retry. If issue persists, contact system administrator.
500	Internal Server Error	Technical	Yes	Internal Error. Please retry. If issue persists, contact system administrator.
502	Bad Gateway	Technical	Yes	Network error. Please retry. If issue persists, contact system administrator.
503	Service Unavailable	Technical	Yes	Possible Maintenance on ITSM. Please retry. If issue persists, contact system administrator.
504	Gateway Timeout	Technical	Yes	Connection timed out. Please retry. If issue persists, contact system administrator.
511	Network Authentication Required	Technical	Yes	Network Access Issue. Contact system administrator.
598	Network read timeout error	Technical	Yes	Connection timed out. Please retry. If issue persists, contact system administrator.
599	Network connect timeout error	Technical	Yes	Connection timed out. Please retry. If issue persists, contact system administrator.

This release supports a new Security Advisories Data report. The Security Advisories Data report supports the following features:

• Applied filters: Device Type, Location, Impact

• Displayed device data by column: Device Name, IP Address, Device Type, Serial Number, Image Version, Site, Advisory ID, CVSS Score, and Impact

  Note

  Each row in the report is a unique match of device and advisory, since there can be a one-to-many relationship between devices and advisories. For devices that were not scanned, they are included in the report and labeled as not scanned. For devices that were scanned and have no advisories, they are labeled as no advisories found.

For detailed information about the new security advisories report, see the Cisco DNA Center Platform User Guide, Chapter 7, Reports.

This release supports the following new licensing reports:

• AireOS Controllers Licenses Provides license information about the AireOS controllers.

• License Usage Upload Details Provides information about the license usage uploading schedule.

• Non Compliance Summary Provides the device series for which the number of used licenses are greater than the number of purchased licenses.

• Non Compliant Devices: Provides information about any noncompliant devices.

For detailed information about the new licensing reports, see the Cisco DNA Center Platform User Guide, Chapter 7, Reports.

This release support filtering of the Cisco DNA Center APIs. You can filter on the following fields:

• Device

• Site

• Timestamp

• Description

• Workflow (policy, assurance)

• User

This release lists Audit Log APIs under Event Management.

The following GET methods are supported:

• GET <cluster-ip>/dna/intent/api/v1/event/event-series/audit-log/summary

  Retrieve the Audit Log Summary from the Event-Hub.

• GET <cluster-ip>/dna/intent/api/v1/event/event-series/audit-logs

  Retrieve the Audit Log Event instances from the Event-Hub.

• GET <cluster-ip>/dna/intent/api/v1/event/event-series/audit-log/parent-records

  Retrieve the parent Audit Log Event instances from the Event-Hub.

To access the new APIs in the Cisco DNA Center GUI, click the Menu icon () and choose Platform > Developer Toolkit > APIs.

In the left pane, click Event Management.

This release lists Event Subscription and Notification APIs under Event Management.

The following POST methods are supported:

• POST <cluster-ip>/dna/intent/api/v1/event/subscription/email

  Create the email subscription endpoint for list of registered events.

• POST <cluster-ip>/dna/intent/api/v1/event/subscription/syslog

  Create the syslog subscription endpoint for list of registered events.

• POST <cluster-ip>/dna/intent/api/v1/event/subscription/rest

  Create the REST API or webhook subscription endpoint for list of registered events.

• POST <cluster-ip>/dna/intent/api/v1//event/subscription

  Subscribe subscription endpoint to list of registered events.

The following PUT methods are supported:

• PUT <cluster-ip>/dna/intent/api/v1/event/subscription/rest

  Update the REST API or webhook subscription endpoint for list of registered events.

• PUT <cluster-ip>/dna/intent/api/v1/event/subscription/syslog

  Update the syslog subscription endpoint for list of registered events.

• PUT <cluster-ip>/dna/intent/api/v1/event/subscription/email

  Update the email subscription endpoint for list of registered events.

• PUT <cluster-ip>/dna/intent/api/v1/event/subscription

  Update subscription endpoint to list of registered events.

The following GET methods are supported:

• GET <cluster-ip>/dna/intent/api/v1/event/event-series/count

  Retrieve the count of published notifications.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription/count

  Retrieve the list of subscriptions related to the respective event IDs (comma separated).

• GET <cluster-ip>/dna/intent/api/v1/event/artifact

  Retrieve the list of artifacts based on provided offset and limit.

• GET <cluster-ip>/dna/intent/api/v1/event/event-series

  Retrieve the list of published notifications.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription-details/syslog

  Retrieve the list of subscription details for the specified connector type.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription/syslog

  Retrieve the list of syslog subscriptions based the provided offset and limit.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription-details/email

  Retrieve the list of subscription details for the specified connector type.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription/email

  Retrieve the list of email subscriptions based on the provided offset and limit.

• GET <cluster-ip>/dna/intent/api/v1/events/count

  Retrieve the count of registered events with the provided eventIds or tags as mandatory

• GET <cluster-ip>/dna/intent/api/v1/event/artifact/count

  Retrieve the count of registered event artifacts with the provided eventIds or tags as mandatory.

• GET <cluster-ip>/dna/intent/api/v1/dna/data/api/v1/events

  Retrieve the list of registered events with the provided eventIds or tags as mandatory.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription

  Retrieve the list of subscriptions based on provided offset and limit

• GET <cluster-ip>/dna/intent/api/v1/event/subscription/rest

  Retrieve the list of REST/webhook subscriptions based on the provided offset and limit.

• GET <cluster-ip>/dna/intent/api/v1/event/subscription-details/rest

  Retrieve the list of subscription details for specified connector type.

• GET <cluster-ip>/dna/intent/api/v1/event/api-status/${executionID}

  Retrieve the status events of API calls with the provided execution ID as a mandatory path parameter.

The following DELETE methods are supported:

• DELETE <cluster-ip>/dna/intent/api/v1/event/subscription

  Delete the list of event subscription IDs (comma separated).

To access the new APIs in the Cisco DNA Center GUI, click the Menu icon () and choose Platform > Developer Toolkit > APIs.

In the left pane, click Event Management.

This release supports a new Security Advisories API. The following new methods are supported:

• GET: <cluster-ip>/dna/intent/api/v1/security-advisory/advisory

  Retrieve the list of advisories on the network.

• GET: <cluster-ip>/dna/intent/api/v1/security-advisory/advisory/aggregate

  Retrieve the advisory summary list.

• GET: <cluster-ip>/dna/intent/api/v1/security-advisory/device/{deviceId}/advisory

  Retrieve the list of advisories for a device.

• GET: <cluster-ip>/dna/intent/api/v1/security-advisory/device/{deviceId}

  Retrieve the list of advisory IDs for a device.

• GET: <cluster-ip>/dna/intent/api/v1/security-advisory/advisory/{advisoryId}/device

  Retrieve the list of advisories for a device.

To access the new APIs using the GUI, choose Platform > Developer Toolkit > APIs > Know Your Network > Security Advisories.

The Cisco DNA Center platform supports the following new Reports APIs.

The following GET methods are supported:

• GET <cluster-ip>/dna/intent/api/v1/data/view-groups/${viewGroupId}

  Retrieve a list of summaries of all views for a given view group.

• GET <cluster-ip>/dna/intent/api/v1/data/view-groups/${viewGroupId}/views/${viewId}

  Retrieve the complete information of the view that is required to configure a report.

• GET <cluster-ip>/dna/intent/api/v1/data/reports

  Retrieve the list of scheduled report configurations.

• GET <cluster-ip>/dna/intent/api/v1/data/view-groups

  Retrieve a list of summaries of all view groups.

• GET <cluster-ip>/dna/intent/api/v1/data/reports/${reportId}/executions

  Retrieve the details of all executions for a given report.

• GET <cluster-ip>/dna/intent/api/v1/data/reports/${reportId}

  Retrieve the scheduled report configuration using report id.

• GET <cluster-ip>/dna/intent/api/v1/data/reports/${reportId}/executions/${executionId}

  Retrieve the report content.

The following POST method is supported:

• POST <cluster-ip>/dna/intent/api/v1/data/reports

  Create and schedule a report configuration.

The following DELETE method is supported:

• DELETE <cluster-ip>/dna/intent/api/v1/data/reports/${reportId}

  Delete a scheduled report configuration and report executions.

To access the new APIs in the Cisco DNA Center GUI, click the Menu icon () and choose Platform > Developer Toolkit > APIs.

From the Operational Tasks drop-down list, choose Reports.

Resolution of several bugs that enhances the performance and stability of the Cisco DNA Center platform.

The following are the limitations and workarounds for IP Address Manager integration with Cisco DNA Center:

• Infoblox:

  • Infoblox does not expose a name attribute; therefore, the comment field in Infoblox is populated by the IP pool name during a sync.

  • For a pool import, the first 50 characters of the comment field are used. If there are spaces in the comments, they are replaced by underscores.

  • If an IP pool name is updated for an imported pool, the comments are overwritten and the new name is reflected.

• BlueCat: There are no limitations identified with BlueCat integration at this time.

Reports with significant data can sometimes fail to generate in the Cisco DNA Center platform. If this occurs, we recommend that you use filters to reduce the report size to prevent such failures.