Versions Compared

Old Version 18

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update for PDF export

Anchor
TopLicPageTOCTopLicPage
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Table of Contents

Table of Contents
excludeTable of Contents

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 HP Alpha emulators allowed to run.

...

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 a given period of time (the check interval), CHARONwithin 12 hours, CHARON-AXP exits. For more, see Emulator Behavior chapter.

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.

Warning

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.

It is important to connect the HASP license keys to the computer from time to time even if CHARON-AXP is not used. The keys contain a built-in accumulator that needs to be charged. If the accumulator is completely discharged, a the license key can be fatally damaged.

...

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

...

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

Div
classpagebreak


Parameters defined by CHARON-AXP license

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

GeneralProducts relevantOptional

  • 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

...

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

Div
classpagebreak


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

Info

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

Div
classpagebreak



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.

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

In special cases, a software license can also be bound to the fully qualified domain name (FQDN) of the host system. If this name changes, the license will be disabled.

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

Software licenses are

...

  • If the CHARON host runs on real hardware, 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), 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.

In special cases, a software license can also be bound to the fully qualified domain name (FQDN) of the host system. If this name changes, the license will be disabled.

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

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

Back to Table of Contents

Multiple licenses configuration and backup license

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, but it is able to display all available licenses with "-all" parameter. It is also possible to check some specific license by its number using "-key" parameter.

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

Warning

CHARON-AXP cannot: check all the available license keys / software licenses, choose one, automatically switch from one key to another, etc.

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.

...

classpagebreak

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:

...

A number (decimal Sentinel key ID) that specifies regular (N=0) and backup (N=1) license keys to be used by CHARON-AXP.

Example:

set session license_key_id[0]=1877752571
set session license_key_id[1]=354850588

It is also possible to specify both regular and backup key in one line.

Example:

set session license_key_id[0]=1877752571 license_key_id[1]=354850588

Depending on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-AXP behaves differently:

  1. No keys are specified
    CHARON-AXP behaves as usual (performs unqualified search for any suitable key). If no keys are found, CHARON-AXP exits.

  2. Both keys are specified
    CHARON-AXP performs qualified search for regular license key. If it is not found, CHARON-AXP performs qualified search for backup license key. If it is not found, CHARON-AXP exits.

  3. Only regular key is specified
    CHARON-AXP performs qualified search for regular license key. If it is not found, CHARON-AXP performs unqualified search for any suitable key. If it is not found, CHARON-AXP exits.

  4. Only backup key is specified
    CHARON-AXP behaves as usual (performs unqualified search for any suitable key). If no keys are found, CHARON-AXP exits.

Back to Table of Contents

License installation

Installation of Regular and Network license keys

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

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

  2. 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:

...

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

...

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

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

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

TypeText 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:
 

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

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

Note

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.



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

Div
classpagebreak


License installation

Installation of Regular and Network license keys

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


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

  2. 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 -ihv aksusbd-7.63-1.i386.rpm charon-license-4.10-20200.el74.x86_64.rpm


div
Info

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.

classpagebreak

Info

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

Back to Table of Contents

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

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
Back to Table of Contents


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


Div
classpagebreak



Installation and update of CHARON-AXP Software License or HL/HASP dongle License

CHARON-AXP software licenses Software Licenses (SL) can be installed / updated according to the procedure described below. This procedure is also applicable for update of a license in case of HL/HASP dongles.

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

  • 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

  • In case of Software License installation and if there are already installed network-wide SL's in local network disable access to network licenses in the following way:
    • Go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
    • Select "Configuration" option at the left panel, then "Access to Remote License Managers" tab.
    • Uncheck the highlighted options:
      Image Removed
    • Press the "Submit" button to apply settings
    • Select "Network" tab.
    • Switch "Network visibility" to "None":
      Image Removed
    • Press the "Submit" button to apply setting.
    • Do not forget to return these settings back after SL installation.
  • Connect HASP dongle to host system (in case of update of a license in a dongle)

  • Collect CHARON-AXP host fingerprint file (".c2v") - in case of first installation of Software License:

    # hasp_srm_view -fgp my_host.c2v

    or collect ".c2v" file in case if already installed Software License or 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.

    Info

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

    Info

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

    Info

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

  • On server side (where network license will reside): open port 1947 for both TCP and UDP
    • 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.


    Info

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


    Info

    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.


    Info

    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.

    Back to Table of Contents

    Div

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

    Div
    classpagebreak


    License management

     

    CHARON-AXP license management is performed by the Sentinel Admin Control Center and specific utilities.

    These

    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 go to open the http://localhost:1947  page.

    Info

    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, enter open the http://localhost:1947 and press Enter. Web page. The web interface of the Sentinel Admin Control Center will appear.

     The screenshot below gives an example of its interface:

    Image RemovedImage Added

    This example demonstrates that 4 license keys are available:

    1. Network A network key ("HASP-HL NetTime") on the host "XEON4WAYW7"

    2. Network A network key installed locally

    3. An HASP-HL installed locally

    4. NetworkA network-wide software license on the host "RH64"


    The Sentinel Admin Control Center reports that there is one opened session on key (4)#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.

    Back to Table of Contents
    Disable remote keys access 
    Include Page
    KBCOMMON:DOC-GoToToc
    KBCOMMON:DOC-GoToToc

    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 and , uncheck the "Allow Access to Remote Licenses" checkbox . Then and press the "Submit" button to apply this setting:

    Image RemovedImage Added

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

    Image Removed

    Back to Table of Contents

    Image Added

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

    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.The first step is to edit the :

    Image Added

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

    # vivi /etc/hasplm/hasplm.ini

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

    Div
    classpagebreak


    Allow remote access by changing the "ACCremote" parameter from "0" to "1"

    .Then restart Sentinel Admin Control Center run-time:
    # systemctl restart aksusbd
    If the CHARON-

    , 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 (put

    command (replace "CHARON_MACHINE" by the real CHARON-

    AXP

    VAX host name

    instead of "CHARON_MACHINE"

    ):


    # ssh # ssh -L8080:CHARON_MACHINE:1947 root@CHARON_MACHINE
    This will expose the Sentinel Admin Control Center on port 8080 to any computer, and Sentinel Admin Control Center it will believe commands are coming from the local host.
    Back to Table of Contents
    Include Page
    KBCOMMON:DOC-GoToToc
    KBCOMMON:DOC-GoToToc

    License management utilities

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


    Info

    Applying updates (".v2c" files) is typically done using the Sentinel Admin Control Center (see above) , but alternatively it is also possible to use a the specific "hasp_update" utility for that.

    Please refer to the Utilities section of this Guide for more details.
    Back to Table of Contents
    Include Page
    KBCOMMON:DOC-GoToToc
    KBCOMMON:DOC-GoToToc

    Removing CHARON-AXP software licenses

    • 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.
    • Backup license may be valid only until a certain date. Please check with STROMASYS management.
    Back to Table of Contents

    The following procedure must be applied to remove software license:
     

    1. Go to Using your web browser, open the http://localhost:1947 to page to access the "Sentinel HASP Admin Control Center" (ACC).
    2. In the "Sentinel HASP Admin Control Center" (ACC), locate the target "Sentinel SL AdminMode" license.
    3. Press the "Certificates" button at the right side of the SL description: 
      Image Modified 
    4. Note the name of the correspondent corresponding certificate and path to the certificates base in the "Certificates" section.
    5. Remove the target certificate file from the specified directory (, in most cases it is : "/var/hasplm/installed/68704/").
    6. Reboot CHARON host.
    7. Start "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.
    Back to Table of Contents
    Div
    classpagebreak

    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).
    Back to Table of Contents

    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:

    1. /".
    2. Restart the aksusbd service (# systemctl restart aksusbd or # service aksusbd restart) or reboot the CHARON host.
    3. Start the "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.
    Include Page
    KBCOMMON:DOC-GoToToc
    KBCOMMON:DOC-GoToToc

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


    Div
    classpagebreak



    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
    Include Page
    KBCOMMON:DOC-GoToToc
    KBCOMMON:DOC-GoToToc