Field Notice: FN74148 - PAK and RTU Licenses Cannot Be Converted to Smart Licenses When Doing Direct (Long-Jump) Upgrades from Cisco IOS XE Software Release 17.3 or Earlier to Release 17.11 or Later - Workaround Provided

Available Languages

Updated:June 21, 2024
Document ID:FN74148

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected


Affected Software Product Affected Release Affected Release Number Comments
IOS XE ROMMON Software 17 17.3(1r), 17.3(2r), 17.3(3r), 17.4(1r), 17.6(8.1r), 17.6(8r), 17.7(3r)  

Defect Information


Defect IDHeadline
1undefined

Problem Description


Product Activation Key (PAK) and Right To Use (RTU) licenses cannot be honored when upgrading from Cisco IOS XE Software Release 17.3.4 or earlier to Release 17.11 or later.

Devices that do not have a PAK or RTU license are not affected.


Background


Cisco IOS XE Software releases interact with PAK and RTU licenses in the following ways:

Cisco IOS XE Software Release Behavior with PAK and RTU Licenses
17.3.4 and earlier Software can read and honor PAK and RTU licenses.
17.3.5 through 17.10.x Software can read and honor PAK and RTU licenses. Software takes a snapshot of the licenses for future software to honor PAK and RTU.
17.11.1 and later Software cannot read PAK and RTU licenses. Software uses only the snapshot information to honor PAK and RTU licenses.

Problem Symptom


When migrating directly from Cisco IOS XE Software Release 16.9 to Release 17.12, High Security License (HSEC) will not work and Device Lead Conversion (DLC) is not available.


Workaround/Solution


Solution

If a device has PAK and RTU licenses, complete the migration steps shown in the following table:

Current Cisco IOS XE Software Release Fix Instructions
17.3.4 and earlier 
  1. Migrate to 17.3.5 or later or 17.6.2 or later.
  2. Send the license usage report and ensure that DLC is successful.
  3. Migrate to 17.11 or later
17.4.1
17.5.1
17.6.1
  1. Migrate to 17.6.2 or later.
  2. Send the license usage report and ensure that DLC is successful.
  3. Migrate to 17.11 or later.
 

Note: For devices that do not have PAK or RTU licenses, migrate directly to Cisco IOS XE Software Release 17.11 or later. There is no need to migrate to an intermediate snapshot-taking release.

To download software, use the Cisco Software Download Center.


How to Identify Affected Products


To see the current software release, use either the show version or the show environment command.

After migrating to a snapshot-taking release, check the contents of the snapshot using the show platform software sl-infra pak-info command.


Revision History


VersionDescriptionSectionDate
1.0Initial Release—2024-JUN-21

For More Information

For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:

Receive Email Notification About New Field Notices

To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco