mirror of https://github.com/ceph/ceph
101 lines
2.8 KiB
ReStructuredText
101 lines
2.8 KiB
ReStructuredText
|
-----------------------------------------
|
|||
|
|
The iSCSI Initiator for Microsoft Windows
|
|||
|
|
-----------------------------------------
|
|||
|
|
|
|||
|
|
**Prerequisite:**
|
|||
|
|
|
|||
|
|
- Microsoft Windows 2016
|
|||
|
|
|
|||
|
|
**iSCSI Initiator, Discovery and Setup:**
|
|||
|
|
|
|||
|
|
1. Install the iSCSI initiator driver and MPIO tools.
|
|||
|
|
|
|||
|
|
2. Launch the MPIO program, click on the “Discover Multi-Paths” tab select “Add
|
|||
|
|
support for iSCSI devices”.
|
|||
|
|
|
|||
|
|
3. On the iSCSI Initiator Properties window, on the "Discovery" tab, add a target
|
|||
|
|
portal. Enter the IP address or DNS name and Port of the Ceph iSCSI gateway.
|
|||
|
|
|
|||
|
|
4. On the “Targets” tab, select the target and click on “Connect”.
|
|||
|
|
|
|||
|
|
5. On the “Connect To Target” window, select the “Enable multi-path” option, and
|
|||
|
|
click the “Advanced” button.
|
|||
|
|
|
|||
|
|
6. Under the "Connet using" section, select a “Target portal IP” . Select the
|
|||
|
|
“Enable CHAP login on” and enter the "Name" and "Target secret" values from the
|
|||
|
|
Ceph iSCSI Ansible client credentials section, and click OK.
|
|||
|
|
|
|||
|
|
7. Repeat steps 5 and 6 for each target portal defined when setting up
|
|||
|
|
the iSCSI gateway.
|
|||
|
|
|
|||
|
|
**Multipath IO Setup:**
|
|||
|
|
|
|||
|
|
Configuring the MPIO load balancing policy, setting the timeout and
|
|||
|
|
retry options are using PowerShell with the ``mpclaim`` command. The
|
|||
|
|
reset is done in the MPIO tool.
|
|||
|
|
|
|||
|
|
.. NOTE::
|
|||
|
|
It is recommended to increase the ``PDORemovePeriod`` option to 120
|
|||
|
|
seconds from PowerShell. This value might need to be adjusted based
|
|||
|
|
on the application. When all paths are down, and 120 seconds
|
|||
|
|
expires, the operating system will start failing IO requests.
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
Set-MPIOSetting -NewPDORemovePeriod 120
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
mpclaim.exe -l -m 1
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
mpclaim -s -m
|
|||
|
|
MSDSM-wide Load Balance Policy: Fail Over Only
|
|||
|
|
|
|||
|
|
1. Using the MPIO tool, from the “Targets” tab, click on the
|
|||
|
|
“Devices…” button:
|
|||
|
|
|
|||
|
|
2. From the Devices window, select a disk and click the
|
|||
|
|
“MPIO…” button:
|
|||
|
|
|
|||
|
|
3. On the "Device Details" window the paths to each target portal is
|
|||
|
|
displayed. If using the ``ceph-iscsi-ansible`` setup method, the
|
|||
|
|
iSCSI gateway will use ALUA to tell the iSCSI initiator which path
|
|||
|
|
and iSCSI gateway should be used as the primary path. The Load
|
|||
|
|
Balancing Policy “Fail Over Only” must be selected
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
mpclaim -s -d $MPIO_DISK_ID
|
|||
|
|
|
|||
|
|
.. NOTE::
|
|||
|
|
For the ``ceph-iscsi-ansible`` setup method, there will be one
|
|||
|
|
Active/Optimized path which is the path to the iSCSI gateway node
|
|||
|
|
that owns the LUN, and there will be an Active/Unoptimized path for
|
|||
|
|
each other iSCSI gateway node.
|
|||
|
|
|
|||
|
|
**Tuning:**
|
|||
|
|
|
|||
|
|
Consider using the following registry settings:
|
|||
|
|
|
|||
|
|
- Windows Disk Timeout
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
DiskTimeout = 25
|
|||
|
|
|
|||
|
|
- Microsoft iSCSI Initiator Driver
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
HKEY_LOCAL_MACHINE\\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\<Instance_Number>\Parameters
|
|||
|
|
|
|||
|
|
::
|
|||
|
|
|
|||
|
|
SRBTimeoutDelta = 5
|