Page Comparison

...

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.

Div

class	pagebreak

The following table shows 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 product	Minimum number of host CPU cores	Recommended number of host CPU cores
HP AlphaServer 400 - HP AlphaServer 4100	2	2
HP AlphaServer DS10	2	2
HP AlphaServer DS20	4	4
HP AlphaServer ES40	6	8
HP AlphaServer GS80	10	16
HP AlphaServer GS160	18	32
HP AlphaServer GS320	34	48

Note
Hyperthreading must be switched off completely. Disable hyperthreading in the BIOS settings of the physical host or, for a VMware virtual machine, edit the virtual machine properties, select the Resources tab then select Advanced CPU. Set the Hyperthreaded Core Sharing mode to None.

...

Back to Table of Contents

Div

class	pagebreak

Software Requirements

Linux Red Hat Enterprise 7.0 and 7.1, 64bit
Linux Fedora Core 20, 21, and 22, 64bit
VMware ESXi 5.x and 6.0 (requires a supported Linux operating system on top of a ESXi virtual machine)

...

Before installation

Login as system administrator ("root") on the host system. Because Sentinel HASP runtime relies on 32-bit compatibility libraries to run on Linux, the 32-bit compatibility libraries should be installed first:

# yum install glibc.i686

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

Note

Sometimes it is not possible to use an online repository for the installation of 32-bit glibc package. In this case the following procedure should be followed:

1. If you have a Linux distributibe CD-ROM, insert it into CD-ROM drive

1.1. If auto-mount is not enabled, mount the CD-ROM. Example:

# mount /dev/sr0 /mnt

2. If you have an ISO image of the distribution CD, you can mount it using a loopback device:

# mount /path/to/ISO-image.iso /mnt -o loop

3. Switch to the directory containing the packages. This directory depends on your Linux distribution. Example:

# cd /mnt/Packages/

4. Locate the target "glibc.i686" package:

# ls -la glibc-*i686.rpm

5. Install the "glibc.i686" and the packages it depends on. Example:

# rpm -i glibc-2.17-157.el7.i686.rpm nss-softokn-freebl-3.16.2.3-14.4.el7.i686.rpm

6. If the above command reports additional unsatisfied dependencies, add the corresponding packages to the above command line.

7. Umount the CD-ROM or ISO file if necessary:

# umount /mnt

Create a directory for the CHARON-AXP distribution and copy the TAR.GZ files there. Set this directory as the default with a "cd" command as shown in the following example:
# mkdir /charon_dist
# cp /temp/charon-axp-4.7-17101.68704.fc20.tar.gz /charon_dist
# cd /charon_dist

Warning

title	WARNING

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 before proceeding with the installation steps described below

...

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

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

where:

	Description
VER	Version of CHARON-AXP product, for example 4.7
BN	Build Number of CHARON-AXP product, for example 17101
VC	68704 - CHARON-AXP product vendor code
ZZ	CHARON-AXP target operating system identifier. For Fedora Core 20 'ZZ' value is 'fc20', for Red Hat Linux 7.1 the value is 'el71'

Example:

# tar -xvzf charon-axp-4.7-17101.68704.fc20.tar.gz

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

Switch to the directory, created by the "tar" command in the previous step:
# cd charon-axp-<VER>-<BN>.<VC>.<ZZ>
Example:
# cd charon-axp-4.7-17101.68704.fc20

The distribution directory contains the following RPM files with CHARON-AXP product, Sentinel run-time, license support and utilities:

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

Example:

# ls
aksusbd-2.5-1.i386.rpm
charon-axp-4.7-17101.68704.fc20.x86_64.rpm
charon-license-4.7-17101.68704.fc20.x86_64.rpm charon-utils-4.7-17101.68704.fc20.x86_64.rpm

Back to Table of Contents

...

Issue the following command to install all the RPMs in the directory:

# yum install *.rpm

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

Example:

Dependencies Resolved

================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
aksusbd i386 2.5-1 /aksusbd-2.5-1.i386 2.9 M
charon-axp x86_64 4.7-17101 /charon-axp-4.7-17101.68704.fc20.x86_64 260 M
charon-license
x86_64 4.7-17101 /charon-license-4.7-17101.68704.fc20.x86_64 2.9 M
charon-utils
x86_64 4.7-17101 /charon-utils-4.7-17101.68704.fc20.x86_64 1.8 M

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

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

Check that the installation process has completed successfully.

Example:

Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction (shutdown inhibited)
Installing : aksusbd-2.5-1.i386 1/4
Starting aksusbd (via systemctl): [ OK ]
Installing : charon-utils-4.7-17101.x86_64 2/4
ln -s '/usr/lib/systemd/system/ncu.service' '/etc/systemd/system/multi-user.target.wants/ncu.service'
Installing : charon-license-4.7-17101.x86_64 3/4
Installing : charon-axp-4.7-17101.x86_64 4/4
Verifying : aksusbd-2.5-1.i386 1/4
Verifying : charon-license-4.7-17101.x86_64 2/4
Verifying : charon-axp-4.7-17101.x86_64 3/4
Verifying : charon-utils-4.7-17101.x86_64 4/4

Installed:
aksusbd.i386 0:2.5-1 charon-axp.x86_64 0:4.7-17101
charon-license.x86_64 0:4.7-17101 charon-utils.x86_64 0:4.7-17101

Complete!

Div

class	pagebreak

Re-login (as "root") to apply PATH settings or execute the following command:

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

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 executables
/cfg	Contains templates of configuration files
/doc	Contains documentation
/log	Contains log files
/disks	Contains disk containers
/drivers	Contains CHARON drivers

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

...

Create a specific account "charon" for running CHARON:

# 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 to specific groups:

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

Example:

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

Re-login to apply changes.

...

Copy aksusbd-2.5-1.i386.rpm and charon-license-4.7-<build>.68704.<OS identifier>.x86_64.rpm files (see above) to the server in any directory, for example "/temp"
Login as "root" on the server
Switch to that directory
Install the copied file using "yum"
Example:
# cd /temp
# yum install aksusbd* charon-license-*

Connect the network HASP dongle to the server USB port.

...

Info
Network HASP (red dongles) licenses have no restrictions with remote access

Div

class	pagebreak

Software license

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

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
Send the resulting file to STROMASYS. In return STROMASYS will provide you with a "*.v2c" file, for example "your_license.v2c"
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.
In the ACC use the following menu items: first "Browse" for the "your_license.v2c" file and then "Apply File"
Ensure that the software license appears now in the "Sentinel Keys" menu of the ACC.

Info
Alternatively it is also possible to use "hasp_update" utility for applying ".v2c" file.

...

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.

Example:

# 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
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: 21-SEP-2015
Release time: 15:15:15
Update number: 1
End User name: MSC
Purchasing Customer name: STROMASYS...

Div

class	pagebreak

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_srm_view -all

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)

...

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

Problem	Action
No license is displayed	Make 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 incorrect	Contact STROMASYS to request a new license update.
Several License keys / SLs are displayed	Remove all of them except the one provided by STROMASYS for just installed version of CHARON.

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 explanation below).

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

# hasp_srm_view -tfr <Key ID>

Example:

# hasp_srm_view -tfr 12345678

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

Div

class	pagebreak

Uncheck "Allow Access to Remote Licenses" and "Broadcast Search for Remote Licenses" checkboxes from the "Access to Remote License Managers" tab, then press "Submit" button to apply changes.

Info

It is also possible to leave several licenses available to CHARON-AXP at the same time, but in this case you have to specify it in the CHARON-AXP configuration file what license must be used.

Example:

set session license_key_id[0]=1877752571

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

set session license_key_id[0]=1877752571 license_key_id[1]=354850588

CHARON-AXP checks its licences from time to time starting with the main license. If it is inaccessible, it attempts to access backup license

Back to Table of Contents

Network configuration

In most cases, CHARON will use a network. If so, CHARON requires a dedicated network interface with any other protocols including TCP/IP removed at the host level.

...

Login as root. Type "ncu" and press Enter. The following menu will appear:

Interfaces Dedicated to State
---------- ------------ ------------
eth0 host         connected to host
eth1       host         connected from host
lo         host         unmanaged from host

==================================================================
bridge name     bridge id        STP enabled            interfaces

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

The utility lists available network interfaces (both physical and virtual) and indicates whether they are dedicated to the host or to CHARON and whether they are currently in use by host operating system.

Div

class	pagebreak

"ncu" offers several options:

...

Enter "1", then type "eth1" and press Enter:

Specify the interface to dedicate to CHARON:eth1
Turning off offloading for eth1.. Please wait

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

Now the interface "eth1" is dedicated to CHARON-AXP:

Interfaces Dedicated to State
---------- ------------ ------------
eth0       host         connected to host
eth1       CHARON       disconnected from host
lo         host         unmanaged from host

==================================================================
bridge name     bridge id        STP enabled            interfaces

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

Enter "6" to return to console prompt.

...

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

# ifconfig

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

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

...

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. The file must look like this ("eth1" is used as example):

DEVICE="eth1"
HWADDR="00:06:2B:00:6A:87"
NM_CONTROLLED="no"
ONBOOT="no"

Switching off the offload parameters

First determine what additional parameters are currently set to "on" on the host network adapter to be used by CHARON. To do that type:

# ethtool -k <device>

Example:

# 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

Then use ethtool to switch off all the offload parameters:

# ethtool -K <device> <parameter> off

Example:

# 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

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 for each reboot:

ethtool -K eth1 rx off
ethtool -K eth1 tx off
ethtool -K eth1 sg off
ethtool -K eth1 gso off ethtool -K eth1 gro off

Div

class	pagebreak

Let's suppose that the name of the file is "offload_off_eth1.txt". In this case running it on system startup can be done in the following ways:

On Red Hat Linux:

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

On Fedora Core:

# echo '#!/usr/bin/bash' > /etc/rc.d/rc.local        Do not use double quotes, use single ones
# cat offload_off_eth1.txt >> /etc/rc.d/rc.local
# chmod 755 /etc/rc.d/rc.local 
# ln -s /usr/lib/systemd/system/rc-local.service /etc/systemd/system/rc-local.service 
# systemctl daemon-reload

Back to Table of Contents

...

Versions Compared

Old Version 21

New Version 22

Key

Software Requirements

Before installation

Software license

Network configuration

Switching off the offload parameters