Page Comparison

...

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

Starting with kit 1.56, the '.tar' file name has been changed to Charon-AXPVAX_linux_toolkit.V<version>.tar.The following operations must be performed as 'root' user:

• 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_linux_toolkit.V1.5758.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_linux_toolkit.V1.5758.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)

...

• read the release notes available here: Charon-AXP/VAX Linux Toolkit - Current version
  .

• copy and extract the files from the tar file to the CHARON installation directory, subdirectory ‘utils'.
  Kit 1.56 '.tar' file name has been changed to Charon-AXPVAX_linux_toolkit.V1.56.tar.

  # cd /opt/charon/utils # tar –xf charon_linux_toolkit.V1.58.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.

In case of upgrade from a kit older than 41 on a CentOS 7 or Red Hat Enterprise Linux 7.x system, you must first stop all services, including the virtual machines running, and remove the services that were defined using the previous method as described below:

List installed services

Remove installed services

Once these services are removed, you can perform a standard kit upgrade

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.