Versions Compared

Old Version 13

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: typo and added Rotating log file size is multiple of 64K and bugs in links solved

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

...

The following table describes all available "session" parameters, their meaning and examples of their usage:

hw_model

Parameterhw_model
TypeText string
Value

Virtual HP Alpha system hardware model to be emulated.

Use a default configuration template for each particular model as a starting point for a custom configuration. This would ensure that the parameter is set correctly.

Example:

set session hw_model="AlphaServer_ES40"

Available models are:

  • AlphaServer_AS400

  • AlphaServer_AS800

  • AlphaServer_AS1000

  • AlphaServer_AS1000A

  • AlphaServer_AS1200

  • AlphaServer_AS2000

  • AlphaServer_AS2100

  • AlphaServer_AS4000

  • AlphaServer_AS4100

  • AlphaServer_DS10

  • AlphaServer_DS10L

  • AlphaServer_DS15

  • AlphaServer_DS20

  • AlphaServer_DS25

  • AlphaServer_ES40

  • AlphaServer_ES45

  • AlphaServer_GS80

  • AlphaServer_GS160

  • AlphaServer_GS320

(info) Refer to this section to find how to set a particular HP Alpha model supported by CHARON-AXP.

configuration_name

Parameterconfiguration_name
TypeText string
Value

Name of the CHARON-AXP instance (ir must be unique):

set session configuration_name="MSCDV1"

The value of this parameter is used as a prefix to the event log file name. (see below).

From the example above, the CHARON-AXP log file will have the following name:

MSCDV1-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

xxxxxxxxx is an increasing decimal number starting from 000000000 to separate log files with the same time of creation (in case the log is being written faster than one log file per second).

(warning) It is strictly recommended to use the "configuration_name" parameter if more than one CHARON instance runs on the same server.

log

Parameterlog
TypeText string
Value

The log file or directory name is where the log file for each CHARON-AXP execution session is stored.

Panel
borderColor#3AAADC
bgColor#FFFFFF
titleColor#FFFFFF
titleBGColor#3AAADC
titleLog specified as a file name

It is possible to overwrite the existing log file or to extend it using the "log_method" parameter.

(info) The "log_method" parameter is effective only when a single log file is specified, not a directory.

Example:

set session log="/charon/es40prod.log"



Panel
borderColor#0062AB
bgColor#FFFFFF
titleColor#FFFFFF
titleBGColor#0062AB
titleLog specified as a directory

CHARON-AXP automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted, CHARON-AXP creates a log file for each CHARON-AXP execution session in the directory where the emulator was started. In these two cases, the log rotation mode is enabled, meaning a new log file is created each time the virtual machine is started and when the log file size exceeds the one specified (see log_file_size) and/or when the log file is older than a specified number of days (see log_rotation_period).

(info) A symbolic link located in the same directory will be created, pointing to the active log file. Its name is based on the hw_model parameter or the configuration_name parameter if specified.

If the "configuration_name" parameter of the session is specified, the log file name is composed as follows:

<configuration_name>-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

If the "configuration_name" parameter is omitted, the log file name will have the following format:

<hw_model>-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

where "xxxxxxxxx" is an increasing decimal integer, starting from 000000000 to separate log files with the same time of creation (in case the log is being created faster than one log file per second).

(warning) Only existing directory can be specified. If the directory specified does not exist, this will be considered as a flat file.

Example:

set session configuration_name="es40prod"

set session log="/charon/logs"

The execution of the virtual machine will create a log file, named /charon/logs/es40prod-2016-10-13-10-00-00-000000000.log (for example) and a symbolic link named /charon/logs/es40prod.log pointing to this file. The link will be updated when the log rotation will occur.



Div
classpagebreak


log_method

...

Parameter

log_file_size

TypeText string
Value

If log rotation is enabled, the log_file_size parameter determines the log file size threshold at which the log is automatically rotated. Rotating log file size is multiple of 64K

  • "unlimited" or "0" (default) - the feature is disabled
  • "default" - default size is used (4Mb)
  • <size>[KMG] - size of the current log file in bytes with additional multipliers:

    • K - Kilobyte - multiply by 1024

    • M - Megabyte - multiply by 1024*1024

    • G - Gigabyte - multiply by 1024*1024*1024

Examples:

set session log_file_size="default"


set session log_file_size=10M

(warning) Minimum (info) Minimum LOG File size is 64K, maximum is 1G. Setting size less then than 64K effectively makes the LOG File unlimited.

...

Parameterlog_rotation_period
TypeText string
Value
  • "default" - default value, 7 days. This values is used even if the "log_rotation_period" is not specified.
  • "daily" or "1"
  • "weekly" or "7"
  • "never" or "0"
  • <N> - in N days where N is greater than 0

If the rotation log mode is enabled this parameter controls switching to next log file based on period of time passed. If enabled the switching to next log file appears at midnight.

Examples:

set session log_rotation_period="weekly"


set session log_rotation_period=14


...

Parameter

license_key_id

TypeText string
Value

A set of Sentinel Key IDs that specifies the license keys to be used by CHARON. It is also possibly to use a keyword "any" to force CHARON to look for suilable a suitable license in all available keys if the license is not found in the specified keys.

Example:

set session license_key_id = "1877752571,354850588,any"

Based on the presence of this parameter in the configuration file, CHARON behaves as follows:
 

  1. No keys are specified (the parameter is absent)
    CHARON performs an unqualified search for any suitable key in unspecified order. If no key is found, CHARON exits.

  2. One or many keys are specified
    CHARON performs a qualified search for a regular license key in the specified order. If it is not found, CHARON exits (if the keyword "any" is not set).

If the keyword "any" is specified then if no valid license has been found in the keys with specified ID’s all other available keys are examined for valid license as well.

Note

The order in which keys are specified is very important. If a valid license was found in the key which ID was not the first one specified in configuration file, then available keys are periodically rescanned re-scanned and if the key with the ID earlier in the list than the current one is found CHARON tries to find a valid license there and in case of success switches to that key.


...

Parameter

license_id

TypeText string
Value

A set of license indetifiers identifiers that specifies the licenses to be used by CHARON. This parameter is applicable only to new licenses.licenses on which Stromasys placed restrictions on what products can be combined on a single license key. Please contact your Stromasys representative or VAR for more information.

Example:

set session license_id = "2718281828,314159265"

If this parameter is set, Charon considers for validation only the available licenses with license ID parameter set and equal to one of
the license ID's specified in the configuration. This prioritized list corresponds to the "Product License Number" line in the Product section of the license.

license_key_lookup_retry

Parameterlicense_key_lookup_retry
TypeText String
Value

In case the CHARON-AXP license connection is not present when the guest starts up, this parameter specifies how many times CHARON-AXP will try to establish the connection and, optionally, a period of time between retries.

Syntax:

set session license_key_lookup_retry = "N [, T]"

Options:

  • N - Number of retries to look for license keys.
  • T - Time between retries in seconds. If not specified 60 seconds are used

Example 1

set session license_key_lookup_retry = 1

If license key is not found during initial scan, do only one more attempt after 60 seconds.

Example 2

set session license_key_lookup_retry = "1,30"

Same as above but retry in 30 seconds.

Example 3

set session license_key_lookup_retry = "3,10"

If license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them.

Example 4

set session license_key_lookup_retry = "5"

If license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them.

...

Parametern_of_cpus
TypeNumeric
Value

Limits the number of emulated CPUs.

Example:

set session n_of_cpus=3

The maximum number of CPUs enabled by CHARON-AXP is specified by the license key, but cannot exceed the original hardware restrictions:

HP Alpha ModelNumber of emulated CPUs

AlphaServer_AS400

1
AlphaServer_AS8001
AlphaServer_AS10001
AlphaServer_AS1000A1
AlphaServer_AS12002
AlphaServer_AS20002
AlphaServer_AS21004
AlphaServer_AS40002
AlphaServer_AS41004
AlphaServer_DS101
AlphaServer_DS10L1
AlphaServer_DS151
AlphaServer_DS202
AlphaServer_DS252
AlphaServer_ES404
AlphaServer_ES454
AlphaServer_GS808
AlphaServer_GS16016
AlphaServer_GS32032


...