...
After attaching the virtual disk, as described in Preparing to Install the Guest Utilities, use the POLYCENTER Software Installation (PCSI) utility to install the Bypass Driver. The following example demonstrates the PCSI PRODUCT INSTALL commands to execute and the expected output (the example assumes the utilities virtual disk image is attached at DKA400:).
| Panel |
|---|
| bgColor | #ffffff |
|---|
| titleBGColor | #f0f0f0 |
|---|
| title | Bypass Driver Installation |
|---|
|
$ PRODUCT INSTALL CHARON_DISK/SOURCE=DKA400:[BYPASS]
%PCSI-I-CANNOTVAL, cannot validate DKA400:[BYPASS]SRI-AXPVMS-CHARON_DISK-V0104--1.PCSI;1
-PCSI-I-NOTSIGNED, product kit is not signed and therefore has no manifest file
The following product has been selected:
SRI AXPVMS CHARON_DISK V1.4 Layered Product
Do you want to continue? [YES] YES
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements.
SRI AXPVMS CHARON_DISK V1.4: Charon disk driver V1.4 for OpenVMS Alpha.
Copyright (C) 1976, 2009 Software Resources International
CHARON_DISK was produced by Software Resources International
* This product does not have any configuration options.
Execution phase starting ...
The following product will be installed to destination:
SRI AXPVMS CHARON_DISK V1.4 DISK$TARDISSYSTEM:[VMS$COMMON.]
Portion done: 0%...10%...20%...80%...100%
The following product has been installed:
SRI AXPVMS CHARON_DISK V1.4 Layered Product
|
|
...
One of the benefits of the Bypass Driver is that it allows you to specify a storage technology other than SCSI for the controller. This can be particularly important if an existing native environment has been set up as dependant on a certain type of storage technology. The table below shows the command necessary to define a storage controller for the supported technologies. In the configuration command definition, n denotes the number of controllers to create.
| Panel |
|---|
| bgColor | #ffffff |
|---|
| titleBGColor | #f0f0f0 |
|---|
| title | Bypass Driver Storage Controllers |
|---|
|
| Control Type | Storage Technology | Configuration Commands |
|---|
| PG | FibreChannel | load n PG bypass | | PI | DSSI | load n PI bypass | | PK | SCSI | load n PK bypass | | PQ | IDE | load n PQ bypass | | PR | RAIDArray | load n PR bypass | | PU | MSCP | load n PU bypass |
|
...
Configuring a disk device as attached to a bypass enabled controller is no different for SCSI devices. For other storage technologies only the device class changes, all other object members mentioned in ... are applicable. The table below lists the disk device class for each storage technology.
| Panel |
|---|
| bgColor | #ffffff |
|---|
| titleBGColor | #f0f0f0 |
|---|
| title | Bypass Disk Device Classes |
|---|
|
| Device Class | Storage Technology | Example load Command |
|---|
| DG | FibreChannel | load DGA500 | | DI | DSSI | load DIA0 | | DK | SCSI | load DKA400 | | DQ | IDE | load DQA0 | | DR | RAIDArray | load DRA0 | | DU | MCSP | load DUA0: |
|
| Infonote |
|---|
It is not supported to connect non-disk devices (such as tape) to a storage adapter configured to use the bypass driver. |