Anchor

	TOC
	TOC

Include Page

	KBCOMMON:KB-CSSstyle
	KBCOMMON:KB-CSSstyle

...

When a CHARON Virtual Machine (VM) is created from a template using the CHARON Virtual Machines Machine Manager, it has to be updated to meet the desired configuration.
This configuration is represented as a text file ("configuration file") containing some specific keywords to define the main settings such as the text-based configuration file is copied from a template file. This configuration file must be customized for your specific configuration. The configuration file consists of directives written in the Charon-AXP "configuration syntax" which define all aspects of the emulated system, including amount of memory, number of CPUs, peripheral devices as well as specifics of CHARON VM executions such as name of VM log file, number of host CPUs used for emulation, etc.To change , the location of various associated files, to name some examples.

To edit the configuration file, open the CHARON Virtual Machines Machine Manager from its shortcut on Desktop / Start menu or from the tray menu item, select the target CHARON VM and press the "Edit Configuration" button:

Image RemovedImage Added

Div

class	pagebreak

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

Alpha model specification

The first configuration statement is the specification of the exact HP Alpha hardware model to emulate, for example:

set session hw_model = AlphaServer_ES40

You must leave this line untouchedThis line must not be changed.

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

...

The configuration name is reported in the log file and is used to set the log file name for rotating log (see explanations further).
Changing the configuration name in the "configuration_name.icfg" file does not change the name of the virtual machine at Virtual Machines Machine Manager level.
The "configuration_name.icfg" file can be found in the home directiory of the VM. Select the target VM, open "VM Configuration" tab and press "Explore" button.

...

Panel

borderColor	#EDEDEE
bgColor	#FFFFFF
titleColor	#000000
titleBGColor	#EDEDEE
title	CHARON-AXP log file example (part1)

2019022120200524:160742:INFO :0:00000249:ethane.cxx(9026): Logging started. 2019022120200524:160742:INFO :0:000003A5:ethane.cxx( 147): session: loading built-in configuration "AlphaServer_ES40"... 2019022120200524:160742:INFO :0:000003A6:ethane.cxx( 179): session: ... done loading built-in configuration "AlphaServer_ES40" 2019022120200524:160742:INFO :0:000003A7:ethane.cxx( 337): session: loading service configuration "My_ES40"... 2019022120200524:160742:INFO :0:000003A8:ethane.cxx( 372): session: ... done loading service configuration "My_ES40" 2019022120200524:160742:INFO :0:000003AA:ethane.cxx( 420): session: loading configuration file "es40.cfg"... 2019022120200524:160742:INFO :0:000003AB:ethane.cxx( 456): session: ... done loading configuration file "es40.cfg" 2019022120200524:160742:INFO :0:0000032B:ethane.cxx(2707): Start request received. 2019022120200524:160742:INFO :0:000003AC:ethane.cxx( 818): session: process affinity is 00000000000000FF, system affinity is 00000000000000FF 2019022120200524:160742:INFO :0:000003D1:ethane.cxx(1476): session: I/O domain affinity is 0000000000000003, CPU domain affinity is 00000000000000FC 2019022120200524:160742:INFO :0:0000024D:licenseman(1823): Checking the available license key "1422726238". 2019022120200524:160742:INFO :0:0000024D:licenseman(1823): Found license key: "1422726238". 2019022120200524:160742:INFO :0:0000024D:licenseman(1823): Checking product section 0. 2019022120200524:160742:INFO :0:0000024D:licenseman(1823): The value "ALPHASERVER_ES40" of the required parameter "P_HW" is not found in the list "PDP1193,PDP1194" for the product 0. 2019022120200524:160742:INFO :0:0000024D:licenseman(1823): Checking product section 1. 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): HASP clock: 2124-FebMay-2019 2020 17:08:01. 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): Host clock: 2124-FebMay-2019 2020 16:07:43. 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): License number: "003.msc.test.center.kirill". 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): Product License number: "p.axp". 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): CHARON product code: "CHAXP-4xxxx-WI-LI". 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): Unlimited license. 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): Feature 2 check interval 1 hour(s). 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): Concurrency info: 2019022120200524:160743:INFO :0:0000024D:licenseman(1823): There are 4 instances allowed. 2019022120200524:160743:INFO :0:0000024D:ethane.cxx(2838): STROMASYS SA, (C) 2009-20192020 2019022120200524:160743:INFO :0:00000408:ethane.cxx(2880): CHARON-AXP (AlphaServer ES40), V 4.10 11 B 2020020404, Jan May 24 2019 2020 / 003.msc.test.center.kirill / 1422726238 2019022120200524:160743:INFO :0:00000336:ethane.cxx(2921): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: http://www.stromasys.com/pub/doc/30-17-033.pdf 2019022120200524:160743:INFO :0:00000097:ethane.cxx(3000): OS Environment: Microsoft Windows 10 Pro, 64-bit (Build 17134). 2019022120200524:160743:INFO :0:00000098:ethane.cxx(3005): Host CPU: Intel(R) Xeon(R) CPU E31275 @ 3.40GHz x8. 2019022120200524:160743:INFO :0:00000099:ethane.cxx(3010): Host Memory: 24320Mb 2019022120200524:160743:INFO :0:0000041F:ethane.cxx(3236): Configuration dump:: . session: . . configuration_name = "ES40 test" . . log = "log.txt"

. . log_method = "overwrite" . . log_locale = "English" . . log_show_messages = "all" . . log_repeat_filter = "off" . c_chip: . . mm_timer_correction_disable = "false" . RAM: . . size = "512" . 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 = "EV6" . . locked_size = "16"

...

Panel

borderColor	#EDEDEE
bgColor	#FFFFFF
titleColor	#000000
titleBGColor	#EDEDEE
title	CHARON-AXP log file example (part3)

2019022120200524:160743:INFO :0:00000418:busemul.cx( 188): ISA: MultiMedia Timer correction is enabled. 2019022120200524:160743:INFO :0:00000420:dit_server(1038): ACE: ACE is on, Running 2 translators. 2019022120200524:160743:INFO :0:0000034B:scsi_disk.( 485): PKA_0: open I/O handle container = "C:\Dev\test\performancecomparison-axp.vdisk" 2019022120200524:160743:INFO :0:0000034B:scsi_cdrom( 211): PKA_400: open I/O handle container = "C:\Dev\test\ALPHA084.ISO" 2019022120200524:160743:INFO :0:0000034B:scsi_tape.( 348): PKA_600: open I/O handle container = "C:\Dev\test\test_tape.vtape" 2019022120200524:160743:INFO :0:00000400:ethdev.cxx( 388): EWA: RX FIFO size is 512KB. 2019022120200524:160743:INFO :0:0000032C:ethane.cxx(2743): "ES40 test" started. 2019022120200524:160743:INFO :0:00000419:winsckio.c(2703): OPA0: Connected. Remote 127.0.0.1:65128.

...

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

Rotating log (default)

By default the CHARON VM default CHARON utilizes a so-called "rotating log" methodmechanism. This means that a new default log file is always created each time the CHARON VM starts and can switch to another log file if the size of the log file exceeds 64Kb (previous log files are kept).This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is this behavior can be changed with the "set session log_file_size" and "set session log_rotation_period" parameters; see more details in the "General Settings" chapter of this guide).

This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is pointing to a directory rather than to a file. If a directory is specified, the log files will be created in that directory.

...

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").

...

The example above directs CHARON VM to use 2 host CPUs for CHARON I/O operations.

Note that the number of the specified CPUs dedicated to CHARON VM 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.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Setting a specific

...

Alpha model

CHARON-AXP allows to specify an exact model of HP Alpha.

For example for HP AlphaServer ES40 family the template configuration file contains the following options:

#============================================================================
#
#

AlphaServer

ES40

6/500
#
#----------------------------------------------------------------------------

#set

ace

cpu_architecture

=

EV6
#set

rom

dsrdb[0]

=

1816

system_name

=

"AlphaServer

ES40

6/500"
#set

rom

version[1]

=

1.98-4

version[2]

=

1.92-5

#============================================================================
#
#

AlphaServer

ES40

6/667
#
#----------------------------------------------------------------------------

set

ace

cpu_architecture

=

EV67
set

rom

dsrdb[0]

=

1820

system_name

=

"AlphaServer

ES40

6/667"

Just uncomment the provided lines to apply a certain model (It is "AlphaServer ES40 6/667" in the example above).

...

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

...

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

...

The TOY and ROM containers have to be configured. 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, starting the CHARON VM will create it.

...

The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each HP Alpha model. It is very important to keep the listed predefined increment between possible memory values.

The following table shows all the parameters:

Hardware Model	RAM size (in MB)
	Min	Max	Default	Increment
AlphaServer 400	64	1024	512	64
AlphaServer 800	256	8192	512	256
AlphaServer 1000	256	1024	512	256
AlphaServer 1000A	256	1024	512	256
AlphaServer 1200	256	32768	512	256
AlphaServer 2000	64	2048	512	64
AlphaServer 2100	64	2048	512	64
AlphaServer 4000	64	32768	512	64
AlphaServer 4100	64	32768	512	64
AlphaServer DS10	64	32768	512	64
AlphaServer DS10L	64	32768	512	64
AlphaServer DS15	64	32768	512	64
AlphaServer DS20	64	32768	512	64
AlphaServer DS25	64	32768	512	64
AlphaServer ES40	64	32768	512	64
AlphaServer ES45	64	32768	512	64
AlphaServer GS80	256	65536	512	256
AlphaServer GS160	512	131072	512	512
AlphaServer GS320	1024	262144	1024	1024

...

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

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

The next step is the specification of the HP Alpha console (OPA0) serial line.

...

#set COM1 alias = OPA0 line = "COM1:" #set COM1 alias = OPA0 port = 10003 #set COM1 alias = OPA0 port = 10003 application = "opa0.ht" set COM1 alias = OPA0 port = 10003 application = "putty -load OPA0 -P 10003" #set COM1 alias = OPA0 port = 10003 application = "c:\kea\user\opa0.ktc"

The goal of this configuration step is to tell CHARON-AXP what host device to use as the virtual system console. The following options are available:

Option	Description
line	Mapping to host serial line, "COM<n>:".
port	Mapping to an IP port of the CHARON host. Using this mapping it is possible to connect to the CHARON console and disconnect from it at any time.
application	Starting some application (typically terminal emulator) with its specific options and switches to communicate to CHARON using the IP port defined by the "port" parameter (see above)
alias	Define some meaningful name for "COM1" and "COM2". Usually it is "OPA0" for "COM1" and "TTA0" for "COM2" (see below)

The second console line "TTA0" can be also optionally configured (for 1 CPU models such as HP AlphaServer 400, HP AlphaServer 800, HP AlphaServer 1000, HP AlphaServer 1000A, HP AlphaServer DS10, HP AlphaServer DS10L and HP and AlphaServer DS15):

#set COM2 alias = TTA0 line = "COM2:" #set COM2 alias = TTA0 port = 10000 #set COM2 alias = TTA0 port = 10000 application = "tta0.ht" set COM2 alias = TTA0 port = 10000 application = "putty -load TTA0 -P 10000" #set COM2 alias = TTA0 port = 10000 application = "c:\kea\user\tta0.ktc"

Note that additional parameters for the CHARON VM serial lines configuration can be added. Follow this link for details.

...

Exit on pressing F6 button

Despite the fact that the CHARON VM can stop with the "power off" command entered at SRM console level, it is recommended to set a hot key to stop the VM from the console (when the console is accessed remotely for example):

...

This line allows the CHARON VM to be stopped by pressing the "F6" keyThe following directive configures the emulator to exit immediately when the F6 key sequence is sent to the emulator console:

set OPA0 stop_on = F6

This means that if the F6 key is pressed in the terminal emulator being used to connect to the console (PuTTY, for example), the emulator will exit immediately.

Please note that the emulator can be stopped when at the SRM prompt ("P00>>>") by type power off, as well as from the Virtual Machine Manager. To shut down the guest safely, Stromasys recommends the following procedure:

Shut down the guest OS (OpenVMS/Tru64 UNIX)
Wait for the SRM prompt ("P00>>>")
Type power off at the SRM prompt
The connection to the console will be lost when the emulator exits, which means the terminal emulator window will probaly disappear.
At this point you can stop or restart the emulator host safely

Stromasys does not recommend enabling this feature. It means that any person (or software) which connects to the console port on the emulator host can stop the emulator and thus "pull the virtual power cable" from the OpenVMS or Tru64 UNIX guest. In particular, many organizations have deployed automated port scanners in their datacenters to discover open ports on the systems in the network. Many such port-scanning solutions, if they are able to connect to an open port, will next try to send data to the port. In many cases this data can be interpreted as the stop sequence and cause the emulator to exit.

If you must allow incoming connections to the console port, you should configure the Windows firewall with a "whitelist" of IP addresses from which such connections are allowed, and disallow all other addresses.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

Some network adapters available in CHARON-AXP are preloaded (for example, HP AlphaServer DS15 contains 2 preloaded adapters EWA and EWB), so their configuration in CHARON VM is even more simple:

load packet_port/chnetwrk EWA0 interface = "connection:Charon"

...

Please note:

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.

...

The AlphaServer 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

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

...

File representing a physical disk of the HP Alpha system (disk image)
- "<file-name>.vdisk"
  These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files.
  Mapping may also include the full path, for example: "C:\My disks\my_boot_disk.vdisk". If the path is not specified, the disk images are expected to be in the CHARON VM home directory.
  WarningUsing
  Important note: using compressed folders to store virtual disks and tapes is not supported
  .
Physical disk
- "\\.\PhysicalDrive<N>"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake.
  These disks must not be formatted by the host OS.
  .
Physical disk by its WWID
- "\\.\PhysicalDrive(DevID =XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake.
  These disks must not be formatted by the host OS.
  DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).
  Example:
  set PKA container[100]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"
  .
iSCSI disks
- "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
  
  Parameter Description
  iScsiTarget Addresses the disk by its iSCSI target name.
  LUN Specifies the LUN on the connected iSCSI disk.
  Example:
  
  Div
  class small
  set PKA container[200]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"
  
  .

SCSI device unknown to Windows for direct mapping, for example, a SCSI disk or tape reader

"\\.\Scsi<N>:<X>:<Y>:<Z>"
The values of N, X, Y and Z can be collected using special utility "Host Device Check" included in the CHARON distributive - or manually by investigation of the devices connected to CHARON host in the "Device Manager" applet.

Parameter	Description
N	A logical number assigned by host operating system (Microsoft Windows) to logical or host’s physical storage resource such as physical SCSI HBA
X	An internal SCSI bus number (usually 0) on host’s physical SCSI HBA
Y	A SCSI ID of physical SCSI target device attached to host’s physical SCSI HBA
Z	A logical unit number inside physical SCSI target device attached to host’s physical SCSI HBA

.

CD-ROM device
- "\\.\CdRom<N>"
  .
ISO file for reading distribution CD-ROM image
- "<file-name>.iso"
  Mapping may also include the full path, for example: "C:\My disks\vms_distributive.iso". If the path is not specified, the CD-ROM images are expected to be in the CHARON VM home directory.
  Div
  class pagebreak
  
  .
Host tape device
- "\\.\Tape<N>"
  .
File representing the tape (tape image)
- Using
  "<file-name>.vtape"
  These files are created automatically.
  Mapping may also include a full path, for example: "C:\My tapes\backup.vtape". If the path is not specified, the tape images are expected to be in the CHARON VM home directory.
  Warning
  
  Important note: using compressed folders to store virtual disks and tapes is not supported.
  .
Floppy drive
- "\\.\A:"
  .
Other type of drive, for example magneto-optical drive
- "\\.\<N>:"
  .

...

The numbers in the square brackets represent the SCSI addresses and LUNs associated with each container of the KZBPA controller. They have the following structure:

[XXYY], where:

Parameter Range Description

XX

0...15

Stands for SCSI ID of each connected unit.

Note that the KZPBA itself has some ID associated with it. By default it is 7 but it can be changed in the following way:

load KZPBA PKA scsi_id = 0

In this example an instance "PKA" of KZPBA controller is assigned with SCSI ID 0.

YY 00...07 Stands for LUN.

It is possible to load several KZPBA controllers: DKB, DKC, etc. by configuring specific placement for them on the PCI bus. It is discussed in details in the "Configuration details" chapter of this Guide.

Some HP Alpha systems emulated by CHARON-AXP have already one or two KZPBA controllers pre-loaded. If the system has only one preloaded controller, the template configuration file usually provides some sample line on how to add another one. For example:

...

They can be configured in 3 modes:

Below is an example of a KGPSA-CA controller loading:

...

Follow this link for details on the KGPSA-CA controllers configuration.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Anchor
KGPSACA1
KGPSACA1
KGPSA-CA mapping to the host resources

...

load KGPSA FGA

#set FGA container[0] = "<file-name>.vdisk"#set FGA container[100]="\\.\PhysicalDrive0"#set FGA container[200]="\\.\PhysicalDrive(DevID=XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"#set FGA container[300]="\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"

...

File representing a physical disk of the HP Alpha system (disk image)
- "<file-name>.vdisk"
  These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files.
  Mapping may also include the full path, for example: "C:\My disks\my_boot_disk.vdisk". If the path is not specified, the disk images are expected to be in the CHARON VM home directory.
  WarningUsing
  Important note: using compressed folders to store virtual disks and tapes is not supported.
  .
Physical disk
- "\\.\PhysicalDriveN"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake.
  These disks must not be formatted by the host OS.
  .
Physical disk by its WWID
- "\\.\PhysicalDrive(DevID =XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake.
  These disks must not be formatted by the host OS.
  DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).
  Example:
  set PKA container[100]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"
  .
iSCSI disks
- "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
  iScsiTarget addresses the disk by its iSCSI target name. LUN specifies LUN on the connected iSCSI disk.
  Example:
  
  Div
  class small
  set PKA container[200]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"
  
  .

...

This line loads an instance of KGPSA-CA controller and maps it to some external controller having ID "5008-05F3-0005-2950-5008-05F3-0005-2951".

Type of mapping

Description

storage_controller_path_id = <Storage controller path ID>

"Storage controller path ID" is a storage (for example SAN) controller path ID.

This ID can be obtained from the special utility "Device check tool" (accessible in the "Host Information and Utilities" section of the CHARON Virtual

Machines

Machine Manager). Once specified, all the disks attached to the storage are automatically mapped as disk units to the CHARON VM.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

...

The "host_bus_location" parameter addresses the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter in the following way:

Parameters	Description
"PCI bus X"	PCI bus number of the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter
"device Y"	PCI bus device number of the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter
"function Z"	The "function" parameter of the the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter

...

The following is the list of EMULEX LightPulse PCI/PCI-X/PCIe FC adapters supported by the CHARON-AXP PCI Pass Through driver and suitable for the emulation of a KGPSA-CA PCI FC adapter in CHARON PCI Pass Through mode:

Supported	Not Supported	Not tested
LP8000 LP9000 LP9002 LP9802 LP10000 LP10000DC LP10000-S LPX1000 LP11002 LPe11002 (FC2242SR, A8003A) LPe1105	LPe1150 (FC2142SR, A8002A)	LPe11000

...

Pay attention to the proper placement of the emulated DEFPA adapter on the virtual HP Alpha PCI bus (it is controlled by "bus", "device", "function", "irq" and "irq_bus" parameters). Refer to this chapter of this Guide for more information.

The "host_bus_location" parameter addresses the host DEFPA FDDI adapter in the following way:

Parameters	Description
"PCI bus X"	PCI bus number of the host DEFPA FDDI adapter
"device Y"	PCI bus device number of the host DEFPA FDDI adapter
"function Z"	The "function" parameter of the the host DEFPA FDDI adapter

...

Optionally it is possible to configure the folIowing models of PBXDA-xx family controllers.

VIrtual PBXDA-xx

Syntax for loading PBXDA-xx family serial lines adapters:

#load PBXDA/DIGI <name>
#load PBXDA_BA/DIGI <name> #load PBXDA_BB/DIGI <name> #load PBXDA_AC/DIGI <name>

Example:

load PBXDA_AC/DIGI TXA

The adapter instance name ("TXA" in the example above) is used then for parametrization, for example:

set TXA line[2]="COM1:"
set TXA port[3]=1706

The numbers in the square brackets represent line number on the virtual PBXDA adapter starting from 0.

Controller type	Maximum number of lines
PBXDA	2
PBXDA_BA	4
PBXDA_BB	8
PBXDA_AC	16

It is possible to specify either physical port ("COM<n>") or an IP port for connecting the virtual PBXDA-xx to system resources. No other parameters are applicable in this type of emulation.

...

In "pass through" mode PBXDA-xx family controllers are mapped to specific models of the physical DIGI serial lines adapters installed on the CHARON VM host:

DEC PBXDA-xx adapter	Name of the device to map to	Controller	Vendor ID	Device ID
PBXDA-BA	DIGI AccelePort 4r 920	ASIC PCI	114Fh	0026h
PBXDA-BB	DIGI AccelePort 8r 920	ASIC PCI	114Fh	0027h
PBXDA-AC	DIGI AccelePort Xem	ASIC PCI	114Fh	0004h
PBXDA-AC	DIGI AccelePort Xem	ASIC PCI	114Fh	0008h

...

Pay attention to the proper placement of the emulated PBXDA-xx adapter on the virtual HP Alpha PCI bus (it is controlled by "bus", "device", "function", "irq" and "irq_bus" parameters). Refer to this chapter of this Guide for more information.

...

The "host_bus_location" parameter addresses the host DIGI adapter in the following way:

Parameters	Description
"bus X"	PCI bus number of the host DIGI adapter
"device Y"	PCI bus device number of the host DIGI adapter
"function Z"	The "function" parameter of the the host DIGI adapter

...

Non-US-EN installations of Windows may present “Location:” string in local language, but "host_bus_location" parameter requires English notation, so the words “PCI”, “bus”, “device”, and “function” must be specified in English.

Div

class	pagebreak

Auto boot

The CHARON VM Charon-AXP can be configured to automatically boot an operating system at start up immediately after it has started by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.

Example: dka0 is defined as the default boot device

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

Network boot

Charon-AXP can be configured to boot on network if the legacy operating system allows it via MOP. MOPv3 (DECnet) and MOPv4 (LANCP) are supported.

Usage/example:

P00>>>boot [-flags ...] [-file ...] ewa0

Both EW and EI adapters are supported for MOP network boot.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Versions Compared

Old Version 53

New Version Current

Key

Alpha model specification

Rotating log (default)

Setting a specific

Alpha model

Exit on pressing F6 button

Anchor
KGPSACA1
KGPSACA1
KGPSA-CA mapping to the host resources

VIrtual PBXDA-xx

Auto boot

Network boot

Parameter	Description
iScsiTarget	Addresses the disk by its iSCSI target name.
LUN	Specifies the LUN on the connected iSCSI disk.

Page Comparison

Versions Compared

Old Version 53

New Version Current

Key

Alpha model specification

Rotating log (default)

Setting a specific

Alpha model

Exit on pressing F6 button

AnchorKGPSACA1KGPSACA1KGPSA-CA mapping to the host resources

VIrtual PBXDA-xx

Auto boot

Network boot

Anchor
KGPSACA1
KGPSACA1
KGPSA-CA mapping to the host resources