The pay-as-you-grow licensing of the 7750 SR hardware platforms includes the ability to distribute software based licenses to operational systems in a live network. This is done by the creation of a license key file containing various individual licenses, making this file available to a system, and then activating that license key file on the system. Nokia provides the Configuration License Manager (CLM) tool to assist in this process. Normally, the CLM would perform all the steps in license distribution to a target system and only the assignment of individual licenses within a system itself need to be managed using the management mechanism for the system itself.
The license key file is a secure distribution mechanism for the licenses. Within the license key file, are one or more license keys. Each license key is assigned for a particular target system identified using a UUID. This UUID is tied to the chassis of the system and therefore the license key can only be validated on the system with that chassis. Each license key is also tied to a specific major software release of SR OS.
When a license key file is available to a target system and is activated it is first validated to ensure it is applicable for the specified target. For the license key of the SR OS hardware platform to be valid, the operator must ensure that the:
license is for a 7xxx platform
UUID of the system matches the one encoded in the "UUID-locked" license key
SR OS software version (the major release number) matches the one encoded in the license key
license file is not expired
Validation or activation of the license key file results in zero or one license key that is valid for the running software on the target. If there is a valid license key, the records contained in that key are read and made available to the system (see Software License Records).
There may be additional license keys in the file that are for the target system but for a different software release. This is the case when an upgrade of the system is planned. Those license keys shall be considered available however, the feature licenses contained within them are not available for use. These can be seen using the show system license available-licenses command.
A:bkvm20# show system license available-licenses
===============================================================================
Available Licenses
License name : sr-regress@list.nokia.com
License uuid : ab516e50-2413-44aa-9f7c-34b4e5b64d19
Machine uuid : ab516e50-2413-44aa-9f7c-34b4e5b64d19
License desc : 7xxx Platform
License prod : 7xxx Platform
License sros : TiMOS-[BC]-16.0.*
Current date : FRI NOV 03 15:53:54 UTC 2017
Issue date : FRI SEP 22 20:55:14 UTC 2017
Start date : FRI SEP 15 00:00:00 UTC 2017
End date : THU MAR 15 00:00:00 UTC 2018
-------------------------------------------------------------------------------
License name : sr-regress@list.nokia.com
License uuid : ab516e50-2413-44aa-9f7c-34b4e5b64d19
Machine uuid : ab516e50-2413-44aa-9f7c-34b4e5b64d19
License desc : 7xxx Platform
License prod : 7xxx Platform
License sros : TiMOS-[BC]-17.0.*
Current date : FRI NOV 03 15:53:54 UTC 2017
Issue date : FRI SEP 22 20:55:14 UTC 2017
Start date : FRI SEP 15 00:00:00 UTC 2017
End date : THU MAR 15 00:00:00 UTC 2018
-------------------------------------------------------------------------------
2 license(s) available.
===============================================================================
On a system boot, the license key file pointed to by the BOF is activated. If new license key files are activated on a system, the BOF should be updated to point to the new license key file. If there are active licenses in system that are in use and the node reboots and the license key file pointed to by the BOF either fails to validate or does not contain the in-use license records, the system is considered to be in unlicensed state. In this state, the node reboots every 60 minutes until the records are no longer in-use or a valid license key is provided that includes all the in use license records.