| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Table of Contents
| Table 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. Note that 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.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Parameters defined by CHARON-AXP license
The following table represents all the parameters defined by CHARON-AXP license:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
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.
| 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 "471924900License 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 | ||
|---|---|---|
| ||
Software licenses
The CHARON-AXP Software License is a "virtual" key with exactly the same functionality as the hardware dongle.
...
| Include Page | ||||
|---|---|---|---|---|
|
Multiple licenses configuration
For any type of licensing, CHARON-AXP can use only one valid ("active") license (of given vendor code) at a time.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
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:
|
| Info | |
|---|---|
In case of network-wide license (red dongle) do the following:
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. | |
| Div | |
| class | pagebreak
| Info |
|---|
Some additional packages may be needed in certain cases, for example "glibc.i686" |
| Include Page | ||||
|---|---|---|---|---|
|
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
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
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Installation and update of CHARON-AXP Software License or HL/HASP dongle 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.c2vor 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.c2vSend 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, "" for the "*.v2c" file and then "".
Ensure that the license appears in the “” 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:
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. |
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
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.
...
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.
| Include Page | ||||
|---|---|---|---|---|
|
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:
| Include Page | ||||
|---|---|---|---|---|
|
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 :
In this cannot be done using the WEB interface, edit the "hasplm.ini" file:
|
In the file does not exist, please refer to this article: How-to enable remote connection to Sentinel Admin Control Center without GUI
| Div | ||
|---|---|---|
| ||
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:
# |
(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 # ssh -L8080:CHARON_MACHINE:1947 root@CHARON_MACHINE |
| Include Page | ||||
|---|---|---|---|---|
|
License management utilities
| Info |
|---|
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. |
| Include Page | ||||
|---|---|---|---|---|
|
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/". - Reboot Restart the aksusbd service (
# systemctl restart aksusbdor# 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.
| Include Page | ||||
|---|---|---|---|---|
|
License
Deinstallationdeinstallation
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-<...> |
| Div | ||
|---|---|---|
| ||
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 | ||||
|---|---|---|---|---|
|