To configure or change the boot license on the device, use the license boot command in global configuration mode. To remove a configured boot license, use the no form of this command. If you remove all boot license configurations on the device, the system reverts to the default value.
license boot
{
level
technology-package
|
suite
suite
}
[
disable
]
no license boot
{
level
technology-package
|
suite
suite
}
[
disable
]
Syntax Description
level technology-package
|
Configures a technology package.
A technology package is an image level license. You can configure one or more of the following technology packages: appxk9,
securityk9, uck9.
Note
|
If a technology package is configured, do not configure the suite, which the technology package belongs to - even in releases
where the system permits this. For example, if you configure appxk9, or securityk9, then don't also configure FoundationSuiteK9. For more information, see the Usage Guidelines below.
|
|
suite suite
|
Configures a suite license.
A suite is a superset of one or more image level and feature licenses.
If a suite is configured, you cannot additionally configure technology packages that are included in the suite. The system
rejects such configuration if you do. You can configure the following suites:
-
FoundationSuiteK9: This suite includes the “appxk9” and “securityk9” licenses.
-
AdvUCSuiteK9: This suite includes the "uck9", "cme-srst", and “cube” licenses.
|
disable
|
Disables a PAK license and sets it to “not-in-use”.
Note
|
Although visible on the CLI, this keyword is not supported starting with Cisco IOS XE Gibraltar 16.10.1.
|
|
Command Default
The ipbasek9 technology package is activated by default. It is always enabled, and you can display it by using the show version privileged EXEC command. It is not displayed in any of the licensing related show command outputs .
You cannot disable it or enable it, using the command line interface.
No other boot license is configured by default.
Command Modes
Global configuration (config)
Command History
Release |
Modification |
Cisco IOS XE Release 3.9.1S
|
This command was implemented on Cisco 4000 Series Integrated Services Routers.
|
Cisco IOS XE Everest 16.6.2
|
This command was implemented on Cisco 1000 Series Integrated Services Routers.
|
Cisco IOS XE Gibraltar 16.10.1
|
The disable keyword is no longer supported.
|
Cisco IOS XE Cupertino 17.9.1a
|
Inconsistent system behavior was rectified. The system does not allow duplicate suite and technology package configuration to co-exist.
|
Usage Guidelines
Use the license boot command to:
Depending on your requirements, configure the required technology packages, and suites. If you configure a technology package,
do not also configure the suite it belongs to. If you configure a suite, do not configure the technology packages that are
included in the suite. For example, if you configure the appxk9 , or securityk9 technology packages, do not configure the FoundationSuiteK9 suite. But you can configure AdvUCSuiteK9 .
After you configure the command, remember to save configuration changes. Only then does the configuration change take effect
at the next reboot. When the device reloads, the licensing infrastructure checks the startup configuration for any licenses.
If there is a license in the configuration, the device boots with that license. If there is no license, the licensing infrastructure
follows the image hierarchy to check for licenses.
In scenarios where you change or remove existing boot license configurations, after you save and reload the first time, the
changes are reflected correctly in the output of the show running-config | include boot privileged EXEC command, but not in certain other show command outputs, like show version or show license summary . This has no functional impact, and it does not mean that the configuration changes have not taken effect. You only have to save and reload a second time for the show command outputs to be synchronized.
System Behaviour Change in Boot License Configuration
-
Prior to Cisco IOS XE Cupertino 17.9.1a:
If you configure a suite followed by a technology package which belongs to the suite, the technology package configuration
is rejected.
If you configure a technology package followed by the suite, which the technology package belongs to, the technology package
configuration is permitted by the system, but not recommended. This inconsistent and incorrect system behaviour also causes license count to be reflected incorrectly.
-
Starting with Cisco IOS XE Cupertino 17.9.1a: The system does not allow overlapping suite and technology package configuration to co-exist, regardless of the order in
which you configure.
Examples
The following example shows you how to configure a suite.
If you configure a suite, you cannot configure any of the technology packages that are included in the suite after that. In
this example, we’re configuring the AdvUCSuiteK9 suite. After this the "uck9", "cme-srst" and “cube” technology packages cannot
be configured, but the “appxk9” and “securityk9” technology packages can.
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash: isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# license boot suite AdvUCSuiteK9
% use 'write' command to make license boot config take effect on next boot
Device(config)# exit
Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash: isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite AdvUCSuiteK9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# show version
Cisco IOS XE Software, Version 17.09.01a
Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2022 by Cisco Systems, Inc.
Compiled Mon 07-Mar-22 01:36 by mcpre
.
.
.
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 None Smart License None
securityk9
appxk9
AdvUCSuiteK9 AdvUCSuiteK9 Smart License AdvUCSuiteK9
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 None Smart License None
uck9 uck9 Smart License None
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
<output truncated>
Device# reload
Proceed with reload? [confirm]
*May 27 09:43:35.850: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
Initializing Hardware ...
<output truncated>
Device# show version
<output truncated>
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 None Smart License None
securityk9
appxk9
AdvUCSuiteK9 AdvUCSuiteK9 Smart License AdvUCSuiteK9
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 None Smart License None
uck9 None Smart License None
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
Device# show license summary
Account Information:
Smart Account: BU Production Test As of May 20 18:53:04 2022 UTC
Virtual Account: DLC-VA1
License Usage:
License Entitlement Tag Count Status
-----------------------------------------------------------------------------
booster_performance (ISR_4431_BOOST) 1 IN USE
AdvUCSuiteK9 (ISR_4400_AdvancedUCSuite) 1 IN USE
Examples
The following example shows how to configure a technology package, when a suite license configuration already exists. In this
example, AdvUCSuiteK9 is already configured. Therefore, the only technology packages you can configure are the ones that are
not included in AdvUCSuiteK9, that is, appxk9 and securityk9.
The sample configuration also shows you what happens if you try to configure a technology package (uck9) that is part of the
already configured suite (AdvUCSuiteK9).
Device# show running-config | include boot
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
license boot suite AdvUCSuiteK9
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# license boot level ?
appxk9 Appx License Level
securityk9 Security License Level
Device(config)# license boot level appxk9
% use 'write' command to make license boot config take effect on next boot
Device(config)# license boot level uck9
^
% Invalid input detected at '^' marker.
Device(config)# exit
Device# show running-config | include boot
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
license boot suite AdvUCSuiteK9
license boot level appxk9
Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# reload
Proceed with reload? [confirm]
*May 27 10:16:55.439: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
*May 27 10:17:07.137: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: process exit with reload chassis code
<output truncated>
Device# show version
Cisco IOS XE Software, Version 17.09.01a
Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2022 by Cisco Systems, Inc.
Compiled Mon 07-Mar-22 01:36 by mcpre
.
.
.
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 None Smart License None
securityk9
appxk9
AdvUCSuiteK9 AdvUCSuiteK9 Smart License AdvUCSuiteK9
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 appxk9 Smart License appxk9
uck9 None Smart License None
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
<output truncated>
Device# show license summary
Account Information:
Smart Account: Eg-SA As of May 20 18:53:04 2022 UTC
Virtual Account: Eg-VA
License Usage:
License Entitlement Tag Count Status
-----------------------------------------------------------------------------
booster_performance (ISR_4431_BOOST) 1 IN USE
appxk9 (ISR_4400_Application) 1 IN USE
AdvUCSuiteK9 (ISR_4400_AdvancedUCSuite) 1 IN USE
Examples
The following example shows you how to configure multiple technology packages. In this example there are no existing boot
license configurations on the device - technology packages or suites. The appxk9 and uck9 technology packages are configured.
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# license boot level appxk9
% use 'write' command to make license boot config take effect on next boot
Device(config)# license boot level uck9
% use 'write' command to make license boot config take effect on next boot
Device(config)# exit
Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot level appxk9
license boot level uck9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# reload
Proceed with reload? [confirm]
*May 27 15:51:25.530: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
Device# show version
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 None Smart License None
securityk9
appxk9
AdvUCSuiteK9 None Smart License None
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 appxk9 Smart License appxk9
uck9 uck9 Smart License uck9
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
<output truncated>
Device# show license summary
Account Information:
Smart Account: Eg-SA As of May 20 18:53:04 2022 UTC
Virtual Account: Eg-VA
License Usage:
License Entitlement Tag Count Status
-----------------------------------------------------------------------------
booster_performance (ISR_4431_BOOST) 1 IN USE
appxk9 (ISR_4400_Application) 1 IN USE
uck9 (ISR_4400_UnifiedCommun...) 1 IN USE
Examples
The following example shows you how the system behaves when you configure a technology package, followed by the suite, which
the technology package belongs to.
In this example, the software version running on the device is Cisco IOS XE Cupertino 17.9.1a and there is no existing boot
license configuration on the device. Here we configure technology package appxk9, and then the corresponding suite FoundationSuiteK9,
followed by another technology package which is not part of configured suite (uck9 is part of AdvUCSuiteK9 and not FoundationSuiteK9).
Even though the system saves the configuration as displayed in the output of the show running-config command before reload, after reload, appxk9 is removed from configuration and only FoundationSuiteK9 is retained. The uck9
technology package is not part of FoundationSuiteK9, so this configuration is retained after reload.
Note |
There is a difference in the system’s behavior before and after 17.9.1 for this scenario. In releases prior to 17.9.1, appxk9
and FoundationSuiteK9 are retained even after reload.
Configuring a technology package and the suite it belongs to, is not recommended in any release.
|
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# license boot level appxk9
% use 'write' command to make license boot config take effect on next boot
Device(config)# license boot suite FoundationSuiteK9
% use 'write' command to make license boot config take effect on next boot
Device(config)# license boot level uck9
% use 'write' command to make license boot config take effect on next boot
Device(config)# exit
Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite FoundationSuiteK9
license boot level appxk9
license boot level uck9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# reload
Proceed with reload? [confirm]
*May 27 16:39:43.657: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
*May 27 16:39:55.969: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: process exit with reload chassis code
<output truncated>
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite FoundationSuiteK9
license boot level uck9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Output of the show version and show romvar privileged EXEC commands after the first reload: Device# show version
Cisco IOS XE Software, Version 17.09.01a
Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2022 by Cisco Systems, Inc.
Compiled Mon 07-Mar-22 01:36 by mcpre
.
.
.
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 FoundationSuiteK9 Smart License FoundationSuiteK9
securityk9
appxk9
AdvUCSuiteK9 None Smart License None
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 appxk9 Smart License appxk9
uck9 uck9 Smart License uck9
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
<output truncated>
Device# show romvar | include BOOT
FACTORY_BOOT_LEVEL =
BOOT = bootflash:isr4400-universalk9.17.09.01a.SPA.bin;
LICENSE_BOOT_LEVEL = appxk9,appxk9:esg;uck9,uck9:esg;
Saving configuration, a second time:Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# show romvar | include BOOT
FACTORY_BOOT_LEVEL =
BOOT = bootflash:isr4400-universalk9.17.09.01a.SPA.bin,1;
LICENSE_BOOT_LEVEL = uck9,uck9:esg;
Reloading, a second time:Device# reload
Proceed with reload? [confirm]
*May 27 17:56:31.606: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
May 27 17:56:43.839: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: process exit with reload chassis code
Initializing Hardware ...
All show command outputs are synchronized after saving configuration and reloading a second time: Device# show version
Cisco IOS XE Software, Version 17.09.01a
Cisco IOS Software [Cupertino], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.9.1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2022 by Cisco Systems, Inc.
Compiled Mon 07-Mar-22 01:36 by mcpre
.
.
.
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 FoundationSuiteK9 Smart License FoundationSuiteK9
securityk9
appxk9
AdvUCSuiteK9 None Smart License None
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 None Smart License None
uck9 uck9 Smart License uck9
securityk9 None Smart License None
ipbase ipbasek9 Smart License ipbasek9
Device# show license summary
Account Information:
Smart Account: Eg-SA As of May 20 18:53:04 2022 UTC
Virtual Account: Eg-VA
License Usage:
License Entitlement Tag Count Status
-----------------------------------------------------------------------------
booster_performance (ISR_4431_BOOST) 1 IN USE
uck9 (ISR_4400_UnifiedCommun...) 1 IN USE
FoundationSuiteK9 (ISR_4400_FoundationSuite) 1 IN USE
Examples
The following example shows you how the system behaves when you configure the no form of the command.
In this example, the FoundationSuiteK9 suite and the uck9 technology package are already configured on the device. The no form of the command is used to remove only uck9. After saving the configuration change and reloading the device, FoundationSuiteK9
is the only boot license configuration remaining on the device.
If FoundationSuiteK9 configuration is also removed, then the device will revert to default.
Device# show running-config | include boot
boot-start-markerb
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite FoundationSuiteK9
license boot level uck9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device(config)# no license boot level uck9
% use 'write' command to make license boot config take effect on next boot
Device(config)# exit
Device# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite FoundationSuiteK9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
Device# reload
Proceed with reload? [confirm]
*May 31 05:37:52.350: %SYS-5-RELOAD: Reload requested by test on console. Reload Reason: Reload Command.
May 31 05:38:04.863: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: process exit with reload chassis code
Initializing Hardware ...
<output truncated>
Device# show running-config | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.17.09.01a.SPA.bin
boot-end-marker
license boot suite FoundationSuiteK9
diagnostic bootup level minimal
snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail