...
An ISR 4000 series router might lose Boost license configuration while using a 16.12 release and it is registered to On-prem server, there is a surplus of boost licenses. This syslog entry can be seen at random times: Dec 25 22:23:36.755: %BOOST_PERFORMANCE-2-CONFIG_REMOVED: Boost capability removed. Throughput will be defaulted on next reload. Reason: Insufficient license in Virtual account This causes the boost throughput configuration to be lost. A deregister and register is required to fix the problem, however it reoccurs. We see the below output in "show lic eventlog" 2021-01-25 10:01:20.084 EST SAEVT_TAG_OOC count="1" entitlementTag="regid.2017-05.com.cisco.ISR_4300_BOOST_DEMO,1.0_18514d25-c5a0-4299-afbd-5dc97d2e4bb1" Tested with On-prem 8-202006 and 8-202010 and same issue. + The VA in the On-prem reports the below at the time of the event, so looks that device keeps asking for boost demo for some reason even if it was authorized for regular boost + "The Virtual Account "Default" reported a shortage of 1 "Boost Performance Demo License for ISR4300" + With "show lic usage" we see "DEMO boost" and regular boost license being asked for, after authorization is finished, regular boost is shown as authorized but "DEMO boost" is shown as out of compliance. Expected behavior: Demo boost should no longer be asked for from the device if customer has a surplus of permanent boost licenses.
Devices that had boost previously installed with Traditional Licensing (.lic) are not having the problem after the upgrade, issue has been seen with device that did not had a boost license installed before the upgrade to a Smart Licensing only release. + Reboot was done an same issue + Customer is using smart trust as transport + Surplus of boost licenses in On-prem + Tested with On-prem 8-202006 and 8-202010 and same issue.
+ Deregister and register to On-prem + Then wait for boost option to re-appear + Configure boost throughput back again. + However , this is temporary, since issue reapers after a random number of days.
Issue has been fixed with On-Prem versions 8-202102/8-202105. Issue has not been seen with 17.3.3 and newer releases.