Versions Compared

Old Version 61

changes.mady.by.user W.Erber

Saved on

compared with

New Version 62

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sentinel/Gemalto-specific tools and configuration options on in Charon -SSPemulator kits:

In Charon -SSPemulator kits, the Sentinel/Gemalto-specific license tools and configuration options are available when installing the management packages for the VE-capable Charon-SSP complete emulator packages. These tools and options are in particular the following:

  • 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

The above tools cannot be used for managing Charon-SSP VE licenses. Please ignore them if you have a VE license.

...

classpagebreak

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:

...

  • Charon-PAR:
    • The command-line tools in /opt/charon/bin
    • Certain configuration parameters in the configuration file (in particular license_id, hasp_lost_usr_cmd, license_changed_usr_cmd, and license_expiration_warning_usr_cmd).

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

Div
classpagebreak


Actions that can Invalidate a VE License

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.

However, the following actions will invalidate the license:

  • 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
    • Changing the number of CPU cores of the license server system.
  • VMware environments:
    • 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.
  • AutoVE deployments:
    • Charon emulator host instance register with their license server only once at start. This is recorded on the license server in /opt/license-server/instances.db. If this file is lost, the license is not invalidated from the license server's view, but it can no longer be used from the Charon host instances as they will not register a second time. The Charon host instances would have to be recreated (fresh instance launch from a supported marketplace instance). Therefore, it is very important to backup up the instance database file.

...

Code Block
languagetext
(License loss detected)

2020-07-16 22:25:56 ERROR VE       Failed to connect with the license server!
2020-07-16 22:25:56 WARN  VE       Charon will be terminated within 2 hours!

(License server connection restored)

2020-07-16 23:26:01 INFO  VE       Connected with license server: 127.0.0.1
2020-07-16 23:26:01 INFO  VE       Found available license ID: 01.00000001.002.044.
2020-07-16 23:26:01 INFO  VE        VE       Customer name: Stromasys/Testing.
2020-07-16 23:26:01 INFO Customer name: Stromasys/Testing.
2020-07-16 23:26:01 INFO  VE       Virtual hardware model Charon-SSP/4M is licensed.
2020-07-16 23:26:01 INFO  VE       Maximum concurrent instances are limited to 4.
2020-07-16 23:26:01 INFO  VE       Maximum allowed virtual CPU(s) are 4.
2020-07-16 23:26:01 INFO  VE       Maximum allowed virtualized memory is 512 MB.
2020-07-16 23:26:01 INFO  VE       Major allowed version number is 4.
2020-07-16 23:26:01 INFO  VE       Minor allowed version number is 2.
2020-07-16 23:26:01 INFO  VE       Expiration UTC time: 2020-12-31 15:55:00.
2020-07-16 23:26:01 INFO  VE       Local UTC time: 2020-07-16 15:26:01.
2020-07-16 23:26:01 INFO  VE       The license is verified, back to normal operation.

Please note: The output shows a 2 hour grace period. The grace period implementation changed several times. In VE versions before version 4.1.21, the grace period was 24 hours. It was shortened to two hours after the introduction of the backup license server feature in 4.1.19. Since version 1.1.12, the grace period is determined by the corresponding license parameter. If a valid license has not become available before the end of the grace period, the emulator will be stopped.

Div
classpagebreak


Switch to backup license server:

Code Block
languagetext
2020-06-29 18:08:25 ERROR VE     Failed to Virtual hardware model Charon-SSP/4M is licensed.connect with the license server!
2020-0706-1629 2318:2608:0125 INFO  VE     Trying to Maximumlogin concurrentto instanceslicense are limited to 4.server: 127.0.0.1
2020-0706-1629 2318:2608:0134 INFOERROR  VE     Failed to Maximumconnect allowed virtual CPU(s) are 4.with the license server!
2020-0706-1629 2318:2608:0143 INFOWARN  VE     Charon will Maximumbe allowedterminated virtualizedwithin memory is 512 MB.2 hours!
2020-0706-1629 2319:2608:0157 INFO  VE     Connected with Major allowed version number is 4.license server: 172.31.40.62
2020-0706-1629 2319:2608:0157 INFO  VE     Found available license    Minor allowed version number is 2.
2020-07-16 23:26:01 INFOID: 01.00000001.002.045.


License Server version mismatch:

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   Expiration UTC time: 2020-12-31 15:55:00.
2020-07-16 23:26:01 INFO  data from license server!


Code Block
languagetext
2021-08-10 17:03:42 FATAL VE       LocalLicense UTCserver time: 2020-07-16 15:26:01.
2020-07-16 23:26:01 INFO is unavailable!


Newer versions have a more descriptive error message:

Code Block
languagetext
2021-08-10 17:16:41 ERROR VE       The license is verified, back to normal operation.

Please note: The output shows a 2 hour grace period. The grace period implementation changed several times. In VE versions before version 4.1.21, the grace period was 24 hours. It was shortened to two hours after the introduction of the backup license server feature in 4.1.19. Since version 1.1.12, the grace period is determined by the corresponding license parameter. If a valid license has not become available before the end of the grace period, the emulator will be stopped.

...

classpagebreak

Switch to backup license server:

Code Block
languagetext
2020-06-29 18:08:25 ERROR VE     Failed to connect with the license server!
2020-06-29 18:08:25 INFO  VE     Trying to login to license server: 127.0.0.1
2020-06-29 18:08:34 ERROR VE     Failed to connect with the license server!
2020-06-29 18:08:43 WARN  VE     Charon will be terminated within 2 hours!
2020-06-29 19:08:57 INFO  VE     Connected with license server: 172.31.40.62
2020-06-29 19:08:57 INFO  VE     Found available license ID: 01.00000001.002.045.

License Server version mismatch:

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:03:42 FATAL VE       License server is unavailable!

Newer versions have a more descriptive error message:

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

Charon-PAR Emulator Log Files

The default location for the Charon-PAR emulator log files is the directory in which the emulator was started. The name and location can be influenced via the configuration file and using a start-up parameter.

By default log file name is charon-par.<YYMMDD>-<timestamp>-<incremental number>.log.

The link charon-par.log points to the current log file.

Log File Samples

Working license found during emulator start:

Code Block
20211213:120216.970965:Trying to login to license server: 127.0.0.1
20211213:120219.975731:License allowed CPUs: 8.
20211213:120219.975746:License allowed memory size: 32768.
20211213:120219.979873:Connected with license server: 127.0.0.1
20211213:120219.979900:Found available license ID: 03.00000003.002.006.
20211213:120219.979908:Customer name: Stromasys
20211213:120219.979915:Grace period is 120 minutes.
20211213:120219.979928:Virtual hardware model Charon-PA9-64-L4 is licensed.
20211213:120219.979937:Maximum concurrent instances are limited to 10.
20211213:120219.979950:Maximum allowed virtual CPU(s) are 8.
20211213:120219.979959:Maximum allowed virtualized memory is 32768 MB.
20211213:120219.979967:Major allowed version number is 3.
20211213:120219.979976:Minor allowed version number is 0.
20211213:120219.979988:Expiration UTC time: 2022-06-08 23:55:00.
20211213:120219.980216:Product Name = Charon-PA9-64-L4 License key ID = 03.00000003.002.006.


License server not found at start:

Code Block
20211213:143042.636793:VE primary license 192.168.2.2
20211213:143042.637170:There is no VE backup server.
20211213:143042.646820:Trying to login to license server: 192.168.2.2
20211213:143051.649398:warn:Unable to login to server because error 100
20211213:143051.649580:err:Failed to connect with the license server.
20211213:143051.649618:err:Failed to connect with the license server.
20211213:143051.649669:err:Exit
20211213:143051.655735:err:Invalid license product name


Management GUI Web Server Log File

...