Page Comparison

Anchor

	TopRunningPage
	TopRunningPage

...

Running from the console

Copy the selected configuration template from the "/opt/charon/cfg/" directory to some local file and set the correct privileges to that for the file to be able to edit itedited.

Example:

$ cp /opt/charon/cfg/es40.cfg.template my_es40.cfg $ chmod 644 my_es40.cfg

Now let's execute CHARON Run the virtual machine using this template configuration file:

$ es40 my_es40.cfg

You will see Below is an example of a normal HP Alpha test sequence, followed by the prompt sign (">>>"):

initializing ...

polling for units on kzpba0, slot 2, bus 0, hose 1 ...
pka0.0.0.2.1 PKA0 Q-Logic/ISP PCI SCSI HBA

... enter console

P00>>>

The next stage can be either installation of a new HP Alpha/VMS system using a distribution provided by HP or data transfer of data from some existing HP Alpha system. These possibilities will be discussed in details in the next chapters.

If for some reason CHARON-AXP refuses to start, please look for files with .log extension (CHARON-AXP log files) located in the directory from which where CHARON-AXP startswas started, open them with an editing tool and analyze their content. In most cases those files contain very helpful information on what may possibly gone went wrong.

To exit from the CHARON-AXP emulator use the following methods:

Configuration How to exit

No changes change to the template configuration file

Type Enter "power off" in the CHARON console

Enable "F6" button in configuration file to trigger exit from CHARON:

#----------------------------------------------------------------------------
#
# Uncomment to allow 'F6' to terminate the running emulator.
#
#----------------------------------------------------------------------------

set OPA0 stop_on = F6

Press the "F6" key

Please note that before stopping CHARON-AXP, one must a clean shutdown of the operating system running in CHARON-AXPon the virtual machine has to be performed.

Back to Table of Contents

...

It is possible to run CHARON-AXP as a daemon (service). In this case the CHARON-AXP process will be detached from its parent process and from the terminal window in which it runs.

Follow the description below to establish install and run execute CHARON-AXP as a daemon:

Installation and start of CHARON-AXP service

...

Copy the sample script "/opt/charon/bin/charon.service" ( "/opt/charon/bin/charon" for Red Hat Linux 6.x) to thr "/usr/lib/systemd/system/" directory (or to your home directory (for Red Hat Enterprise Linux 6.x)), for example.

Example:

Red Hat Linux 6.x	`$ cp /opt/charon/bin/charon /my_services/es40_service` `$ chmod 755 /my_services/es40_service`
Red Hat Linux 7.x and CentOS 7.x	`$ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/es40.service` `$ chmod 755 /usr/lib/systemd/system/es40.service`

Edit the renamed file to replace sample values of the following parameters, for example.

Example:

Red Hat Linux 6.x	`exec="/opt/charon/bin/es40"` `prog="my_es40"` `config="/my_services/es40-service.cfg"`
Red Hat Linux 7.x and CentOS 7.x	`ExecStart=/opt/charon/bin/es40 -d /my_services/es40-service.cfg` `WorkingDirectory=/my_services`

"my_es40" is a service name in the example above

Create and edit the configuration file ( "/my_services/es40-service.cfg" in the examples above) the way it was described before and make sure that the following pre-requisites are met:

OPA0 must be configured as a virtual port or physical console, not as an operator console, for example.
Example:
load virtual_serial_line OPA0 port=10003 #load operator_console OPA0

Use only absolute paths to log, toy clock, nvram files and all the other data such as disk images, etc. The names of the references files must be unique too, for example.

Example:

...

set session log="/CharonInstances/1st_es40.log" set rom container="/CharonInstances/1st_es40.bin" set toy container="/CharonInstances/1st_es40.dat"

set PKA container[0]="/CharonInstances/1st_es40_boot_disk.vdisk"

...

Make sure the same physical devices are not used by other CHARON-AXP daemons , same for and the OPA0 console port number is unique across the CHARON server.

Div

class	pagebreak

Once the configuration file is ready run , execute the following commands (from based on the examples above) to install and start CHARON-AXP as a daemon:

Red Hat Linux 6.x	`# ln -sf /my_services/es40_service /etc/init.d/es40_service` `# chkconfig es40_service on` `# service es40_service start`
Red Hat Linux 7.x and CentOS 7.x	`# systemctl enable es40.service` `# systemctl start es40.service`

...

Warning

Note that a certain delay may appear in finding network license licenses by Sentinel Run-time on CHARON-AXP host system startup. So if If the CHARON-AXP service is starting automatically on a at host system startup, it may report a "License not found" error and exit.

This problem can be avoided by specifying the "license_key_lookup_retry" parameter in the following way:

set session license_key_lookup_retry = "N [, T]"

where:

N - = Number of retries looking for the license key (or keys)
T - =Time between retries in seconds. If not specified, 60 seconds is used

Example:

set session license_key_lookup_retry = 5

In this example, if the license key is not found during initial scan, CHARON-AXP will do 5 more attempts waiting 60 seconds between them.

See General Settings section for more details.

...

To stop a CHARON-AXP daemon, use the following command, for examplecommands.

Example:

Red Hat Linux 6.x	`# service es40_service stop`
Red Hat Linux 7.x and CentOS 7.x	`# systemctl stop es40`

Please note that before stopping a CHARON-AXP service, one must a clean shutdown of the operating system running in CHARON-AXP. on the virtual machine has to be performed.

Back to Table of Contents

...

To remove a CHARON-AXP daemon use the following commands, for example.

Example:

Red Hat Linux 6.x	`# chkconfig es40_service off` `# chkconfig --del es40_service` `# rm -f /etc/init.d/es40_service`
Red Hat Linux 7.x and CentOS 7.x	`# systemctl disable es40.service # rm -f /usr/lib/systemd/system/es40.service`

Please note that before removing a CHARON-AXP service one must shutdown , a clean shutdown of the operating system running in CHARON-AXP and then stop the corresponding CHARON-AXP service. on the virtual machine has to be performed and the service has to be stopped.

Please refer to the next chapters for more details concerning CHARON-AXP configuration details

...

Versions Compared

Old Version 9

New Version 10

Key

Running from the console

Installation and start of CHARON-AXP service