Versions Compared

Key

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

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

Table of contents

Table of Contents
excludeTable of contents

Installation

The tools are provided in a tar file that must be extracted into the /opt/charon/utils folder.

  • If the folder does not exist, by default created at Charon installation, create it and copy the tar file in this directory. In the example below, we assume the tar file was downloaded in the /charon folder:

    # mkdir -p /opt/charon/utils
    # cp /charon/Charon-PAR_Linux_Toolkit.V1.34.tar /opt/charon/utils

    .

  • Extract the files from the tar file to the Charon installation directory, subdirectory ‘utils’

    # cd /opt/charon/utils
    # tar –xf Charon-PAR_Linux_Toolkit.V1.34.tar

    .

  • Execute the installation script:

    # ./menusetup

    .

  • The setup will check first your terminal settings, if set to VT100 you will not be able to continue until you set the TERM value to VT200, dtterm or xterm (see how to here: Configuration)

...

  • Mandatory and recommended packages installation will be checked.
    • (warning) If some mandatory packages are missing you will not be able to continue.
    • (info) If some recommended packages are missing, installation will continue. Installation of these packages can be done later if needed

...

  • Recurring jobs will be added in the crontab file:
    • if the crontab file does not exist, it will be automatically filled
    • if it already exists, you will be prompted to update it via the selected editor: a check will be performed and the missing entries will be added
Div
classpagebreak

...



  • Alerts parameters will now have to be filled (see Alerts management chapter for more if needed)
    • Select between HTML or pure TEXT emails
    • Mail recipients list (used for alerts, not for sending files like log and configuration files for example)
    • Mail sender (can be used to change the displayed name of the sender)
    • Customize emails footer: if needed, add here your disclaimer, information on the CHARON Charon server or any information you think useful
    • Enable/disable wall alert messages
    • Install or update the alert script. It can be customized later, in this case it is recommended to do this once the virtual machines are installed
    • Select the alert level from guests log files: 0 = none, 1 = informational+warning+error entries, 2 = warning+error entries (default), 3 = error entries only

    • View alerts if any

    • Send immediate alert on dongle removal or not (with counter alert)
    • (info) The alerts simulator can be used to send all the know alerts via email (for checks)

    • Reduce the number of warning messages sent on dongle removal or not

      Example:

       

  • When the setup is completed, either log out and login again to define the command aliases or execute the following command:

    # . /etc/profile.d/charon_menu.sh


Div
classpagebreak


Upgrade

Except if mentioned in the release notes, an upgrade does not require the Charon virtual machines to be stopped.

To upgrade the kit, you will need to:

  • read the release notes available here: Charon-PAR Linux Toolkit - Current version
    .
  • copy and extract the files from the tar file to the CHARON installation directory, subdirectory ‘utils'.


    # cd /opt/charon/utils
    # tar –xf Charon-PAR_Linux_Toolkit.V1.4.tar


    .

  • To install newly defined aliases (logtail, logview, vmlist, ...), please run the following command:


    # cd /opt/charon/utils (if not already done)
    # ./menusetup -a


    then either logout or execute the following command for the changes to take effect:


    # . /etc/profile.d/charon_menu.sh


    .

You can then run the 'menu' command as usual.


Please refer to release notes for post upgrade operations. The operations to perform are detailed in the release notes. Usually upgrades can require the log monitoring services to be restarted and/or the alert script to be re-installed.

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