Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 19401 replaced by 19402

Anchor
TopConfigurationPageTOCTopConfigurationPage
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

Note: the lines preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

HP Alpha model specification

...

If you create the CHARON-AXP configuration file from scratch, it must be the very first uncommented line in the configuration file.

...

configuration file.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Configuration name

The next configuration statement is the "Configuration name" option.

...

You can optionally uncomment this line to differentiate this CHARON-AXP instance from all others in a multi-instances environment. The configuration name can be any label that is meaningful. It is reported in the log file and is used to set the log file name for rotating log (see further: Rotatinglog(default) ).

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Log file parameters

Execution of CHARON-AXP creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation - start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of possible problems either with the running CHARON-AXP or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting. If it becomes necessary to contact Stromasys for support, the configuration and log files, plus the license number, will be requested to begin problem resolution.

...

20180521:035210:INFO :0:000003A5:hexane.cxx(5938): session: loading built-in configuration "AlphaServer_ES40"...
20180521:035210:INFO :0:000003A6:hexane.cxx(5959): session: ... done loading built-in configuration "AlphaServer_ES40"
20180521:035210:INFO :0:000003AA:hexane.cxx(5988): session: loading configuration file "es40.cfg"...
20180521:035210:INFO :0:000003AB:hexane.cxx(6012): session: ... done loading configuration file "es40.cfg"
20180521:035210:INFO :0:000003F2:sesmgr.cxx(1410): session: default log file size limit is 4194304 bytes
20180521:035210:INFO :0:0000032B:hexane.cxx(2698): Start request received.
20180521:035211:INFO :0:000003AC:hexane.cxx(1424): session: process affinity is 000000000000000F, system affinity is 000000000000000F
20180521:035211:INFO :0:000003D1:hexane.cxx(1686): session: I/O domain affinity is 0000000000000001, CPU domain affinity is 000000000000000E
20180521:035211:INFO :0:0000024D:licenseman(1823): Checking the available license key "1918154109".
20180521:035211:INFO :0:0000024D:licenseman(1823): Found license key: "1918154109".
20180521:035211:INFO :0:0000024D:licenseman(1823): Checking product section 0.
20180521:035211:INFO :0:0000024D:licenseman(1823): License number: "000.msc.test.center.nikolaev".
20180521:035211:INFO :0:0000024D:licenseman(1823): Product License number: "CHAXP/AXP".
20180521:035211:INFO :0:0000024D:licenseman(1823): CHARON product code: "CHAXP-490xx-WI-LI".
20180521:035211:INFO :0:0000024D:licenseman(1823): Unlimited license.
20180521:035211:INFO :0:0000024D:licenseman(1823): Feature 2 check interval 1 hour(s).
20180521:035211:INFO :0:0000024D:licenseman(1823): Concurrency info:
20180521:035211:INFO :0:0000024D:licenseman(1823): There are 10 instances allowed.
20180521:035211:INFO :0:0000024D:hexane.cxx(2848): STROMASYS SA, (C) 2009-2018
20180521:035211:INFO :0:00000408:hexane.cxx(2892): CHARON-AXP (AlphaServer ES40), V 4.9 B 1940119402, May 10 2018 / 000.msc.test.center.nikolaev / 1918154109
20180521:035211:INFO :0:00000336:hexane.cxx(2924): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: /pub/doc/30-17-033.pdf
20180521:035211:INFO :0:00000097:hexane.cxx(2999): OS Environment: Linux 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 13 10:46:25 EDT 2017 x86_64.
20180521:035211:INFO :0:00000098:hexane.cxx(3004): Host CPU: GenuineIntel, Family 6, Model 42, Stepping 1, Intel Xeon E312xx (Sandy Bridge), 1 Sockets, 1 Cores per Socket, 4 Threads per Core, at ~2593 MHz, 4 cpu's available
20180521:035211:INFO :0:00000099:hexane.cxx(3009): Host Memory: 3840Mb
20180521:035211:INFO :0:0000041F:hexane.cxx(3224): Configuration dump::
. session:
. . configuration_name = "AlphaServer_ES40"
. . log_method = "overwrite"
. . hw_model = "AlphaServer_ES40"
. . log_mode = "shared"
. . log_locale = "english"
. RAM:
. . size = "256"
. ACE:
. . num_entries = "2139"
. . num_translators = "0"
. . cache_size = "1024"
. . cache_base_size = "200"
. . host_options = " --locked-size=16"
. . enabled = "true"
. . ext_compiler = "ml64.exe"
. . ext_path = ""
. . cpu_architecture = "EV67"
. . locked_size = "16"
. cpu_0:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_1:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_2:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_3:
. . locked_size = "16"
. . wtint_idle = "true"
. ROM:
. . container = "clipper.bin"
. . dsrdb[0] = "1820"
. . dsrdb[1] = "50"
. . dsrdb[4] = "50"
. . dsrdb[11] = "1050"
. . dsrdb[12] = "1050"
. . system_name = "AlphaServer ES40 6/667"
. ISA:
. . clock_period = "10000"
. TOY:
. . container = "clipper.dat"
. COM1:
. . line = "OPA0"
. . communication = "console"
. COM2:
. . line = "(void)"
. . communication = "ascii"
. OPA0:
. . trace = "disabled"
. . stop_on = "F6"
. . tx_flush_delay = "0"
. EWA:
. . adapter_mode = "auto"
. . interface = "EWA0"
. . rx_fifo_delay_on_overload = "false"
. EWA0:
. . interface = "eth1"
. . disabled_mode = "10BaseT-HD"
. . port_show_driver_statistics = "false"
. . port_enable_mac_addr_change = "true"
. . port_snd_sock_buf_size_kb = "0"
. PKA:
. . scsi_id = "7"
. . min_n_of_threads = "0"
. . container[0] = "/home/charon/Charon/test/performancecomparison-axp.vdisk"

The next group of parameters defines the name of the CHARON-AXP log file and how CHARON-AXP will use it:

#set set session log_method = append
#set session log_method = overwrite
#set session log = "AlphaServer_ES40.log"

...

set session log_method = append
set session log = "/my_logs/my_es40.log"

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

CPU affinity

This setting binds the running instance of the emulator CPUs to particular host CPUs. This should be used for soft partitioning host CPU resources or for isolating multiple CHARON instances on the same host from each other. By default the emulator instance allocates as many host CPUs as possible.

...

(warning) Note that the number of the specified host CPUs must correspond to the number of the emulated CPUs (one host CPU for one emulated CPU; this value is specific for each HP Alpha model) and number of CPUs needed for CHARON application itself ("n_of_io_cpus").

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Number of host CPUs dedicated to CHARON I/O

...

(warning) Note that the number of the specified CPUs dedicated to CHARON I/O operations must correspond to the total number of available for CHARON CPUs (restricted by "affinity" parameter if needed) and the number of the virtual HP Alpha CPUs to be emulated.

...

to be emulated.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Setting a specific HP Alpha model

...

The full description of the parameters, with other models that can be also configured, is available in the "Configuration details" chapter of this User's Guide.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Reducing number of emulated CPUs

If the CHARON host contains does not contain enough CPUs to emulate full range of the CPUs provided by a certain HP Alpha model, it is possibe possible to direct CHARON-AXP to reduce the number of emulated Alpha CPUs in the configuration:

...

set session n_of_cpus=1

Back to the Table of Contents

AXP to reduce the number of emulated Alpha CPUs in the configuration:

set session n_of_cpus=1

This parameter can also be used to avoid warning messages in the log if the number of CPUs allowed by the license is less than the default number of CPUs of the emulated HP Alpha model.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Setting system serial number

...

set rom system_serial_number = SN01234567

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

TOY and ROM containers

The next objects to be configured are TOY and ROM containers (their presence depends on the HP Alpha model). It is always recommended to enable them. If a container file of the given name does not exist, CHARON-AXP will create it. It is recommended to specify the path for each file so that time and console parameters will be kept whatever the current directory is when starting the guest.

...

set rom container="clipper.bin"

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Emulated memory (RAM) size

...

Note that in some particular orders your license may restrict the maximum RAM amount of each HP Alpha model.

...

HP Alpha model.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Console

Mapping to system resources

...

OptionDescription
line

Mapping to host serial line, both physical and virtual. Use the following mapping for different types of host serial lines:

MappingDescription
/dev/tty<N> Virtual serial lines
/dev/ttyS<N>Onboard serial lines
/dev/ttyUSB<N>Modem or usb serial lines adapters
(console)Mapping to the current TTY console


Note

The specific account for running CHARON ("charon") does not allow the usage of physical consoles, "/dev/tty<N>", as CHARON consoles. If you plan to map the CHARON console to "/dev/tty<N>", use only the "root" account to run CHARON.


port

Mapping to an IP port of the CHARON -VAX host.
Using this mapping it is possible to connect to the CHARON -VAX console and disconnect from it at any time.

applicationStarting some application (typically another xterm terminal) with its specific options and switches to communicate to CHARON using the IP port defined by the "port" parameter (see above)
aliasDefine some meaningful name for "COM1" and "COM2". Usually it is "OPA0" for "COM1" and "TTA0" for "COM2" (see below)

...

This line provides CHARON-AXP the ability to exit by pressing the "F6" key.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Improve granularity of emulated timer

...

Do not uncomment this parameter unless there are some problems with system time or system clock intervals in guest OS.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

ATAPI CD/DVD-ROM configuration

...

How to find proper "/dev/sg" device is explained in this section.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

AlphaStation Sound Card (AD1848) configuration

...

Note

The "Pulse Audio" packages of the last versions must be installed on CHARON host to support audio playback. Please refer to Linux documentation.

...

.


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Networking

CHARON-AXP supports DE435, DE450, DE500AA, DE500BA, DE602 and DE602AA virtual network adapters.

...

Info
CHARON supports VLAN adapters. If used, proceed with their installation and configuration according to the network adapter vendor User's Guide and then use the resulting VLAN interface the same way as the regular network interface. 


Note

The AlphaServer DS 15 DS15 and DS25 contain two built-in PCI Ethernet adapters. Models and names (EI* or EW*) of them depend on configuration addon. Choose one of the two or none, but not both. The first instantiates onboard network interfaces as EIA and EWA. While the second - EWA and EWB (enabled by default for backward compatibility)

Example:

#include ds25-onboard-nics.icfg
include ds25-onboard-nics-ew.icfg

(info) It could be necessary to specify the path to the .icfg file if you use your own configuration file using the "include /opt/charon/cfg/ds25-onboard-nics-ew.icfg" syntax.


Follow this link for more details of CHARON-AXP network controllers configuration.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Disk/tape subsystem

The next step is configuration of the disk/tape subsystem and mapping it to system resources using the samples given in the template configuration files.

...

Follow this link for details of KZPBA controllers configuration.

...

KZPBA controllers configuration.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

KGPSA-CA PCI FC disk controller

...

Follow this link for details of KGPSA-CA controllers configuration.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

KGPSA-CA mapping to the host resources

...

Numbers in the square brackets represent KGPSA-CA units. They can be in the range 0..32766, but no more than 255 units can be configured on a single controller.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc


Div
classpagebreak


KGPSA-CA pass through mode

...

Follow this link for detailed description of building and installation of an EMULEX LightPulse PCI/PCI-X/PCIe FC adapter driver.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Auto boot

CHARON-AXP can be configured to automatically boot an operating system at start up by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.

...

>>>set bootdef_dev dka0
>>>set auto_action restart

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc