Page Comparison

...

...

The most important directory at this stage is the "/cfg" directory since it contains template configuration files with examples of typical configuration parameters and commentaries. We will pay focus our attention to on this subject in the next chapter.

...

Back to Table of Contents

...

Regular HASP USB dongle

If the CHARON license represents is a regular USB dongle, just connect it to the host USB port.

Network HASP USB dongle

If the CHARON license is a network license (red USB dongle) it is possible either to connect it to the host USB port (to use it locally providing and provide it to other hosts on local network in the same time) or to install it on some local network "server" for remote access from this particular host.

...

• Copy aksusbd-2.5-1.i386.rpm and charon-hasp-4.6-<build>.68704.<OS identifier>.x86_64.rpm files (see above) to the server to some in any directory, for example "/temp"
• Login as "root" to on the server
• Switch to that directory

• Install the copied file using "yum"
  Example:

  # cd /temp # yum install aksusbd* charon-hasp-*

...

Software license

If the CHARON license is a software license (SL) it is required to install it installed on the host using the following procedure:

1. Run hasp_srm_view utility in the following way to get the host fingerprint file ("my_host.c2v" in this example):

   # hasp_srm_view -fgp my_host.c2v

2. Send the resulting file to STROMASYS. In return STROMASYS will provide you with a "*.v2c" file, for example "your_license.v2c"
3. Copy the received "your_license.v2c" file to the CHARON host to any folder then invoke the system default web browser and enter URL http://localhost:1947 to display "Sentinel Admin Control Center" (ACC) web interface. This interface allows you to view and manage CHARON licenses.
4. In the ACC use the following menu items: first "Browse" for the "your_license.v2c" file and then secondly "Apply File"
5. Ensure that the software license appears now in the "Sentinel Keys" menu of the ACC.

...

Back to Table of Contents

License validity verification

Check available the CHARON license validity. To do that, invoke the hasp_srm_view utility to make sure that the CHARON license is visible and looks Okis correct:

• Text of the license is displayed correctly by the hasp_srm_view utility, no error messages are shown
• Content of the license looks correct. For example license number, major and minor versions, minimum and maximum build numbers, CHARON-AXP products and allowed hardware (CHARON-AXP models) should be checked. More details on the license content can be found in the CHARON-AXP Licensing chapter of this Guide.

...

Troubleshooting

If the CHARON license content cannot be displayed by hasp_srm_view utility or it is incorrect, check the license is available and correctly used:

...

Removing licenses can be done by physical disconnection of the corresponding USB HASP keys from the CHARON host and physical disconnection of the network HASP keys from all hosts on local network (or by disabling remote access to network licenses from the CHARON host - see detailed explanations explanation below).

Software licenses can also be uninstalled with the hasp_srm_view utility "-tfr" option in the following way:

...

It is also possible to disable access to network licenses if just only a local license must is to be used: Click on "Configuration" link to open up "Configuration for Sentinel Manager" page.

...

Back to Table of Contents

...

Network configuration

In most cases it is assumed that , CHARON will use a network. In this case some important steps must be performed, since If so, CHARON requires a dedicated network interface cleared from with any other protocols including TCP/IP removed at the host level.

Two ways of network configuration are possible:

• With a help of "ncu" utility
• ManualManually

The first way is a way simplier, so use the manual approach only in absence of the "ncu" utility or impossibility inability to use it.

Configuration with NCU utility

...

• Dedicate interface to CHARON (press option "1")
• Release interface to host (press option "2")
• Create a bridge between a chosen physical network interface and the Linux virtual network and create a number of virtual network interfaces (press option "3")
• Remove the Linux virtual network and all the created virtual network interfaces (press option "4")
• Print status (press option "5") - use it to display status of network interfaces and the menu shown above
• Exit (press option "6")

In the example above we see 2 network interfaces - "eth0" and "eth1", both of them are dedicated to host, but host uses only the interface "eth0".

...

Now "eth1" can be used by CHARON-AXP.

Manual Configuration

Choosing a network interface

To choose an interface to be used for CHARON networking do the following:

...

To designate the chosen interface to CHARON open up the file "/etc/sysconfig/network-scripts/ifcfg-ethN" (where N is the number of the interface to be used for CHARON, in our case it is "1") and make sure that all the IP-setup related parameters are removed. Basically the The file must look like this ("eth1" is used as example):

...

Switching off the offload parameters

A first step is to find First determine what additional parameters are currently set to "on" on the host network adapter to be used by CHARON. To do that issuetype:

...

For In the example above let's create a temporary file containing the commands to be run on system startup, since the offload parameters must be switched off on for each reboot:

...

• Reboot the host system to apply the offload parameters switching them to off
• Login as user "charon"

...

Upgrade to new version

To upgrade an already installed CHARON-AXP kit to a more recent one:

1. Ensure your license allows you to upgrade to that version. If not, please generate a C2V file and send it to STROMASYS for update. See CHARON-AXP for Linux utilities - 'hasp_srm_view' utility
2. Prepare the new kit RPM files as it is described in "Before Installation" and "Distribution preparation" sections.
3. Stop all running CHARON-AXP instances.
4. Make sure that no template files (i.e. "es40.cfg.template") have been used for your specific configuration. Otherwise copy those files to some place to save place.
5. Login as "root" user.
6. Remove the old CHARON-AXP version as described in the "CHARON-AXP for Linux deinstallation" chapter.
7. Proceed with the instructions on the new kit installation as described in "Installation" section.

8. Install the license for the new CHARON-AXP as described in "License installation" section.

9. Start all the CHARON-AXP services stopped on the step (2).

Back to Table of Contents