| Anchor | ||||
|---|---|---|---|---|
|
...
|
| Div | ||
|---|---|---|
| ||
|
Some network adapters available in CHARON-AXP are preloaded (for example, HP AlphaServer DS15 contains 2 preloaded adapters EWA and EWB), so their configuration is even more simple:
...
| Type of mapping | Description | ||||||
|---|---|---|---|---|---|---|---|
| "<file-name>.vdisk" | Mapping to files representing physical disks of the HP Alpha system (disk images). | ||||||
| "/dev/sd<L>" | Mapping to physical disk. "L" is letter here. These disks must not be formatted by the host OS.
| dm-<N>"
| mapper/mpath<N>"
| ||||
"/dev/dm-<N>" | Mapping to multipath disk.  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. | ||||||
| "/dev/sg<N>disk/by-*" | Direct mapping to some SCSI device, for example, a SCSI disk or tape reader. How to find proper "/dev/sg" device is explined in this section. | ||||||
"/dev/sr<N>" | Mapping to host CD-ROM device. | ||||||
| "<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM image. Mapping may also include the full path (recommended), for example: "/my_disks/vms_distributive.iso" | ||||||
| "<file-name>.vtape" | Mapping to the file representing the tape (tape image). These files are created automatically. Mapping may also include a full path (recommended), for example: "/my_tapes/backup.vtape" |
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. Additionally it is possible to specify a parameter "media_type" to assign the type of the attached media explicitly.
Example:
|
Numbers in the square brackets represent 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.
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 had one or two KZPBA controllers preloaded. 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:
load KZPBA PKA bus=pci_1 device=1 function=0 irq_bus=isa irq=24 |
Follow this link for details of KZPBA controllers configuration.
Back to Table of Contents
KGPSA-CA PCI FC disk controller
Optionally it is possible to configure KGPSA-CA FC disk controller.
It can be configured in 2 modes:
Below is an example of KGPSA-CA controller loading:
|
Optionally another KGPSA-CA adapter can be loaded similar way:
|
Follow this link for details of KGPSA-CA controllers configuration.
Back to Table of Contents
KGPSA-CA mapping to the host resources
Below is the typical configuration options for KGPSA-CA PCI FC disk controller, mapped to the host resources ("L" is letter here):
|
The first line ("load KGPSA FGA") loads disk controller KGPSA with name "FGA", followed by 2 groups of lines showing different ways of mapping to the host resources:
| Type of mapping | Description |
|---|---|
| "<file-name>.vdisk" | Mapping to the file representing a physical disk of the HP Alpha system (disk image). 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 (recommended), for example: "/my_disks/my_boot_disk.vdisk" |
| "/dev/sd<L>" | Mapping to physical disk. "L" is letter hereMapping to physical disk.
These disks must not be formatted by the host OS. |
| "/dev/sg<N>" | Direct mapping to some SCSI device, for example, a SCSI disk or tape reader. How to find proper "/dev/sg" device is explined in this section. |
"/dev/sr<N>" | Mapping to host CD-ROM device. |
| "<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM image. Mapping may also include the full path (recommended), for example: "/my_disks/vms_distributive.iso" |
| "<file-name>.vtape" | Mapping to the file representing the tape (tape image). These files are created automatically. Mapping may also include a full path (recommended), for example: "/my_tapes/backup.vtape" |
Additionally it is possible to specify a parameter "media_type" to assign the type of the attached media explicitly.
Example:
|
Numbers in the square brackets represent 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.
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 had one or two KZPBA controllers preloaded. 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:
load KZPBA PKA bus=pci_1 device=1 function=0 irq_bus=isa irq=24 |
Follow this link for details of KZPBA controllers configuration.
Back to Table of Contents
KGPSA-CA PCI FC disk controller
Optionally it is possible to configure KGPSA-CA FC disk controller.
It can be configured in 2 modes:
Below is an example of KGPSA-CA controller loading:
|
Optionally another KGPSA-CA adapter can be loaded similar way:
|
Follow this link for details of KGPSA-CA controllers configuration.
Back to Table of Contents
KGPSA-CA mapping to the host resources
Below is the typical configuration options for KGPSA-CA PCI FC disk controller, mapped to the host resources ("L" is letter here):
|
The first line ("load KGPSA FGA") loads disk controller KGPSA with name "FGA", followed by 2 groups of lines showing different ways of mapping to the host resources:
| Type of mapping | Description | ||
|---|---|---|---|
| "<file-name>.vdisk" | Mapping to the file representing a physical disk of the HP Alpha system (disk image). 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 (recommended), for example: "/my_disks/my_boot_disk.vdisk" | ||
| "/dev/sd<L>" | Mapping to physical disk. "L" is letter here These disks must not be formatted by the host OS.
| ||
| "/dev/dm-<N>" "/dev/mapper/mpath<N>" "/dev/mapper/disk<N>" | Mapping to multipath disk. 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. | ||
| "/dev/disk/ | sd<L><N>" where N is the number of partition to be used.by-*" | Mapping to physical disk.
These disks must not be formatted by the host OS. |
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 pass through mode
...
Follow this link for detailed description of building and installation of EMULEX LightPulse PCI/PCI-X/PCIe FC adapter driver.
Back to Table of Contents
Auto boot
CHARON-AXP can be configured to automatically boot an operating system at start up by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.
...