Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reviewed to match AXP&VAX

Anchor
TopLicPage
TopLicPage
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

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

Warning

The CHARON-VAX / CHARON-PDP software license is not distributed for Proof-of-Concept and evaluation installations. Only hardware dongles are used in this these cases.

It is important to connect the HASP license keys to the computer , powered on even if the CHARON VM is not running , because the because the keys contain a built-in accumulator battery that needs to be charged. If the accumulator battery is completely discharged, the license key can be irreparably damaged.

Update of the CHARON VM license can be performed on the fly without stopping the CHARON VM. All the parameters including the  The expiration date and time execution counter can be updated w/o any restrictions., however the CHARON VM virtual hardware configuration should remain unchanged. At the next license check, the CHARON VM will use the updated license normally.

The following sections list all the main parameters of the CHARON-VAX / CHARON-PDP licensing mechanism.

...

Regular Sentinel HASP keys

This is the most common way of CHARON-VAX / CHARON-PDP licensing. 

The CHARON-VAX / CHARON-PDP license PDP license is embedded in a Sentinel HASP dongle. This license is available only on the host where the dongle is physically installed.

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

Info

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


...

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

If CHARON-VAX / CHARON-PDP 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-VAX / CHARON-PDP installation. If the host does not have CHARON-VAX / CHARON-PDP installed, the host can still distribute the connected network license to CHARON VMs (s) to the CHARON virtual machines running on other hosts. In this case the Sentinel driver must be installed on the host manually.

...

Once the Sentinel run-time driver is installed and the network license is connected, the CHARON VM can be started on any appropriate host on the LAN network segment. A network

Info

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-VAX / CHARON-PDP Software License (SL) is a "virtual" key with exactly the same functionality as the hardware dongle. The CHARON-VAX / CHARON-PDP Software License It does not require any hardware but it requires the installation of the Sentinel run-time environment is required.

Note

The Software licenses Licenses (SL) 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), 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 Windows, 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, a CHARON VM can use only one valid ("active") license (of given vendor code) at a time.

The "HASP License details" utility (it can be started from CHARON Virtual Machines Manager) displays a range of available licenses , but note that, by default, a CHARON VM may use any of them as the "active" one - unless it is directly specified by the "license_key_id" parameter (see below). The utility provides the license numbers and ID / IP addresses of the hosts where the licenses are installed.

Warning

A CHARON VM cannot: 

  • check all the available license keys / software licenses,
  • choose one,
  • automatically switch from one key to another (except when the backup license is specified in its configuration file).

The general recommendation is to avoid the 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 VM hosts.

Div
classpagebreak


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

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 the CHARON VM.

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, the CHARON VM behaves differently:
 

  1. No keys are specified
    The CHARON VM behaves as usual (performs unqualified search for any suitable key). If no keys are found, the CHARON VM exitsstops.

  2. Both keys are specified
    The CHARON VM performs qualified search for regular license key. If it is not found, the CHARON VM performs qualified search for backup license key. If it is not found, the CHARON VM exitsstops.

  3. Only regular key is specified
    The CHARON VM performs qualified search for regular license key. If it is not found, the CHARON VM performs unqualified search for any suitable key. If it is not found, the CHARON VM exitsstops.

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

Status
colourRed
titleTO DO
the sentence below needs to be verified:

This parameter also specifies the license which will be used as backup if the active license expires.

...

Installation from scratch

Info

Before installation of installing the license make sure that the Sentinel run-time (driver) to be installed is collected from your CHARON kit or provided by STROMASYS on request for your particular product. Do not update the Sentinel run-time (driver) from online or any other sources, including the Sentinel web site.

In case of several CHARON kits containing different versions of Sentinel run-time (driver), the last one (, having more the most recent version) , must be installed. The CHARON installation performs this operation automatically.

...

Installation of a CHARON-VAX / CHARON-PDP regular or network licenses license consists of:
 

  1. Installation of the Sentinel run-time environment on the CHARON-VAX / CHARON-PDP host (regular and network keys) or on the host that will distribute CHARON-VAX / CHARON-PDP licenses over a local network segment (network key only). The Sentinel software is installed automatically by CHARON-VAX / CHARON-PDP for Windows.
  2. Physical connection of the HASP license dongle to the CHARON-VAX / CHARON-PDP host or to the host distributing the CHARON-VAX / CHARON-PDP license over the local network segment.
  3. Collecting the system fingerprint (*.c2v file), sending it to STROMASYS and applying the update (*.v2c file) in case of software license (and in case of updating HASP dongle license). See the details below.

When a manual installation of the Sentinel run-time is required (in the case of the network license server that does not have CHARON-VAX / CHARON-PDP installed):

  1. Login as Administrator
  2. Open the CHARON-VAX / CHARON-PDP kit folder
  3. Switch to the "hasp_install" subfolder
  4. Unzip the archive located in this folder
  5. Open "cmd.exe" and switch to the folder where the files were unzipped
  6. Execute the following commands:

    ...> haspdinst.exe -fr -kp -nomsg
    ...> haspdinst.exe -install -cm



    Info

    Note that the following operations have to be performed on installation phase for network licenses:

    • 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 Windows 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 "Sentinel HASP License Manager" (hasplms.exe) service (it will be installed by CHARON-VAX / CHARON-PDP).

Replacement of currently installed Sentinel run-time

Replacement of the currently installed Sentinel Run-time can be needed in case of installation of specific run-time provided by STROMASYS.

Below please find step-by-step instructions on the run-time replacement:

Remove To proceed, remove the current version of Sentinel run-time:

  • Login as Administrator

  • Extract the content of the unique ZIP file residing in “hasp_install” directory of the CHARON distribution to the same folder.

  • Run “cmd.exe” from the “Start” menu of host computer

  • “cd” to the “hasp_install” directory

  • Issue the following command:

    ...> haspdinst.exe -fr -kp -nomsg

    .

Install the other Sentinel run-time:

  • “cd” to the directory where the target run-time resides
  • Issue the following command:

    ...> haspdinst.exe -fr -kp -nomsg

    .


Info

You do not need to perform this procedure for Sentinel HL keys - local and network ones (red dongle) used as local.


Back to Table of Contents

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

Status
colourYellow
titleBM Marker

The CHARON-VAX / CHARON-PDP software licenses can be installed / updated according to the procedure described below. This procedure is also applicable for an update of a license located on HL/HASP dongle.

...

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.

...

Removing CHARON-VAX / CHARON-PDP software licenses

The following procedure must be applied to remove the software license:


  1. Open the CHARON Virtual Machines Manager, switch to the "Host Information & Utilities" tab and press the "Sentinel Admin Control Center" button:
    Status
    colourRed
    titleTO DO
    missing screenshot here (see AXP guide)
    or - alternatively - start any web browser on this system and go to the http://localhost:1947 page.
  2. In the "Sentinel HASP Admin Control Center" (ACC), select the "Sentinel Keys" option in the left pane and 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 corresponding certificate file in the "C:\Program Files\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704" folder.  In the example above the file to remove is "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel LDK\installed\68704\387285561437702475_base.v2c".

  6. Reboot the CHARON host.

  7. Start the "Sentinel HASP Admin Control Center" (ACC) again to ensure the SL has been removed.
Div
classpagebreak


License Deinstallation

...