Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Table of Contents

General description

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 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 a given period of time (the check interval), CHARON-AXP exits.

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.

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 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 license key can be fatally damaged.

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.

Back to Table of Contents

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

Back to Table of Contents

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

CHARON-AXP/VAX version 4.7 build 171-01 introduced a change with respect to network licenses:

In previous versions of CHARON-AXP/VAX a network license controlled the maximum number of client host systems and CHARON instances per host system (station/instance mode).

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 installation of the Sentinel run-time environment.

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

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.


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:

ParameterTypeValue
license_key_id[N], N=0 or 1Numeric

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:

# rpm --nodeps -ihv aksusbd-2.5-1.i386.rpm charon-license-4.8-18302.el71.x86_64.rpm

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

  • On server side (where 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"

Back to Table of Contents


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

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

CHARON-AXP software licenses 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.

  • Install CHARON-AXP together with Sentinel run-time (Sentinel run-time is an essential part of CHARON-AXP for Linux distribution)

  • Reboot 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:
    • Press the "Submit" button to apply settings
    • Select "Network" tab.
    • Switch "Network visibility" to "None":
    • 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.


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

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

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


License management 

CHARON-AXP license management is performed by the Sentinel Admin Control Center and specific utilities. These 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 http://localhost:1947 

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

To access Sentinel Admin Control Center start any web browser, enter http://localhost:1947 and press Enter. Web interface of the Sentinel Admin Control Center will appear.

 The screenshot below gives an example of its interface:

This example demonstrates that 4 license keys are available:

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

  2. Network key installed locally

  3. HASP-HL installed locally

  4. Network-wide software license on the host "RH64"


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 Sentinel Admin Control Center it is possible to check available keys, verify hosts on which they reside, verify opened sessions etc. For a more detailed description of Sentinel Admin Control Center, please refer to its "Help" section.

Back to Table of Contents

Disable remote keys access 

A helpful feature of 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 press "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 and uncheck the "Allow Access from Remote Clients" checkbox. Then press "Submit" button to apply this setting:

Back to Table of Contents

Accessing Sentinel Admin Control Center from remote hosts

By default, Sentinel Admin Control Center forbids accessing its web interface from remote machines. To allow access, configure ACC for remote management.

The first step is to edit the "hasplm.ini" file:

# vi /etc/hasplm/hasplm.ini


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-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 Linux documentation for details on how to configure the firewall. It is also possible to use SSH port forwarding with the following command (put the real CHARON-AXP host name instead of "CHARON_MACHINE"):
# ssh -L8080:CHARON_MACHINE:1947 root@CHARON_MACHINE
This will expose Sentinel Admin Control Center on port 8080 to any computer, and Sentinel Admin Control Center will believe commands are coming from the local host.
Back to Table of Contents

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 license(-s) content, and to collect key status information and host fingerprint (C2V) files.


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

Please refer to the Utilities section of this Guide for more details.
Back to Table of Contents

Removing CHARON-AXP software licenses

The following procedure must be applied to remove software license:
 

  1. Go to http://localhost:1947 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: 
     
  4. Note the name of the correspondent 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



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:

  • 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
  • No labels


© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.