Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 32-bit glibc package installation is described

...

Each CHARON emulated CPU requires a corresponding physical core. So the total number of the host CPUs must exceed the number of emulated CPUs.

Div
classpagebreak

 


Below please find a table describing minimal and recommended number of CPUs required for each product:

CHARON-VAX model

Minimal number of CPU cores

Recommended number of CPU cores

VAX 6610

2

4

VAX 6620

3

4

VAX 6630

4

6

VAX 6640

6

8

VAX 6650

8

12

VAX 6660

8

12

Other models22
Note

Hyper-threading must be switched off completely. Disable hyper-threading 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 Hyper-threaded Core Sharing mode to None.

...

Back to Table of Contents

Before installation

Login as system administrator ("root") to 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:

...

  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

    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
  2. Create a special directory for the CHARON-VAX 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-vax-4.7-17101.68704.fc20.tar.gz /charon_dist
    # cd /charon_dist
Warning
titleWARNING
  • If you plan to install CHARON-AXP 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-VAX, please stop all running CHARON virtual machines and uninstall CHARON products before proceeding with the installation steps described below

...

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

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

    where:

     

    Description

    VER

    Version of CHARON-VAX product, for example 4.7

    BN

    Build Number of CHARON-VAX product, for example 17101

    VC

    68704 - CHARON-VAX product vendor code

    ZZ

    CHARON-VAX 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-vax-4.7-17101.68704.fc20.tar.gz 

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

  2. Switch to the directory, created by "tar" on the previous step:

    # cd charon-vax-<VER>-<BN>.<VC>.<ZZ>

    Example:

    # cd charon-vax-4.7-17101.68704.fc20

         

  3. The distribution directory contains the following RPM files with additional material, libraries and utilities:

    File name

    Description

    charon-vax-VER-BN.VC.ZZ.x86_64.rpmCHARON-VAX

    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-vax-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-vax x86_64 4.7-17101 /charon-vax-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-vax-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-vax-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-vax.x86_64 0:4.7-17101 
charon-license.x86_64 0:4.7-17101 charon-utils.x86_64 0:4.7-17101 

Complete!

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

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

Info

Note that Network Configuration Utility ("ncu") package has the following dependencies:

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

During "ncu" 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 at this stage is the "/cfg" directory since it contains template configuration files with examples of typical configuration parameters and commentaries. We will pay our attention to 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
Warning

The specific account created above does not allow to use virtual consoles "/dev/tty<N>" as CHARON consoles. If you plan to map CHARON console to "/dev/tty<N>" use only "root" account for CHARON running.

...

  • 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 to some directory, for example "/temp"
  • Login as "root" to 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

...

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

 


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-VAX products and allowed hardware (CHARON-VAX models) should be checked. More details on the license content can be found in the CHARON-VAX Licensing chapter of this Guide.
Div
classpagebreak

 

 



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

Note

Reminder: If CHARON host is accessed remotely please note that regular HASP licenses cannot be displayed and used in this case. As workaround it is possible to install CHARON as daemon. This procedure will be described later.

 


Troubleshooting

If 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 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 CHARON host - see detailed explanations below). Software licenses can also be uninstalled with 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 just a local license must be used: Click on "Configuration" link to open up "Configuration for Sentinel Manager" page. 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.

 
Div
classpagebreak


Info

It is also possible to leave several licenses available to CHARON-VAX at the same time, but in this case you have to specify in CHARON-VAX 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 not accessible:

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

CHARON-VAX checks its licences from time to time starting from main license and if it is not accessible it tries to access backup license

...

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

# ncu
CHARON Network Configuration Utility, STROMASYS (c) 2015 Version 1.5 

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.

...

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

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

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

# 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

For 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 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
 

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

...