Versions Compared

Old Version 49

changes.mady.by.user W.Erber

Saved on

compared with

New Version Current

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Small clarification

...

Table of Contents
excludeContents
stylesquare

Sentinel/Gemalto

...

Tools not Applicable to the VE License Server

Any Sentinel/Gemalto-specific license tools provided with the emulator installation are not applicable to the VE license server configuration.

...

Actions that can Invalidate a VE License

class
Excerpt

For cloud deployments: if supported by the cloud provider, the VE license server instance can be moved to a different subnet, as long as the original instance can be moved.

It is also possible to backup and restore (to the same instance) the license server data. Please note: it is not possible to use such a backup to revert to a previous license version.

However, the following actions will invalidate the license:

  1. All supported environments:
    • Copying the license server data to a different instance.
    • Seriously damaging the root filesystem of the license server system.
    • Re-installing the license server system.
    • Copying the virtual machine on which the license server runs. This includes cloning a virtual machine, or recovering a backup into a new virtual machine.
    • Changing the number of CPU cores of the license server system.
  2. VMware environments:
    • Restrictions from point 1 above. 
    • If the license server is bound to the ESXi host: using vMotion on the VM in which the VE license server runs
    • Changes to the API interface of the ESXi host or vCenter Server
    • The license can become temporarily unavailable if the user credentials or address information recorded by esxi_bind are changed. In this case, esxi_bind must be run again to define the correct user credentials and address information.
Div
pagebreak


Starting and Stopping the License Server

...

The licensed service logs information to its log file in /opt/license-server/license_loglog/license.log and to journalctl.

...

The example below shows the output of such a time-limited license:

Code Block
languagetext
# /opt/license-server/license_viewer 
<<License Viewer>> Current license:
License fingerprint: 07792211fc8ce3fdc085 <truncated>
Customer name: Stromasys
License ID: 01.00000001.002.020
Key type: COUNTDOWN
Expiration date: 100 hour(s)
Platform: amazon.aws
Release date: 2021-06-17 13:08:01
Grace period: 120 minutes
License check interval: 60 minutes

Virtual Hardware: Charon-SSP/4M,Charon-SSP/4U
Product code: Charon-SSP/ALL
Expiration date: 2021-12-22 23:55:00
Major Version: 5
Minor Version: 3
Maximum CPU: 64
Maximum virtual memory: 1048576MB
Instances allowed: 3

...

Should the primary license server become unavailable, the emulator tries to connect to the backup license server. If this succeeds, the emulator continues to run without interruption. If no connection to a valid license can be established within 2 hours after the loss of the license has been detected, the emulator will stop. The grace period is defined on the license.

Please note: If you do not have a valid backup license and the primary license server is unavailable for more than 2 hoursthe grace period, make sure to shut down the guest operating system cleanly before the end of the grace period. Failure to do so may cause data loss or corruption.

If the primary license server becomes available again after the emulator has switched to the backup server, the emulator will automatically switch back to the primary server to avoid unnecessary depletion of the backup license runtime hours in VE license server mode.

Div
classpagebreak


Log Files

...

License server log file /opt/license-server/license_log/license.log

At every license server start, a new version of the log file is created and the previous file is rotated to license.log.1. Other existing versions are rotated accordingly.

...

The software checks for compatible protocol versions between license server and emulator software. It logs an error if the versions are not compatible.

The following messages may logged in older versions:

Code Block
languagetext
2020-01-16 11:24:38 WARN  VE  Failed to get data from license server!

...

Code Block
languagetext
2021-08-10 17:16:41 ERROR VE       License protocol version is invalid.

Management GUI Web Server Log File

This log file contains errors encountered by the web server providing the management GUI of the VE license server.

Log file location: /opt/license-server/error.log

Sample content:

Code Block
languagetext
$ cat /opt/license-server/error.log

<attempt to start the license server a second time>
[1636549131] [error] [client ] cannot bind to 80: 98 (Address already in use)
[1636549131] [error] [client ] cannot bind to 8084s: 98 (Address already in use)
[1636549131] [error] [client ] Failed to setup server ports

<restart of the license server>
[1636551531] [error] [client 192.168.2.80] SSL syscall error 104
[1636551532] [error] [client 192.168.2.80] SSL syscall error 104


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc