To deploy Cisco DNA Center as the controller, complete the following workflow:

Product Instance Configuration → Cisco DNA Center Configuration

1. Product Instance Configuration

   Where task is performed: Product Instance

   Enable NETCONF. Cisco DNA Center uses the NETCONF protocol to provision configuration and retrieve the required information from the product instance - the product instance must therefore have NETCONF enabled, to facilitate this.

   For more information, see the Programmability Configuration Guide, Cisco IOS XE Amsterdam 17.3.x. In the guide, go to Model-Driven Programmability > NETCONF Protocol.

2. Cisco DNA Center Configuration

   Where tasks is performed: Cisco DNA Center GUI

   An outline of the tasks you must complete and the accompanying documentation reference is provided below. The document provides detailed steps you have to complete in the Cisco DNA Center GUI:

   1. Set-up the Smart Account and Virtual Account.

      Enter the same log in credentials that you use to log in to the CSSM Web UI. This enables Cisco DNA Center to establish a connection with CSSM.

      See the Cisco DNA Center Administrator Guide of the required release (Release 2.2.2 onwards) > Manage Licenses > Set Up License Manager.

   2. Add the required product instances to Cisco DNA Center inventory and assign them to a site.

      This enables Cisco DNA Center to push any necessary configuration, including the required certificates, for Smart Licensing Using Policy to work as expected.

      See the Cisco DNA Center User Guide of the required release (Release 2.2.2 onwards) > Display Your Network Topology > Assign Devices to a Site.

   3. Trigger the required workflows to install authorization codes if applicable.

      See the Cisco DNA Center Administrator Guide of the required release (Release 2.2.2 onwards) > Manage Licenses > Install the Authorization Code and Enable the High Security License.

      On the Cisco DNA Center GUI, you can generate the SLAC only for HSECK9 licenses, and only for these product instances:

      Table 1. Product Instances that Support SLAC Generation for HSECK9 license on the Cisco DNA Center GUI

      Product Instance	Minimum Required Cisco DNA Center Release	Minimum Required Cisco IOS XE Version
      Cisco 1000 Series Integrated Services Routers	Cisco DNA Center Release 2.2.2	Cisco IOS XE Amsterdam 17.3.2
      Cisco 4000 Series Integrated Services Routers		Cisco IOS XE Amsterdam 17.3.2
      Catalyst 8300 Series Edge Platforms		Cisco IOS XE Amsterdam 17.3.2
      Catalyst 8500 Series Edge Platforms		Cisco IOS XE Amsterdam 17.3.2
      Catalyst 8200 Series Edge Platforms		Cisco IOS XE Bengaluru 17.4.1

Result:

After you implement the topology, you must trigger the very first ad hoc report in Cisco DNA Center, to establish a mapping between the Smart Account and Virtual Account, and product instance. See the Cisco DNA Center Administrator Guide of the required release (Release 2.2.2 onwards) > Manage Licenses > Upload Resource Utilization Details to CSSM. Once this is done, Cisco DNA Center handles subsequent reporting based on the reporting policy.

If multiple policies are available, Cisco DNA Center maintains the narrowest reporting interval. You can change this, but only to report more frequently (a narrower interval). See the Cisco DNA Center Administrator Guide of the required release (Release 2.2.2 onwards) > Manage Licenses > Modify License Policy.

If you want to change the license level after this, see the Cisco DNA Center Administrator Guide of the required release (Release 2.2.2 onwards) > Manage Licenses > Change License Level.

To deploy Cisco vManage as the controller, complete the following workflow:

Smart Account Set-Up → Product Instance Configuration → Cisco vManage Configuration → Authorization Code Installation (Only if Applicable)

1. Smart Account Set-Up

   Where tasks are performed: CSSM Web UI, https://software.cisco.com/

   Ensure that you have a user role with proper access rights to a Smart Account and the required Virtual Accounts.

   Note

   If you are migrating from an earlier release to the Connected to CSSM Through Controller topology (where Cisco vManage is deployed as the Controller), first check that all the licenses that you ordered are displayed in your Smart Accout and Virtual Account in CSSM. If licenses are missing, contact Cisco TAC for help with the correction, and only then proceed with topology implementation.

2. Product Instance Configuration

   Where tasks are performed: Product Instance

   To use Cisco vManage to manage a product instance you must complete the standard bring-up process.

   See the Cisco SD-WAN Getting Start Guide > Cisco SD-WAN Overlay Network Bring-Up Process.

3. Cisco vManage Configuration

   Where tasks are performed: Cisco vManage portal

   See the Cisco SD-WAN Getting Start Guide > License Management for Smart Licensing Using Policy .

   Cisco vManage Configuration applies only to Cisco IOS XE Bengaluru 17.5.1a and later releases.

   From Cisco IOS XE Amsterdam 17.3.2 to Cisco IOS XE Bengaluru 17.4.x, Cisco vManage does not support license management. You can configure the product instance to operate in "controller mode", but usage reporting is not supported.

4. Authorization Code Installation (Only if Applicable)

   Where tasks are performed: Product Instance and CSSM Web UI

   To use an export-controlled license or throughput greater than 250 Mbps, complete SLAC installation (choose one):

   • Option 1:

     Generate a SLAC in CSSM, download it to a file, and then install it.

     1. Generating and Downloading SLAC from CSSM to a File

     2. Installing a File on the Product Instance

   • Option 2:

     Establish connectivity to CSSM, establish trust, and then request and install SLAC. (The example here uses Smart transport for connectivity to CSSM, you can use any of the other options to connect directly to CSSM.)

     Note	Even though you are configuring a connection to CSSM and establishing trust, a product instance in the SD-WAN “controller mode” does not send RUM reports.

     1. Set the transport type to smart and configure the corresponding URL. If the transport mode is set to license smart transport smart , and you configure license smart url default , the Smart URL (https://smartreceiver.cisco.com/licservice/license) is automatically configured. Remember to save any changes to the configuration file.

        Device(config)# license smart transport smart
        Device(config)# license smart url default
        Device(config)# exit
        Device# copy running-config startup-config

     2. Generate one token for each Virtual Account you have. You can use same token for all the product instances that are part of one Virtual Account: Generating a New Token for a Trust Code from CSSM

        Having downloaded the token, you can now install the trust code on the product instance: Establishing Trust with an ID Token.

        Device# license smart trust idtoken NGMwMjk5mYtNZaxMS00NzMZmtgWm all force

     3. Request and install SLAC: Manually Requesting and Auto-Installing a SLAC

        Device# license smart authorization request replace hseck9 local
        Device(config)# exit
        Device# copy running-config startup-config

Result:

Cisco vManage records usage and automatically sends RUM reports to CSSM at the fixed reporting interval of 24 hours. You can assign licences to edge devices, view information about the licenses that are being used and the licenses that are available for assignment.

SSM On-Prem Installation and Configuration → Product Instance Addition → Product Instance Configuration→ Initial Usage Synchronization

1. SSM On-Prem Installation and Configuration

   Where task is performed: A physical server such as a Cisco UCS C220 M3 Rack Server, or a hardware-based server that meets the necessary requirements.

   Download the file from Smart Software Manager > Smart Software Manager On-Prem.

   Refer to the Cisco Smart Software On‐Prem Installation Guide and the Cisco Smart Software On‐Prem User Guide for help with installation.

   Installation is complete when you have deployed SSM On-Prem, configured a common name on SSM On-Prem (Security Widget > Certificates), synchronized the NTP server (Settings widget > Time Settings), and created, registered, and synchronized (Synchronization widget) the SSM On-Prem local account with your Smart Account and Virtual Account in CSSM.

   Note

   Licensing functions in the On-Prem Licensing Workspace are greyed-out until you complete the creation, registration, and synchronization of the local account with your Smart Account in CSSM. The local account synchronization with CSSM is for the SSM On-Prem instance to be known to CSSM, and is different from usage synchronization which is performed in 4. Initial Usage Synchronization below.

2. Product Instance Addition

   Where task is performed: SSM On-Prem UI

   Depending on whether you want to add a single product instance or multiple product instances, follow the corresponding sub-steps: Adding One or More Product Instances (SSM On-Prem UI).

3. Product Instance Configuration

   Where tasks are performed: Product Instance and the SSM On-Prem UI

   Remember to save any configuration changes on the product instance, by entering the copy running-config startup-config command in privileged EXEC mode.

   1. Ensuring Network Reachability for SSM On-Prem-Initiated Communication

   2. Enable the utility mode only if you have an MSLA: Enabling the Utility Mode

   3. Complete this sub-step only if you want to use a license that requires authorization before use (enforcement type: enforced or export-controlled), or to configure throughput greater than 250 Mbps (on supported product instances): Submitting an Authorization Code Request (SSM On-Prem UI, Disconnected Mode).

      The uploaded codes are now applied to the product instances the next time SSM On-Prem runs an update. An initial usage synchronization with the product instance is being performed in Step 4 below so this will be completed then.

4. Initial Usage Synchronization

   Where tasks are performed: SSM On-Prem, and CSSM

   1. Retrieve usage information from the product instance.

      In the SSM On-Prem UI, navigate to Reports > Synchronisation pull schedule with the devices > Synchronise now with the device.

      If the utility mode is enabled on the product instance, the RUM report that SSM On-Prem retrieves, is flagged accordingly.

      In the Alerts column, the following message is displayed: Usage report from product instance.

      Tip	It takes 60 seconds before synchronization is triggered. To view progress, navigate to the On-Prem Admin Workspace, and click the Support Centre widget. The system logs here display progress.

   2. Synchronize usage information with CSSM (choose one)

      • Option 1:

        SSM On-Prem is connected to CSSM: In the SSM On-Prem UI, Smart Licensing workspace, nagivate to Reports > Usage Schedules > Synchronize now with Cisco.

      • Option 2:

        SSM On-Prem is not connected to CSSM. See: Exporting and Importing Usage Data (SSM On-Prem UI).

Result:

You have completed initial usage synchronization. Product instance and license usage information is now displayed in SSM On-Prem. SSM On-Prem automatically sends the ACK back to the product instance. To verify that the product instance has received the ACK, enter the show license status command in privileged EXEC mode, and in the output, check the date for the Last ACK received field.

If the RUM report to CSSM was flagged with the utility mode, the ACK from CSSM includes the subscription ID - as in Smart Account and Virtual account of the product instance. Subsequent RUM reports that are sent include the subscription ID for each license in use. In the utility mode, an ACK is required every 30 days.

For subsequent reporting, you have the following options:

• To retrieve usage information from the product instance, you can:

  • In the SSM On-Prem UI, Smart Licensing workspace, nagivate to Reports > Usage Schedules > Synchronize now with Cisco.

  • Schedule periodic retrieval of information from the product instance by configuring a frequency. In the SSM On-Prem UI, Smart Licensing workspace, nagivate to Reports > Usage Schedules > Synchronisation pull schedule with the devices. Enter values in the following fields:

    • Days: Refers to how often synchronization occurs. For example, if you enter 2, synchronization occurs once every two days.

    • Time of Day:: Refers to the time at which synchronization occurs, in the 24-hour notation system. For example, if you enter 14 hours and 0 minutes, synchronization occurs at 2 p.m. (1400).

  • Collect usage data from the product instance without being connected to CSSM. In the SSM On-Prem UI, Smart Licensing workspace, nagivate to Inventory > SL Using Policy tab. Select one or more product instances by enabling the coresponding check box. Click Actions for Selected... > Collect Usage. On-Prem connects to the selected Product Instance(s) and collects the usage reports. These usage reports are then stored in On-Prem’s local library. These reports can then be transferred to Cisco if On-Prem is connected to Cisco, or (if you are not connected to Cisco) you can manually trigger usage collection by selecting Export/Import All.. > Export Usage to Cisco.

• To synchronize usage information with CSSM, you can:

  • Schedule periodic synchronization with CSSM. In the SSM On-Prem UI, navigate to Reports > Usage Schedules > Synchronization schedule with Cisco. Enter the following frequency information and save:

    • Days: Refers to how often synchronization occurs. For example, if you enter 2, synchronization occurs once every two days.

    • Time of Day:: Refers to the time at which synchronization occurs, in the 24-hour notation system. For example, if you enter 14 hours and 0 minutes, synchronization occurs at 2 p.m. (1400).

  • Upload and download the required files for reporting: Exporting and Importing Usage Data (SSM On-Prem UI)).