Product Documentation and Knowledge Base - HomeDocumentation


Charon-VAXCharon-AXPCharon-PDPCharon-SSPCharon-PAR

Introduction

Table of contents

Important note

This document applies to Linux Toolkit version 1.48

Kit download

To download the kit, you must issue a request via email to the Stromasys support team (support@stromasys.com) or ask your reseller

Prerequisites

  • Basic knowledge of Unix commands

  • Basic knowledge of Charon products

  • Charon qualified versions:

    Charon-AXP V4.5 Build 155-05 (+ patches)

    Charon-AXP V4.6 Build 166-03 (+ patches)

    Charon-AXP V4.7 Build 171-01 (+ patches)

    Charon-AXP V4.8 Build 183-02 (+ patches)

    Charon-VAX V4.6 Build 165-02 (+ patches)

    Charon-VAX V4.7 Build 171-01 (+ patches)

    Charon-VAX V4.8 Build 183-02 (+ patches)


  • Scripts have been tested and validated on the following Linux distributions/versions:

    CentOS 7

    Red Hat Enterprise Linux Server release 6.x

    Red Hat Enterprise Linux Server release 7.x

     



  • Some packages have to be installed on the Charon server:

    • Mandatory packages:
      • glibc.i686
      • bc
      • perl
      • at

    • Recommended packages:
      • telnet : recommended for connection from the Charon server to the virtual machine console
      • expect : recommended if ssh cannot be used to execute shutdown commands from the console
      • evince : recommended for reading online documentation
      • postfix : recommended, Mail Transport Agent used to send emails
      • firefox : recommended for checking and updating licenses, accessing online documentation
        .

  • All described operations will have to be performed on the Charon server and logged in as 'root' (no other user supported).
    (warning)The 'menu' must be used by one user at a time only

  • Charon-AXP and Charon-VAX installations are supported when installed in /opt/charon folder only

  • Mail service must have been configured. Mail transfer agent can be postfix, sendmail, ...

  • (warning) Within the Charon virtual machines configuration files:
    • do not use spaces or tabs between a parameter and its value as the toolkit does not handle this correctly, i.e.: parameter=value is correct, parameter = value is not correct.
    • do not add devices parameters on the same line, please split the line in 2 lines

      Unsupportedset PKA container[600]= "/home/vdisk/axp/ALPHA084.iso" media_type[600]="RRD47"

      Supported

      set PKA container[600]= "/home/vdisk/axp/ALPHA084.iso"
      set PKA media_type[600]="RRD47"

Conventions

Throughout the document(s) these conventions are followed

Notation

Description

$

The dollar sign in interactive examples indicates an operating system prompt for VMS.

The dollar sign can also indicate non superuser prompt for UNIX / Linux.

#

The number sign represents the superuser prompt for UNIX / Linux.

>The right angle bracket in interactive examples indicates an operating system prompt for Windows command (cmd.exe).

User input

Bold monospace type in interactive examples indicates typed user input.

<path>

Bold monospace type enclosed by angle brackets indicates command parameters and parameter values.

Output

Monospace type in interactive examples, indicates command response output.

[ ]

In syntax definitions, brackets indicate items that are optional.

...

In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times.

dsk0

Italic monospace type, in interactive examples, indicates typed context dependent user input.

The following definitions apply

TermDescription
HostThe system on which the emulator runs, also called the Charon server
GuestThe operating system running on a Charon instance, for example, Tru64 UNIX, OpenVMS, Solaris, MPE or HP-UX

Note related to display/edit options

Some menu options will allow you to display or edit files using available editors (if installed) between:

EditorInterfaceDescription
geditGraphicalWindows notepad like
emacsGraphicalWindows notepad like, advanced
nanoTextBasic text editor
viTextAdvanced users
vimTextAdvanced users with more features (colored & highlights)
gvimGraphicalAdvanced users with more features (colored & highlights)

Select the one you prefer or refer to 'man pages' for more information on available ones.

Note related to emails

There are 2 kinds of emails:

TypeDescription
Results

Some menu options will allow you to send results via email.

  • Example: license display, log and configuration files.

  • The recipient will then be unique

AlertsBy default, the alert script will send alerts via email (plus 'wall' notifications if enabled). A recipients list can be defined in this case.
  • Wall notification can be enabled/disabled from the menu
  • The alert script can be customized. You can for example use command lines linked to your monitoring software and disable emails.

(info) Do not use Stromasys email address to send results directly, for example to support@stromasys.com. The sender will be unknown to us, it is then recommended to send results to yourself first and to forward us the email you received.

(warning) Both use 'sendmail' command to send emails. Mail transfer agent can be postfix, sendmail, ...



© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.