vSIM software licensing

vSIM licensing overview

This section describes how software licensing applies to vSIMs. For a vSIM to be fully functional, the system must load a valid license file at bootup. The license file encodes the allowed capabilities and features of the vSIM system. Contact your Nokia account representative to obtain license files associated with a purchase order or trial request.

vSIM license keys

When you purchase software licenses for one or more vSIMs, your Nokia account representative will provide you with corresponding vSIM license key files, which could be one license file for all the vSIMs or a separate license file for each one.

Each vSIM requires its own license tied to the specific UUID of the individual vSIM VM, but more than one license may be included in a license file. The virtual machines acting as the CPMs of each vSIM must have their UUID identifiers manually set to the specified values. See Domain name and UUID for more information UUID identifiers.

The license-file boot-option parameter of each vSIM indicates the location of the license file, which can be a local disk location or an FTP server location. The license-file parameter can be specified by editing the BOF file (before or after bootup), or by including it in the SMBIOS information provided to each CPM virtual machine of the vSIM. See Sysinfo for more information about the SMBIOS parameters.

Note: Both CPMs in a redundant vSIM system should have the same BOF setting for the license-file parameter. Also, if the license-file is stored on the local disk (CF3) of the active CPM, it should also be stored on the local disk (CF3) of the standby CPM. You can use the admin redundancy synchronize boot-env command to synchronize the BOF settings and copy the license-file to the standby CPM if it is stored locally.

When the vSIM software starts booting and determines that it should serve the function of a CPM in a vSIM system, it attempts to read and parse the referenced license file.

If the CPM cannot find a valid license key and it is the only CPM of the vSIM, the system is allowed to complete its bootup procedures but only a limited number of non-configuration-related commands are available in this state, and the system is forced to reboot after 60 minutes.

If the CPM cannot find a valid license key (with matching UUID, major software version, and valid date range), and the vSIM has another CPM with a valid license key, only the CPM without a license will be rebooted after 60 minutes. In the meantime the system is fully functional. However, if either CPM of a vSIM system has a corrupt license file or a license file for the wrong type of product, the entire chassis will be forced to reboot after 60 minutes.

Note: The IOMs of a vSIM system do not need their own license keys; they inherit the license state of the system, as determined by the CPMs. The IOMs reboot immediately if no CPM has a valid license.

Checking the license status

After the vSIM is operational, you can check the license status of the system. At the prompt, type the following:

show system license ↵

The following is example output for a vSIM emulating a 7750 SR-7 chassis with a valid license:

A:Dut-A# show system license 
System License
License status : monitoring, valid license record
Time remaining : 99 days 4 hours
License name   : name@organization.com
License uuid   : 00000000-0000-0000-0000-000000000000
Machine uuid   : a8812f3e-a90d-4de3-8a5e-6e44001e35f6
License desc   : 7xxx vm-training-sim
License prod   : Virtual-SIM
License sros   : TiMOS-[BC]-16.0.*
Current date   : WED OCT 24 20:52:37 UTC 2018
Issue   date   : THU AUG 02 17:40:35 UTC 2018
Start   date   : WED AUG 01 00:00:00 UTC 2018
End     date   : FRI FEB 01 00:00:00 UTC 2019