Versions Compared

Old Version 37

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

Saved on

compared with

New Version Current

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

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DE602 syntax is added

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

...

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.

...

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 DE500BA/dec21x4x EWA interface=EWA0
load packet_port/chnetwrk EWA0 interface="connection:Charon"

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"; the following line maps it to host network interface having a name "Charon" (/"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:

  1. 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
  2. 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): 

load DE500BA/dec21x4x EWA interface=EWA0
load packet_port/chnetwrk EWA0 interface="connection:Charon1"
load DE500BA/dec21x4x EWB interface=EWB0
load packet_port/chnetwrk EWB0 interface="connection:Charon2"

...

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"

...


    • .
  • Physical disk
    • "\\.\PhysicalDrive<N>"

...

    • (warning) 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.

      .
  • Physical disk by its WWID
    • "\\.\PhysicalDrive(DevID =

...

    • XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"

...

    • (warning) 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]=

...

    • "\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)

...

    • "

      .

  • iSCSI disks

    • "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"

...



    • ParameterDescription
      iScsiTargetAddresses the disk by its iSCSI target name.
      LUNSpecifies 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.

      ParameterDescription
      NA logical number assigned by host operating system (Microsoft Windows) to logical or host’s physical storage resource such as physical SCSI HBA
      XAn internal SCSI bus number (usually 0) on host’s physical SCSI HBA
      YA SCSI ID of physical SCSI target device attached to host’s physical SCSI HBA
      ZA 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 (recommended), for example: "C:\My disks\vms_distributive.iso"
      .
  • Host tape device
    • "\\.\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"

...

    • .

...

...

  • Floppy drive

...

    • "\\.\

...

    • A:"

...

    • .
  • Other type of drive, for example magneto-optical

...

  • drive
    • "\\.\<N>:"
      .

Additionally it is possible to specify a parameter "media_type" to assign the type of the attached media explicitly.

...

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:

...

  • 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"

...


    • .
  • Physical disk
    • "\\.\PhysicalDriveN"

...

    • (warning) 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.
      .

  • Physical disk by its WWID
    • "\\.\PhysicalDrive(DevID =

...

    • XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"

...

    • (warning) 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]=

...

    • "\\.\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.

...

classpagebreak

...

Below is an example of KGPSA-CA PCI FC disk controller, mapped to some storage controller (for example SAN) using its "presentation" mode:

load KGPSA FGA storage_controller_path_id = 5008-05F3-0005-2950-5008-05F3-0005-2951

Div
classpagebreak

 

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 mappingDescription
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

...

SupportedNot SupportedNot tested

LP8000
LP9000
LP9002
LP9802
LP10000
LP10000DC
LP10000-S
LPX1000
LP11002
LPe11002 (FC2242SR, A8003A)
LPe1105

LPe1150 (FC2142SR, A8002A)LPe11000

Back to Table of Contents

Div
classpagebreak

 

FDDI support via DEFPA PCI FDDI controller in "pass through" mode

...

(warning) 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
classpagebreak

 

Serial lines support via emulated PBXDA-xx family PCI controllers in "pass through" mode

...