Page Comparison

AnchorTOCTOC Include PageKBCOMMON:KB-CSSstyleKBCOMMON:KB-CSSstyle

Introduction

CHARON-VAX products are distributed

Anchor

	TOC
	TOC

Include Page

	KBCOMMON:KB-CSSstyle
	KBCOMMON:KB-CSSstyle

Introduction

CHARON-VAX products are distributed in form of archive TAR.GZ files that contain RPM modules for different components. Generally it is recommended to install all the RPM modules but it is possible to omit some RPM files if they are not needed.

...

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 models	2	2

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.

...

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-19401.x86_64 2/4 Installing : charon-license-4.9-19401.x86_64 3/4 Installing : charon-vax-4.9-19401.x86_64 4/4 Verifying : aksusbd-7.63-1.i386 1/4 Verifying : charon-license-4.9-19401.x86_64 2/4 Verifying : charon-vax-4.9-19401.x86_64 3/4 Verifying : charon-utils-4.9-19401.x86_64 4/4 Installed: aksusbd.i386 0:7.63-1 charon-vax.x86_64 0:4.9-19401 charon-license.x86_64 0:4.9-19401 charon-utils.x86_64 0:4.9-19401 charon-license.x86_64 0:4.9-19401 charon-utils.x86_64 0:4.9-19401 Complete!

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

...

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

...

class	pagebreak

...

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

ethtool
bridge-utils
net-tools
iproute
NetworkManager

...

:4.9-19401 Complete!

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

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

Div

class	pagebreak

Info

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

ethtool
bridge-utils
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.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

CHARON-VAX home directory

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

The most important at this stage is the "/cfg" directory since it contains template configuration files with examples of typical configuration parameters and comments. We will focus our attention on this subject in the next chapter.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Specific user account creation

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

...

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

The most important at this stage is the "/cfg" directory since it contains template configuration files with examples of typical configuration parameters and comments. We will focus our attention on this subject in the next chapter:

# 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 -G disk,tape,cdrom,dialout,lock -g <user name> <user name>

Example:

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

Warning
The specific account created above does not allow to use physical consoles "`/dev/tty<N>`" as CHARON consoles. If you plan to map CHARON console to "`/dev/tty<N>`" use only "root" account for CHARON running.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Specific user account creation

Create a specific user account named "charon" for running 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:

...

Example:

...

Warning
The specific account created above does not allow to use physical consoles "`/dev/tty<N>`" as CHARON consoles. If you plan to map CHARON console to "`/dev/tty<N>`" use only "root" account for CHARON running.

...

class	pagebreak

License installation

Regular HASP USB dongle

If CHARON license is located on a regular USB dongle, just connect it to the host USB port.

Note
If the CHARON host is accessed remotely, please note that regular HASP licenses cannot be displayed and used to start a CHARON virtual machine. As a workaround it is possible to install CHARON as a daemon (service). This procedure will be described later.

Network HASP USB dongle

If the CHARON license is a network license (red USB dongle), it is possible either to connect it to the host USB port (to use it locally and provide it to other hosts on the local network at the same time) or to install it on a local network "license server" for remote access from this particular host.

If a remote license server is to be used:

...

Install the copied files using "yum".
Example:

...

Connect the network HASP dongle to one of the server USB ports.

Info
The network HASP (red dongles) licenses have no restrictions with respect remote access

Software license

If CHARON license is a software license (SL), it is installed on the host using the following procedure:

Run hasp_srm_view utility in the following way to get the host fingerprint file ("my_host.c2v" in this example):

...

Info
It is also possible to use the "hasp_update" utility for applying ".v2c" files.

Info
The Software Licenses (SL) are always network licenses, they have no restrictions with respect to being displayed or accessed via a remote connection.

Info
A "Provisional" (demo) license does not require collecting a fingerprint. For its installation start at step 3 in the sequence above

...

class	pagebreak

License validity verification

To check the CHARON license validity, invoke the hasp_srm_view utility to make sure that CHARON license is visible is correct:

Text of the license is displayed correctly by the hasp_srm_view utility, no error messages are shown.
The content of the license looks correct. For example: license number, major and minor versions, minimum and maximum build numbers, CHARON-VAX products and allowed hardware (CHARON-VAX models) should be checked. More details on the license content can be found in the CHARON-VAX Licensing chapter of this Guide.

Example:

# hasp_srm_view

...

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:

...

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)

Note
Reminder: If the CHARON host is accessed over a remote connection, please note that regular HASP licenses cannot be displayed and used in this case. As a workaround it is possible to install CHARON as a daemon (service). This procedure will be described later.

Troubleshooting

If the CHARON license content cannot be displayed by the hasp_srm_view utility or it is incorrect, check the license is available and correctly used:

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.

...

class	pagebreak

...

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

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.

...

Div

class	pagebreak

License installation

Regular HASP USB dongle

If CHARON license is located on a regular USB dongle, just connect it to the host USB port.

Note
If the CHARON host is accessed remotely, please note that regular HASP licenses cannot be displayed and used to start a CHARON virtual machine. As a workaround it is possible to install CHARON as a daemon (service). This procedure will be described later.

Network HASP USB dongle

If the CHARON license is a network license (red USB dongle), it is possible either to connect it to the host USB port (to use it locally and provide it to other hosts on the local network at the same time) or to install it on a local network "license server" for remote access from this particular host.

If a remote license server is to be used:

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 "/tmp"
Login as "root" to the server.
Switch to that directory.
Install the copied files using "yum".
Example:
# cd /tmp
# yum install aksusbd* charon-license-*

Connect the network HASP dongle to one of the server USB ports.

Info
The network HASP (red dongles) licenses have no restrictions with respect remote access

Software license

If CHARON license is a software license (SL), it is installed on the host using the following procedure:

Run hasp_srm_view utility in the following way to get the host fingerprint file ("my_host.c2v" in this example):
# hasp_srm_view -fgp my_host.c2v
Send the resulting file to STROMASYS. In return STROMASYS will provide you with a ".v2c" file, for example "your_license.v2c".
Copy the received file to any folder on the CHARON host, invoke the system default web browser and enter URL http://localhost:1947 to display the "Sentinel Admin Control Center" (ACC) web interface. This interface allows you to view and manage the CHARON licenses.
In the ACC perform the following steps: select Update/Attach from the menu on the left pane then use the Browse button to select the received file and click on the Apply File button to install the license.
Ensure that the software license is now visible in the "Sentinel Keys" section of the ACC.

Info
It is also possible to use the "hasp_update" utility for applying ".v2c" files.

Info
The Software Licenses (SL) are always network licenses, they have no restrictions with respect to being displayed or accessed via a remote connection.

Info
A "Provisional" (demo) license does not require collecting a fingerprint. For its installation start at step 3 in the sequence above

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

License validity verification

To check the CHARON license validity, invoke the hasp_srm_view utility to make sure that CHARON license is visible is correct:

Text of the license is displayed correctly by the hasp_srm_view utility, no error messages are shown.
The content of the license looks correct. For example: license number, major and minor versions, minimum and maximum build numbers, CHARON-VAX products and allowed hardware (CHARON-VAX models) should be checked. More details on the license content can be found in the CHARON-VAX Licensing chapter of this Guide.

Example:

# 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: 1422726238
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: 12-MAY-2018
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_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)

Note
Reminder: If the CHARON host is accessed over a remote connection, please note that regular HASP licenses cannot be displayed and used in this case. As a workaround it is possible to install CHARON as a daemon (service). This procedure will be described later.

Troubleshooting

If the CHARON license content cannot be displayed by the hasp_srm_view utility or it is incorrect, check the license is available and correctly used:

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.

Div

class	pagebreak

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.

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 "Allow Access to Remote Licenses" checkbox from the "Access to Remote License Managers" tab then press the "Submit" button to apply changes.

Note

Starting with Charon-AXP/VAX 4.9 for Linux and Charon-AXP/VAX version 4.8 for Windows the Charon emulator products do not follow the settings in the Sentinel ACC with respect to querying remote license servers and network visibility. They perform a broadcast search for network licenses even if this has been disabled in the Sentinel ACC. If this behavior has to be prevented for specific reasons, the network access of the system has to be temporarily restricted or disabled, for example by blocking the relevant traffic in a firewall. Another possibility would be to block access to the network license at the license server side.

Note that such methods can negatively impact other functions of the system or, in the case of blocking access to a network license on the server, even the functions on other license clients.

Info

It is also possible to leave several licenses available to CHARON-VAX 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-VAX checks its licenses from time to time starting with main license. If it becomes unavailable, it attempts to access the backup license.

...

Versions Compared

Old Version 41

New Version 42

Key

Table of contents

Introduction

Table of contents

Introduction

CHARON-VAX home directory

Specific user account creation

Specific user account creation

License installation

Regular HASP USB dongle

Network HASP USB dongle

Software license

License validity verification

Troubleshooting

License installation

Regular HASP USB dongle

Network HASP USB dongle

Software license

License validity verification

Troubleshooting