General description

The CHARON-AXP products are protected by licenses, issued by STROMASYS for each customer individually. The CHARON-AXP license defines a set of Alpha emulators allowed to run.

The license is implemented in the form of a hardware dongle (a Sentinel HASP key) or a software license bound to the hardware. Please be careful with your license key. In case of loss or damage, CHARON-AXP will not run or start unless the license key is replaced. For extra protection, STROMASYS recommends the use of a backup license key (purchased separately) that can replace the main license key for a restricted period of time. It is possible to specify the backup license in the CHARON-AXP configuration file to prevent CHARON-AXP from stopping in case its main license is no longer accessible.

The CHARON-AXP license is read upon the start of each instance of CHARON-AXP and at a specified interval (defined by the license content) during the emulated system execution. If CHARON-AXP detects the absence (or malfunction) of the license key / software license, CHARON will try to use a backup license (if specified in the configuration file). If the license is not available / not specified, CHARON displays a warning message in the log file requesting license key reconnection or software license reactivation. If the license is not reconnected within 12 hours, CHARON-AXP exits. For more, see the Emulator Behavior chapter further down on this page.

Note that if the time-restricted license is used and it expires, CHARON-AXP tries to find its replacement automatically and, if found, CHARON-AXP proceeds using the replacement license.

Please note:

The CHARON-AXP software license is not distributed in case of Proof-of-Concept and evaluation installations. Only hardware dongles are used in this case.
Hardware dongles, apart from HL-MAX dongles, are equipped with a battery and a clock, which makes them independent of the host clock. The battery is not rechargeable. However, the dongle can use the power provided by the host system while it is plugged in. By doing this, the depletion of the battery can be slowed down. Check the dongle at regular intervals if it is not permanently connected to a system. If the battery becomes completely depleted, the dongle will be permanently unusable and must be replaced. See also: How long does the license USB dongle battery last upon a full charge.

Update of the CHARON-AXP license can be performed on the fly without stopping CHARON-AXP. At the next license check, CHARON-AXP will use the updated license normally.

The following sections list all the main parameters of the CHARON-AXP licensing mechanism.

Parameters defined by CHARON-AXP license

The following table represents all the parameters defined by CHARON-AXP license:

General	Products relevant	Optional
Physical key ID License Number End user name Master key ID License release date and time Update Number Purchasing Company name. In most cases the company to which the key was issued originally	Commercial product name Commercial product code Commercial product version and range of build numbers suitable for running Range of CHARON-AXP virtual models available for running Type of host CPU required Host operating system required Number of virtual CPUs enabled for virtual SMP systems Minimum number of host CPU cores required Minimum host memory required Maximum memory emulated. If not present the value defaults to the maximum memory possible for the particular virtual system. Note that the maximum memory may not be available to the virtual system if the host computer has insufficient physical memory. Maximum number of CHARON-AXP instances that can be run concurrently Whether or not CHAPI (CHARON-AXP API) can be used with this product Product and Field Test expiration dates (if any) Product and Field Test executions counter (if any) Maximum number of hosts that may run CHARON-AXP concurrently (in the case of a networking license) Level of support (if any), end date of any support contract, the "First Line" Service Provider Frequency of CHARON-AXP license checking during CHARON-AXP execution	Parameter that reduces the maximum speed of the program Parameter that prohibits use of Advanced CPU Emulation. If not present the Advanced CPU Emulation is enabled

CHARON-AXP licensing models

CHARON-AXP licensing models are divided in 3 groups:

Regular Sentinel HASP keys

This is most common way of CHARON-AXP licensing, the CHARON-AXP license is embedded in a Sentinel HASP dongle. This license is available only on the host where the dongle is physically installed.

The CHARON-AXP installation procedure takes care of the Sentinel HASP run-time (driver) installation. Once the CHARON-AXP product has been installed, it is possible to plug-in the regular license key and proceed with CHARON-AXP usage without additional configuration steps.

The number of CHARON-AXP instances allowed to run on a particular host may be restricted by the license content (see above).

Network Sentinel HASP keys

The Network Sentinel HASP key (red dongle) can be shared between several hosts running CHARON-AXP including the host on which the network license is installed.

If CHARON-AXP is installed on the host where the network key is connected, no additional steps are required. The Sentinel driver is activated as part of the CHARON-AXP installation. If the host does not have CHARON-AXP installed, the host can still distribute the connected network license to CHARON-AXP instances running on other hosts. In this case the Sentinel driver must be installed on the host manually.

The Sentinel run-time driver is distributed as a separate RPM package in the CHARON-AXP kit. Please see the "CHARON-AXP for Linux HASP licensing#License installation" section of this chapter for details.

Once the Sentinel run-time driver is installed and the network license is connected, CHARON-AXP can be started on any appropriate host on the LAN network segment. In the current CHARON-AXP/VAX versions, a network license controls the maximum overall number of active instances, which can be distributed across client host systems according to the preference of the customer.

Software licenses

The CHARON-AXP Software License is a "virtual" key with exactly the same functionality as the hardware dongle.

The CHARON-AXP Software license does not require any hardware but it requires the installation of the Sentinel run-time environment.

Please note:

Software licenses are best suited for stable environments, because their correct function depends on certain characteristics of the host system. Changing any of these characteristics will invalidate the license.

If the CHARON host runs on real hardware, the software licenses are by default tightly bound to the hardware for which they were issued. If major hardware characteristics of the system are changed, the license will be disabled.
If the CHARON host runs in a virtual environment (e.g. VMware), the software licenses are normally bound to the virtual machine ID and a set of additional characteristics of the virtual machine. If any of these parameters are changed, the license will be disabled.

For a more detailed description of the restrictions, please refer to the Software Licensing restrictions article or contact your Stromasys representative.

Software licenses are always network-wide on Linux so they behave the same way as Network HASP keys.

Multiple licenses configuration

For any type of licensing, CHARON-AXP can use only one valid ("active") license (of given vendor code) at a time.

The "hasp_srm_view" utility displays the "active" license by default and is able to display all available licenses with the "-all" parameter. It is also possible to check some specific license by its number using the "-key" parameter.

The utility provides the license number and ID / IP address of the host where the active license is installed.

The general recommendation is to avoid usage of multiple keys in one network segment. Use only one locally installed license per host or one network license per local network segment containing several CHARON-AXP hosts.

When needed, it is possible to use a special parameter in the CHARON-AXP configuration file to specify exactly which license must be used by each particular instance of CHARON-AXP:

Parameter	license_key_id
Type	Text string
Value	A set of Sentinel Key IDs that specifies the license keys to be used by CHARON. It is also possibly to use a keyword "any" to force CHARON to look for a suitable license in all available keys if the license is not found in the specified keys. Example: `set session license_key_id = "1877752571,354850588,any"` Based on the presence of this parameter in the configuration file, CHARON behaves as follows: No keys are specified (the parameter is absent) CHARON performs an unqualified search for any suitable key in unspecified order. If no key is found, CHARON exits. One or many keys are specified CHARON performs a qualified search for a regular license key in the specified order. If it is not found, CHARON exits (if the keyword "any" is not set). If the keyword "any" is specified then if no valid license has been found in the keys with specified ID’s all other available keys are examined for valid license as well. The order in which keys are specified is very important. If a valid license was found in the key which ID was not the first one specified in configuration file, then available keys are periodically re-scanned and if the key with the ID earlier in the list than the current one is found CHARON tries to find a valid license there and in case of success switches to that key.

License installation

Installation of Regular and Network license keys

Installation of CHARON-AXP regular and network licenses consists of:

Installation of the Sentinel run-time environment on the CHARON-AXP host (regular and network keys) or on the host that will distribute CHARON-AXP licenses over a local network segment (network key only). The Sentinel software (the “aksusbd” RPM package) is installed automatically by CHARON-AXP for Linux.
Physical connection of the HASP license dongle to the CHARON-AXP host or to the host distributing the CHARON-AXP license over the local network segment.

When manual installation of Sentinel run-time is required (in the case of the network license server that does not have CHARON-AXP installed), open the CHARON-AXP kit folder and proceed the following way:

# rpm--nodeps-ihvaksusbd-7.63-1.i386.rpm charon-license-4.10-20200.el74.x86_64.rpm

In case of network-wide license (red dongle) do the following:

On the server side (where the network license will reside): open port 1947 for both TCP and UDP
On the client side, if broadcast search for remote licenses is to be used, UDP traffic from port 1947 of the license server to ports 30000-65535 of the client must be permitted.
Both on server and client sides: setup default gateway

Please consult with your Linux User's Guide on details.

If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "/usr/sbin/hasplmd" daemon.

Some additional packages may be needed in certain cases, for example "glibc.i686"

Replacement of currently installed Sentinel run-time

Replacement of currently installed Sentinel Run-time may be needed in case of:

Upgrade to a newer version of CHARON-AXP
Installation of a specific CHARON-AXP license Run-time provided by STROMASYS

Run-time replacement is a two step process:

Remove the current run-time (and the package "charon-license-<...>.rpm" containing the run-time customization) with the command
# rpm --nodeps -e aksusbd charon-license-<...>
Change to the directory where the new run-time RPM resides (along with the corresponding "charon-license-<...>.rpm" customization package) and issue the command:
# rpm --nodeps -ihv aksusbd<…>.rpm charon-license-<...>.rpm

Installation and update of CHARON-AXP Software or Hardware License

CHARON-AXP Software Licenses (SL) can be installed / updated according to the procedure described below.

Install CHARON-AXP together with Sentinel run-time (Sentinel run-time is an essential part of CHARON-AXP for Linux distribution)
Reboot the host system
Connect the HASP dongle to the host system (in case of update of a license in a dongle)
Collect the CHARON-AXP host fingerprint file (".c2v") - in case of first installation of a Software License:
# hasp_srm_view -fgp my_host.c2v
or collect the ".c2v" file in case a Software License is already installed or the connected HL/HASP dongle needs updating:
# hasp_srm_view -c2v current_license.c2v
Send the ".c2v" file ("my_host.c2v" / "current_license.c2v" in the examples above) to STROMASYS
Receive a ".v2c" file in return and put it somewhere on the CHARON-AXP host.
Start any web browser on this system and go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC) or configure ACC for remote access (see the details below).
In ACC, under the Options menu, select Update/Attach, "Browse" for the "*.v2c" file and then "Apply File".
Ensure that the license appears in the “Sentinel Keys” menu.

Alternatively it is also possible to use "hasp_update" command line utility for applying the ".v2c" file.

The content of the installed software license is not shown by the Sentinel HASP Admin Control Center. To see it please run the "hasp_srm_view" utility from the local console or configure remote access according to the instructions given in the "hasp_srm_view" utility section.

In case of network-wide software license do the following:

On the server side (where the network license will reside): open port 1947 for both TCP and UDP
On the client side, if broadcast search for remote licenses is to be used, UDP traffic from port 1947 of the license server to ports 30000-65535 of the client must be permitted.
Both on server and client sides: setup default gateway

Please consult with your Linux User's Guide on details.

If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "/usr/sbin/hasplmd" daemon.

License management

CHARON-AXP license management is performed by the Sentinel Admin Control Center and specific utilities. They are described in the sub-sections below.

Sentinel Admin Control Center

General Description

The Sentinel Admin Control Center (ACC) is the web-interface to the Sentinel run-time environment. It allows viewing/managing available keys, enabling and disabling them, controlling usage of remote keys etc.

To access the ACC, start any web browser and open the http://localhost:1947 page.

The Sentinel Admin Control Center is not able to display CHARON-AXP licenses - to view key contents, use the "hasp_srm_view" utility.

To access the Sentinel Admin Control Center start any web browser, open the http://localhost:1947 page. The web interface of the Sentinel Admin Control Center will appear.

The screenshot below gives an example:

This example demonstrates that 4 license keys are available:

A network key ("HASP-HL NetTime") on the host "XEON4WAYW7"
A network key installed locally
An HASP-HL installed locally
A network-wide software license on the host "RH64"

The Sentinel Admin Control Center reports that there is one opened session on key #4. The other keys are not being used at the moment.

Using the Sentinel Admin Control Center it is possible to check the available keys, verify the hosts on which they reside, verify the opened sessions, etc. For a more detailed description of the Sentinel Admin Control Center, please refer to its "Help" section.

Disable remote keys access

A helpful feature of the Sentinel Admin Control Center is the ability to disable access to remote keys. If the network key is installed locally, access to the key from remote hosts can be disabled. The following examples demonstrate how this can be done.

To disable access to remote keys, switch to the "Access to Remote License managers" tab, uncheck the "Allow Access to Remote Licenses" checkbox and press the "Submit" button to apply this setting:

To disable access to the locally installed license key from remote hosts, switch to the "Access from Remote Clients" tab, uncheck the "Allow Access from Remote Clients" checkbox and press the "Submit" button to apply this setting:

Accessing Sentinel Admin Control Center from remote hosts

By default, the Sentinel Admin Control Center forbids accessing its web interface from remote machines.

To allow access, configure the ACC for remote management:

In this cannot be done using the WEB interface, edit the "hasplm.ini" file:

# vi /etc/hasplm/hasplm.ini

If the file does not exist, please refer to this article: How-to enable remote connection to Sentinel Admin Control Center without GUI

Allow remote access by changing the "ACCremote" parameter from "0" to "1", make sure the parameter "bind_local_only" is set to 0 (the value 1 means localhost-only) then restart the Sentinel Admin Control Center run-time:

# systemctl restart aksusbd

(or for RHEL 6.x: # service aksusbd restart)

If the CHARON-AXP host firewall is blocking remote access to the Sentinel Admin Control Center, please configure the firewall to open the port 1947 (TCP protocol). Refer to the Linux documentation for details on how to configure the firewall. It is also possible to use SSH port forwarding with the following command (replace "CHARON_MACHINE" by the real CHARON-VAX host name):

# ssh -L8080:CHARON_MACHINE:1947 root@CHARON_MACHINE

This will expose the Sentinel Admin Control Center on port 8080 to any computer, and it will believe commands are coming from the local host.

License management utilities

CHARON-AXP for Linux provides a specific utility for license management - "hasp_srm_view".This utility is used to display the license(-s) content, to collect the key(s) status information and host fingerprint (C2V) files.

Applying updates (".v2c" files) is typically done using the Sentinel Admin Control Center (see above) but alternatively it is also possible to use the specific "hasp_update" utility. Please refer to the Utilities section of this Guide for more details.

Removing CHARON-AXP software licenses

The following procedure must be applied to remove software license:

Using your web browser, open the http://localhost:1947 page to access the "Sentinel HASP Admin Control Center" (ACC).
In the "Sentinel HASP Admin Control Center" (ACC), locate the target "Sentinel SL AdminMode" license.
Press the "Certificates" button at the right side of the SL description:
Note the name of the corresponding certificate and path to the certificates base in the "Certificates" section.
Remove the target certificate file from the specified directory, in most cases: "/var/hasplm/installed/68704/".
Restart the aksusbd service (# systemctl restart aksusbd or # service aksusbd restart) or reboot the CHARON host.
Start the "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.

License deinstallation

To completely remove a CHARON-AXP license from a host, it is enough to remove the Sentinel run-time daemon (and the package "charon-license-<...>.rpm" containing the run-time customization)using the following command:

# rpm --nodeps -e aksusbd charon-license-<...>

Then just physically disconnect the license key (in the case of protection by dongles).

Special "backup" license keys

Backup keys are provided by STROMASYS along with standard license dongles. It is strongly recommended to order a backup key to recover immediately from damage or loss of the main license key. Backup keys use a counter (integer) value hardcoded inside the key. This integer value is a number of hours CHARON-AXP is allowed to run. Each time CHARON-AXP checks the license (every hour), the value is decreased (by 1 hour). Please note that backup keys have restricted functionality:

CHARON run time is typically limited to 720 hours (30 days). This should be more than enough time to get a replacement key from STROMASYS.
A backup license may be valid only until a certain date. Please check with STROMASYS management.

Emulator Behavior

Charon products check the availability of a valid license under several conditions:

1. At startup:

If no valid license is found, an error message will be written to the emulator log file and the emulator will not start.
In some emulator products it is possible to configure the number of retries and the waiting time between them by adding parameters to the emulator configuration file. Please refer to chapter General Settings/license_key_lookup_retry the details.

2. At regular intervals during the runtime of the emulator (the default license check period of 1 hour can be changed by Stromasys using the appropriate license parameters):

If the previously used valid license has been removed, has disappeared, is defect, or has become invalid, the emulator will report the loss of the license in the log file and continue operation for a limited amount of time as described below.
If there is another valid license, for example a backup license defined in the configuration file, it will be used.
Charon allows for a grace period of 12 hours during which the software checks for the presence of a valid license every 10 minutes until a valid license is found. If no valid license is found after the grace period has expired, the emulator will stop.
If a time-restricted license is used and it expires, the Charon instance tries to find its replacement automatically and, if found, proceeds using the replacement license

Table of Contents

Browser not supported