| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
| Note |
|---|
Important information for software upgrades: Upgrading to this Charon-PAR from an older version requires a license update. Please contact your VAR or Stromasys representative to plan the update. Charon-PAR version 2.0 and higher is incompatible with licenses of earlier versions. Earlier product versions are incompatible with licenses for Charon-PAR 2.0 and higher. Software licenses may have to be newly created from a fingerprint file during an upgrade from versions before Charon-PAR 1.10. Charon-PAR/PA3 licenses for version 2.1 are not backward compatible for emulators running with version 2.0. |
...
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 the product documentation for the details regarding the relevant parameters: license_retry_period and license_retry_count parameters (obsolete starting with version 1.10)
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):
...
Depending on customer requirements, Stromasys can provide several different license types.
Local Hardware License
...
Local hardware licenses are USB dongles and work on the system they are physically connected to. For Windows systems supporting AnywereUSB®, hardware licenses can also be connected over the network. They can easily be moved to a different system, if required. The content of the dongle can be updated if a change to the license or an extension of a time-based license is required. The necessary steps will be described later in this document.
Please note:
- Hardware dongles require the Sentinel HASP run-time (driver) installation before the dongle can be connected to and used by the system.
- Hardware dongles (with the exception of HL-MAX dongles) are equipped with a battery and a clock, which makes them independent of the host clock. To keep the battery charged, the dongle should occasionally be connected to a system even if it is not currently needed. If the battery becomes completely depleted, the dongle will be permanently unusable. See also: How long does the license USB dongle battery last upon a full charge.
Software License
...
A software license is a "virtual" key with functionality very similar to a HASP network-enabled hardware dongle.
A software license does not require any special hardware but it still requires installation of the Sentinel runtime environment.
Please note:
- To avoid unexpected problems, do not use any Sentinel runtime software that was not provided by Stromasys without being advised to do so by 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
...
- .
...
- Software licenses are very sensitive to even small changes on the host system. Therefore, it is especially important to provide for a backup license that will ensure continued operation should there be a problem with the software license. See Handling Multiple License Keys and Product Licenses for details.
For a more detailed description of the restrictions, please refer to Software Licensing restrictions or contact your Stromasys representative.
| Div | ||
|---|---|---|
| ||
Network License
...
The network Sentinel HASP key (red USB dongle) can be shared between several hosts running a Charon emulator product (including the host on which the network license is installed).
All software licenses are also network licenses.
If the Charon emulator product is installed on the host where the network license is connected, no additional steps are required. The Sentinel driver is installed as part of the Charon product installation. If the host does not have a Charon emulator product installed, the host can still distribute the connected network license to emulator instances running on other hosts.
The Sentinel HASP runtime software must be installed on such a "license server" and on the client system. For details regarding the installation, please refer to the software installation section in this document. Once both the Sentinel runtime software and the network license are installed, the Charon emulator product can be started on any appropriate client host on the LAN, provided access to the license is enabled.
- The network license will be visible to all hosts that can access the license server over IP. Access to the license server must be possible on port 1947 via UDP (discovery process) and TCP (actual access to license). Further information (e.g., use of additional UDP ports) can be found in the section Firewall Considerations.
- The license server and the client must both allow access to the network license using the appropriate management tools.
The maximum number of concurrently active Charon instances is determined by the parameters of the license.
If you need to install a standalone license server, please refer to the installation section of the Licensing Handbook.
...
- Display the default license: run the command without options or with
-l - Display all licenses: run the command with the option
-all - Display a license with a specific ID: run the command with the option
-key
Please note
...
: Local hardware licenses can only be displayed from a local connection to the system, for example via the console. If you are connected via a remote connection, for example via ssh, the hasp_srm_view command will return an error. Network licenses do not have this problem.
...
A workaround is described below.
Workaround when logged in via a remote connection:
When connected to the system via a remote connection, the command to display a local hardware license will return an error. As a workaround, you can display the license contents with the following command (adapt the path of the command if your installation location is different):
$ ssh localhost /opt/charon/bin/hasp_srm_view
Please note: Starting with Charon-PAR 1.10, the hasp_srm_view utility on Linux does not follow the settings in the Sentinel ACC with respect to querying remote license servers and network visibility. The utility performs
...
a broadcast search for network licenses even if this has been disabled in the Sentinel ACC. If this behavior has to be prevented for specific reasons, the network access of the system must be temporarily restricted or disabled, for example by blocking the relevant traffic with a firewall. Alternatively, access to the network license at the license server side can be blocked. Note that such methods can negatively impact other functions of the system or, in case of blocking access to a network license on the server, even the functions on other client host systems.
| Div | ||
|---|---|---|
| ||
The following shows sample output of the hasp_srm_view command on Linux (to display all available licenses, use the -all parameter):
...
# /opt/charon/bin/hasp_srm_view -fgp <filename.c2v> |
The fingerprint will be written to the filename specified.
Please note:
- Charon-PAR before 1.10: the above command will terminate with the error message "
Can not retrieve the C2V (host fingerprint mode) data"or with "Can not retrieve the C2V (host fingerprint mode) data"if a network-wide software license is visible to the system. Access to such a license needs to be temporarily disabled before creating the fingerprint file.
...
- Charon-PAR versions 1.10 and higher can create a fingerprint file even in the presence of a network-wide software license.
The fingerprint will be written to the filename specified.
Step 2: Send the resulting fingerprint file to Stromasys orders administration using the email address that Stromasys will provide to you.
...
# /opt/charon/bin/hasp_update u /path/filename.v2c |
...
This section describes the installation of a new software license. However, the commands to install a V2C file are identical when updating a hardware license.
Important caveat:
- When updating a hardware license you will in most cases receive two V2C files, a *_fmt.v2c file and a *.v2c file. The *_fmt.v2c file formats the dongle and the *.v2c file contains the updated license data. In such cases the *_fmt.v2c file must be applied first.
| Div | ||
|---|---|---|
| ||
Installing a Network License
...
The C2V file will be written to the filename specified.
Please note
...
: The license content cannot be read if you are connected to the system via a remote connection (e.g., via ssh). The hasp_srm_view command will return an error. You can use the following workaround:
$ ssh localhost /opt/charon/bin/hasp_srm_view -c2v <filename>
Step 2: Send the resulting C2V file to Stromasys orders administration using the email address that Stromasys will provide to you.
...
Step 3: After receiving the V2C file(s) from Stromasys, copy the file(s) to the system where the license needs to be installed and install the new license:
...
Important caveat:
- If a hardware USB key is to be updated, in most cases you will have received two files: a *_fmt.v2c file and a *.v2c file. The *_fmt.v2c file formats the dongle and the *.v2c file contains the updated license data. In such cases the *_fmt.v2c file must be applied first.
On Linux, the command hasp_update can be used to apply V2C files.
...