Review the bundles and their current status that appear on the screen.

Additional information provided may include:

• 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 appears underneath the header.

An Information field appears in the window.

After clicking Enable 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.

  Configure and enable an integration flow schedule, only after you have finished configuring the bundle. To configure and enable an integration flow schedule, return to this view and click Schedule. You can also click the View Flows link in the Configure Basic ITSM (ServiceNow) CMDB synchronization slide-in pane. Alternatively, click the menu icon and choose 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, select 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, select 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 select 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 Catalyst app. You should use this destination type, if you are using the Cisco Catalyst 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 Catalyst app. Ensure that the created staging table has a field called u_inventory_details. The inventory details from the Cisco Catalyst 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 move the data from the staging table and map it to the ServiceNow CMDB.

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

Click Next.

Note

Inventory data fields are Cisco created data types that can be designated as an attribute or reference to be synchronized into a CMDB or staging table.

To select all inventory data fields for synchronization, click the top check box in the Select Inventory Data Fields. If you want to synchronize only specific fields, review each one and select the appropriate check boxes.

The Select Inventory Data Fields window consists of these 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).

The integration supports only '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 Catalyst 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 Catalyst application in ServiceNow. The type and number of device families vary, depending on the different Cisco devices in the user's network.

Note

Catalyst Center platform is able to automatically retrieve all of the device families in the user's Catalyst Center network and display them in this GUI window.

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

This table displays the Catalyst 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 must either manually create the corresponding CI Classes and attribute or reference mappings, or use a pre-existing CI class as a parent CI class. Ensure that 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.

Note

After configuring the bundle and setting up the schedule, if a new device (device family) is discovered and it lacks a CI class mapping in the Update Transform window, you must reconfigure the bundle to include a CI class mapping. This ensures that all devices are properly synced to the CMDB CI tables as expected.

Configure these values:

• Source Identifier (Exact Match): 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, one of the existing preconfigured values is used for the integration.

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

• Inventory Items Per Iteration: Maximum number of devices that can be synchronized in an iteration (single API call). We recommend that you set the limit to 100 devices.

After entering the information, click Next.

After reviewing the information, click Configure.

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

A Configurations window opens that contains an Events Settings section.

This Event Settings information appears:

• Event Name: Name of the Catalyst Center event.

• Domain: Domain of the Catalyst 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

  Assign Severity 1 to the events with most important or critical priority.

• 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.

Select 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 Catalyst Center when the event occurs.

Review the displayed bundles and their status.

You can view all provisioned fabric domains in the window.

The screen displays all the fabric sites in the domain.

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

Note

A blue circle indicates any device you add to the fabric in the Device Role column.

Note

• To configure a device as a fabric-in-a-box, select the Control Plane, Border, and Edge options.

• To configure the device as a control plane and a border node, select both Control Plane and Border.

Note

If you select Later to schedule a ticket creation at a specific time, the request goes to the Catalyst Center scheduler.

• 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 Catalyst Center Platform User Guide.