The Event Notifications window opens.

Each notification is represented by a tile and contains link to view notification details. From the CHANNELS area in the left pane, click the radio button next to the notification channels to view the existing tiles with the selected channel.

Click Let's Do It to go directly to the workflow.

The Select Channels window opens.

Click Next to configure the values in the corresponding Settings window.

The Summary window opens.

To make any changes, click Edit.

The Done! Your new notification is complete window appears.

For more information, see Work with Event Notifications in the Cisco DNA Center Platform User Guide and Create an Event Notification in the Cisco DNA Center User Guide.

A Configurations window that contains an Events Settings section is displayed.

• Event Name: Name of the Cisco DNA Center event.

• Domain: Domain of the Cisco DNA Center event.

• Type: Network, App, System, Security, or Integrations.

• Category: Error, Warn, Info, Alert, Task Progress, or Task Complete.

• Severity: 1 to 5.

  Note	Severity 1 is the most important or critical priority and should be assigned for this type of event.

• Workflow: Incident, Problem, Event, or RFC (Request for Change).

• Actions: Edit.

To change what is displayed in the table, click the Filter icon or enter a keyword in the Find field. For example, to view all network notifications, enter Network in the Find field. To view all severity 1 notifications, enter 1 in the Find field.

You must choose the events in the Event Settings section to configure events for an ITSM integration. This enables notifications through Cisco DNA Center when the event occurs in the future.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

• Contents: Tab that accesses the APIs and integration flows that make up the bundle, or provides information about the integration flows that make up the bundle.

• Release Notes: Tab that displays latest release information about the bundle, including its version.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

A configuration slide-in pane appears.

For configuring an existing ServiceNow Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Host name: Hostname for the ServiceNow system.

• Username: Username required to access the ServiceNow system.

• Password: Password required to access the ServiceNow system.

After a successful test of connectivity to the server, configure Destination to receive events.

For configuring an existing Destination Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Destination to receive events: Choose one of the following:

  • Event Management: When setting up Cisco DNA Center integration with ServiceNow without using the Cisco DNA app, choose the Event Management option. The Event Management option also requires that you have the Event Management plug-in configured within the ServiceNow instance.

  • REST API Endpoint: The REST API Endpoint option can be used with the Cisco DNA app. With this option, data is sent to a REST API endpoint within the Cisco DNA app.

  • Generic REST Endpoint in ServiceNow: With this option, you can send the data to a different staging table in ServiceNow.

• Destination URI: Enter a destination URI (Uniform Resource Indicator) for the Generic REST Endpoint in ServiceNow option. This field is mandatory for this option.

After entering this information, proceed to the next step.

The changes made to the bundle begin to take effect immediately. Additionally, the bundle status changes from ENABLED to ACTIVE.

A Configurations window opens that contains an Events Settings section.

• Event Name: Name of the Cisco DNA Center event.

• Domain: Domain of the Cisco DNA Center event.

• Type: Network, App, System, Security, Integrations type.

• Category: Error, Warn, Info, Alert, Task Progress, Task Complete.

• Severity: P1 (Severity 1) through P5 (Severity 5).

  Note	Severity 1 is the most important or critical priority and should be assigned as such.

• Workflow: Incident, Problem, Event, or RFC (Request for Change).

• Actions: Edit.

You can adjust what is displayed in the table by clicking the Filter icon and using the filter, or by typing a keyword in the Find field. For example, to display all access point notifications, type AP in the Find field. To view all network notifications, type Network in the Find field. To view all severity notifications, type 1 in the Find field.

Choose a setting by clicking on the downward pointing angle and adjust the value. For example, click Network and adjust to App. This changes the event type from a network type to an application type. Click Severity and adjust to 1 from 5. This raises the severity level from 5 to 1.

This enables notifications through Cisco DNA Center when the event occurs in the future.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

• Contents: Tab that accesses the APIs and integration flows that make up the bundle, or provides information about the integration flows that make up the bundle.

• Release Notes: Tab that displays latest release information about the bundle, including its version.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

A configuration slide-in pane appears.

For configuring an existing ServiceNow Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Host name: Hostname for the ServiceNow system.

• Username: Username required to access the ServiceNow system.

• Password: Password required to access the ServiceNow system.

After a successful test of connectivity to the server, activate the bundle.

For configuring an existing Destination Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Destination to receive events: Choose one of the following:

  • Event Management: When setting up Cisco DNA Center integration with ServiceNow without using the Cisco DNA App, choose the Event Management option. The Event Management option requires that you have the Event Management plug-in configured within the ServiceNow instance.

  • REST API Endpoint: The REST API Endpoint option can be used with the Cisco DNA App. Data is sent to a REST API endpoint within the Cisco DNA App with the REST API Endpoint option.

  • Generic REST Endpoint in ServiceNow: For the Generic REST Endpoint in ServiceNow option, you can send the data to a different staging table in ServiceNow.

• Destination URI: Enter a destination Uniform Resource Indicator (URI) for the Generic REST Endpoint in ServiceNow option. This field is mandatory for this option.

After entering this information, proceed to the next step.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

• Contents: Tab that accesses the integration flows and APIs that make up the bundle.

• Release Notes: Tab that displays latest release information about the bundle, including its version.

An integration flow or list of integration flows appear underneath the header.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

• Review the Description, Tags, How to Use this Flow, and scheduler.

• Click Run Now (to run the scheduler now), Run Later (to schedule for a later time), or Recurring (to set up a recurring schedule).

  For Run Later, you need to select a date, time, and time zone. For Recurring, you need to set a repeating interval (daily or weekly), an interval duration (minutes or hours), and a start and end date.

• Click Schedule to enable the scheduler.

  Important

  Only configure and enable an integration flow schedule, after you have finished configuring the bundle itself as described in this procedure. You configure and enable an integration flow schedule by returning to this view and clicking Schedule, or by clicking the View Flows link in the Configure Basic ITSM (ServiceNow) CMDB synchronization slide-in pane (see following steps), or by clicking the menu icon () > Platform > Developer Toolkit > Integration Flows > Schedule to Publish Inventory Details-ServiceNow Connector.

A configuration slide-in pane appears. Review the CMDB synchronization information.

For configuring an existing setting, choose it from the drop-down menu in the window and click Next.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

Click Next.

• Hostname: Hostname or IP address of the ServiceNow server.

• Username: Username for access to the ServiceNow server.

• Password: Password for access to the ServiceNow server.

Click Check Connectivity to check access to the ServiceNow server.

Click Next.

For configuring an existing instance, choose it from the drop-down menu in the window and click Configure.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

Click Next.

• Destination Type: There are two destination type options to choose from:

  • Synchronize device inventory directly with CMDB

  • Post device inventory details to a staging table

  Note

  Use the Synchronize device inventory directly with CMDB destination type to send data to a REST API endpoint within the Cisco DNA app. You should use this destination type, if you are using the Cisco DNA app and do not have your own customized ServiceNow instance. Use the other destination type (Post device inventory details to a staging table) to send data to a REST API endpoint outside of the Cisco DNA app. Ensure that the created staging table has a field called u_inventory_details. The inventory details from the Cisco DNA app are mapped to this field. With the Post device inventory details to a staging table destination type, after data transfer you must write custom code to take the data from the staging table and map it to the ServiceNow CMDB.

• Destination URI: Uniform Resource Indicator of the ServiceNow server (CMDB) or staging table.

Click Next.

Clicking the top check box in the Select Inventory Data Fields window will select all of the inventory data fields for synchronization. Click this top check box if you want to sync all of the inventory data fields. Otherwise, review and click one check box at a time to create a smaller subset of inventory data fields for synchronization.

The Select Inventory Data Fields window consists of the following columns:

• Name: Name of the inventory data field.

• Description: Brief description of the inventory data field.

• Is Attribute/Is Reference: Whether the inventory data field is an attribute or a reference. A reference data field is used to create a relationship between two tables in a database. This is used for querying purposes. An attribute data field is used to add more data to a table in a database.

To change a data field's default designation, just click the desired data field designation (Attribute or Reference).

Currently, the integration only supports 'location', 'building', and 'part number' as reference fields.

After selecting the data fields to be synchronized and whether the data field is an attribute or reference, click Next.

Device families are the Cisco DNA Center device classifications (for example, Unified AP, Routers, Wireless Controller, Switches, and Hubs), where the inventory attributes/references mapping to ServiceNow is already available in the existing Cisco DNA Center application in ServiceNow. The type and number of device families can vary depending upon the different Cisco devices in the user's network.

CI classes are the database tables for ServiceNow (for example, cmdb_ci_wap_network, cmdb_ci_ip_router, cmdb_ci_ip_switch, and x_caci_cisco_dna_wireless_lan_controller). The CI Class column in the GUI window is used to map the CI classes to their respective device families.

The following table displays the Cisco DNA Center default CI classes for each device family. The default CI classes can be modified by the user. In case of other device families not listed below, Cisco will not have any default values specified in the CI Class column. The ServiceNow application user needs to either manually create the corresponding CI Classes and attributes/references mapping or use a pre-existing CI class a 'parent' CI class. Ensure the pre-existing or newly created class is inherited from the Network Gear (cmdb_ci_netgear) class.

After accepting or updating the information in this window, click Next.

Configure the following values:

• Enter Destination Type: Enter the same value as previously selected or keep the value at its default, Other Automated.

  • Synchronize device inventory directly with CMDB

  • Post device inventory details to a staging table

  Note	Other Automated is a preconfigured value for the discovery source attribute in an OOB ServiceNow instance. This is the value that indicates the data source from where the ServiceNow CI was discovered. As a default, Cisco uses one of the existing preconfigured values for the integration.

  We recommend that the user creates their own discovery source, so as to uniquely identify the source from where the devices were fetched to sync into the ServiceNow instance. The steps to create a new discovery source are described in the ServiceNow App 'Installation and Configuration guide'.

• Enter the Max Limit: Maximum number of devices that can be synchronized in an iteration (single API call).

After entering the above information, click Next.

After reviewing the information, click Configure.

For a successful configuration, you will receive a Done! Bundle Configured message.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

• Contents: Tab that accesses the APIs and integration flows that make up the bundle, or provides information about the integration flows that make up the bundle.

• Release Notes: Tab that displays latest release information about the bundle, including its version.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

A configuration slide-in pane appears.

For configuring an existing ServiceNow Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Host name: Hostname for the ServiceNow system.

• Username: Username required to access the ServiceNow system.

• Password: Password required to access the ServiceNow system.

After a successful test of connectivity to the server, configure Destination to receive events.

For configuring an existing Destination Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Destination to receive events: Choose one of the following:

  • Event Management: When setting up Cisco DNA Center integration with ServiceNow without using the Cisco DNA app, choose the Event Management option. The Event Management option also requires that you have the Event Management plug-in configured within the ServiceNow instance.

  • REST API Endpoint: The REST API Endpoint option can be used with the Cisco DNA app. With this option, data is sent to a REST API endpoint within the Cisco DNA app.

  • Generic REST Endpoint in ServiceNow: With this option, you can send the data to a different staging table in ServiceNow.

• Destination URI: Enter a destination URI (Uniform Resource Indicator) for the Generic REST Endpoint in ServiceNow option. This field is mandatory for this option.

After entering this information, proceed to the next step.

The changes made to the bundle begin to take effect immediately. Additionally, the bundle status changes from ENABLED to ACTIVE.

A Configurations window opens that contains an Events Settings section.

The following Event Settings information is displayed:

• Event Name: Name of the Cisco DNA Center event.

• Domain: Domain of the Cisco DNA Center event.

• Type: Network, App, System, Security, Integrations type.

• Category: Error, Warn, Info, Alert, Task Progress, Task Complete.

• Severity: P1 (Severity 1) through P5 (Severity 5).

  Note	Severity 1 is the most important or critical priority and should be assigned as such.

• Workflow: Incident, Problem, Event, or RFC (Request for Change).

• Actions: Edit.

You can adjust what is displayed in the table by clicking the Filter icon and using the filter, or by typing a keyword in the Find field. For example, to display all access point notifications, type AP in the Find field. To view all network notifications, type Network in the Find field. To view all severity notifications, type 1 in the Find field.

Choose a setting by clicking the downward pointing angle and adjust the value. For example, click Network and adjust to App. This changes the event type from a network type to an application type. Click Severity and adjust to 1 from 5. This raises the severity level from 5 to 1.

This enables notifications through Cisco DNA Center when the event occurs in the future.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

• Contents: Tab that accesses the APIs and integration flows that make up the bundle, or provides information about the integration flows that make up the bundle.

• Release Notes: Tab that displays latest release information about the bundle, including its version.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

A configuration slide-in pane appears.

For configuring an existing ServiceNow Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Host name: Hostname for the ServiceNow system.

• Username: Username required to access the ServiceNow system.

• Password: Password required to access the ServiceNow system.

After a successful test of connectivity to the server, activate the bundle.

For configuring an existing Destination Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Destination to receive events: Choose one of the following:

  • Event Management: When setting up Cisco DNA Center integration with ServiceNow without using the Cisco DNA App, choose the Event Management option. The Event Management option requires that you have the Event Management plug-in configured within the ServiceNow instance.

  • REST API Endpoint: The REST API Endpoint option can be used with the Cisco DNA App. Data is sent to a REST API endpoint within the Cisco DNA App with the REST API Endpoint option.

  • Generic REST Endpoint in ServiceNow: For the Generic REST Endpoint in ServiceNow option, you can send the data to a different staging table in ServiceNow.

• Destination URI: Enter a destination Uniform Resource Indicator (URI) for the Generic REST Endpoint in ServiceNow option. This field is mandatory for this option.

After entering this information, proceed to the next step.

Review the displayed bundles and their status.

The window displays all the provisioned fabric domains.

The resulting screen displays all the fabric sites in the fabric domain.

The Fabric Infrastructure table lists all devices in the network that have been inventoried.

• Status of the fabric ticket request: Ticket Approved, Ticket Rejected, or Failed.

• Timestamp of the fabric ticket.

The SDA Provision Creation Request slide-in pane displays the Event ID, Source, Destination, ITSM Workflow, ITSM Status, ITSM ID, ITSM Link, ITSM Last Updated Time, ITSM Entity Severity/Priority, and Event Severity of an individual fabric event. For more information, see Review the Event Summary in the Cisco DNA Center Platform User Guide.

Review the displayed bundles and their current status.

Additional information provided may include the following:

• General information: Vendor, version, platform, tags displayed under the square icon.

• Information: Tab that displays general information (purpose of bundle and how bundle works in the network), sample schemas, configuration notes, and other data about the bundle.

  Note

  The specific endpoint attribute data that is retrieved is displayed in the Information tab. The following endpoint attribute data will be retrieved from ServiceNow (with the display name in Cisco DNA Center within the parenthesis): Asset Tag (CMDB asset tag) Model Category (CMDB model category) Model (CMDB model) Managed by (CMDB managed by) Serial Number (CMDB serial number) Location (CMDB location) Department (CMDB department) MAC Address (CMDB MAC address) Display Name (CMDB display name)

• Contents: Tab that accesses the APIs and integration flows that make up the bundle, or provides information about the integration flows that make up the bundle.

• Release Notes: Tab that displays the latest release information about the bundle, including its version.

The integration flows appear underneath the header.

An Information field appears in the window.

After clicking the Enable button to confirm, a success message appears.

For the schedule-based integration flow (Scheduler for ServiceNow Asset Sync), perform the following tasks:

• Review the Description, Tags, How to Use this Flow, and scheduler.

• Click Run Now (to run the scheduler now), Run Later (to schedule for a later time), or Recurring (to set up a recurring schedule).

  For Run Later, you need to select a date, time, and time zone. For Recurring, you need to set a repeating interval (hourly, daily or weekly), an interval duration (minutes or hours), and a start and end date.

• Click Schedule to enable the scheduler.

  Important

  Only configure and enable an integration flow schedule after you have finished configuring the bundle itself as described in this procedure. You can configure and enable an integration flow schedule by returning to this view and clicking Schedule, or by clicking the View Flows link in the Endpoint Attribute Retrieval with ITSM (ServiceNow) slide-in pane (see the following steps), or by clicking the menu icon () > Platform > Developer Toolkit > Integration Flows > Scheduler for ServiceNow Asset Sync. When you perform the synchronization once, it is always a full sync. The incremental sync is performed only on the scheduled synchronization. The Recurring synchronization is scheduled synchronization, while the Run Later synchronization is a one-time sync. The first occurrence of recurring synchronization is also a full sync. You must configure a minimum of two occurrences for the recurring synchronization. To complete the first full synchronization, you must configure the synchronization schedule with an hourly difference of at least two hours.

A configuration slide-in pane appears. Review the Configure Endpoint Attribute Retrieval with ITSM (ServiceNow) information.

A configuration slide-in pane appears.

For configuring an existing ServiceNow Connection instance, choose it from the drop-down menu in the window and click Activate.

• Instance Name: Name of the instance.

• Description: Descriptive text of the instance.

• Host name: Hostname for the ServiceNow system.

• Username: Username required to access the ServiceNow system.

• Password: Password required to access the ServiceNow system.

1. Click the Create a new instance radio button and do the following to configure a new ServiceNow connection instance:

   1. In the INFORMATION area enter the instance name and description.

   2. In the SYNCHRONIZATION OPTIONS area check the Incremental Sync check box to select the incremental sync of endpoints and specify the maximum limit for incremental sync record to pull in each cycle.

      It is recommended to use the Incremental Sync that allows you to first retrieve all the data from the service now and later retrieve only the modified data from the subsequent iterations.