Showing results for 
Search instead for 
Did you mean: 

Smart Licensing Using Policy (Routing) – A Simplified Licensing Approach- FAQ




This event had place on Tuesday 18th, May 2021 at 9hrs PDT 


Smart Licensing Using Policy (SLP) is an enhanced version of Smart Licensing which simplifies the licensing activation experience by removing Day-0 friction.This session helped you to understand the technical details of SLP, the Greenfield and Brownfield scenario, deployment details for devices, the new Cisco Smart Licensing utility (CSLU), and controllers (CSLU, CSSM Cloud, CSSM On-Prem, and DNAC).

Featured Expert

Featured Speaker

Pradeep Chaudhari brings 16 years of rich industry experience in the Enterprise and Service Provider Networking domains. He has been with Cisco for 13+ years.

Since joining Cisco in 2008, he has been part of multiple teams within Cisco and held various technical and consulting roles focusing on different SP accounts and technologies (MPLS-VPN, MPLS-TE, etc.). 

In the Enterprise space, Pradeep also led the charge on complex network design and implementation projects for Cisco SDN-based ACI Solutions for industry verticals including Banking-Finance and IT.  Presently a Technical Marketing Engineer on the IBNG Routing Platform Team, he is responsible for the ISR4000 and Catalyst 8300 Series Edge Platforms family. He is also a SME for Smart Licensing. On a personal front, Pradeep holds a Bachelor of Engineering degree in Electronics & Telecommunication from the University of Mumbai, India. He also holds three CCIE certifications (Routing & Switching, Service Provider, and Data Center).

You can download the slides of the presentation in PDF format here.

Live Questions

Q:I'm in the middle of deploying onprem-ssm to enable smart licensing for IOS-XE devices older than 16.10.1a.What exactly do I need to do now to move to Smart Licensing using policy? Upgrade all devices to the supported 17.x versions? Upgrade onprem-ssm version?

A:On-Prem SSM needs to upgrade to SLP supported version V8-202102. Device needs to be upgraded to 17.3.3 or later to support On-Prem SSM with SLP.¬

Q:What happens with Device Lead Conversion (DLC)? Is that still needed on SLP?

A: In SLP, Device Led Conversion (DLC) is still needed but you do not need to initiate DLC manually anymore. DLC will be automatically initiated once device upgrade to SLP code 17.3.2 & later. The DLC request will be forwarded to CSSM via CSLU, on-prem DNAC or On-prem SSM depend on the connectivity and CSSM will revert back with DLC completion status to device.

Q:Is there any enforcement of license for CSR1kv? Does the throughput drop down to the original value if 1) the device does not send reports and 2) if it loses access to the CSSM?

A: Yes, CSR1kv was always enforced license which is acquire before use of license

Q:What version of DNAC is required for acting as CSLU?

A: and later release.¬

Q:What about when CSR1kv lost access to the CSSM/CSLU....does the throughput drop then too?

A: Not for 90-days within which there is an expectation to reach CSSM.¬

Q:You talked about the client we are split across multiple sites so ideally would need to have multiple people using the client to look at the licenses - does the client work this way?

A: If CSLU - you define the scope of CSLU across locations as it relates to the SA/ VA.

Q:Is there a list available which licenses are enforced? I experienced this on CUBE: *Mar 9 16:49:55.491: %SIP-1-LICENSING: SIP service disabled until license report is acknowledged. in 17.04.01b Was there a misconfiguration or is this license enforced?

A:Cube is enforced...HSEC is enforced.

Q:What version of DNAC is required for acting as CSLU?

A: & later.. for on-prem CSLU use-case.

Q:What about Cat9k....does that support SLP with 17.3.2 and higher as well? Did not see that on the list.

A:It does support Cat9K. All Enterprise Products (Router, Switch & wireless, IoT) supports SLP. This session was focused on Enterprise Routing Products, hence we covered only routing platforms ASR1K, iSR1K, ISR4K, Catalyst8K, Cat8KV.

Q:What happens after this 90 days period? Is the license enforced meaning that there is no more operation until a successful report takes place?

A: Not exactly. At this point, there will be no enforcement from the Cisco side. Once this is very highly trust model, we recommend every customer to do the reporting part but from a functionality point of view there is absolutely no enforcement at this moment from Cisco side.

Q:What is SLR & PLR?

A:SLR is stands for a smart licensing reservation and PLR is permanent licensing reservation. So, these are the licenses that were specifically for the offline customer like government customer who don't want to have their devices to access the internet and reach to the Cisco smart licensing.¬

Q:How will we see adoption of the licenses (through telemetry) if devices are not connected?

A: In case of Air-Gap environment, license consumption report needs to manually download from device and upload it into customer specific smart account / virtual account in CSSM portal. The CSSM portal reflects the license consumption for such scenarios.

Q:Does the SSM(Satellite Sever) support (Authorize License-Enforced Features) via a single device or multiple devices? SSM does not and never did support SLR.

A: On-Prem SSM supports Authorize License-Enforced Features via both a single device or multiple devices

Q:What information and file type are needed for "Authorize License-Enforced Features" for multiple devices? (i.e. Do you just need the Serial number and PID and can you upload a .csv or .xls)?

A: You can upload .csv file to request Authorize License-enforced Features auth code for multiple devices. You will need the Host Name (IP Address), UDI, and Serial Number.

Q:Can the SSM push out Authorize License-Enforced Features auth codes to PIs?

A: Yes. On-Prem SSM push the auth code (SLAC) onto Device once they receive it from CSSM.

Q:Can CSLU automatically discover all SLU capable devices or should we do it from devices?

A: Zero-touch DNS discovery of cslu-local. Once device upgrade to SLP code, the default transport is cslu and cslu-local as dns name. Devices can discovered the CSLU if you have configured the name server with an entry where hostname cslu-local is mapped to the CSLU IP address (the windows host where you installed CSLU), no configuration is required. The product instance automatically discovers hostname cslu-local.¬

Q:How often does CSLU talk to CSSM?

A: It depends on the configured value.

Q:Shouldn’t we have there an Orange case mentioning the configuration of URL?

A: Please refer Deploying Smart License Using Policy section in the pdf for configuration.

Q:So, to understand, if I upgrade directly from 16.9.5 (non-Smart licensing) to 17.3.2 (or later), it is NOT necessary to do Device Led Conversion (DLC) manually anymore?

A: That’s correct. DLC will be automatically initiated once device upgrade to SLP code 17.3.2 & later. The DLC request will be forwarded to CSSM via CSLU, on-prem DNAC or On-prem SSM depend on the connectivity and CSSM will revert back with DLC completion status to device.¬

Q:If I have onprem-ssm I assume I'll need to upgrade to the new version supporting SLP in order for DLC work automatically, right?

A: On-Prem SSM needs to upgrade to SLP supported version V8-202102.Device needs to be upgraded to 17.3.3 or later to support On-Prem SSM with SLP.

Q:Maybe I got it wrong (or missed it) but from what I’ve seen devices adding on CSLU is done one by one. Is there any way to do a « bulk » add of several devices?

A: Device can be added in CSLU by both ways: • Bulk Upload using CSV file • Add one-by-one using GUI.

Related Information