Versions Compared

Old Version 44

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version Current

changes.mady.by.user Kirill Nikolaev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

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

When starting, the CHARON-VAX software checks the available number of host CPU cores. Currently, this check is based on the maximum number of VAX CPUs that can be emulated, not on the number of the actually configured VAX CPUs. Therefore the number of host CPU cores recommended for the maximum number of emulated CPUs - as shown in the right column of the table above - must be available. If the available number of host CPU cores is below this number, CHARON-VAX will issue a warning message even if the requirements for the configured number of VAX CPUs are fulfilled. The CHARON-VAX software will work despite this warning if the requirements for the configured number of VAX CPUs are fulfilled.

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.

...

Info

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

The following workarounds are avaibleavailable:

  • import Import the virtual machine from an older version of ESXi
  • do not select Windows Server 2012 or 2016 Do not select "Red Hat Enterprise Linux 7 (64-bit)" nor "CentOS 7 (64-bit)" during virtual machine creation but "Windows 10/64bit" or "Other/Other 64bit" for examplebut select "Linux" as "Guest OS family" and "Other 3.x Linux (64-bit)" as Guest OS version".

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

...

  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-VAX distribution, copy the TAR.GZ files there and change to this directory as shown in the following example:

    # mkdir /charon_dist
    # cp /tmp/charon-vax-4.9-1940119402.el74.tar.gz /charon_dist
    # cd /charon_dist


...

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

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

    where:

     

    Description

    VER

    Version of CHARON-VAX product, for example 4.9

    BN

    Build Number of CHARON-VAX product, for example 1940119402

    ZZ

    CHARON-VAX 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.9 the value is 'el65'.

    Example:

    # tar -xvzf charon-vax-4.9-1940119402.el74.tar.gz 

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

  2. Switch to that directory:

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

    Example:

    # cd charon-vax-4.9-1940119402.el74

         

  3. The distribution directory contains the following RPM files:

    File name

    Description

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

    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

    Example:

    # ls
    aksusbd-7.63-1.i386.rpm
    charon-vax-4.9-1940119402.el74.x86_64.rpm
    charon-license-4.9-1940119402.el74.x86_64.rpm
    charon-utils-4.9-1940119402.el74.x86_64.rpm     

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

...

Dependencies Resolved  

================================================================================ 
Package Arch Version Repository Size 
================================================================================ 
Installing: 
aksusbd i386 7.63-1 /aksusbd-7.63-1.i386 2.9 M 
charon-vax x86_64 4.9-19401 19402 /charon-vax-4.9-1940119402.68704.el74.x86_64 260 M 
charon-license 
x86_64 4.9-19401 19402 /charon-license-4.9-1940119402.68704.el74.x86_64 2.9 M 
charon-utils 
x86_64 4.9-19401 19402 /charon-utils-4.9-1940119402.68704.el74.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

...

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.9-1940119402.x86_64 2/4 
Installing : charon-license-4.9-1940119402.x86_64 3/4 
Installing : charon-vax-4.9-1940119402.x86_64 4/4 
Verifying : aksusbd-7.63-1.i386 1/4 
Verifying : charon-license-4.9-1940119402.x86_64 2/4 
Verifying : charon-vax-4.9-1940119402.x86_64 3/4 
Verifying : charon-utils-4.9-1940119402.x86_64 4/4 

Installed: 
aksusbd.i386 0:7.63-1 charon-vax.x86_64 0:4.9-19401 19402 
charon-license.x86_64 0:4.9-19401 19402 charon-utils.x86_64 0:4.9-19401 19402 

Complete!

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

...

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

...

License validity verification

...

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 the local network (or by disabling remote access to network licenses from the CHARON host - see detailed explanations below).

For license servers accessible only via non-broadcast search it is also possible to disable access to network licenses if only a local license is to be used: Click on the "Configuration" link to open the "Configuration for Sentinel Manager" page.

Uncheck the "Allow Access to Remote Licenses" checkbox from the "Access to Remote License Managers" tab then press the "Submit" button to apply changes.

...

  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-VAX for Linux utilities - 'hasp_srm_view' utility
  2. Prepare the new kit RPM files as it is described in "Before installation" and "DistributionpreparationDistribution 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 a dedicated folder.
  5. Login as "root" user.
  6. Remove the old CHARON-VAX version as described in the "CHARON-VAX for Linux deinstallation" chapter.
  7. Proceed with the same instructions on the new kit installation as described in the "Installation" section.

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

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

...