Versions Compared

Old Version 4

changes.mady.by.user Kirill Nikolaev

Saved on

compared with

New Version Current

changes.mady.by.user Kirill Nikolaev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
excludeTable of Contents

Back to Table of Contents

...

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

Back to Table of Contents

Running CHARON-AXP emulators

...

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

Back to Table of Contents 

Running from the console

...

ConfigurationHow to exit
No changes to the template configuration file

Type "power off" in 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 "F6"

 


(warning) Please note that before stopping CHARON-AXP, one must shutdown the operating system running in CHARON-AXP.

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.


Back to Table of Contents

Running as system service (daemon)

...

Installation and start of CHARON-AXP service

 


  1. Copy the sample script "/opt/charon/bin/charon" ( "/opt/charon/bin/charon.service" for Fedora Core Linux ) to your home directory (Red Hat Linux) or to "/usr/lib/systemd/system/" directory (Fedora Core), for example:

    Red Hat Linux

    $ cp /opt/charon/bin/charon /my_services/es40_service
    $ chmod 755 /my_services/es40_service

    Fedora Core

    $ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/es40.service
    $ chmod 755 /usr/lib/systemd/system/es40.service


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

    Red Hat Linux

    exec="/opt/charon/bin/es40"
    prog="my_es40"
    config="/my_services/es40-service.cfg"

    Fedora Core

    ExecStart=/opt/charon/bin/es40 -d /my_services/es40-service.cfg
    WorkingDirectory=/my_services

    (warning) "my_es40" is a service name in the example above

              

  3. 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 virtual port or physical console, not as operator console, for 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

      ...

      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 the OPA0 console port number.

 
Div
classpagebreak


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

...

Warning

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

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

set session license_key_lookup_retry = "N [, T]"

where:

  • N - Number of retries looking for 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.

...


Back to Table of Contents

Stopping CHARON-AXP service

...

(warning) Please note that before stopping CHARON-AXP service, one must shutdown the operating system running in CHARON-AXP. 

Back to Table of Contents 

Removing CHARON-AXP service

...

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

Back to Table of Contents