...

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.

...

• Charon-SSP:
  • HASP Viewer, HASP Updater, and HASP Manager in the Tools > HASP Tools menu of the Charon Manager
  • The Regular and Backup License parameter in the emulator license configuration section
  • The command-line tools in /opt/charon-agent/ssp-agent/utils/license
• Charon-PAR:
  • The command-line tools in /opt/charon/bin (including the update tool hasp_update, and the license viewer and C2V creation tool hasp_srm_view)
    
  • The license_id configuration parameter is not supported. To choose a specific product section, the passphrase of the section is used.

The above tools and commands cannot be used for managing VE licenses. Please ignore them if you have a VE license.

Actions that

...

Can Invalidate a VE License

...

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.

However, the following actions will invalidate the license:

...

• 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
• Changing the number of CPU cores of the license server system.

...

• 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.

...

Starting and Stopping the License Server

...

• For general VE license mode, backup licenses are typically limited to a certain number of emulator runtime hours. The backup license server is only used for failover if the primary license server fails in order not to deplete the available runtime hours unnecessarily.
• For AutoVE mode, the two license servers act as peers between which the client database is synchronized. The total number of instances available on both servers determines the number of Charon host cloud instances that can be licensed from the license server pair. Each instance can connect to either of the two servers. However, if one of the peers fails and there are not enough available instances on the second peer, there is no backup for an instance trying to fail over to the second  peer due to failure of its primary server - and the emulators running on this instance will fail. The license on the server designated as backup server can be a countdown license (specified number of runtime hours) or a normal license.

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

...

License server not found at start:

2021121320211214:143042193342.636793307175:VE primary license 192.168.2.2
2021121320211214:143042193342.637170307701:There is no VE backup server.
2021121320211214:143042193342.646820334171:Trying to login to license server: 192.168.2.2
2021121320211214:143051193351.649398337196:warn:Unable to login to server because error 100
20211213:143051.649580 the license server failed to respond
20211214:193351.337392:err:Failed to connect with the license server.
2021121320211214:143051193351.649618337457:err:Failed to connect with the license server.
2021121320211214:143051193351.649669337509:err:Exit
2021121320211214:143051193351.655735339823:err:Invalid license product name

...

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

Sample content:

$ cat /opt/license-server/log/errorwebserver.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

...