Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add pointer how to enable logging in ACC.

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

...

  • Upgrading to this Charon-PAR from an older version requires a license update. Please contact your VAR or Stromasys representative to plan the update.
  • Charon-PAR version 3.0 and higher is incompatible with licenses of earlier versions. Earlier product versions are incompatible with licenses for Charon-PAR 3.0 and higher. Charon-PAR/PA3 licenses for version 3.0 are not backward compatible for emulators running with version 2.x.

Please note: The Charon-PAR version 3.0 and higher emulator kits contain the haspvlib library and the hasp_srm_view and hasp_update utilities. This means that there may be installation conflicts with other Charon emulator products on the same host systems. Such conflicts can be overcome either by not installing the conflicting modules of the other products (if possible), or by forcing the installation of the Charon-PAR kit. Please refer to the documentation of your host system (man rpm) in such cases and ensure that this will not negatively influence any other installed products. If you use the --force option for an installation, please uninstall older packages of the same product before.

Charon-PAR Software Packages Overview

...

The following table lists the required installation packages (the placeholder <version> denotes the version of the package, for example, 3.0.13):

par emulator executable, template configuration files for the different supported hardware models, PuTTY configurations, etc. for Linux systems.par<version> emulator executable, template configuration files for the different supported hardware models, PuTTY configurations, etc. for Linux 8.x systems.
PackageDescription
Sentinel runtime environment. Required for licensing the Charon-PAR software.
aksusbd-7.63-1.i386.rpm32-bit package for CentOS/RHEL 7.x; requires the 32-bit glibc package.
aksusbd-8.13-1.x86_64.rpm64-bit package for RHEL 7.7 and higher; RHEL 8; CentOS 8. (see also https://docs.sentinel.thalesgroup.com/ldk/LDKdocs/rte/linux-rh-suse-centos.html)
Charon-PAR tape utilityemulator
charon-mtdpar-<version>.el7.x86_64.rpmCharon-PAR tape utility for CentOS/RHEL emulator executable, template configuration files for the different supported hardware models, PuTTY configurations, etc. for Linux 7.x systems.
charon-mtdpar-<version><version>.el8.x86_64.rpmCharon-PAR tape utility for CentOS/RHEL emulator executable, template configuration files for the different supported hardware models, PuTTY configurations, etc. for Linux 8.x systems.
Charon-PAR emulatorutilities
charon-mtd-<version>.el7.x86_64.rpmCharon-PAR tape utility for CentOS/RHEL 7.x
charon-mtd-<version>.el8.x86_64.rpmCharon-PAR tape utility for CentOS/RHEL 8.x
xhpterm-free-<version>.el7.x86_64.rpmTerminal emulation for block mode applications (CentOS/RHEL 7.x)
xhpterm-free-<version>.el7.x86_64.rpmTerminal emulation for block mode applications (CentOS/RHEL 8.x)

Obtaining the Charon-PAR software:

...

  • For the installation of a Charon-PAR/PA3 emulated system, a preinstalled MPE/iX 7.5 disk image (mpe75a.dsk.bz2) is required. This will be provided by Stromasys.
  • For the installation of a Charon-PAR/PA9 emulated system, a HP-UX ISO is required. 

...

Installation OptionDescription
Package manager (uses repositories, takes care of dependencies, etc.)

# yum install <package-name>

On Linux 8.x, replace yum with dnf. if a filename is specified, locally stored RPM packages can be installed.

Command to install individual local packages.# rpm -i </path/to/package>

...


StepCommand
1Log in as the privileged user on the system ("root").
2Go to the directory in which the rpm packages were stored.

cd <path-to-kits-dir>

3Install the Charon-PAR emulator and utilities packages.

# yum install charon*.rpm xhpterm*.rpm (Linux 7.x)

# dnf install charon*.rpm xhpterm*.rpm (Linux 8.x)

or

# rpm -i *.rpm

...

Post-Installation Tasks

Installing PuTTY

A recommended post-installation task is the installation of PuTTY to connect to the emulated console. The associated package is part of the EPEL repository. 

PuTTY installation steps CentOS/Red Hat 7.x:


StepCommand
1Log in as the privileged user on the system ("root").
2If the additional repository has not yet been installed, install it. The rpm package to install the EPEL repository is included in the extras repository of Red Hat and CentOS.Older Red Hat / CentOS 7 versions:
StepCommand1Log in as the privileged user on the system ("root").
2Check the PuTTY version available in the EPEL repository for CentOS / Red Hat 7.xUsing a web-browser, go to
http://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/p/
and determine the filename of the PuTTY package.
It will be in the format putty-<version>.el7.x86_64.rpm
3Install PuTTY.

yum --enablerepo=extras install epel-release

Current Red Hat and CentOS versions (version 7 example):


# yum install Up-to-date information can be found on the following page: https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

Additionally recommended on Red Hat 7 (as EPEL packages may depend on the extras repositories:

# subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms"

Up-to-date information can be found on the following page: https://fedoraproject.org/wiki/EPEL

3Install PuTTY.yum install putty
4

If you used PuTTY before, you will have a .putty or .config/putty directory under your home directory already.

If the PuTTY configuration directory does not already exist, create the .config/putty directory in the home directory of the root user.

Start PuTTY: # putty

Select and load the default settings.

Click on Save.

Exit PuTTY.

5Copy the Charon-PAR profiles to the PuTTY sessions directory of the root user (depending on where you stored you session data).

cp /opt/charon/cfg/PAR* /root/.putty/sessions

or

# cp /opt/charon/cfg/PAR* /root/.config/putty/sessions

Div
classpagebreak

PuTTY installation steps CentOS/Red Hat 8.x:

At the time of writing, PuTTY is not yet included in the CentOS and Red Hat EPEL version 8 repositories. However, it is possible to install the package from the EPEL repository for Linux version 7 using the following steps:

# dnf install \
http://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/p/putty-
<version>.el7.x86_64.rpm
wiki/EPEL

3Install PuTTY.yum install putty
4

If you used PuTTY before, you will have a .putty or .config/putty directory under your home directory already.

If the PuTTY configuration directory does not already exist, create the .config/putty directory in the home directory of the root user.

Start PuTTY: # putty

Select and load the default settings.

Click on Save.

Exit PuTTY.

5Copy the Charon-PAR profiles to the PuTTY sessions directory of the root user (depending on where you stored you session data).

cp /opt/charon/cfg/PAR* /root/.putty/sessions

or

# cp /opt/charon/cfg/PAR* /root/.config/putty/sessions

Please note: in some versions of CentOS/RHEL 8 PuTTY was not included in the EPEL repository. In such cases, the version from RHEL/

.config/putty/sessions

CentOS 7 could be used.

Div
classpagebreak



Installing the Linux Toolkit

This is not a mandatory, but a recommended step.

The Linux Toolkit support the management of emulator related tasks, such as

Please refer to Charon-PAR Linux Toolkit for further information.
  • License Management
  • Starting and stopping the emulator
  • Log file monitoring
  • Alert management
  • Information collection to facilitate product suppprt

Stromasys will provide you with a download link for the Linux Toolkit.

  • Alert management
  • Information collection to facilitate product suppprt

Stromasys will provide you with a download link for the Linux Toolkit.

Please refer to Charon-PAR Linux Toolkit for further information.

Sentinel License Driver Post-Installation Tasks

The following post-installation tasks are strongly recommended to improve security and to enable additional trouble-shooting options:


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