ceph/doc/rbd/iscsi-initiator-win.rst

   1 -------------------------------------
   2 iSCSI Initiator for Microsoft Windows
   3 -------------------------------------
   4
   5 **Prerequisite:**
   6
   7 -  Microsoft Windows Server 2016
   8
   9 **iSCSI Initiator, Discovery and Setup:**
  10
  11 #. Install the iSCSI initiator driver and MPIO tools.
  12
  13 #. Launch the MPIO program, click on the "Discover Multi-Paths" tab, check the
  14    "Add support for iSCSI devices” box, and click "Add". This will require a
  15    reboot.
  16
  17 #. On the iSCSI Initiator Properties window, on the "Discovery" tab, add a target
  18    portal. Enter the IP address or DNS name and Port of the Ceph iSCSI gateway.
  19
  20 #. On the “Targets” tab, select the target and click on “Connect”.
  21
  22 #. On the “Connect To Target” window, select the “Enable multi-path” option, and
  23    click the “Advanced” button.
  24
  25 #. Under the "Connet using" section, select a “Target portal IP” . Select the
  26    “Enable CHAP login on” and enter the "Name" and "Target secret" values from the
  27    Ceph iSCSI Ansible client credentials section, and click OK.
  28
  29 #. Repeat steps 5 and 6 for each target portal defined when setting up
  30    the iSCSI gateway.
  31
  32 **Multipath IO Setup:**
  33
  34 Configuring the MPIO load balancing policy, setting the timeout and
  35 retry options are using PowerShell with the ``mpclaim`` command. The
  36 rest is done in the iSCSI Initiator tool.
  37
  38 .. note::
  39   It is recommended to increase the ``PDORemovePeriod`` option to 120
  40   seconds from PowerShell. This value might need to be adjusted based
  41   on the application. When all paths are down, and 120 seconds
  42   expires, the operating system will start failing IO requests.
  43
  44 ::
  45
  46     Set-MPIOSetting -NewPDORemovePeriod 120
  47
  48 ::
  49
  50     mpclaim.exe -l -m 1
  51
  52 ::
  53
  54     mpclaim -s -m
  55     MSDSM-wide Load Balance Policy: Fail Over Only
  56
  57 #. Using the iSCSI Initiator tool, from the “Targets” tab, click on
  58    the “Devices...” button.
  59
  60 #. From the Devices window, select a disk and click the
  61    “MPIO...” button.
  62
  63 #. On the "Device Details" window the paths to each target portal is
  64    displayed. If using the ``ceph-ansible`` setup method, the
  65    iSCSI gateway will use ALUA to tell the iSCSI initiator which path
  66    and iSCSI gateway should be used as the primary path. The Load
  67    Balancing Policy “Fail Over Only” must be selected
  68
  69 ::
  70
  71     mpclaim -s -d $MPIO_DISK_ID
  72
  73 .. note::
  74   For the ``ceph-ansible`` setup method, there will be one
  75   Active/Optimized path which is the path to the iSCSI gateway node
  76   that owns the LUN, and there will be an Active/Unoptimized path for
  77   each other iSCSI gateway node.
  78
  79 **Tuning:**
  80
  81 Consider using the following registry settings:
  82
  83 -  Windows Disk Timeout
  84
  85    ::
  86
  87        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk
  88
  89    ::
  90
  91        TimeOutValue = 65
  92
  93 -  Microsoft iSCSI Initiator Driver
  94
  95    ::
  96
  97        HKEY_LOCAL_MACHINE\\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\<Instance_Number>\Parameters
  98
  99    ::
 100        LinkDownTime = 25
 101        SRBTimeoutDelta = 15