Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: RHEL6 support removed

...

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

Div
classpagebreak


Hardware Requirements

Number of CPU cores

...

classpagebreak

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):

CHARON-AXP productMinimum number of host CPU coresRecommended number of host CPU cores

HP AlphaServer 400 - HP AlphaServer 4100

2

2

HP AlphaServer DS10/DS10L/DS15

2

2

HP AlphaServer DS20/DS25

4

4

HP AlphaServer ES40/ES45

6

8

HP AlphaServer GS80

10

16

HP AlphaServer GS160

18

32

HP AlphaServer GS320

34

48

...

  • 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.


Div
classpagebreak


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.

...

Software Requirements

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

...

  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

    (info) 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

    .

    On RHEL 7.x and CentOS 7.x.

  3. On RHEL/CentOS 7 and 8, the "libev" package is required. If it is reported as missing during CHARON installation on RHEL 7.x /8, 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


Warning
titleWARNING
  • If you plan to install CHARON-VAX on the same server, both products, CHARON-AXP and CHARON-VAX, will have to be the same build number.
  • If you upgrade from a previous version of CHARON-AXP, please stop all running CHARON virtual machines and , uninstall CHARON products and reboot the Linux server (recommended) before proceeding with the installation steps described below.

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

Distribution preparation

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

...

Copy the download kit (in /tmp for example) to the folder created in the previous chapter:

# cp /tmp/charon-axp-<VER>-<BN>.<ZZ>.tar.gz /charon_dist

where:

...

ItemDescription

VER

Version of CHARON-AXP product, for example 4.

...

11

BN

Build Number of CHARON-AXP product, for example

...

20404

ZZ

CHARON-AXP target operating system identifier

...

where:

  • ZZ = "el8" for CentOS/Red Hat Enterprise Linux 8
  • ZZ = "el74" for CentOS/Red Hat Enterprise Linux 7

...

  • ZZ = "el65" for Red Hat Enterprise Linux 6

...

Example:

...

Extract the contents of the distribution .tar.gz file to the current directory:

# cd /charon_dist
tar -xvzf charon-axp-

...

<VER>-

...

<BN>.<ZZ>.tar.gz

Example:

tar -xvzf charon-axp-4.11-20404.el74.tar.gz 

...

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

...


...

classpagebreak


Switch to that directory:

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

Example:

# cd charon-axp-4.

...

11-

...

20404.el74

The distribution directory contains the following RPM files:

File nameDescription
aksusbd-7.63-1.i386.rpmHASP Run-time
charon-axp-VER-BN.ZZ.x86_64.rpmCHARON-AXP

...

aksusbd-7.63-1.i386.rpm

...

charon-license-VER-BN.ZZ.x86_64.rpm

CHARON Libraries

charon-

...

mtd-VER-BN.ZZ.x86_64.rpm

...

MTD utility

charon-

...

utils-VER-BN.ZZ.x86_64.rpm

...

CHARON Utilities

Example:

# ls
aksusbd-7.63-1.i386.rpm
charon-axp-4.

...

11-

...

20404.el74.x86_64.rpm
charon-license-4.

...

11-

...

20404.el74.x86_64.rpm
charon-

...

mtd-4.

...

11-

...

20404.el74.x86_64.rpm
charon-

...

utils-4.

...

11-

...

20404.el74.x86_64.rpm

...


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

Div
classpagebreak


Installation

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

# yum yum install *.rpm

Enter "y" to agree to install all the listed packages.

...

Dependencies Resolved  

================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
aksusbd i386 7.63-1 /aksusbd-7.63-1.i386 2.9 M
charon-axp x86_64 4.1011-20200 20404 /charon-axp-4.1011-2020020404.el74.x86_64 260 M
charon-license
x86_64 4.1011-20200 20404 /charon-license-4.1011-2020020404.el74.x86_64 2.9 M
charon-utils
x86_64 4.1011-20200 20404 /charon-utils-4.1011-2020020404.el74.x86_64 1.8 M
charon-mtd 
x86_64 4.1011-20200 20404 /charon-mtd-4.1011-2020020404.68704.el74.x86_64 1.2 M 


Transaction Summary
================================================================================
Install 4 Packages

Total size: 267 M
Installed size: 267 M
Is this ok [y/d/N]: y

...

Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction (shutdown inhibited)
Installing : aksusbd-7.63-1.i386 1/4
Starting aksusbd (via systemctl): [ OK ]
Installing : charon-utils-4.1011-2020020404.x86_64 2/5
Installing : charon-mtd-4.1011-2020020404.x86_64 3/5 

Installing : charon-license-4.1011-2020020404.x86_64 4/5 
Installing : charon-axp-4.1011-2020020404.x86_64 5/5
Verifying : aksusbd-7.63-1.i386 1/5 
Verifying : charon-license-4.1011-2020020404.x86_64 2/5 
Verifying : charon-axp-4.1011-2020020404.x86_64 3/5 
Verifying : charon-utils-4.1011-2020020404.x86_64 4/5
Verifying : charon-mtd-4.1011-2020020404.x86_64 4/5 


Installed:
aksusbd.i386 0:7.63-1 charon-axp.x86_64 0:4.1011-20200 20404
charon-license.x86_64 0:4.1011-20200 20404 charon-utils.x86_64 0:4.1011-2020020404
charon-mtd.x86_64 0:4.1011-2020020404


Complete!


Div
classpagebreak


...

# . /etc/profile.d/charon.sh

If "putty" terminal emulator is going to be used as an additional option copy the following file to your home directory:

# mkdir -p $HOME/.config/putty/sessions (if it does not already exist)
cp /opt/charon/putty/sessions/CHTERM-VT100 $HOME/.config/putty/sessions


Info

Note that the "charon-utils" package has the following dependencies:

  • ethtool
  • bridge-utils
  • net-tools
  • iproute
  • NetworkManager

During "charon-utils" installation using "yum", these packages will be installed automatically if some of them are absent on the host system.

...

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

Directory

Description

/bin

Contains all the executable files

/cfg

Contains the configuration files templates

/doc

Contains the documentation

/log

Contains the log files

/disks

Contains the disk containers

/drivers

Contains the CHARON drivers

...

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

# useradd useradd -G disk,tape,cdrom,dialout,lock -c "Charon User" -m charon
# passwd charon

Any existing user can also be used to run CHARON. In this case issue the following command to include this existing user into these specific groups:

# usermodusermod -G disk,tape,cdrom,dialout,lock -g <user name> <user name>

Example:

# usermodusermod -G disk,tape,cdrom,dialout,lock -g tommy tommy


Div
classpagebreak


Re-login to apply changes.

...

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

...

...

License installation

Regular HASP USB dongle

...

  • Copy the aksusbd-7.63-1.i386.rpm and charon-license-4.9-<build>.<OS identifier>.x86_64.rpm files (see above) to the server, for example to "/tmp".
  • Login as "root" on the server.
  • Switch to that directory.
  • Install the copied files using "yum".
    Example:

    # cd cd /tmp
    # yum yum install aksusbd* charon-license-*


...

# hasp_srm_view 

License Manager running at host: dlao.msc.masq
License Manager IP address: 192.168.1.129

HASP Net key detected

The Physical KeyId: 1422726238
License Type: License Dongle (Network Capable)
CHARON Sentinel HASP License key section
Reading 4032 bytes

The License Number: 000.msc.sanity.tests
The License KeyId: 1422726238
The Master KeyId: 827774524
Release date: 1210-SEPMAR-2016 2020 
Release time: 15:15:15
Update number: 1
End User name: MSC
Purchasing Customer name: STROMASYS
... 

...

Note

If multiple licenses are available, it is possible to check them using the "-all" parameter with the hasp_srm_view utility in the following way:

# hasp

hasp_srm_view -all

(info) It it also possible to display the license content for one specific key using the "-key" parameter and specifying the Key Id (see "# hasp_srm_view -h" for more)

...

  1. Invoke the system default web browser and enter the URL http://localhost:1947 to display the "Sentinel Admin Control Center" (ACC) web interface.
  2. Click on "Sentinel Keys" link to open the corresponding page.
  3. Make sure that one and only one CHARON HASP or SL license is present.

(info) To facilitate troubleshooting, Stromasys recommends to enable logging from the Sentinel Admin Control Center as described in this article: Enabling logging in Sentinel Admin Control Center.

ProblemAction
No license is displayedMake sure that all the recommendations above about remote access to the host are fulfilled (if remote access takes place), that the HASP USB key is not broken and its LED indicator is lit (meaning that it is used by the host).
Only one License key / SL is seen and its content is incorrectContact STROMASYS to request a new license update.
Several License keys / SLs are displayedRemove all of them except the one provided by STROMASYS for the just installed version of CHARON.

...

Info

It is also possible to leave several licenses available to CHARON-AXP at the same time but in this case they have to be specified in the configuration file.

Example:

set session license_key_id=1877752571

It is also possible to have one "main" and one "backup" license in case the main license becomes unavailable:

set session license_key_id="1877752571,354850588"

CHARON-AXP checks its licenses from time to time starting with the main license. If it becomes unavailable, it attempts to access the backup license.

...

# ncu
CHARON Network Configuration Utility, 
STROMASYS (c) 2016 2020 Version 1.67


Interfaces Dedicated to State
---------- ------------ ------------
eth0         host         connected to host
eth1         host         disconnected from host
lo           host         unmanaged by host
virbr0-nic   bridge       unmanaged by bridge

==================================================================
bridge name bridge id          STP enabled   interfaces
==================================================================
virbr0     8000.5254004608c0  yes            virbr0-nic

==================================================================

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Add VLAN
6 - Remove VLAN
7 - Print status
8 - Exit
:> 1

...

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

# ifconfigifconfig
eth0 Link encap:Ethernet HWaddr 00:60:52:0A:A9:1E
... 
eth1 Link encap:Ethernet HWaddr 00:C0:26:60:FB:15 
...
eth2 Link encap:Ethernet HWaddr 00:1A:92:E1:3F:7F

...

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

# eethtool -k <device>

Example:

# ethtool ethtool -k eth1
Offload parameters for eth1:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off

Use "ethtool" to switch off all the offload parameters:

# e# ethtool -K <device> <parameter> off

Example:

# ethtool ethtool -k eth1
Offload parameters for eth1:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off

...

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

cat offload_off_eth1.txt >> /etc/rc.d/rc.local

...

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

Upgrade

...

from previous 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 installation695402677" and "Distribution preparation695402677" 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 and reboot the Linux server (recommended).
  7. Proceed with the instructions on the new kit installation as described in the "Installation695402677" section.
  8. Once installation is completed, it is recommended to reboot the Linux server (possible issues with licenses detection could occur).
  9. Install the license for the new CHARON-AXP as described in the "License installation695402677" section.

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

If you did not reboot your Linux server at step 6, you may experience issues with 'aksusbd' service installation and then license detection.

Example:

  Installing : aksusbd-8.13-1.x86_64 1/5
Failed to execute operation: Access denied
Failed to restart aksusbd.service: Access denied

To solve this problem, remove all Charon installed product and restart from step 6 above.

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