| Anchor |
|---|
| TopConfigurationPage |
|---|
| TopConfigurationPage |
|---|
|
| Include Page |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
|
...
| Type of mapping | Description |
|---|
| "<file-name>.vdisk" | Mapping to files representing physical disks of the VAX system (disk images).
These files can be created from scratch with "mkdskcmd" utility. Data and OS disk 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: "/my_disks/my_boot_disk.vdisk" |
| "/dev/sd<L>" | Mapping to physical disks. "L" is letter here. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake! These disks can not be formatted by the host OS.  It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used.
| Note |
|---|
Since "/dev/sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/ |
sr<N>"Mapping to CD-ROMs. There are some variants of this mapping: disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages (see below). |
|
| "/dev/ | cdrom<N>dm-<N>" | or
"/dev/mapper/ | cdrommpath<N>"
" | <file-name>.iso/dev/mapper/disk<N>" | Mapping | to an ISO file for reading distribution CD-ROM images.
Numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, line 3 of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.
...
to multipath disk.  Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake. These disks must not be formatted by the host OS. |
| "/dev/disk/by-*" | Mapping to physical disk. - by-id (addressing by the disk ID, for example "/dev/disk/by-id/ata-ST1000DM003-9YN162_S1D01QJ4")
- by-label (addressing by the disk label, for example "/dev/disk/by-label/MyStorage")
- by-uuid (addressing by the disk UUID, for example "/dev/disk/by-uuid/0e808a2f-cdd3-4944-a245-f729ffd73882")
Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake. These disks must not be formatted by the host OS. |
| "/dev/sr<N>" | Mapping to CD-ROMs. There are some variants of this mapping: "/dev/cdrom<N>" or "/dev/cdrom" |
| "<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM images. |
Numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, line 3 of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.
It is possible to load several RQDX3 controllers DUB, DUC, etc. (see lines 6-7, above) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX console to determine the addresses. Please refer to specific HP documentation for further information.
...
Follow this link for details of (T)MSCP controllers configuration.
Back to Table of Contents
SCSI controller NCR53C94
The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.
...
# Mapping to disk image
load virtual_scsi_disk pka_0 scsi_bus=pka scsi_id=0
set pka_0 container="<file-name>.vdisk"
# Mapping to physical disk
load virtual_scsi_disk pka_1 scsi_bus=pka scsi_id=1
set pka_1 container="/dev/sd<L>"
# Mapping to some SCSI device connected to the host
load physical_scsi_device pka_2 scsi_bus=pka scsi_id=2
set pka_2 container="/dev/sg<N>"
# Mapping to host CD-ROM or DVD-ROM
load virtual_scsi_cdrom pka_3 scsi_bus = pka scsi_id = 3
set pka_3 container = "/dev/cdrom<N>"
#set pka_3 container = "/dev/sr<N>"
# Mapping to *.ISO image
load virtual_scsi_cdrom pka_4 scsi_bus=pka scsi_id=4
set pka_4 container="<file-name>.iso"
# Mapping to tape drive
load physical_scsi_device pka_5 scsi_bus=pka scsi_id=5
set pka_5 container="/dev/sg<N>"
# Mapping to tape image
load virtual_scsi_tape pka_6 scsi_bus=pka scsi_id=6
set pka_6 container="<file-name>.vtape"
# Include this line to get access to "PKB" adapter
include kzdda.cfg
|
| Mapping Object | Description |
|---|
| virtual_scsi_disk | Mapping to a file representing VAX disk (disk image) on the host physical disk: "<file-name>.vdisk"
These files can be created from scratch with "mkdskcmd" utility. Data and OS disk 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: "/my_disks/my_boot_disk.vdisk"
"/dev/sd<L>" - name of a physical disk. "L" is letter here."/dev/dm-<N>", "/dev/mapper/mpath<N>", "/dev/mapper/disk<N>" - for multipath disks. N is 0,1,2...# Mapping to host floppy drive
load virtual_scsi_disk pkb_6 scsi_bus=pkb scsi_id=6
set pkb_6 container="/dev/fd<N>"
|
Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:
_scsi_disk pkb_6 scsi_bus=pkb scsi_id=6
set pkb_6 container="/dev/fd<N>"
|
Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:
| Mapping Object | Description |
|---|
| virtual_scsi_disk | Mapping to a file representing VAX disk (disk image) on the host physical disk: - "<file-name>.vdisk"
These files can be created from scratch with "mkdskcmd" utility. Data and OS disk 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: "/my_disks/my_boot_disk.vdisk"
- "/dev/sd<L>" - name of a physical disk. "L" is letter here.
- "/dev/dm-<N>", "/dev/mapper/mpath<N>", "/dev/mapper/disk<N>" - for multipath disks. N is 0,1,2...
- "/dev/disk/by-id/..." - addressing by the disk ID, for example "/dev/disk/by-id/ata-ST1000DM003-9YN162_S1D01QJ4"
- "/dev/disk/by-label/..." - addressing by the disk label, for example "/dev/disk/by-label/MyStorage"
- "/dev/disk/by-uuid/..." - addressing by the disk UUID, for example "/dev/disk/by-uuid/0e808a2f-cdd3-4944-a245-f729ffd73882"
- "/dev/df<N>" - name of host CD-ROM drive. N is 0,1,2... This parameter can be omitted.
Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake! These disks can not be formatted by the host OS. | Note |
|---|
Since "/dev/sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages. |
It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used. |
| physical_scsi_device | Mapping to a host SCSI device: - "/dev/sg<N>" - name of the SCSI device for direct mapping, for example, a SCSI disk or tape reader.
|
| virtual_scsi_cdrom | Mapping to a host CD-ROM (not only SCSI) or to ISO image: - "/dev/sr<N>", "/dev/cdrom", "/dev/cdrom<N>" - name of host CD-ROM drive
- "<file-name>.iso" - name of ISO image. It may contain the full path, for example: "/my_disks/vms_distributive.iso"
|
| virtual_scsi_tape | Mapping to a file representing tape (tape image). It may contain a path, for example: "/my_tapes/backup.vtape" |
Let's look at the syntax of the mapping objects. All of them have several important parameters:
...