Complete First-Time Setup
First-Time Setup Workflow
After you finish configuring all of the Cisco DNA Center appliances you have installed, perform the tasks described in this chapter to prepare Cisco DNA Center for production use. Note the following points:
-
For the parameter information you need to complete this work, see Required First-Time Setup Information.
-
If you plan to deploy high availability (HA) in your production environment, you will need to redistribute services among your cluster nodes to optimize HA operation (see Activate HA). Complete this step after you have configured the SNMP settings for your appliances.
Compatible Browsers
The Cisco DNA Center GUI is compatible with the following HTTPS-enabled browsers:
-
Google Chrome: Version 93 or later.
-
Mozilla Firefox: Version 92 or later.
We recommend that the client systems you use to log in to Cisco DNA Center be equipped with 64-bit operating systems and browsers.
Complete the Quick Start Workflow
After you have installed and configured the Cisco DNA Center appliance, you can log in to its GUI. Use a compatible, HTTPS-enabled browser when accessing Cisco DNA Center.
When you log in for the first time as the admin superuser (with the username admin and the SUPER-ADMIN-ROLE assigned), the Quick Start workflow automatically starts. Complete this workflow to discover the devices that Cisco DNA Center will manage and enable the collection of telemetry from those devices.
Before you begin
To log in to Cisco DNA Center and complete the Quick Start workflow, you will need:
-
The admin superuser username and password that you specified while completing one of the following procedures:
-
Configure the Primary Node Using the Advanced Install Configuration Wizard (44- or 56-core appliance)
-
Configure the Primary Node Using the Advanced Install Configuration Wizard (112-core appliance)
-
The information described in Required First-Time Setup Information.
Procedure
Step 1 |
After the Cisco DNA Center appliance reboot is completed, launch your browser. |
||
Step 2 |
Enter the host IP address to access the Cisco DNA Center GUI, using HTTPS:// and the IP address of the Cisco DNA Center GUI that was displayed at the end of the configuration process. After entering the IP address, one of the following messages appears (depending on the browser you are using):
|
||
Step 3 |
Ignore the message and click Advanced. One of the following messages appears:
These messages appear because the controller uses a self-signed certificate. For information on how Cisco DNA Center uses certificates, see the "Certificate and Private Key Support" section in the Cisco DNA Center Administrator Guide. |
||
Step 4 |
Ignore the message and do one of the following:
The Cisco DNA Center login screen appears. |
||
Step 5 |
Do one of the following and then click Log In:
In the next screen, you are prompted to specify a new admin password (as a security measure). |
||
Step 6 |
Do one of the following:
|
||
Step 7 |
Enter your cisco.com username and password (which are used to register software downloads and receive system communications) and then click Next.
The Terms & Conditions screen opens, providing links to the software End User License Agreement (EULA) and any supplemental terms that are currently available. |
||
Step 8 |
After reviewing these documents, click Next to accept the EULA. The Quick Start Overview slider opens. Click > to view a description of the tasks that the Quick Start workflow will help you complete in order to start using Cisco DNA Center. |
||
Step 9 |
Complete the Quick Start workflow: |
Integrate Cisco ISE with Cisco DNA Center
Cisco DNA Center provides a mechanism to create a trusted communications link with Cisco ISE and to share data with Cisco ISE in a secure manner. After Cisco ISE is registered with Cisco DNA Center, any device that Cisco DNA Center discovers, along with relevant configuration and other data, is pushed to Cisco ISE. You can use Cisco DNA Center to discover devices and then apply both Cisco DNA Center and Cisco ISE functions to them because these devices will be displayed in both the applications. Cisco DNA Center and Cisco ISE devices are all uniquely identified by their device names.
As soon as the devices are provisioned and assigned to a particular site in the Cisco DNA Center site hierarchy, Cisco DNA Center devices are pushed to Cisco ISE. Any updates to a Cisco DNA Center device (such as changes to IP address, SNMP or CLI credentials, Cisco ISE shared secret, and so on) will be sent to the corresponding device instance on ISE automatically. Note that Cisco DNA Center devices are pushed to Cisco ISE only when these devices are associated with a particular site where Cisco ISE is configured as its AAA server.
Before you begin
Before attempting to integrate Cisco ISE with Cisco DNA Center, ensure that you have met the following prerequisites:
-
You have deployed one or more Cisco ISE hosts on your network. For information on supported Cisco ISE versions, see the Cisco DNA Center Compatibility Matrix. For information on installing Cisco ISE, see the Cisco Identity Services Engine Install and Upgrade guides.
-
If you have a standalone Cisco ISE deployment, you must integrate Cisco DNA Center with the Cisco ISE node and enable the pxGrid service and External RESTful Services (ERS) on that node.
Note
Although pxGrid 2.0 allows up to four pxGrid nodes in the Cisco ISE deployment, Cisco DNA Center releases earlier than 2.2.1.x do not support more than two pxGrid nodes.
-
If you have a distributed Cisco ISE deployment:
-
You must integrate Cisco DNA Center with the primary policy administration node (PAN), and enable ERS on the PAN.
Note
We recommend that you use ERS through the PAN. However, for backup, you can enable ERS on the PSNs.
-
You must enable the pxGrid service on one of the Cisco ISE nodes within the distributed deployment. Although you can choose to do so, you do not have to enable pxGrid on the PAN. You can enable pxGrid on any Cisco ISE node in your distributed deployment.
-
The PSNs that you configure in Cisco ISE to handle TrustSec or SD Access content and PACs must also be defined in . For more information, see the Cisco Identity Services Engine Administrator Guide.
-
-
Only a user with Super Admin role permissions can integrate Cisco ISE with Cisco DNA Center.
-
Cisco DNA Center does not support ERS API access if the Use CSRF Check for Enhanced Security option is enabled in Cisco ISE.
-
You must enable communication between Cisco DNA Center and Cisco ISE on the following ports: 443, 5222, 8910, and 9060.
-
The Cisco ISE host on which pxGrid is enabled must be reachable from Cisco DNA Center on the IP address of the Cisco ISE eth0 interface.
-
The Cisco ISE node can reach the fabric underlay network via the appliance's NIC.
-
Cisco DNA Center will check the certificate revocation status if Online Certificate Status Protocol (OCSP) or certificate revocation list (CRL) validation is defined for the certificates used by the Cisco ISE services.
-
The Cisco ISE admin node certificate must contain the Cisco ISE IP address or FQDN in either the certificate subject name or the Subject Alternative Name (SAN).
-
Your ability to use an FQDN-only system certificate depends on whether LAN automation is enabled in your Cisco DNA Center deployment. For more information, see the alt_names section bullet in Step 3 of the Cisco DNA Center Security Best Practices Guide's "Generate a Certificate Request Using Open SSL" topic.
Note
For Cisco ISE 2.4 Patch 13, 2.6 Patch 7, and 2.7 Patch 3, if you are using the Cisco ISE default self-signed certificate as the pxGrid certificate, Cisco ISE might reject that certificate after applying those patches. This is because the older versions of that certificate have the Netscape Cert Type extension specified as the SSL server, which now fails (because a client certificate is required).
This issue does not occur in Cisco ISE 3.0 and later. For more information, see the Cisco ISE Release Notes.
For more information about configuring Cisco ISE for Cisco DNA Center, see the "Integration with Cisco DNA Center" topic in the Cisco Identity Services Engine Administrator Guide.
Procedure
Step 1 |
Enable the pxGrid service and ERS on Cisco ISE: |
Step 2 |
Add the Cisco ISE node to Cisco DNA Center as a AAA server: When the integration with Cisco ISE is initiated, you will see a notification that the certificate from Cisco ISE is not yet trusted. You can view the certificate to see the details. Click Accept to trust the certificate and continue with the integration process, or choose Decline if you do not wish to trust the certificate and terminate the integration process. After the integration completes successfully, a confirmation message is displayed. If there is any issue in the integration process, an error message is displayed. An option to edit or retry is displayed where applicable.
|
Step 3 |
Verify that Cisco DNA Center is connected to Cisco ISE, and that the Cisco ISE SGT groups and devices are pushed to Cisco DNA Center:
|
Step 4 |
Verify that Cisco ISE is connected to Cisco DNA Center and that the connection has subscribers: |
Group-Based Access Control: Policy Data Migration and Synchronization
When You Start Using Cisco DNA Center
In earlier releases of Cisco DNA Center, the Group-Based Access Control policy function stored some policy Access Contracts and Policies locally in Cisco DNA Center. Cisco DNA Center also propagated that data to Cisco ISE. Cisco ISE provides the runtime policy services to the network, which includes group-based access control policy downloads to the network devices. Usually, the policy information in Cisco DNA Center matches the policy information in Cisco ISE. But it is possible that the data is not in sync; the data may not be consistent. Because of this, after installing or upgrading to Cisco DNA Center, the following steps are necessary before you can use the Group-Based Access Control capabilities.
-
Integrate Cisco ISE with Cisco DNA Center, if it is not already integrated.
-
Upgrade Cisco ISE, if the version is not the minimum required. See the Cisco DNA Center Release Notes for the required versions of Cisco ISE.
-
Perform Policy Migration and Synchronization.
What Is “Migration and Synchronization”?
Cisco DNA Center reads all the Group-Based Access Control policy data in the integrated Cisco ISE and compares that data with the policy data in Cisco DNA Center. If you upgraded from an earlier version, existing policy data is retained. You must synchronize the policies before you can manage Group-Based Access Control Policy in Cisco DNA Center.
How Does Migration and Synchronization Work?
Usually, the policy data in Cisco ISE and in Cisco DNA Center is consistent, so no special handling or conversion of data is necessary. Sometimes, when there are minor discrepancies or inconsistencies, only some of the data is converted during the migration. If there is a conflict, the data in Cisco ISE is given precedence, so as not to introduce changes in policy behavior in the network. The following list describes the actions taken during migration:
-
Security Groups: The Security Group Tag (SGT), which is a numeric value, uniquely identifies a Security Group. Cisco ISE Security Groups are compared to Security Groups in Cisco DNA Center.
-
When the Name and SGT value are the same, nothing is changed. The information in Cisco DNA Center is consistent with Cisco ISE and does not need to be changed.
-
When a Cisco ISE Security Group SGT value does not exist in Cisco DNA Center, a new Security Group is created in Cisco DNA Center. The new Security Group is given the default association of “Default_VN.”
-
When a Cisco ISE Security Group SGT value exists in Cisco DNA Center, but the names do not match, the name from Cisco ISE Security Group replaces the name of that Security Group in Cisco DNA Center.
-
When the Cisco ISE Security Group Name is the same, but the SGT value is different, the Security Group from Cisco ISE is migrated. It retains the name and tag value, and the Cisco DNA Center Security Group is renamed. A suffix of “_DNA” is added.
-
Contracts
All the SGACLs in Cisco ISE that are referenced by policies are compared to Contracts in Cisco DNA Center.
-
When the SGACL and Contract have the same name and content, there is no need for further action. The information in Cisco DNA Center is consistent with Cisco ISE and does not need to be changed.
-
When the SGACL and Contract have the same name, but the content is different, the SGACL content from Cisco ISE is migrated. The previous Contract content in Cisco DNA Center is discarded.
-
When the SGACL name does not exist in Cisco DNA Center, a new Contract with that name is created, and the SGACL content from Cisco ISE is migrated.
![]() Note |
When creating new Access Contracts based on Cisco ISE SGACL content, Cisco DNA Center parses the text command lines, and, where possible, renders these SGACL commands as a modeled Access Contract. Each ACE line renders as an “Advanced” application line. If a Cisco ISE SGACL contains text that cannot be parsed successfully, the text content of the SGACL is not converted into modeled format. It is stored as raw command line text. These SGACL text contracts may be edited, but no parsing or syntax checking of the text content is performed during migration. |
Policies
A Policy is uniquely identified by a source group-destination group pair. All Cisco ISE TrustSec Egress Policy Matrix policies are compared to the policies in Cisco DNA Center.
-
When a policy for a source group-destination group references the same SGACL/Contract name in Cisco ISE, no changes are made.
-
When a policy for a source group-destination group references a different SGACL/Contract name in Cisco ISE, the Cisco ISE Contract name is referenced in the policy. This overwrites the previous Contract reference in Cisco DNA Center.
-
The Cisco ISE default policy is checked and migrated to Cisco DNA Center.
![]() Note |
Cisco DNA Center supports a single contract in access policies. Cisco ISE has an option to use multiple SGACLs in access policies, but this option is not enabled by default in Cisco ISE, and in general is not widely used. Existing SDA customers who have been using the previous release of Cisco DNA Center to manage Group-Based Access Control policy did not use this option. |
If you enabled the option to allow multiple SGACLs on Cisco ISE and used this when creating policies, those policies cannot be migrated to Cisco DNA Center in this release. The specific policy features that make use of the “multiple SGACL” option and cannot be migrated are:
-
Multiple SGACLs in a policy.
-
Policy Level catch-all rules set to “Permit” or “Deny.” Only the value of “None” is currently supported for migration to Cisco DNA Center.
-
Default Policy set to use a customer-created SGACL, but only the standard values of “Permit IP,” “Permit_IP_Log,” “Deny IP,” and “Deny_IP_Log” are currently supported for migration to Cisco DNA Center.
If any of the preceding SGACLs are detected during the policy migration and synchronization operation, a notification is generated, and you must choose between the following options to continue:
-
Manage Group-Based Access Control policy in Cisco DNA Center: If this option is selected, all management of Group-Based Access Control Policy is done in Cisco DNA Center. The user interface screens in Cisco ISE for management of Cisco ISE Security Groups, SGACLs, and Egress Policies are available in Read-Only mode. If there were any issues migrating policies (due to use of multiple SGACLs in Cisco ISE), those policies have no contract selected in Cisco DNA Center. The policy uses the default policy, and you can select a new contract for those policies after completing the migration. If there was an problem migrating the default policy, the default policy is set to "Permit."
-
Manage Group-Based Access Control Policy in Cisco ISE: If this option is selected, Cisco DNA Center Group-Based Access Control policy management is inactive. No changes are made to Cisco ISE and there is no effect on policy enforcement in the network. Group-Based Access Control policy is managed in Cisco ISE at the TrustSec workcenter.
-
Manage Group-Based Access Control policy in both Cisco DNA Center and Cisco ISE: This option is not recommended for general use, because policy changes made in Cisco ISE are not synchronized with Cisco DNA Center. The two systems cannot be kept in sync. This option is intended as a short-term or interim option, and should only be considered when you enabled the “Allow Multiple SGACLs” option in Cisco ISE. Use this option if you need more time and flexibility updating Cisco ISE.
Configure Authentication and Policy Servers
Cisco DNA Center uses AAA servers for user authentication and Cisco ISE for both user authentication and access control. Use this procedure to configure AAA servers, including Cisco ISE.
Before you begin
-
If you are using Cisco ISE to perform both policy and AAA functions, make sure that Cisco DNA Center and Cisco ISE are integrated.
-
If FIPS mode is enabled for Cisco DNA Center, ensure that you enable KeyWrap when integrating Cisco DNA Center and Cisco ISE. See Step 2e in Integrate Cisco ISE with Cisco DNA Center.
Note
You cannot enable KeyWrap if Cisco DNA Center and Cisco ISE have already been integrated. To enable this feature, you need to delete Cisco ISE and then reintegrate it with Cisco DNA Center.
-
If you are using another product (not Cisco ISE) to perform AAA functions, make sure to do the following:
-
Register Cisco DNA Center with the AAA server, including defining the shared secret on both the AAA server and Cisco DNA Center.
-
Define an attribute name for Cisco DNA Center on the AAA server.
-
For a Cisco DNA Center multihost cluster configuration, define all individual host IP addresses and the virtual IP address for the multihost cluster on the AAA server.
-
-
Before you configure Cisco ISE, confirm that:
-
You have deployed Cisco ISE on your network. For information on supported Cisco ISE versions, see the Cisco DNA Center Compatibility Matrix. For information on installing Cisco ISE, see the Cisco Identity Services Engine Install and Upgrade guides.
-
If you have a standalone ISE deployment, you must integrate Cisco DNA Center with the Cisco ISE node and enable the pxGrid service and External RESTful Services (ERS) on that node.
Note
Although pxGrid 2.0 allows up to four pxGrid nodes in the Cisco ISE deployment, Cisco DNA Center releases earlier than 2.2.1.x do not support more than two pxGrid nodes.
-
If you have a distributed Cisco ISE deployment:
-
You must integrate Cisco DNA Center with the primary policy administration node (PAN), and enable ERS on the PAN.
Note
We recommend that you use ERS through the PAN. However, for backup, you can enable ERS on the PSNs.
-
You must enable the pxGrid service on one of the Cisco ISE nodes within the distributed deployment. Although you can choose to do so, you do not have to enable pxGrid on the PAN. You can enable pxGrid on any Cisco ISE node in your distributed deployment.
-
The PSNs that you configure in Cisco ISE to handle TrustSec or SD Access content and PACs must also be defined in . For more information, see the Cisco Identity Services Engine Administrator Guide.
-
-
You must enable communication between Cisco DNA Center and Cisco ISE on the following ports: 443, 5222, 8910, and 9060.
-
The Cisco ISE host on which pxGrid is enabled must be reachable from Cisco DNA Center on the IP address of the Cisco ISE eth0 interface.
-
The Cisco ISE node can reach the fabric underlay network via the appliance's NIC.
-
The Cisco ISE admin node certificate must contain the Cisco ISE IP address or FQDN in either the certificate subject name or the Subject Alternative Name (SAN).
-
The Cisco DNA Center system certificate must list both the Cisco DNA Center appliance IP address and FQDN in the SAN field.
Note
For Cisco ISE 2.4 Patch 13, 2.6 Patch 7, and 2.7 Patch 3, if you are using the Cisco ISE default self-signed certificate as the pxGrid certificate, Cisco ISE might reject that certificate after applying those patches. This is because the older versions of that certificate have the Netscape Cert Type extension specified as the SSL server, which now fails (because a client certificate is required).
This issue does not occur in Cisco ISE 3.0 and later. For more information, see the Cisco ISE Release Notes.
-
Procedure
Step 1 |
Click the menu icon ( |
||||
Step 2 |
From the Add drop-down list, choose AAA or ISE. |
||||
Step 3 |
To configure the primary AAA server, enter the following information:
|
||||
Step 4 |
To configure a Cisco ISE server, enter the following details:
|
||||
Step 5 |
Click Advanced Settings and configure the settings:
|
||||
Step 6 |
Click Add. |
||||
Step 7 |
To add a secondary server, repeat the preceding steps. |
Configure SNMP Properties
You can configure the retry and timeout values for SNMP.
Before you begin
Only a user with SUPER-ADMIN-ROLE permissions can perform this procedure. For more information, see the Cisco DNA Center Administrator Guide.
Procedure
Step 1 |
Click the menu icon ( |
||
Step 2 |
Configure the following fields:
|
||
Step 3 |
Click Save.
|