Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
You can optionally uncomment this line to differentiate this CHARON-AXP instance from all others in a multi-instance environment. The configuration name can be any label that is meaningful.
It is possible to specify a configuration name containing spaces, in this case use quotation marks:
set session configuration_name = "My ES40" |
The configuration name is reported in the log file and is used to set the log file name for rotating log (see further: Rotating log (default) ).
...
Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.
Note |
---|
Only existing directory can be used as a value of the "log" parameter. |
Single log
Alternatively it is possible to use just a single log file. Uncomment the "set session log" line and specify the desired CHARON-AXP log file name. Optionally, a path can be added to the log file name. If the path is not specified, the log file is created in the directory from where the guest (emulated machine) is started.
...
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 ; this value is specific for each HP Alpha model.
...
) and number of CPUs needed for CHARON application itself ("n_of_io_cpus").
Number of host CPUs dedicated to CHARON I/O
...
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.
...
Option | Description | |||||||
---|---|---|---|---|---|---|---|---|
physical_serial_line | Mapping to host "\\.\COM<n>" ("COM<n>:") physical serial line. | |||||||
virtual_serial_line | Mapping to an IP port of CHARON-AXP host.
Example:
In the example above, CHARON-AXP use the IP port "10003" for the HP Alpha console and starts the "Putty" terminal emulator (included in each CHARON distributive) with the "OPA0" saved session directing it to connect to the IP port "10003". If the terminal emulator is closed, it is always possible to reopen it with the "Show Console" command from the CHARON system tray icon: |
The default setting is "load virtual_serial_line/chserial OPA0 port=10003 application="putty.exe -load OPA0".
...
CHARON-AXP supports DE435, DE450, DE500AA, DE500BA and , DE602 virtual and DE602AA virtual network adapters.
All of them are configured in a similar way:
|
load DE602/i8255x EIA interface=EIA0 load packet_port/chnetwrk EIA0 interface="connection:Charon" |
In the example examples above the first line loads DE500BA/DE602 virtual adapter with a name "EWA"/"EIA" (note that "/i8255x" syntax must be used only in case of DE602 and DE602AA adapters); the following line maps it to host network interface having a name "Charon" ("connection" is a key word). Note that the mapping is performed in 2 steps:
- A mapping object "packet_port" with a name "EWA0"/"EIA0" is loaded and connected to host interface having a name "Charon", so CHARON-AXP will use this interface for its networking
- The loaded DE500BA virtual DE500BA/DE602 virtual adapter "EWA"/"EIA" is connected to the "packet_port" object "EWA0"/"EIA0".
It is possible to load several DE435, DE450, DE500AA, DE500BA or DE602 controllers, for example (for DE500BA):
|
...
The first line ("load KZPBA PKA") loads disk controller KZPBA with name "PKA", followed by 8 group of lines showing different ways of mapping to the host resources:
...
- 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 (recommended), for example: "C:\My disks\my_boot_disk.vdisk"
- "<file-name>.vdisk"
...
.
- Physical disk
- "\\.\
...
- PhysicalDrive<N>"
- PhysicalDrive<N>"
...
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
These disks must not be formatted by the host OS.
.
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
- Physical disk by its WWID
- "\\.\PhysicalDrive(DevID =
...
- XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
- XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
...
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP 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]=
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
...
"\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)
...
"
.
- iSCSI disks
"\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
Mapping to iSCSI disks.
Parameter Description iScsiTarget Addresses the disk by its iSCSI target name. LUN Specifies LUN on connected iSCSI disk. Example:
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>"
.
- \\.\CdRom<N>"
- ISO file for reading distribution CD-ROM image
- "<file-name>.iso"
Mapping may also include the full path (recommended), for example: "C:\My disks\vms_distributive.iso"
.
- "<file-name>.iso"
- Host tape device
- "\\.\Tape<N>"
- "\\.\Tape<N>"
...
- .
- File representing the tape (tape image)
- "<file-name>.vtape"
These files are created automatically.
Mapping may also include a full path (recommended), for example: "C:\My tapes\backup.vtape"
- "<file-name>.vtape"
...
- .
...
...
- Floppy drive
...
- "\\.\
...
- A:"
...
.
- Other type of drive, for example magneto-optical drive
- "\\.\<N>:"
.
- "\\.\<N>:"
Additionally it is possible to specify a parameter "media_type" to assign the type of the attached media explicitly.
...
Parameter | Range | Description | |
---|---|---|---|
XX | 0...15 | Stands for SCSI ID of each connected unit. Note that KZPBA itself has some ID associated with it. By default it is 7, but it can be changed in the following way:
In this example an instance "PKA" of KZPBA controller is assigned with SCSI ID 0. | |
YY | 00...07 | Stands for LUN. |
...
Follow this link for details of KZPBA controllers configuration.
Back to Table of Contents
KGPSA-CA PCI FC disk controller
...
Follow this link for details of KGPSA-CA controllers configuration.
Back to Table of Contents
KGPSA-CA mapping to the host resources
...
The first line ("load KGPSA FGA") loads disk controller KGPSA with name "FGA", followed by 2 group of lines showing different ways of mapping to the host resources:
...
ways of mapping to the host resources:
- 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 (recommended), for example: "C:\My disks\my_boot_disk.vdisk"
- "<file-name>.vdisk"
...
.
- Physical disk
- "\\.\PhysicalDriveN"
- "\\.\PhysicalDriveN"
...
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
These disks must not be formatted by the host OS.
.
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
- Physical disk by its WWID
- "\\.\PhysicalDrive(DevID =
...
- XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
- XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
...
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP 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]=
- Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake.
...
"\\.\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 connected iSCSI disk.
...
Example:
set PKA container[200]=
...
"\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)
...
"
.
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.
Back to Table of Contents
KGPSA-CA mapping to a storage controller using its "presentation" mode
...
The main benefit in this type of mapping is a flexible way of the virtual disks management depending on the mapped storage controller configuration. For example if an extra disk is added to the storage controller it automatically appears as a new disk unit on the corresponding KGPSA-CA virtual adapter mapped to that storage controller.
Div | ||
---|---|---|
| ||
|
Below is an example of KGPSA-CA PCI FC disk controller, mapped to some storage controller (for example SAN) using its "presentation" mode:
|
Div | ||
---|---|---|
| ||
|
This line loads an instance of KGPSA-CA controller and maps it to some extarnal controler having 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 "Host Device Check". Once specified, all the disks attached to the storage are automatically mapped as disk units to CHARON-AXP. |
Back to Table of Contents
KGPSA-CA pass through mode
...
Supported | Not Supported | Not tested |
---|---|---|
LP8000 | LPe1150 (FC2142SR, A8002A) | LPe11000 |
Back to Table of Contents
Div | ||
---|---|---|
| ||
|
FDDI support via DEFPA PCI FDDI controller in "pass through" mode
...
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.
Back to Table of Contents
Div | ||
---|---|---|
| ||
|
Serial lines support via emulated PBXDA-xx family PCI controllers in "pass through" mode
...
Example: dka0 is defined as the default boot device
|
...