Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Layout reviewed for PDF export bugs

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

...

Regular Sentinel HASP keys

This is most common way of CHARON-VAX licensing. 

The CHARON-VAX 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 installation procedure takes care of the Sentinel HASP run-time (driver) installation. Once the CHARON-VAX product has been installed, it is possible to plug-in the regular license key and proceed with CHARON-VAX usage without additional configuration steps.

Info

The number of CHARON-VAX 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-VAX (including the host on which the network license is installed).

If CHARON-VAX 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 installation. If the host does not have CHARON-VAX installed, the host can still distribute the connected network license to CHARON-VAX 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-VAX 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-VAX can be started on any appropriate host on the LAN network segment.

Info

The Network license key contains a specific parameter to restrict the number of hosts allowed to run CHARON-VAX at the same time. Together with a parameter defining the number of CHARON-VAX instances that may run at the same time, the network license sets the total number of running CHARON-VAX instances on the allowed number of hosts.

 

Software licenses

The CHARON-VAX Software License is a "virtual" key with exactly the same functionality as the hardware dongle.

...

The screenshot below gives an example of its interface:

Image Modified

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.

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:

Image Modified

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:

Image Modified

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:
# /etc/init.d/aksusbd restart
If the CHARON-VAX 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-VAX 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.

License management utilities

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

 

Info

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.

Transferring and removing CHARON-VAX software licenses

Software Licenses Transfer 

Software Licenses (SL) can be transferred from one host to another using the "hasp_srm_view" utility and "Sentinel Admin Control Center" (ACC).

The following example demonstrates the transfer procedure.Let's suppose a Software License must be transferred from a host "SourceHost" to a host "RecipientHost":
  1. Collect the specific information about the "RecipientHost" to issue a transfer license. To do that run "hasp_srm_view" utility on the "RecipientHost" with the following parameters:

    $ hasp_srm_view -idf

    The file "recipient.id" will be created in the current directory.

  2. Copy the "recipient.id" file to the "SourceHost".

    Info
    "recipient.id" file is an ASCII file, so use "ascii" option in case of FTP transfer.

      

  3. On "SourceHost", open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Note the number of the software license you are going to transfer.

  4. Run the "hasp_srm_view" utility in the following way to create a transfer license for the host "RecipientHost":

    $ hasp_srm_view -tfr <license number> recipient.id

    The "license number" is the value collected at step 3.Example of collecting a transfer license:

    $ hasp_srm_view -tfr 12345678 recipient.id

    The file "<license number>.v2c" will then be created in the current directory. In the example above the name of the transfer license will be "12345678.v2c"

  5. Copy the resulting "<license number>.v2c" file to the "RecipientHost".

    Info
    "<license number>.v2c" file is an ASCII file, so use "ascii" option in case of FTP transfer.
  6. On "RecipientHost", open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Apply the "<license number>.v2c" file as described above

Software License Removal

It is also possible to remove Software License completely from a host, the license will then be dumped to a specific license file "*.v2c", so it can be re-applied if needed.

To remove the Software License completely from a host, do the following::
  1. Open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Note the number of the software license you are going to remove.
  2. Run the "hasp_srm_view" utility in the following way to remove the license:

    $ hasp_srm_view -tfr <license number>

    The "license number" is the value collected at the step 1.Example:

    $ hasp_srm_view -tfr 12345678

    The "<license number>.v2c" file will then be created in the current directory. In the example above the name of the transfer license will be "12345678.v2c"

  3. It is always possible to re-apply the created ".v2c" file to restore the deleted software license.

Back to Table of Contents

Cloned Software License Removal

In certain situations Software License may become "Cloned" (disabled). In this case the following procedure must be applied to remove the cloned 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:

    Image Modified

  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.
Div
classpagebreak

 

License Deinstallation 

 To completely remove a CHARON-VAX license from a host, it is enough to remove the Sentinel run-time daemon  (and the package "charon-hasp-<...>.rpm" containing the run-time customization) using the following command:

# rpm -e aksusbd charon-hasp-<...> --nodeps
Then just physically disconnect the license key (in the case of protection by dongles).

 

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-VAX is allowed to run. Each time CHARON-VAX 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 from STROMASYS.
  • Backup license may be valid only until a certain date. Please check with STROMASYS management.