Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update for PDF export

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

...

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

Div
classpagebreak


Hardware Requirements

Number of CPU cores

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.

...

The following table lists 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 networking requires dedicated host Ethernet adapters; their number must be equal to the emulated adapters to be configured in CHARON-AXP. One adapter (optionally) can be left to the host for TCP/IP networking, management interface, etc.

It is also possible to use virtual network interfaces, but for performance considerations, it is recommended to use physical ones only.

Note

For VMware-based CHARON hosts it is mandatary to use the "E1000" virtual network adapter. Please avoid usage of the "E1000E" adapter since it may lead to problems with some TCP/IP services!

...

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

The following workarounds are available:

...

.

It is also possible to use virtual network interfaces, but for performance considerations, it is recommended to use physical ones only.

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

...

  • Red Hat Enterprise Linux 7.x, 64bit
  • Red Hat Enterprise Linux 6.5 - 6.10, 64bit
  • Linux Centos 7.x, 64bit
  • VMware ESXi 5.5 and 6.x up to 6.7 (requires a supported Linux operating system on top of a ESXi virtual machine)
Note

If PBXGA graphics card is going to be used the resolution of CHARON host screen must be not less than 1280x1024 to provide an ability to display the graphics monitor emulation properly.


Note

For CentOS, a connection to the internet is required to install the glibc.i686 package which is not included in the Standard distribution DVD. If there's no connection available, please use the "Everything" distribution DVD.

...

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

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

    where:

     

    Description

    VER

    Version of CHARON-AXP product, for example 4.10

    BN

    Build Number of CHARON-AXP product, for example 20200

    ZZ

    CHARON-AXP 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.10 the value is 'el65'.

    Example:

    # tar -xvzf charon-axp-4.10-20200.el74.tar.gz 

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


    Div
    classpagebreak



  1. Switch to that directory:

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

    Example:

    # cd charon-axp-4.10-20200.el74
    Divclasspagebreak


  2. The distribution directory contains the following RPM files:

    File name

    Description

    charon-axp-VER-BN.ZZ.x86_64.rpmCHARON-AXP

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

    Example:

    # ls
    aksusbd-7.63-1.i386.rpm
    charon-axp-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

...