...
Note | |
---|---|
In AlphaStation 400 configuration use the following syntax for KGPSA-CA storage adapter loading:
|
The adapter instance name ("FGA" in the example above) is used then for parametrization, for example:
...
Configuration parameters
The KGPSA-CA PCI FC adapter emulation has the following configuration parameters:
Anchor | ||||
---|---|---|---|---|
|
Parameter | storage_controller_path_id | |||
---|---|---|---|---|
Type | Text String | |||
Value | Instructs the CHARON software to create a set of virtual FC devices and connect to the virtual system through the virtual KGPSA FC Adapter. In this mode WWID and UDID values are taken from the storage controller directly. Note that some storage controllers may not support aquiring UDID, in this case this way of mapping cannot be used in case of OpenVMS (Tru64 Unix is Ok)! Syntax:
where the "Storage controller path ID" parameter is a storage (for example SAN) controller path ID. This ID can be obtained from the "Host Device Check" utility ("Storage Controllers" section): Once specified, all the disks attached to the storage are automatically mapped as disk units to CHARON. Example:
It is also possible to use wildcards for specifying the ID number, for example:
In this case CHARON will collect the LUNs from all the matching paths. This syntax works disregarding whether Windows MPIO is active or not. If it is active, CHARON uses "active" path (because it works through Windows), if Windows MPIO is OFF, CHARON selects the first matching path (and warns you in the LOG file). Note that LUNs obtained by usage of "storage_controller_path_id" parameter is not re-enumerated on reboot, so this mode is possible to use in case of shared disks clusters. |
Anchor | ||||
---|---|---|---|---|
|
Parameter | host_bus_location | ||
---|---|---|---|
Type | Text String | ||
Value | Establish connection between virtual DEC-KGPSA-CA PCI FC adapter and physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter (pass through mode) Syntax:
where X, Y, and Z describe location of physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter in the host computer (see this section for details). Example:
|
wwid
Parameter | wwid[N] N is 0..32766 (no more than 255 units) | ||
---|---|---|---|
Type | Text String | ||
Value | Sets WWID for emulated KGPSA adapter unit in case if the WWID can not be obtained directly from the device CHARON is mapped to. For example in case of disk images or local physical drives CHARON cannot get its WWID from the the host system, so it is automaticaly introduce some generated WWID. In case if this WWID is not acceptable it can be replaced with the custom one using the "wwid" parameter. Syntax:
Example:
|
Anchor | ||||
---|---|---|---|---|
|
Parameter | container[N] N is 0..32766 (no more than 255 units) | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Type | Text String | |||||||||||||||||||||||
Value | Possible values of the parameter are strings in one of the following forms:
This parameter is initially not set, thus creating NO storage elements on the controller.. |
media_type
Parameter | media_type[N] N is 0..32766 (no more than 255 units) | |
---|---|---|
Type | Text String | |
Value | Instructs CHARON-AXP to use the supplied value as the PRODUCT field in the FC INQUIRY data returned to a software running on virtual HP Alpha system in response to FC INQUIRY command. If not specified, CHARON-AXP attempts to guess the FC INQUIRY data based on virtual FC device type and underlying container (which is specified in the corresponding container configuration parameter). Initially is not specified. Example:
|
removable
Parameter | removable[N] N is 0..32766 (no more than 255 units) | |
---|---|---|
Type | Boolean | |
Value | When set to "true", the removable configuration parameter instructs CHARON-AXP to report the corresponding virtual FC device as removable. By default the removable configuration parameter is set to "false". Example:
|
Div | ||
---|---|---|
| ||
geometry
...
Parameter | use_io_file_buffering[N] N is 0..32766 (no more than 255 units) | |
---|---|---|
Type | Text String | |
Value | Instructs CHARON-AXP to enable host operating system I/O cache on reading/writing operations. The following values are possible:
Note this caching has a significant effect only in case of mapping to disk containers, not physical drives. When enabled, host operating system I/O cache may significantly improve I/O performance of the virtual system. At the same time maintaining I/O cache requires additional host resources (CPU and memory) which may negatively affect overall performance of the virtual system. Initially is set to "false". Example:
|
...
Mode | Description | Pros | Cons |
---|---|---|---|
Fabric virtualization mode | Virtual KGPSA-CA PCI FC adapter is mapped to physical disks (both local, FC and iSCSI) and disk images This is default mode, suitable for most cases |
|
|
"Presentation" mode | CHARON-AXP automatically creates/removes a set of virtual FC devices on a virtual KGPSA-CA FC adapter correspondent to available external SAN LUNs This mode is recommended in case of working with SAN that may change LUN configuration - so CHARON-AXP will reflect it on-fly w/o reconfiguration and restarting. |
|
|
Pass Through mode | This mode allows connection between virtual KGPSA-CA FC adapter and physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter plugged into host’s PCI/PCI-X/PCIe slot This mode is recommended for cluster setups that include HW Alphas |
|
|
...
|
Use only "Mapping by WWID" and "Mapping iSCSI disks" syntax in case of the mapped physical disk located on some external disk controller (SAN, etc) since the "\\.\PhysicalDrive<N>" re-enumeration may happen on CHARON host reboot.
Note that WWID and UDID is generated by CHARON in its mode. It may be important in case of shared disks cluster configurations.
...
Info |
---|
Usage of LUNs in cluster configuration: Note that PATHs (on OpenVMS level) do not affect OpenVMS cluster. What really makes sense is LUN size, geometry, WWI, etc. CHARON obtains these properties from the LUN (within the limits established by Windows), so LUNs should appear similar to all cluster members. |
Note that LUNs obtained by usage of "storage_controller_path_id" parameter is not re-enumerated on reboot, so this mode is possible to use in case of shared disks clusters.
Note that the WWID and UDID are automatically obtained from disk server (SAN) in this mode - it is very convenient in case of shared disks cluster configurations. Also note that some storage controllers may not support aquiring UDID - in this case this way of mapping cannot be used in case of OpenVMS (Tru64 Unix is Ok)!
...
|
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.
...