Versions Compared

Old Version 9

changes.mady.by.user Kirill Nikolaev

Saved on

compared with

New Version 10

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: typo / document reviewed / screenshots to update

Anchor
TopLicPage
TopLicPage

...

Warning

The present CHARON-AXP implementation requires that the expired license be removed to allow the running CHARON-AXP to switch to some other (valid) one.

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-inaccumulator in accumulator that needs to be charged. If the accumulator is completely discharged, a license key can be fatally damaged.

...

Warning

Software Licenses are hightly dependable highly dependent on hardware configuration of CHARON host. Do not change hardware configuration since it leads to disabling of installed Software License!

If CHARON host has to be upgraded use the following procedure:

  1. Transfer Software License to some other host.
  2. Upgrade CHARON host.
  3. Transfer Software License back to CHARON host.

...

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-hasp-<...>.rpm" containing the run-time customization) with the command

    # rpm --nodeps -e aksusbd charon-hasp-<...>

  • Change to the directory where the new run-time RPM resides (along with the corresponding "charon-hasp-<...>.rpm" customization package) and issue the command:

    # rpm --nodeps -ihv aksusbd<…>.rpm charon-hasp-<...>.rpm
Back to Table of Contents

Installation of CHARON-AXP Software License

CHARON-AXP software licenses can be installed according to the following procedure:

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

  • Reboot host system

  • Collect CHARON-AXP host fingerprint file ("*.c2v"):

    # hasp_srm_view -fgp my_host.c2v

  • Send the ".c2v" file ("my_host.c2v" in the example 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.

     

Info

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

Info

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

Info

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 clients side: open UDP ports 30000-65535
  • 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

...

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:
# /etc/init.d/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 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 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.
Back to Table of Contents

Transferring and removing CHARON-AXP 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
Back to Table of Contents

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

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-hasp-<...>.rpm" containing the run-time customization) using the following command:

# rpm --nodeps -e aksusbd charon-hasp-<...>
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