...

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

Preparation

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

  # mkdir /charon

  .

• Download the kits in this folder from the Stromasys sftp server using 'sftp' or your browser with the link provided by Stromasys.

  .

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

  # mkdir /charon/licenses

  .

• Install the CHARON Charon Linux Toolkit as described in the Setup page.
  .

• Install the CHARON Charon product(s) you need from menu option "Install/Upgrade/Remove Charon"
  .

• Dedicate network interfaces to CHARON using menu option "Network Configuration Utility" (see your CHARON product documentation / networking chapterCharon (see the Charon-PAR user's guide).
  .

• Check the license can be read using the "HASP license details" menu option
  .

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

• Prepare your storage configuration and create your vdisk virtual disk files using the "mkdskcmd" command if needed.
  Example:

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

  (see the Charon-PAR user's guide) if needed.

  .

Virtual machines creation

• Use the "VM management - Update guests list" option from the "VM Management (add/remove VM, start, stop, console connection, ...)" menu option to add and start your new virtual machine (guest)
  .
  
  • If you're running Red Hat Enterprise Linux 6, first install the service using the "Install or update service" option.
    .
  • 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 perform a clean shutdown of the virtual machine at service stop.
    It is recommended to test your shutdown scripts before going on production
    .
  • The log file monitoring service is created automatically.

  
  

• Connect to the guest console using the "Connect to guest console" menu option (from the "VM Management" menu) and install or restore the operating system. If 'telnet' is not installed, you can connect via putty for example ( in this case some firewall settings will have to be set, see Connection to guest console blocked by firewall )
  .

...

• You can remove the USB dongle, if any, to verify the dongle removal is identified by the askusbd log monitor service:
  .
  

  • If you enabled 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 (default), 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: "[CHARONCharon] License dongle disconnected" quite immediately (please ensure the email has not been moved to the junk folder). The immediate alert can be followed by an alert coming from the virtual machine log monitoring announcing the time remaining before stop

...

To avoid navigating in the 'menu' options, use the Additional command lines for ease of management:

...