This document describes differences between Traditional, Smart Licensing, and Smart Licensing with Policy on Cisco IOS® XE Routing Platforms.
Cisco recommends that you have knowledge of these topics:
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
For Cisco IOS XE devices, there are 3 licensing models. Based on the platform, there are some optional and mandatory licensing models that are used.
For the Cisco IOS XE physical routers/platforms (ASR1K, ISR4K, ISR1K and CAT8K) the licensing model adoption is:
In this document, the acronym SL is used for Smart Licensing and SLP for Smart Licensing Using Policy.
By late 2025, the traditional and smart licensing models are considered legacy and deprecated schemes as the last code it can be used is in End Of Support status. The only fully supported model is SLP.
In traditional licensing, a .lic extension file that contains a Product Authorization Key (PAK) is used. The file has to be installed in the device in order to be entitled to use the licensed features.This license scheme has limitations:
To improve the licenses for management and accounting, Smart Licensing was developed.
SL model is flexible as the licenses are not node-locked to the hardware. Transfer a license from one device to another is simpler. SL established the licenses pool system, in the case that a device in the organization requires a license it can be requested and consumed. The licenses can be divided in virtual pools and monitored from a centralized portal always updated.
Based on the Smart Licensing way of activation, there are some challenges that have to be overcome such as:
SLP provides another level of flexibility as each license is considered independent. The device now does not require permanent communication with Cisco License Central to have the license in compliance. For most of the common features, it has a Day Zero frictionless deployment.
Some concepts and terminology changed between SL and SLP. This table compares the deployment types per license scheme. The table can be used as a reference to check the SL and SLP documentation.
| Supported Deployments | Traditional Licensing | Smart Licensing | Smart Licensing Using Policy |
| Direct Internet access | Hardware local license install | Communication directly with Cisco License Central | Communication directly with Cisco License Central |
| On-Premises | Hardware local license install | Communication with Cisco License Central On-Prem | Communication with Cisco License Central On-Prem plus Cisco Smart Licensing Utility (CSLU) |
| Air-gapped networks | Hardware local license install | Cisco License Central On-Prem, Specific License Reservation, Permanent License Reservation | Cisco License Central On-Prem, CSLU, transport-off |
| Notes |
Traditional Licensing |
Smart Licensing | Smart Licensing Using Policy |
| Product Instance | No Cisco License Central | Hostname displayed in Cisco License Central | Hostname is no longer displayed on Cisco License Central and License UDI is displayed instead. 17.8.1 to include License UDI and hostname. |
| Relationship with Cisco License Central | No Cisco License Central | Registers with Cisco License Central | Creates a trust relationship with Cisco License Central |
| Day 0 (Licensing deployment) | If no license file is installed, features are not available. | No licensing available without registration. Enforced licenses features cannot be used until licenses are authorized after registration with Cisco License Central. Some features permit evaluation period. | Licenses are enabled by default. Only export-restricted licenses such as HSECK9 require an authorization code before use. Compliance is still required but not mandatory for the initial deployment. |
| Report to Cisco License Central | Does not communicate with Cisco License Central | SL does not report license usage to Cisco License Central. Instead, it authorizes license requests sent by the router. | RUM reports are used as proof of license usage and uploaded to Cisco License Central |
| Communication method | Does not communicate with Cisco License Central | Call-Home | Call-Home or SmartReceiver |
| Revision | Publish Date | Comments |
|---|---|---|
4.0 |
28-May-2026
|
Recertification, Replace references to "Cisco Smart Software Manager (SSM)" with "Cisco License Central." |
3.0 |
02-Dec-2025
|
Recertification |
1.0 |
24-May-2022
|
Initial Release |