Anchor

	TOC
	TOC

Include Page

	KBCOMMON:KB-CSSstyle
	KBCOMMON:KB-CSSstyle

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Hardware Requirements

Number of CPU cores

...

class	pagebreak

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 product	Minimum number of host CPU cores	Recommended number of host CPU cores
HP AlphaServer 400 - HP AlphaServer 4100	2	2
HP AlphaServer DS10/DS10L/DS15	2	2
HP AlphaServer DS20/DS25	4	4
HP AlphaServer ES40/ES45	6	8
HP AlphaServer GS80	10	16
HP AlphaServer GS160	18	32
HP AlphaServer GS320	34	48

...

depends on the amount of HP Alpha memory to be emulated and on the number of CHARON-AXP instances to be executed on one host.
is calculated according to the following formula:
The minimum host memory = (2Gb + the amount of HP Alpha memory emulated) per CHARON-AXP instance.

Div

class	pagebreak

Disk storage

The total amount of disk space required for CHARON-AXP can be calculated as a sum of all the disk/tape image sizes plus 50 MB for the CHARON software plus the space required for the host operating system. Temporary disk storage is often needed when setting up a new virtual machine (for source disks backups storage, software installation kits, etc...).

...

class	pagebreak

...

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!

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, 2016 and Windows 10 templates.

The following workarounds are available:

Import the virtual machine from an older version of ESXi
Do not select "Red Hat Enterprise Linux 7 (64-bit)" nor "CentOS 7 (64-bit)" during virtual machine creation but select "Linux" as "Guest OS family" and "Other 3.x Linux (64-bit)" as Guest OS version".

...

Software Requirements

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

...

Host system preparation

Info
The automatic installation of updates must be disabled. Updates to the CHARON host must be done only in specific service maintenance periods established by the system administrator. Before applying new updates one must shutdown the operating system running on CHARON and stop all the running CHARON instances and services.

If a network-wide license (red dongle or software license) is going to be used, do the following:

On the server side (where the network license will reside): open port 1947 for both TCP and UDP
On the client side, if broadcast search for remote licenses is to be used, UDP traffic from port 1947 of the license server to ports 30000-65535 of the client must be permitted
Both on server and client sides: set default gateway

Please consult with your Linux User's Guide on details.

Info
If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "`/usr/sbin/hasplmd`" daemon.

...

class	pagebreak

Before installation

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:

...

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

.

Create a directory for the CHARON-AXP distribution, copy the TAR.GZ files there and change to this directory as shown in the following example:

...

.

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:

...

Warning

title	WARNING

If you plan to install CHARON-VAX 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-AXP, please stop all running CHARON virtual machines and uninstall CHARON products before proceeding with the installation steps described below.

...

Distribution preparation

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

...

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:

...

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

...

class	pagebreak

Switch to that directory:

...

Example:

...

The distribution directory contains the following RPM files:

...

File name

...

Description

...

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-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.rpmcharon-mtd-4.10-20200.el74.x86_64.rpm

...

class	pagebreak

Installation

Issue the following command to install all the RPM files present in the directory:

...

Enter "y" to agree to install all the listed packages.

Example:

Dependencies Resolved

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Software Requirements

Red Hat Enterprise Linux 8.x - 64bit
Red Hat Enterprise Linux 7.x - 64bit
Linux Centos 8.x - 64bit
Linux Centos 7.x - 64bit
VMware ESXi 5.5 and 6.0 up to 6.7 (requires a supported Linux operating system on top of a ESXi virtual machine)

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.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Host system preparation

Info
The automatic installation of updates must be disabled. Updates to the CHARON host must be done only in specific service maintenance periods established by the system administrator. Before applying new updates one must shutdown the operating system running on CHARON and stop all the running CHARON instances and services.

If a network-wide license (red dongle or software license) is going to be used, do the following:

On the server side (where the network license will reside): open port 1947 for both TCP and UDP
On the client side, if broadcast search for remote licenses is to be used, UDP traffic from port 1947 of the license server to ports 30000-65535 of the client must be permitted
Both on server and client sides: set default gateway

Please consult with your Linux User's Guide on details.

Info
If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "`/usr/sbin/hasplmd`" daemon.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Before installation

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
.
Create a directory for the CHARON-AXP distribution as shown in the following example:
# mkdir /charon_dist
.
On RHEL/CentOS 7 and 8, the "libev" package is required. If it is reported as missing during CHARON installation on RHEL 7/8, 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

Warning

title	WARNING

If you plan to install CHARON-VAX 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-AXP, please stop all running CHARON virtual machines, uninstall CHARON products and reboot the Linux server (recommended) before proceeding with the installation steps described below.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Distribution preparation

Copy the download kit (in /tmp for example) to the folder created in the previous chapter:

# cp /tmp/charon-axp-<VER>-<BN>.<ZZ>.tar.gz /charon_dist

where:

Item

Description

VER

Version of CHARON-AXP product, for example 4.11

BN

Build Number of CHARON-AXP product, for example 20404

ZZ

CHARON-AXP target operating system identifier where:

ZZ = "el8" for CentOS/Red Hat Enterprise Linux 8
ZZ = "el74" for CentOS/Red Hat Enterprise Linux 7
ZZ = "el65" for Red Hat Enterprise Linux 6

Extract the contents of the distribution .tar.gz file to the current directory:

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

Example:

# tar -xvzf charon-axp-4.11-20404.el74.tar.gz

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

Switch to that directory:

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

Example:

# cd charon-axp-4.11-20404.el74

The distribution directory contains the following RPM files:

File name	Description
`aksusbd-7.63-1.i386.rpm`	HASP Run-time
`charon-axp-VER-BN.ZZ.x86_64.rpm`	CHARON-AXP
`charon-license-VER-BN.ZZ.x86_64.rpm`	CHARON Libraries
`charon-mtd-VER-BN.ZZ.x86_64.rpm`	MTD utility
`charon-utils-VER-BN.ZZ.x86_64.rpm`	CHARON Utilities

Example:

# ls
aksusbd-7.63-1.i386.rpm
charon-axp-4.11-20404.el74.x86_64.rpm
charon-license-4.11-20404.el74.x86_64.rpm charon-mtd-4.11-20404.el74.x86_64.rpm charon-utils-4.11-20404.el74.x86_64.rpm

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Installation

Issue the following command to install all the RPM files present 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 7.63-1 /aksusbd-7.63-1.i386 2.9 M
charon-axp x86_64 4.1011-20200 20404 /charon-axp-4.1011-2020020404.el74.x86_64 260 M
charon-license
x86_64 4.1011-20200 20404 /charon-license-4.1011-2020020404.el74.x86_64 2.9 M
charon-utils
x86_64 4.1011-20200 20404 /charon-utils-4.1011-2020020404.el74.x86_64 1.8 M charon-mtd x86_64 4.1011-20200 20404 /charon-mtd-4.1011-2020020404.68704.el74.x86_64 1.2 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.1011-2020020404.x86_64 2/5 Installing : charon-mtd-4.1011-2020020404.x86_64 3/5
Installing : charon-license-4.1011-2020020404.x86_64 4/5
Installing : charon-axp-4.1011-2020020404.x86_64 5/5
Verifying : aksusbd-7.63-1.i386 1/5
Verifying : charon-license-4.1011-2020020404.x86_64 2/5
Verifying : charon-axp-4.1011-2020020404.x86_64 3/5
Verifying : charon-utils-4.1011-2020020404.x86_64 4/5 Verifying : charon-mtd-4.1011-2020020404.x86_64 4/5

Installed:
aksusbd.i386 0:7.63-1 charon-axp.x86_64 0:4.1011-20200 20404
charon-license.x86_64 0:4.1011-20200 20404 charon-utils.x86_64 0:4.1011-2020020404 charon-mtd.x86_64 0:4.1011-2020020404

Complete!

Div

class	pagebreak

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

...

"root") to apply the PATH settings or execute the following command:

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

If "putty" terminal emulator is going to be used as an additional option copy the following file to your home directory:

# mkdir -p $HOME/.config/putty/sessions (if it does not already exist)# cp /opt/charon/putty/sessions/CHTERM-VT100 $HOME/.config/putty/sessions

Info

Note that the "charon-utils" package has the following dependencies:

ethtool
bridge-utils
net-tools
iproute
NetworkManager

During "charon-utils" 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 the executable files
/cfg	Contains the configuration files templates
/doc	Contains the documentation
/log	Contains the log files
/disks	Contains the disk containers
/drivers	Contains the CHARON drivers

...

Create a specific user account named "charon" for running CHARON:

# useradd # 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 into these specific groups:

# usermod# usermod -G disk,tape,cdrom,dialout,lock -g <user name> <user name>

Example:

# usermod# usermod -G disk,tape,cdrom,dialout,lock -g tommy tommy

Div

class	pagebreak

Re-login to apply changes.

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

License installation

Regular HASP USB dongle

...

Copy the aksusbd-7.63-1.i386.rpm and charon-license-4.9-<build>.<OS identifier>.x86_64.rpm files (see above) to the server, for example to "/tmp".
Login as "root" on the server.
Switch to that directory.
Install the copied files using "yum".
Example:
# cd # cd /tmp
# yum # yum install aksusbd* charon-license-*

...

# 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: 1422726238License Type: License Dongle (Network Capable)
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: 1210-SEPMAR-2016 2020
Release time: 15:15:15
Update number: 1
End User name: MSC
Purchasing Customer name: STROMASYS...

...

Note

If multiple licenses are available, it is possible to check them using the "-all" parameter with the hasp_srm_view utility in the following way:

# hasp

# hasp_srm_view -all

It it also possible to display the license content for one specific key using the "-key" parameter and specifying the Key Id (see "# hasp_srm_view -h" for more)

...

Invoke the system default web browser and enter the URL http://localhost:1947 to display the "Sentinel Admin Control Center" (ACC) web interface.
Click on "Sentinel Keys" link to open the corresponding page.
Make sure that one and only one CHARON HASP or SL license is present.

To facilitate troubleshooting, Stromasys recommends to enable logging from the Sentinel Admin Control Center as described in this article: Enabling logging in Sentinel Admin Control Center.

Problem	Action
No license is displayed	Make sure that all the recommendations above about remote access to the host are fulfilled (if remote access takes place), that the HASP USB key is not broken and its LED indicator is lit (meaning that it is used by the host).
Only one License key / SL is seen and its content is incorrect	Contact STROMASYS to request a new license update.
Several License keys / SLs are displayed	Remove all of them except the one provided by STROMASYS for the just installed version of CHARON.

...

Info

It is also possible to leave several licenses available to CHARON-AXP at the same time but in this case they have to be specified in the configuration file.

Example:

set session license_key_id=1877752571

It is also possible to have one "main" and one "backup" license in case the main license becomes unavailable:

set session license_key_id="1877752571,354850588"

CHARON-AXP checks its licenses from time to time starting with the main license. If it becomes unavailable, it attempts to access the backup license.

...

Interfaces Dedicated to State
---------- ------------ ------------
eth0 host connected to host
eth1 host disconnected from host lo host unmanaged by host virbr0-nic bridge unmanaged by bridge

================================================================== bridge name bridge id STP enabled interfaces ================================================================== virbr0 8000.5254004608c0 yes virbr0-nic

==================================================================

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Add VLAN
6 - Remove VLAN
7 - Print status
8 - Exit
:> 1

...

Interfaces Dedicated to State
---------- ------------ ------------
eth0 host         connected to host
eth1 CHARON       disconnected from hostlo host unmanaged by host virbr0-nic bridge unmanaged by bridge------------
eth0 host         connected to host
eth1 CHARON       disconnected from hostlo host unmanaged by host virbr0-nic bridge unmanaged by bridge

================================================================== bridge name bridge id STP enabled interfaces ================================================================== virbr0 8000.5254004608c0 yes virbr0-nic

====================================== bridge name bridge id STP enabled interfaces ================================================================== virbr0 8000.5254004608c0 yes virbr0-nic

==================================================================

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Add VLAN
6 - Remove VLAN
7 - Print status
8 - Exit

:>

Enter "8" to return to the console prompt.

Now "eth1" can be used by CHARON-AXP.

...

class	pagebreak

Manual Configuration

Choosing a network interface

To choose an interface to be used for CHARON networking, do the following:

...

Choose an interface to be used by CHARON, for example "eth1"

Designation of network interface to CHARON

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 this case it is "1") and make sure that all the IP-setup related parameters are removed. The file must look like this:

...

Switching off the offload parameters

Determine what additional parameters are currently set to "on" on the host network adapter to be used by CHARON using the following command:

...

Example:

# ethtool

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Add VLAN
6 - Remove VLAN
7 - Print status
8 - Exit

:>

Enter "8" to return to the console prompt.

Now "eth1" can be used by CHARON-AXP.

Div

class	pagebreak

Manual Configuration

Choosing a network interface

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 an interface to be used by CHARON, for example "eth1"

Designation of network interface to CHARON

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 this case it is "1") and make sure that all the IP-setup related parameters are removed. The file must look like this:

DEVICE="eth1"
HWADDR="00:06:2B:00:6A:87"
NM_CONTROLLED="no"
ONBOOT="no"

Switching off the offload parameters

Determine what additional parameters are currently set to "on" on the host network adapter to be used by CHARON using the following command:

# 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

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

Use "ethtool" to switch off all the offload parameters:

...

Example:

...

class	pagebreak

For the example above let's create a temporary file containing the commands to be executed at system startup as the offload parameters must be switched off following 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 the name of the file is "offload_off_eth1.txt". To execute it on system startup, execute the following command (example):

...

Final steps

Reboot the host system
Login as user "charon"
Verify the offload parameters are effective

...

Upgrade to new version

To upgrade an already installed CHARON-AXP kit to a more recent one:

...

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

...

Div

class	pagebreak

For the example above let's create a temporary file containing the commands to be executed at system startup as the offload parameters must be switched off following 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 the name of the file is "offload_off_eth1.txt". To execute it on system startup, execute the following command (example):

# cat offload_off_eth1.txt >> /etc/rc.d/rc.local

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Final steps

Reboot the host system
Login as user "charon"
Verify the offload parameters are effective

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Upgrade from previous version

To upgrade an already installed CHARON-AXP kit to a more recent one:

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-AXP for Linux utilities - 'hasp_srm_view' utility
Prepare the new kit RPM files as it is described in "695402677" and "695402677" sections.
Stop all running CHARON-AXP instances.
Make sure that no template files (i.e. "es40.cfg.template") have been used for your specific configuration otherwise copy those files to a dedicated folder.
Login as "root" user.
Remove the old CHARON-AXP version as described in the "CHARON-AXP for Linux deinstallation" chapter and reboot the Linux server (recommended).
Proceed with the instructions on the new kit installation as described in the "695402677" section.
Once installation is completed, it is recommended to reboot the Linux server (possible issues with licenses detection could occur).
Install the license for the new CHARON-AXP as described in the "695402677" section.
Start all the CHARON-AXP services stopped at step #3.

Note

If you did not reboot your Linux server at step 6, you may experience issues with 'aksusbd' service installation and then license detection.

Example:

Installing : aksusbd-8.13-1.x86_64 1/5Failed to execute operation: Access deniedFailed to restart aksusbd.service: Access denied

To solve this problem, remove all Charon installed product and restart from step 6 above.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Versions Compared

Old Version 90

New Version Current

Key

Hardware Requirements

Number of CPU cores

Disk storage

Software Requirements

Host system preparation

Before installation

Distribution preparation

Installation

Software Requirements

Host system preparation

Before installation

Distribution preparation

Installation

License installation

Regular HASP USB dongle

Manual Configuration

Choosing a network interface

Designation of network interface to CHARON

Switching off the offload parameters

Manual Configuration

Choosing a network interface

Designation of network interface to CHARON

Switching off the offload parameters

Final steps

Upgrade to new version

Final steps

Upgrade from previous version

Page Comparison

Versions Compared

Old Version 90

New Version Current

Key

Hardware Requirements

Number of CPU cores

Disk storage

Software Requirements

Host system preparation

Before installation

Distribution preparation

Installation

Software Requirements

Host system preparation

Before installation

Distribution preparation

Installation

License installation

Regular HASP USB dongle

Manual Configuration

Choosing a network interface

Designation of network interface to CHARON

Switching off the offload parameters

Manual Configuration

Choosing a network interface

Designation of network interface to CHARON

Switching off the offload parameters

Final steps

Upgrade to new version

Final steps

Upgrade from previous version