Page Comparison

Anchor

	TOC
	TOC

Include Page

	KBCOMMON:KB-CSSstyle
	KBCOMMON:KB-CSSstyle

...

Each model of CHARON-AXP has a symbolic link defined to point to the corresponding CHARON executable (see the table below). If the PATH is correctly defined, you can start a virtual machine by specifying the link followed by the configuration file. This is described further.

Link name	Emulator to run
as400	AlphaServer 400
as800	AlphaServer 800
as1000	AlphaServer 1000
as1000a	AlphaServer 1000A
as2000	AlphaServer 2000
as2100	AlphaServer 2100
as4000	AlphaServer 4000
as4100	AlphaServer 4100
ds10	AlphaServer DS10
ds10l	AlphaServer DS10L
ds15	AlphaServer DS15
ds20	AlphaServer DS20
ds25	AlphaServer DS25
es40	AlphaServer ES40
es45	AlphaServer ES45
gs80	AlphaServer GS80
gs160	AlphaServer GS160
gs320	AlphaServer GS320

...

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

Configuration How to exit

No change to the template configuration file

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, a clean shutdown of the operating system running on the virtual machine has to be performed.

Warning
The total number of devices (both controllers and units, including disks) displayed by CHARON SRM console is limited to 48. Note that it does not affect the actual number of configured devices provided to CHARON guest OS.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

Copy the sample script "/opt/charon/bin/charon.service" ( "/opt/charon/bin/charon" for Red Hat Linux 6.x) to the "/usr/lib/systemd/system/" directory (or to your home directory for Red Hat Enterprise Linux 6.x).
Example:
Red Hat Linux 6.x
$ cp /opt/charon/bin/charon /my_services/es40_service
$ chmod 755 /my_services/es40_service
Red Hat Enterprise Linux
7.x and
/CentOS 7
.x
& 8
$ 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.
Example:
Red Hat Linux 6.x
exec="/opt/charon/bin/es40"
prog="my_es40"
config="/my_services/es40-service.cfg"
Red Hat Enterprise Linux
7.x and
/CentOS 7
.x
& 8
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 the following pre-requisites are met:

OPA0 must be configured as a virtual port or physical console, not as an operator console.
Example:
set COM1 alias=OPA0 port=10003
#set COM1 alias = OPA0 line = (console)

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.

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 and the OPA0 console port number is unique across the CHARON server.

...

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

Red Hat Enterprise Linux
Red Hat Linux 6.x	`# ln -sf /my_services/es40_service /etc/init.d/es40_service` `# chkconfig es40_service on` `# service es40_service start`

7.x and

/CentOS 7

.x

& 8	`# systemctl enable es40.service` `# systemctl start es40.service`

Info

title	Red Hat Enterprise Linux 7.x and /CentOS 7 .x& 8

If you update the /usr/lib/systemd/system/<my virtual machine>.service file, the following command must be executed in order to take changes into account:

# systemctl daemon-reload

Warning

Note that a certain delay may appear in finding network licenses by Sentinel Run-time on CHARON-AXP host system startup. If the CHARON-AXP service is starting automatically 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 commands.

Example:

Red Hat Enterprise Linux
Red Hat Linux 6.x	`# service es40_service stop`

7.x and

/CentOS 7

.x

& 8	`# systemctl stop es40`

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

...

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

Example:

Red Hat Enterprise Linux
Red Hat Linux 6.x	`# chkconfig es40_service off` `# chkconfig --del es40_service` `# rm -f /etc/init.d/es40_service`

7.x and

/CentOS 7

.x

& 8	`# systemctl disable es40.service # rm -f /usr/lib/systemd/system/es40.service`

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

...

Versions Compared

Old Version 30

New Version Current

Key