Versions Compared

Old Version 1

changes.mady.by.user Copy Page Tree

Saved on

compared with

New Version 2

changes.mady.by.user Kirill Nikolaev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Installation procedure description update

...

Each CHARON emulated CPU requires a corresponding physical core. So the total numberr of the host CPUs must exceed the number of emulated CPUs.
Below please find a table describing minimal and recommended number of CPUs required for each product:

2

CHARON-VAX productmodel

Minimal number of CPU cores

Recommended number of CPU cores

CHARON-VAX/XM

2

CHARON-VAX /XL

2

2

CHARON-VAX/ 6610

2

4

CHARON-VAX / 6620

3

4

CHARON-VAX / 6630

4

6

CHARON-VAX / 6640

6

8

CHARON-VAX / 6650

8

12

CHARON-VAX / 6660

8

12

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

...

  • Fedora Core Linux version 20
  • Red Hat Enterprise Linux version 6.2-6.5, 7 (excluding 'ncu' utility)7.x

Back to Table of Contents

...

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

    # yum install glibc.i686

          

  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-xl-4.67-1680217101.68704.fc20.tar.gz /charon_dist
    # cd /charon_dist

    Back to Table of Contents

...

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

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

    where:

     

    Description

    PRODUCTVER

    Name Version of CHARON-VAX product, for example 'xm'

    VER

    Version of CHARON-VAX product, for example 4.64.7

    BN

    Build Number of CHARON-VAX product, for example 1680217101

    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 v6.2-6.5 and 7 7.1 the value is 'el65el71'

    Example:

    # tar -xvzf charon-vax-xl-4.67-1680217101.68704.fc20.tar.gz 

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

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

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

    Example:

    # cd charon-vax-xl-4.67-1680217101.68704.fc20

         

  3. The "main" RPM file of CHARON-VAX products aredistribution directory contains the following RPM files with additional material, libraries and utilities:

    vax-6620-VAX/6620

    File name

    Description

    charon-vax-xm-VER-BN.VC.ZZ.x86_64.rpmCHARON-VAX/XM

    charonaksusbd-vax-xl-VER-BN.VC.ZZ.x86_642.5-1.i386.rpm

    CHARON-VAX/XLHASP Run-time

    charon-vaxlicense-6610-VER-BN.VC.ZZ.x86_64.rpm

    CHARON -VAX/6610Libraries

    charon-

    utils-VER-BN.VC.ZZ.x86_64.rpm

    CHARON

    Utilities

    Example:

    # ls
    aksusbd-2.5-1.i386.rpm
    charon-vax-    6630-VER-BN.VC.ZZ4.7-17101.68704.fc20.x86_64.rpm

    CHARON-VAX/6630

    		charon-vaxlicense-6640-VER-BN.VC.ZZ4.7-17101.68704.fc20.x86_64.rpmCHARON-VAX/6640
    charon-    vax-6650-VER-BN.VC.ZZ.x86_64.rpm

    CHARON-VAX/6650

    		charon-vax-6660-VER-BN.VC.ZZutils-4.7-17101.68704.fc20.x86_64.rpm

    CHARON-VAX/6660

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

    File name

    Description

    aksusbd-2.4-1.i386.rpm

    HASP Run-time

    charon-base-VER-BN.VC.ZZ.x86_64.rpm

    CHARON Libraries

    charon-hasp-VER-BN.VC.ZZ.x86_64.rpm

    hasp_srm_view utility and specific libraries for software licenses support

    charon-ncu-VER-BN.VC.ZZ.x86_64.rpmNetwork Configuration Utility ("ncu")

    Example:

    # ls
    aksusbd-2.4-1.i386.rpm
    charon-base-4.6-16802.68704.fc20.x86_64.rpm
    charon-hasp-4.6-16802.68704.fc20.x86_64.rpm
    charon-vax-xl-4.6-16802.68704.fc20.x86_64.rpm
    charon-ncu-4.6-16802.68704.fc20.x86_64.rpm 

    Back to Table of Contents

Installation

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

...

Network Configuration Utility ("ncu") package cannot be installed on Red Hat Linux 7.

To install all CHARON-VAX packages except the "ncu" one issue:

...

  1.  

    Back to Table of Contents

Installation

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 ResolvedResolved  

================================================================================ 
Package Arch Version Repository Size 
================================================================================ 
Installing: 
aksusbd i386 2.45-1 /aksusbd-2.45-1.i386 3.0 M
charon-base x86_64 4.6-16802 /charon-base-4.6-16802.68704.fc20.x86_64 15 M2.9 M 
charon-hasp vax x86_64 4.67-16802 17101 /charon-haspvax-4.67-1680217101.68704.fc20.x86_64 3.3 M260 M 
charon-vax-xllicense 
x86_64 4.67-16802 17101 /charon-vaxlicense-xl-4.67-1680217101.68704.fc20.x86_64 17 M2.9 M 
charon-ncu utils 
x86_64 4.67-1680217101 /charon-ncuutils-4.67-1680217101.68704.fc20.x86_64 15 M 1.8 M 

Transaction SummarySummary 
 ================================================================================ 
Install 5 4 Packages 

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

Check that the installation process has completed successfully.

Example:

Downloading Packagespackages: 
Running Transaction Checktransaction check 
Running Transaction Testtransaction test 
Transaction Test Succeededtest succeeded 
Running Transactiontransaction (shutdown inhibited) 
Installing : aksusbd-2.4-1.i386 1/5 
Starting aksusbd (via systemctl): [ OK ]
Installing : charon-base-4.6-16802.x86_64 2/5 
Installing : charon-hasp-4.6-16802.x86_64 3/5 5-1.i386 1/4 
Starting aksusbd (via systemctl): [ OK ] 
Installing : charon-vax-xlutils-4.67-1680217101.x86_64 42/54 
Installing : charon-ncu-4.6-16802.x86_64 5/5 
Verifying : charon-base-4.6-16802.x86_64 1/5 
Verifying : charon-hasp-4.6-16802.x86_64 2/5 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.45-1.i386 3/5 1/4 
Verifying : charon-license-4.7-17101.x86_64 2/4 
Verifying : charon-vax-xl-4.67-1680217101.x86_64 43/54 
Verifying : charon-ncuutils-4.67-1680217101.x86_64 54/5  4 

Installed: 
aksusbd.i386 0:2.45-1 charon-basevax.x86_64 0:4.67-16802 17101 
charon-hasplicense.x86_64 0:4.67-16802 17101 charon-vax-xlutils.x86_64 0:4.67-16802
charon-ncu-4.6-1680217101 

Complete!

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

...

Info

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

  • ethtool
  • bridge-utilstunctl
  • 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.

...

Directory

Description

/bin

Contains all executables

/cfg

Contains templates of configuration files

/lib

Contains product libraries

/doc

Contains documentation

/log

Contains log files

/disks

Contains disk containers

/drivers

Contains CHARON drivers

...

In case of remote usage:

  • Copy aksusbd-2.45-1.i386.rpm and charon-hasplicense-4.67-<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-hasplicense-*
  • Connect the network HASP dongle to the server USB port.

...

# hasp_srm_view 

License Manager running at host: XEON4WAYW7dlao.msc.masq 
License Manager IP address: 192.168.1.22 129 

HASP Net key detected 

The Physical KeyId: 3548505881422726238 
CHARON Sentinel HASP License key sectionsection 
Reading 4032 bytes License Manager running at host: XEON4WAYW7
License Manager IP address: 192.168.1.22 

The License Number: nes000.msc.sanity.tests 
The License KeyId: 3548505881422726238 
The Master KeyId: 1712849125827774524 
Release date: 1621-JANSEP-20142015 
Release time: 1715:5315:4115 
Update number: 81 
End User name: Net-Time 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.

...

# ncu
CHARON Network Configuration Utility, STROMASYS (c) 2015 Version 1.4 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

...

  1. Ensure your license allows you to upgrade. If not, please generate a C2V file and send it to STROMASYS for update. See CHARON-VAX 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-VAX instances.
  4. Make sure that no template files (i.e. "mv3k6.cfg.template") have been used for your specific configuration. Otherwise copy those files to some save place.
  5. Login as "root" user.
  6. Remove the old CHARON-VAX version as described in the "xzz" chapter.
  7. Proceed with the same instructions on the new kit installation as described in "Installation" section.
    (info) Note that this time "yum" will request you to confirm the existing kit update. Confirm that.If a new license is required " section.

  8. Install the license for the new CHARON-VAX kit install it  it as described in "License installation" section. Otherwise just skip this step.

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

 

...

  1. ).

Back to Table of Contents