| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
Syntax for loading KGPSA-CA storage adapter:
load KGPSA <name> |
Example:
load KGPSA FGA |
| Note |
|---|
In AlphaStation 400 configuration use the following syntax for KGPSA-CA storage adapter loading:
|
...
Configuration parameters
The KGPSA-CA PCI FC adapter emulation has the following configuration parameters:
host_bus_location
| 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 mode695402720) Syntax:
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. Syntax:
Example:
|
| Div | ||
|---|---|---|
| ||
container
| 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. |
| Div | ||
|---|---|---|
| ||
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 | geometry[N] N is 0..32766 (no more than 255 units) |
|---|---|
| Type | Text String |
| Value | This formatted string value specifies the explicit geometry of the disk storage element. The string format is <X>”/”<Y>[“/”<Z>] or <X>”,”<Y>[“,”<Z>][“,”<B>] where:
If this parameter is not set, CHARON-AXP will configure the geometry based on the most probable disk type. Initially not set. Example:
|
use_io_file_buffering
| Parameter | use_io_file_buffering[N] N is 0..32766 (no more than 255 units) |
|---|---|
| Type | Boolean |
| Value | When set to "true", instructs CHARON-AXP to enable host operating system I/O cache on read/write operations.
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:
|
| Div | ||
|---|---|---|
| ||
io_queue_depth
...
In this mode KGPSA-CA PCI FC adapter can be directly mapped to physical disks (both local and iSCSI) and disk images as shown in the following example:
|
See the "Configuration parameters" section for details.
...
The CHARON-AXP FC Fabric presentation mode allows to use Linux FC HBA directly. When using this mode, there is no need to load KGPSA adapter(s) as it was described before. The following syntax has to be used instead:
Example:
load kgpsa_generic_storage PGA interface="host3" |
Below please find step-by-step explanation on how to configure "kgpsa_generic_storage" instance.
...
First we need to find Linux FC HBA for mapping.
List available adapters
|
So, 2 HBAs, 3 ports are available.
...
Load HBA's kernel modules (drivers)
|
Discover the Linux SCSI hosts the FC HBAs are mapped to
|
So, the available ports are mapped to hosts 3, 4 and 6.
Discover the connected FC HBAs (ports)
|
So the connected hosts are 3 and 6 ("MSA CONTROLLER").
Discover the HBAs port/node names
|
So the names are:
| Host | Mapping | Port name |
|---|---|---|
| 3 | Lancer-X, port 0 ("3:0:0:0") | 0x10000090faa00a31 |
| 4 | Lancer-X, port 1 ("3:0:0:1") | 0x10000090faa00a32 |
| 6 | LP8000 single port | 0x10000000c923ea51 |
...
Specify Linux port name "0x10000090faa00a31" in Charon configuration file:
|
| Note |
|---|
The configuration given with port name is independent on hardware change, modules load order, etc |
By host id name
|
or
|
| Note |
|---|
The configuration given with host id name might change on hardware change, modules load order, etc |
...
| Mapping | Description |
|---|---|
fc_host6 | Emulation over Linux SG (FC) host 6 |
host6 | Emulation over Linux SG (FC) host 6 |
2000-0000-C923-EA51 | Emulation over Linux SG (FC) host given with port/node name |
0x20000000C923EA51 | Emulation over Linux SG (FC) host given with port/node name |
wwn-0x20000000C923EA51 | Emulation over Linux SG (FC) host given with port/node name |
Example:
|
| Div | ||
|---|---|---|
| ||
trace_level
| Value | Description |
|---|---|
0 | none (default) |
1 | All failures and suspects |
| 2 | SCSI, ELS/CT request flow |
3 | MB/IOCB request flow |
Example:
|
io_model
I/O model is used for request processing.
...
| Value | Description |
|---|---|
sync | synchronous |
async | asynchronous (default) |
Example:
|
port_name
The port name in format: %04x-%04x-%04x-%04x. Option to fake guest's port name.
| Note |
|---|
This parameter is needed for debugging puproses only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
By default this value is obtained from the specified hardware port (see above).
...
| Note |
|---|
This parameter is needed for debugging puproses only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
By default this value is obtained from the specified hardware port (see above).
...
When FC wire is removed and then plugged in, Linux rebuilds all the FC objects with new devices names, etc. Fabric presentation mode senses the link up and down events, but optionally it may delay reporting the event (for the given amount of seconds) to let Linux fully initialize FC. If delay is 0, guest OS may start initialization too early and thus fail to find some or all objects.
Example:
|
link_poll_period
The link check poill interval in seconds Default is 1 second.
When FC wire is removed and then plugged in, Linux rebuilds all the FC objects with new devices names, etc. Fabric presentation mode senses the link up and down events, but optionally it may delay reporting the event (for the given amount of seconds) to let Linux fully initialize FC. If delay is 0, guest OS may start initialization too early and thus fail to find some or all objects.
Example:
|
emu_fabric
The way the emulation deals with fabric:
...
Qlogic does not map SG devices for ELS/CT traffic. To work around this, Fabric presentation mode implements emulation of the whole non FCP (scsi) communication over fabric. If fabric is emulated, guest OS will not see non FCP target ports (for example initiators) and will not be able to communicate with ELS/CT over fabric.
Example:
|
| Div | ||
|---|---|---|
| ||
lun_exclude
The list of the LUNs to be excluded. If empty (default), nothing is excluded.
No multi line is possible for this parameter; the maximum number of symbols inside the double quotes is 255. Use "lun_include" parameter instead if a lot of LUNs must be excluded to specify only the included LUNs.
Example:
|
| Note |
|---|
lun_exclude parameter cannot exclude storage mapped to LUN 0 because of its special function. |
lun_include
The list of the LUNs to be included. If empty (default), all LUNs are included. No multi line is possible for this parameter; the maximum number of symbols inside the double quotes is 255. Use "lun_exclude" parameter instead if a lot of LUNs must be included to specify only the excluded LUNs.
Example:
|
scsi_version
This approach of FC emulation downgrades all attached devices to the specifically defined version of SCSI. This is done to make legacy guest operating systems happy with attached modern devices.
...
Refer to your guest OS documentation for more details and public resources for general specification of SCSI.
Example:
|
| Div | ||
|---|---|---|
| ||
device_id
...
| Note |
|---|
This parameter is needed for some specific cases only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
vendor_id
A fake vendor id (if not "lp8000" is needed), the default is "0x10DF" ("lp8000").
| Note |
|---|
This parameter is needed for some specific cases only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
revision_id
A fake revision id (if not "lp8000" is needed), the default is "0x02" ("lp8000").
| Note |
|---|
This parameter is needed for some specific cases only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
scsi_serialize_io
This parameter controls serialization of the SCSI requests.
...
| Note |
|---|
This parameter is needed for some specific cases only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
| Div | ||
|---|---|---|
| ||
scsi_max_queue_depth
...
| Note |
|---|
This parameter is needed for some specific cases only, so it is strongly recommended not to specify any value without particular instructions from Stromasys. |
Example:
|
| Include Page | ||||
|---|---|---|---|---|
|