Page Comparison

...

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

...

...

The table below lists the minimum and recommended number of CPUs required for each product:

When starting, the CHARON-VAX software checks the available number of host CPU cores. This check is based on the maximum number of VAX CPUs that can be emulated. 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. The CHARON-VAX software will work despite this warning.

...

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

   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

   Div
   class pagebreak

   .

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.10-20200.el74.tar.gz /charon_dist # cd /charon_dist

   
   

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

   
   

...

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.10
   BN	Build Number of CHARON-VAX product, for example 20200
   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.10-20200.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.10-20200.el74

        

   Div
   class pagebreak

   
   

3. The distribution directory contains the following RPM files:

   File name	Description
   charon-vax-VER-BN.ZZ.x86_64.rpm	CHARON-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
   charon-mtd-VER-BN.ZZ.x86_64.rpm	MTD utility

   Example:

   # ls aksusbd-7.63-1.i386.rpm charon-vax-4.10-20200.el74.x86_64.rpm charon-license-4.10-20200.el74.x86_64.rpm charon-utils-4.10-20200.el74.x86_64.rpm charon-mtd-4.10-20200.el74.x86_64.rpm

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

...

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 installation481984582" and "Distribution preparation481984582" 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 "Installation481984582" section.

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

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

...