Quick Setup Guide

This article will list the operations to be performed to make your emulator running with the CHARON Linux Toolkit.

• Create a folder to store the CHARON products and CHARON Linux Toolkit(s)
  Example:

  # mkdir /charon

  .

• Optionally create a folder where to store your licenses (C2V and V2C files):
  Example:

  # mkdir /charon/licenses

• Download the kits from the ftp site using 'ftp' or 'FileZilla' for example.

  To install ftp, you can:

  • either use the following command (Red Hat and Fedora):

    # yum install ftp

    .

  • or mount the Linux installation disc (Red Hat), open the "Packages" folder and either double click on the "ftp-*.rpm" file (GUI) or use the "yum install" command.
    Example:

    # yum install "/media/RHEL_6.4 x86_64 Disc 1/Packages/ftp-0.17-53.el6.x86_64.rpm"

    .

• Install the CHARON Linux Toolkit as described in the "Setup" page.
  
  
• Install the CHARON product(s) you need from menu option "Install/Upgrade/Remove CHARON"
  
  
• Dedicate network interfaces to CHARON using menu option "Network Configuration Utility" (ncu) or configure the ifcfg files accordingly (see your CHARON product documentation, network part). In both cases, offloading parameters will be disabled.
  
  
• Check the license can be read using the "License key display/email" menu option
  
  

• Prepare your configuration file(s) or use the clone utility available from the "Service management - Update guests list" menu (see further).
  
  

• Create your vdisk files using the "mkdskcmd" command if needed.
  Example:

  # mkdskcmd -o /data/vms0_rz28.dsk -d rz28

  .

• Use the "Service management - Update guests list" from the "Service management (Start, Stop, Manage automatic boot & shutdown)" menu option to add your new virtual machine (guest)
  • First install the service, option "Install or update service" (Linux distributions not using "systemd" only, i.e. Red Hat Enterprise Linux 6)
  • Optionally, use option "Enable/Disable start at server boot" to prevent the guest from starting automatically when the Linux server is booted
  • Optionally (but highly recommended), use option "Create/Edit guest stop script" to define the stop script that will be used to stop the service (see examples provided in the 'charon_gstart.stop.example' file). It is recommended to test your shutdown scripts before going on production
  • Optionally, create the 'charon_gstart.chkrun' file in the '/opt/charon/utils' folder (by copying the 'charon_gstart.chkrun.example' file) to add information about the guest state when displaying the guests list. See Optional guest display status script
  • Starting with kit 41, the log file monitoring service is created automatically.

   

   
• Connect to the guest console using the "Connect to guest console" menu option and install or restore the operating system (guest must be running)
  .
• You can remove the USB dongle to verify the dongle removal is identified by the askusbd log monitor service:

  • If you did not disable the 'wall' alerts from the "Alerts management" menu, you should receive an immediate 'wall' message.

  • If you disabled the 'wall' alerts from the "Alerts management" menu, you can have a look at the alerts history from the "Alerts management" menu
  • If the mail has been correctly configured, you will receive an alert with subject: "[CHARON] License dongle disconnected"