Table of contents

Introduction

The CHARON-AXP product is distributed in form of archive TAR.GZ files that contain RPM modules for different components. Generally it is recommended to install all the RPM modules but it is possible to omit some RPM files if they are not needed.

...

Hardware Requirements

Number of CPU cores

Each CHARON-AXP emulated CPU requires a corresponding physical core. So the total number of the host CPUs must exceed the number of emulated CPUs since some of the host CPUs must be dedicated to serving CHARON I/O operations and host operating system needs. If several CHARON instances run in parallel, the required number of CPU cores is cumulative.

...

The following table lists the minimum and recommended number of CPUs required for each virtual HP Alpha instance (note that each CHARON instance is able to run on 2 CPU cores hosts, but this configuration does not support emulation of all the virtual CPUs):

...

CPU type and speed

Since CHARON utilizes LAHF instruction in CPU emulation please avoid usage of early AMD64 and Intel 64 CPUs in CHARON host system since they lack it. AMD introduced the instruction with their Athlon 64, Opteron and Turion 64 revision D processors in March 2005 and Intel introduced it with the Pentium 4 G1 stepping in December 2005.

Concerning CPU speed, the general recommendation is that higher the CPU frequency is, better the emulated HP Alpha performances will be. The minimum recommendation is at least 3 GHz.

Operative memory

The minimum host memory size:

• depends on the amount of HP Alpha memory to be emulated and on the number of CHARON-AXP instances to be executed on one host.

• is calculated according to the following formula:

  The minimum host memory = (2Gb +  the amount of HP Alpha memory emulated) per CHARON-AXP instance.

  
  

Disk storage

The total amount of disk space required for CHARON-AXP can be calculated as a sum of all the disk/tape image sizes plus 50 MB for the CHARON software plus the space required for the host operating system. Temporary disk storage is often needed when setting up a new virtual machine (for source disks backups storage, software installation kits, etc...).

When virtual disks/tapes are used to represent physical disk drives / magnetic tapes, the disk/tape image files have the same size as their hardware equivalent, regardless of their degree of utilization.

Ethernet adapters

CHARON-AXP networking requires dedicated host Ethernet adapters; their number must be equal to the emulated adapters to be configured in CHARON-AXP. One adapter (optionally) can be left to the host for TCP/IP networking, management interface, etc.

It is also possible to use virtual network interfaces, but for performance considerations, it is recommended to use physical ones only.

...

Starting with ESXi 6.5, it is not possible to select E1000 adapter when a new virtual machine is created using Windows Server 2012, 2016 and Windows 10 templates.

The following workarounds are available:

...

to use physical ones only.

Software Requirements

• Red Hat Enterprise Linux 7.x, 64bit
• Red Hat Enterprise Linux 6.5 - 6.10, 64bit
• Linux Centos 7.x, 64bit
• VMware ESXi 5.5 and 6.x up to 6.7 (requires a supported Linux operating system on top of a ESXi virtual machine)
  

Host system preparation

...

Before installation

1. Login as the superuser ("root") on the host system. Because Sentinel HASP runtime relies on 32-bit compatibility libraries to run on Linux, the 32-bit compatibility libraries must be installed before continuing. If the emulator host has access to a package repository, either local or remote, use the following command:

   # yum install glibc.i686

   Sometimes it is not possible to use an online repository for the installation of 32-bit glibc package. In this case the procedure described in the appendixes has to be used: glibc.i686 installation without Internet connection

   .

2. Create a directory for the CHARON-AXP distribution, copy the TAR.GZ files there and change to this directory as shown in the following example:

   # mkdir /charon_dist # cp /tmp/charon-axp-4.10-20200.el74.tar.gz /charon_dist # cd /charon_dist

   .

3. On RHEL 7.x and CentOS 7.x, the "libev" package is required. If it is reported as missing during CHARON installation on RHEL 7.x check that the repository "extras" is included and enabled, if not, include and enable it. Please refer to your Linux distribution administrator's guide. Example for RHEL 7.x:

   # yum-config-manager --enable rhel-7-server-extras-rpms

   
   

...

Distribution preparation

• Extract the contents of the distribution TAR.GZ files to the current directory:

  # tar -xvzf charon-axp-<VER>-<BN>.<ZZ>.tar.gz

  where:

  	Description
  VER	Version of CHARON-AXP product, for example 4.10
  BN	Build Number of CHARON-AXP product, for example 20200
  ZZ	CHARON-AXP target operating system identifier. For CentOS 7.x 'ZZ' value is 'el74', for Red Hat Enterprise Linux 7.x the value is 'el74' and for Red Hat Enterprise Linux 6.5 to 6.10 the value is 'el65'.

  Example:

  # tar -xvzf charon-axp-4.10-20200.el74.tar.gz

  As a result, the new directory "charon-axp-<VER>-<BN>.<ZZ>" will be created.
   

  
  

  Div
  class pagebreak

  
  

1. Switch to that directory:

   # cd charon-axp-<VER>-<BN>.<ZZ>

   Example:

   # cd charon-axp-4.10-20200.el74

   
   

2. The distribution directory contains the following RPM files:

   File name	Description
   charon-axp-VER-BN.ZZ.x86_64.rpm	CHARON-AXP
   aksusbd-7.63-1.i386.rpm	HASP Run-time
   charon-license-VER-BN.ZZ.x86_64.rpm	CHARON Libraries
   charon-utils-VER-BN.ZZ.x86_64.rpm	CHARON Utilities
   charon-mtd-VER-BN.ZZ.x86_64.rpm	MTD utility

   Example:

   # ls aksusbd-7.63-1.i386.rpm charon-axp-4.10-20200.el74.x86_64.rpm charon-license-4.10-20200.el74.x86_64.rpm charon-utils-4.10-20200.el74.x86_64.rpm charon-mtd-4.10-20200.el74.x86_64.rpm

   Include Page
   KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc

Installation

Issue the following command to install all the RPM files present in the directory:

...

CHARON-AXP home directory

By default CHARON is installed in the "/opt/charon" directory. It has the following subdirectories:

...

Specific user account creation

Create a specific user account named "charon" for running CHARON:

...

License installation

Regular HASP USB dongle

If the CHARON license is located on 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 and provide it to other hosts on the local network at the same time) or to install it on a local network "license server" for remote access from this particular host.

...

Software license

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

...

License validity verification

To check the CHARON license validity, invoke the hasp_srm_view utility to make sure that the CHARON license is visible and is correct:

...

Troubleshooting

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

...

Network configuration

In most cases CHARON will use a network. In this case CHARON requires one or more dedicated network interfaces with any other protocols including TCP/IP removed at the host level.

...

The first way is recommended. Use the manual approach only in absence of the "ncu" utility or if it impossible to use it.

Configuration with NCU utility

Login as root and enter "ncu". The following menu will appear:

...

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:

...

Choose an interface to be used by CHARON, for example "eth1"

Designation of network interface to CHARON

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 this case it is "1") and make sure that all the IP-setup related parameters are removed. The file must look like this:

Switching off the offload parameters

Determine what additional parameters are currently set to "on" on the host network adapter to be used by CHARON using the following command:

...

For the example above let's create a temporary file containing the commands to be executed at system startup as the offload parameters must be switched off following each reboot:

...

...

Let's suppose the name of the file is "offload_off_eth1.txt". To execute it on system startup, execute the following command (example):

...

Final steps

• Reboot the host system
• Login as user "charon"
• Verify the offload parameters are effective

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 a dedicated folder.
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 the "Installation471924856" section.

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

9. Start all the CHARON-AXP services stopped at step #3.

...