Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Every instance of KGPSA-CA works in one of the two following modes:
- Fabric virtualization mode 18401789411551 (creating virtual fabric in combination with virtual FC-3 Storage Controller). This is default mode.
- Pass Through mode 18401789411551 (using a specific CHARON PCI Pass Through driver)
- Fabric presentation mode 18401789411551 (using Linux FC HBA directly)
...
load KGPSA <name> |
Example:
load KGPSA FGA |
Please note:
In AlphaStation 400 configuration use the following syntax for KGPSA-CA storage adapter loading:
load KGPSA FGA irq_bus=isa
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:
host_bus_location
Parameter | host_bus_location |
---|---|
Type | Text String |
Value | KGPSA-CA PCI Fibre Channel adapter in Pass Through mode only ! Establish connection between virtual DEC-KGPSA-CA PCI FC adapter and physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter (KGPSA-CA PCI Fibre Channel adapter in Pass Through mode) 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:
"/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. These disks must not be formatted by the host OS. Example:
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. Example:
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:
It is possible to specify each parameter independently of another one. The following syntax is used for that: |
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. Note that 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:
|
Div | ||
---|---|---|
| ||
io_queue_depth
...
|
See the "KGPSA-CA PCI Fibre Channel adapter - Configuration parameters" section for details.
Include Page | ||||
---|---|---|---|---|
|
...
- Install the EMULEX LightPulse PCI/PCI-X/PCIe FC adapter (see above for a list of supported models) to some spare PCI/PCI-X/PCIe slot of the host system
- Build PPT driver for EMULEX LightPulse PCI/PCI-X/PCIe FC
- Install PPT driver for EMULEX LightPulse PCI/PCI-X/PCIe FC
- Add PPT driver for EMULEX LightPulse PCI/PCI-X/PCIe FC to Linux startup
- Map KGPSA-CA adapter(-s) to EMULEX LightPulse PCI/PCI-X/PCIe FC adapter instance(-s) in CHARON-AXP configuration file
...
If kernel of the host system has been upgraded or reinstalled all the steps of the PPT KGPSA driver installation must be repeated
Include Page | ||||
---|---|---|---|---|
|
...
Step | Description | |
---|---|---|
1 | Make sure that the required building tools and include files are installed. If they are absent install them:
Info | The kernel version must match the version of the installed kernel-headers (i.e. this packages must have same versions. It can be verified via Check that the "kernel", the "kernel-devel" and the "kernel-headers" have the same version, and ensure that system is booted from this kernel version (not from some older one and etc) with " |
2 | Open xterm and change the default directory to "
| |
3 | Issue "make clean; make" commands to build kernel object:
It is prohibited to use a module built on a certain version of kernel on another one. | |
4 | Check that there are no compilation errors and the file "ppt_kgpsa.ko " has been built |
...
Step | Description | |||||
---|---|---|---|---|---|---|
1 | Disable auto-loading of Linux standard "lpfc" driver on boot. To do that add "blacklist lpfc" to the black list file "/etc/modprobe.d/blacklist.conf " | |||||
2 | Copy the KGPSA-CA kernel module to the location of Linux kernel modules, for example:
The particular path may be different, depending on the kernel version and Linux distribution. | |||||
3 | Enable auto load of the module:
| |||||
4 | Regenerate new "initramfs" image with "mkinitrd":
The particular path may be different, depending on the kernel version and Linux distribution. |
...
To configure KGPSA-CA adapter in pass through mode a special SRM console utility "FCMGR" is used (it has the same functionality as the "WWIDMGR" utility of the native HP Alpha hardware).
Div | ||
---|---|---|
| ||
...
Command | Description |
---|---|
| Scans connected SAN using FC adapters, discovers FC ports, storage controllers, logical units and then builds volatile FC database. The "/verbose" qualifier enables FC communication trace on console (for diagnostic and troubleshooting). |
| Displays corresponding part of volatile FC database. |
| Fills the environment variables wwid0..wwid3 and n1..n4 to identify path(s) to logical unit with the specified UDID. These variables are later used by "INIT" to create device database entries and by OpenVMS/Tru64 to get access to boot and dump disks. This command does NOT make any change to other environment variables. |
fc set {boot | dump} wwid <X> | Fills the environment variables wwid0..wwid3 and n1..n4 to identify path(s) to logical unit with the specified WWID. These variables are later used by "INIT" to create device database entries and by OpenVMS/Tru64 to get access to boot and dump disks. This command does NOT make any change to other environment variables. This parameter is useful if UDID is absent. Please note: Only right part of the displayed WWID is used for specification, for example:
|
| Clears environment variables wwid0..wwid3 and n1..n4, which automatically disable (but do NOT delete) device database entries representing FC attached devices. This command does NOT affect volatile FC database. |
...
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.
...
This mode is available only for CHARON-AXP on RHEL and CentOS 7.x
...
and later versions
...
.
FC HBA interfaces finding
...
|
So the connected hosts are 3 and 6 ("MSA CONTROLLER").
...
|
...
The configuration given with port name is independent on hardware change, modules load order, etc
By host id name
|
...
|
...
The configuration given with host id name might change on hardware change, modules load order, etc
Include Page | ||||
---|---|---|---|---|
|
...
Name of FC, SCSI host or adapter's port/node name, defining a connection to Linux FC HBA, for example:
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:
|
...
I/O model is used for request processing.
...
This parameter is needed for debugging puproses only, so it is strongly recommended not to specify any value without particular instructions from Stromasys.
Value | Description |
---|---|
sync | synchronous |
async | asynchronous (default) |
...
The port name in format: %04x-%04x-%04x-%04x. Option to fake guest's port name.
...
This parameter is needed for debugging puproses only, so it is strongly recommended not to specify any value without particular instructions from Stromasys.
Example:
|
...
The node name in format: %04x-%04x-%04x-%04x. Option to fake guest's node name.
...
This parameter is needed for debugging puproses only, so it is strongly recommended not to specify any value without particular instructions from Stromasys.
Example:
|
...
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:
Div | ||
---|---|---|
| ||
|
Please 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 Please note: 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:
Div | ||
---|---|---|
| ||
|
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.
Value (ANSI SCSI version) | Description |
---|---|
any | Any version |
v1 | SCSI-1 |
v2 | SCSI-2 |
v3 | SCSI-3 |
v3_SPC1 | SCSI-3, primary command level 1 |
v3_SPC2 | SCSI-3, primary command level 2 (default) |
v3_SPC3 | SCSI-3, primary command level 3 |
v3_SPC4 | SCSI-3, primary command level 4 |
Refer Refer to your guest OS documentation for more details and public resources for general specification of SCSI.
...
A fake device id (if not "lp8000" is needed), the default is "0xF800" ("lp8000").
...
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:
|
...
A fake vendor id (if not "lp8000" is needed), the default is "0x10DF" ("lp8000").
...
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:
|
...
A fake revision id (if not "lp8000" is needed), the default is "0x02" ("lp8000").
...
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:
|
...
Value | Description |
---|---|
false | Responses delivered to the emulated KGPSA card in order they were submitted to Linux. This is the default value. |
true | Responses delivered to the emulated KGPSA card in order they were completed by Linux |
...
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:
|
...
Value | Description |
---|---|
unlimited | Linux SG I/O applies limitation of 16 I/Os. Requests are submitted unless write to SG I/O fails. This is the default value. |
1...16 | Only the specified number of the requests are submitted in parallel. |
...
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:
|
...