IOS 16.9.x Traditional vs. Smart Licensing on ISR4321

[TheRealBTU]

We're looking to upgrade our ISR4321 to IOS 16.9.x (IOS 16.9.6 to be exact) and there's some conflicting documentation regarding traditional PAK licensing vs. Smart Licensing.  We're running the traditional PAK license model.

In one support article I read, for ISR4000 routers it states that Smart Licensing does not become mandatory until IOS 16.10.x, and is still optional in 16.9.x.

However, in another article it states that anything after 16.9.1 on ISR4000's use Smart Licensing as the only license method.  There is no documentation in the 16.9.x release notes indicating that a change was made within the 16.9.x release cycle that forced mandatory Smart Licensing.  In the 16.10.x release notes, it is clearly explained that Smart Licensing is mandatory from 16.10.x forward.

With all that said, is anyone running an ISR4000 with 16.9.6 using traditional PAK licensing?  Our ISR4321 is air-gapped and won't be a good candidate for smart licensing.

[Leo Laohoo · Accepted solution]

Cisco Smart License for routers start from 16.10.X.  

16.9.X is still "traditional" license.

Be aware of the following Smart License Field Notice: 

FN - 72323 - Cisco IOS XE Software: QuoVadis Root CA 2 Decommission Might Affect Smart Licensing, Smart Call Home, and Other Functionality

FN - 72578 - Cisco IOS XE - Smart Licensing Using Policy Might Cause High CPU/Memory Usage

[johnlloyd_13 · Accepted solution]

hi,

smart license starts in IOS-XE 16.9.1 and above for catalyst 3650/3850 and 9000 series switches and 16.10.1 and above on ASR1K, ISR1K and ISR4K series routers. refer to link below:

https://wannabelab.blogspot.com/2021/05/cisco-smart-licensing-in-isr-4000.html

you'll still keep your traditional PAK license with IOS-XE 16.9.6

[TheRealBTU]

***NEVERMIND THE BELOW, WE GOT IT TO WORK OUT***

Thanks everyone!

16.9.6 upgrade is failing.  During the IOS upgrade, it automatically upgrades the ROMMON from 16.7(3r) to 16.7(5r) but that only seems to stick on ROM 0 and it leaves 16.7(3r) on ROM 1 which appears to be causing the IOS upgrade to fail.  All of that is happening during the IOS install with no intervention from my side.  After many retries, it ultimately reboots into the old IOS v3.17.04.

I've attached the output from where it attempts the ROMMON upgrade till the end.

Any thoughts?