The Cisco PAK retirement forces every customer onto Smart Licensing. The conversion is not automatic. Telemetry runs in the background. The buyer side reads the conversion math before the cutover.
Cisco retired the PAK licensing model. Every device must convert to Smart Licensing Using Policy. The conversion is not automatic. The buyer side that reads the conversion ahead of the deadline keeps the entitlement intact and shapes the renewal.
This article covers the PAK retirement, the Device Led Conversion path, the CSSM telemetry exposure, the common conversion gaps, and the buyer side moves before the cutover.
Cisco published the PAK retirement schedule across the product portfolio. New shipments stopped accepting PAKs years ago. The conversion deadline runs on a per platform schedule.
Catalyst switches and ISR routers moved first. Nexus data center and ASR aggregation followed. ASA firewalls and Wireless LAN Controllers completed the transition. The wave finishes across the supported install base by the end of 2026.
Cisco frames Smart Licensing as a simplification. The simplification is real for entitlement management at scale. The trade off is the always on telemetry stream into CSSM.
Each platform carries a documented grace period after the PAK end of support. Devices that miss the grace period go into evaluation mode. Evaluation mode disables save operations on licensed features.
Device Led Conversion is the script driven path from PAK to Smart Licensing. The device reads its installed licenses and submits them to CSSM. The process needs CSSM connectivity from the device or a satellite proxy.
The DLC script ships in IOS XE, NX OS, and the platform specific images. The administrator runs the license smart conversion command. The device collects the installed license data and submits to CSSM.
CSSM matches the submission against the customer Smart Account. The match requires the Smart Account ID and a token. The token authorizes the conversion against the entitlement.
A successful conversion moves the entitlement from PAK to Smart Licensing. The device reports consumption on the new model. The PAK record is closed in the Cisco licensing system.
Smart Licensing Using Policy runs telemetry by default. The CSSM stream is always on. The data sits in the Cisco Smart Account and informs the account team conversation.
CSSM collects the device model, the firmware version, the feature set, the consumed license count, and feature specific telemetry. The feature telemetry includes details on collaboration, security, and analytics features.
Cisco uses the CSSM data at the ELA renewal. The renewal letter prices in the consumed licenses plus a forecast. The buyer side that runs the consumption review before the letter lands holds the line.
Some customers limit the telemetry through the policy mode and the on prem satellite. The exact data sent in each policy mode is documented in the Smart Licensing Using Policy guide.
| Connectivity mode | Telemetry frequency | Data scope | Customer control |
|---|---|---|---|
| Direct to CSSM | Real time | Full feature set | Low |
| SSM On Prem satellite | Scheduled batch | Filtered through satellite | Medium |
| Air gap with manual sync | Manual file upload | Reviewable by customer | High |
| Policy mode no connectivity | Local only until next sync | Stored on device | High |
The conversion looks straightforward in the Cisco documentation. In practice five gap patterns appear in most estates.
Many customers run the conversion against a default Smart Account structure that does not match the operating model. Virtual Accounts within the Smart Account need to mirror the business unit or region structure.
The PAK records and the Smart entitlement do not always align one to one. Some PAK licenses convert to a different Smart license name or tier. The conversion mapping needs a manual review.
The DLC script requires a minimum firmware version. Devices below the version cannot complete DLC and need an upgrade first.
Some networks block outbound to CSSM. The conversion stalls until the satellite proxy is deployed.
Devices already in evaluation mode lose feature configuration ability. The reset requires a CSSM ticket and Cisco support assistance.
Smart Licensing telemetry feeds the ELA renewal and the compliance check. The buyer side that runs the math before the renewal holds the line.
The ELA renewal prices the consumed licenses plus a forecast. Consumption is the CSSM reported count. The buyer side that runs the count review identifies the overcount.
Entitlement mismatches between the contract and the CSSM count trigger a Cisco compliance check. The check works against the customer if the conversion is incomplete.
Some features auto enable on a firmware upgrade. The feature consumption shows in CSSM and adds to the renewal.
The buyer side runs five workstreams before, during, and after the conversion. Each stream feeds the renewal math.
The checklist takes the customer from the PAK retirement notice to the executed Smart Licensing model. The earlier the work starts the wider the option set.
Cisco retired the Product Activation Key (PAK) licensing model. New devices ship under Smart Licensing only. Existing devices must convert through Device Led Conversion or migration tools. The cutover applies across Catalyst switches, ISR routers, ASR aggregation routers, Nexus data center, ASA firewalls, and Wireless LAN Controllers.
Smart Licensing Using Policy (SLP) is the current Cisco license model. Devices report consumption telemetry to the Cisco Smart Software Manager (CSSM) at registration and at periodic intervals. CSSM compares the consumed licenses against the customer entitlement. The policy mode allows devices to operate without continuous CSSM connectivity.
Device Led Conversion (DLC) is the script driven migration from PAK to Smart Licensing. The device reads its installed licenses and submits them to CSSM. CSSM matches the submission against the customer Smart Account and converts the entitlement. DLC requires temporary internet connectivity from the device or a satellite proxy.
A device that misses the DLC window goes into evaluation mode after a grace period. In evaluation mode the device runs but cannot save configuration changes that require licensed features. The customer must manually restore the entitlement through a CSSM ticket. The ticket process can take days to weeks.
CSSM collects the device model, the firmware version, the installed feature set, the consumed license count, and the configuration of telemetry sensitive features. The data sits in the Cisco Smart Account and is visible to the Cisco account team. The visibility shapes the next renewal conversation.
Yes. Smart Software Manager On Prem is an on premise satellite that proxies the CSSM connection. The satellite collects the telemetry locally and synchronizes to CSSM on a schedule. The satellite is required for air gapped networks and government deployments.
Cisco uses the CSSM consumption data as the base for the ELA true up at renewal. The buyer side that runs the consumption review before the renewal letter lands holds the negotiation. The review identifies overcounted features and devices in evaluation mode.
Redress runs the conversion analysis inside the Vendor Shield subscription and the Renewal Program. The work includes the device inventory, the conversion plan, the CSSM telemetry review, the entitlement reconciliation, and the renewal math. The independent buyer side position protects against the Cisco account team narrative.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Cisco Services, and the Software Spend Assessment. Independent buyer side advisory means no vendor partner conflicts and no resale margin.
Related reading: the benchmarking service, the Benchmark Program, the case studies, the white paper library, the blog, and the news room.
The companion guide covers Smart Licensing, ELA structures, Meraki bundling, and the renewal moves that hold the line. Pairs with the PAK migration work on every Cisco renewal.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Cisco retired the PAK model but the conversion is not automatic. Every device that misses the registration window goes into evaluation mode. The buyer side that runs the conversion ahead of the deadline keeps the entitlement intact.
Independent Cisco reviews start with the PAK to Smart conversion, the CSSM telemetry exposure, and the ELA renewal math. Vendor Shield subscribers run the conversion ahead of the cutover.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
