- Get Started with Cisco DNA Center
- Configure Cisco DNA Center System Settings
- Configure Site Network Settings
- Discover Your Network
- Manage Your Device Inventory
- Manage Software Images
- Display Your Network Topology
- Design Your Network
- Configure Policies
- Provision Your Network
- Configure Telemetry
- Manage Users
- Back Up and Restore Cisco DNA Center
Discover Your Network
About Discovery
Discovery and Device Inventory function as one service. The process of finding network devices is known as Discovery. The Discovery function scans the devices in your network and sends the list of discovered devices to Device Inventory. Device Inventory retrieves and saves the details about the devices in its database. Device Inventory refreshes every 25 minutes for each device. (At any given time, Device Inventory may be refreshing data for several devices at a time.)
There are two methods for discovering devices:
-
Using CDP and providing a seed IP address.
-
Specifying a range of IP addresses (maximum of 4096 devices).
Regardless of the method you use, you must be able to reach (ping) the device from DNA Center, and you need to configure specific credentials and protocols in DNA Center to discover your devices. These credentials can be configured globally in the Device Credentials page or on a per-job basis on the Discovery page. (Credentials configured in Discovery may be saved to use later as global credentials.)
-
CLI credentials
-
Simple Network Management Protocol (SNMPv2c or SNMPv3) credentials
-
HTTPS credentials (These credentials are required only for discovering devices running Cisco Network Function Virtualization Infrastructure Software (NFVIS).)
-
SSH/Telnet protocol
Because the various devices in a network can have different sets of credentials, you can configure multiple sets of credentials in DNA Center. The discovery process iterates through all of the sets of credentials until it finds a set that works for the device.
For discovery, one set of CLI credentials and one set of SNMP credentials (SNMPv2c Read, SNMPv2cWrite, or SNMPv3) is mandatory. If valid sets of credentials are provided for both SSH and Telnet, SSH credentials will be picked because SSH is more advanced than Telnet. If all three sets of valid SNMP credentials are provided, SNMP v3 will be picked because it's the most advanced protocol of the three.
After discovering devices, Device Inventory retrieves the details about the devices, such as host IP addresses, MAC addresses, and network attachment points, using one of the following protocols, as required:
-
Link Layer Discovery Protocol (LLDP)
-
IP Device Tracking (IPDT) is enabled automatically for the network fabric during the provisioning.
-
LLDP Media Endpoint Discovery (LLDP-MED) (This protocol is used to discover IP phones and some servers.)
-
Network Configuration Protocol (NETCONF) (Only required for devices running NFVIS.)
For information about configuration requirements for specific device types, see Discovery Prerequisites.
Discovery Credentials
Discovery credentials are the CLI, SNMPv2c, SNMPv3, and HTTP configuration values for the devices that you want to discover. You need to specify the credentials based on the types of devices you are trying to discover:
-
Standard Cisco devices—CLI and SNMP credentials.
-
NFVIS devices—HTTP credentials.
-
Both standard and NFVIS devices—CLI, SNMP, and HTTP credentials
If you use the same credential values for the majority of devices in your network, you can configure and save them as global discovery credentials, which you can reuse in multiple discovery jobs. To discover devices with unique credentials, you can add job-specific discovery credentials when you run Discovery. You can define up to five global and one job-specific credential for each of the credential types (CLI, SNMPv2c, SNMPv3, and HTTP).
![]() Note | If you use Cisco ISE for the DNA Center access policy feature, make sure that the device credentials that you use for discovery are also configured as the device credentials used by Cisco ISE. For more information, see Device Inventory and Cisco ISE Authentication. |
Discovery Credentials Guidelines and Limitations
The following are guidelines and limitations for the DNA Center discovery credentials:
-
If you change a device's credential after successfully discovering the device, subsequent polling cycles for that device fail. To correct this situation, use one of the following options:
-
Use the Discovery tool to:
-
Run a new discovery job with job-specific credentials that match the device's new credential.
-
Edit the existing discovery job and re-run the Discovery.
-
-
Use the Design tool to:
-
Create a new global credential and run a new discovery job using the correct global credential.
-
Edit an existing global credential and re-run the discovery job.
-
-
-
If an ongoing discovery polling cycle fails due to a device authentication failure, you can correct the situation using one of following options:
-
Use the Discovery tool to:
-
Stop or delete the current discovery job and run a new discovery job with job-specific credentials that match the device's credential.
-
Stop or delete the current discovery job, edit the existing discovery job, and re-run the Discovery.
-
-
-
Deleting a global credential does not affect previously discovered devices. The status of the previously discovered devices does not indicate an authentication failure. However, the next discovery that tries to use the deleted credential will fail. The discovery will fail before it tries to contact any devices. For example, 25 minutes after you delete the credential, discovery jobs that use it will fail.
-
DNA Center provides a REST API that allows an external application to retrieve a list of the managed network devices and synchronize its own managed inventory with the devices that have been discovered by DNA Center.
Discovery Credentials Example
Assume that a network of 200 devices, which form a Cisco Discovery Protocol (CDP) neighborhood (neighboring devices discovered using CDP), exists. In this network, 190 devices share a global credential (Credential 0) and the remaining devices each have their own unique credential (Credential-1 through Credential-10).
To discover all of the devices in this network using DNA Center, you would perform the following tasks:
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Configure the CLI global credentials as Credential-0. | |
| Step 2 | Configure the SNMP (v2c or v3) global credentials. | |
| Step 3 | Run a discovery job using one of the 190 device IP addresses (190 devices that share the global credentials) and the global Credential-0. | |
| Step 4 | Run 10 separate discovery jobs for each of the remaining 10 devices using the appropriate job-specific credentials, for example, Credential-1, Credential-2, Credential-3, and so on. | |
| Step 5 | Review the results in the Device Inventory window. |
Preferred Management IP Address
DNA Center can use another interface's IP address as the preferred management IP address. DNA Center chooses the preferred management IP address as follows:
-
If the device has one loopback interface, DNA Center uses that loopback interface IP address.
-
If the device has multiple loopback interfaces, DNA Center uses the loopback interface with the highest IP address.
-
If there are no loopback interfaces, DNA Center uses the Ethernet interface with the highest IP address. (Subinterface IP addresses are not considered.)
-
If there are no Ethernet interfaces, DNA Center uses the serial interface with the highest IP address.
Discovery Prerequisites
Make the following configuration changes on these platforms for the Discovery tool to work properly.
|
Feature |
Platform |
Required Configuration |
|---|---|---|
|
Discovery (device inventory collection) |
|
Configure NETCONF on these platforms. For information, see NETCONF Configuration. |
|
Discovery (device inventory collection) |
|
|
|
Discovery (host inventory collection) |
Devices connected to hosts using SNMP. |
Configure SNMP traps on these devices. For information, see SNMP Trap Configuration. |
|
Devices connected to hosts using Switch Integrated Security Features based IP device tracking. |
Enable SISF-based IP device-tracking for these devices. For information, see IP Device-Tracking Configuration. |
NETCONF Configuration
Enable the NETCONF protocol for the Cisco ASR 9000 Series Aggregation Services Routers or other Cisco devices that require NETCONF support for their device pack. If NETCONF is not enabled, the inventory collection process will be incomplete for that device.
![]() Note | Although NETCONF typically runs over SSH or on its own port, with DNA Center, NETCONF is run over a CLI session. |
For specific information about enabling NETCONF on your Cisco device, refer to that device’s configuration guide. the following is an example of a typical configuration sequence on a terminal to enable NETCONF on a Cisco device:
#ssh server v2 #netconf agent tty #! #xml agent tty #! #commit #end #crypto key generate rsa
![]() Note | The RSA key needs to be generated to succeed with SSH. Therefore, run the crypto key generate rsa command in EXEC mode at the end of the configuration sequence if it has not already been done. |
SNMP Trap Configuration
DNA Center uses SNMP traps (notifications) to capture a device's interface status and a host's MAC address, IP address, type, and so on. If you have Device Controllability enabled, DNA Center configures these SNMP traps for you. Otherwise, you need to enable SNMP traps and configure DNA Center's server IP address as the SNMP server. For more information about Device Controllability, see Device Controllability.
Enter the following commands in order, according to the type of device that you are configuring.
Cisco IOS Commands
snmp-server enable traps snmp linkdown linkup snmp-server host IP_address version 2c public
Cisco Nexus Commands
snmp-server enable traps snmp linkdown linkup snmp-server host IP_address version 2c public
Cisco Wireless Controller Commands
config trapflags client enhanced-802.11-associate enable config trapflags client enhanced-802.11-deauthenticate enable config trapflags client enhanced-authentication enable config trapflags client enhanced-802.11-stats enable
![]() Note | Be sure to configure DNA Center's server IP address as the SNMP trap destination. |
IP Device-Tracking Configuration
IP Device Tracking (IPDT) is one of the protocols that DNA Center uses during the discovery process to retrieve host inventory information, such as host IP addresses, MAC addresses, and network attachment points. If you have device controllability enabled, you do not need to configure IPDT manually on your devices. As part of the device controllability function, DNA Center configures IPDT or Switch Integrated Security Features (SISF) IPDT on the device based on the device type and image version that is running. If device controllability is disabled, you need to manually enable IPDT on your devices and interfaces. For more information about device controllability, see Device Controllability. For more information about whether IPDT is supported and enabled on your devices, see the configuration guide for the specific device type.
Discovery Configuration Guidelines and Limitations
The following are guidelines and limitations for DNA Center to discovery your Cisco Catalyst 3000 Series Switch, Catalyst 6000 Series Switches, and Cisco ASR 9000 Series Aggregation Services Routers:
Configure the CLI username and password with privileged EXEC mode (level 15). This is the same CLI username and password that you configure in DNA Center for the Discovery function. DNA Center requires the highest access level to the device.
-
Explicitly specify the transport protocols allowed on individual lines for both incoming and outgoing connections. This configuration is achieved using the transport input and transport output commands. For information about these commands, see the command reference for the specific device type.
-
Do not use the aaa new-model command to change the default login methods for the console port and VTY lines. DNA Center cannot discover devices that have this login method.
Perform Discovery
Discover Your Network Using CDP
-
Enable CDP on your network devices.
-
Configure your network devices as described in Discovery Prerequisites.
-
Configure your network device's host IP address as the client IP address.
Discover Your Network Using an IP Address Range
Your devices must have the required device configurations, as described in Discovery Prerequisites.
Manage Discovery Jobs
Stop and Start a Discovery Job
Clone a Discovery Job
You can clone a discovery job and retain all of the information defined for the job.
You have run at least one discovery job.
Delete a Discovery Job
You have run at least one discovery job.

Feedback