Right way to configure #ISCSI #initiator in #Windows Server 2012 R2

Lately I see a lot of questions about iSCSI and not working or slow connections. There is an easy way to fix this I have never had any issues with the windows initiator. How do you start this. Configuration by PowerShell , If you don’t know the commands there is an easy way to look this up.

get-command *iscsi*

image

Now there is a nice list of all the Command lets. But I this blog I use the GUI more that the screens also work for any other version than windows server 2012 R2.

Go to the control panel or server manager and find ISCSI initiator.

image

image

Click on discover portal and type the ISCSI target IP

image

Easy as this but here are most errors started, a lot are just click on OK this is so wrong Winking smile Go click advanced  Wooowo whole new screen.

image

See what happened when you click OK everything is default.

image image

After selecting the local adapter and set it on Microsoft ISCSI Initiator and select the Nic where your ISCSI IP is located. This is the right way to configure ISCSI. Remember Multi path is using the same config!

It's only fair to share...Tweet about this on TwitterShare on LinkedIn1Share on Google+0Share on Facebook0

Comments (3)

  1. Thanks for the explanation. We do not use the InitiatorIP because we use the EQL HITKit Subnet exclusion options.

    The Powershell Commands on Windows Server 2012 that I use after installing the MPIO feature are:


    #Set the startup-mode for the iSCSI Initiator and start the service
    Set-Service -Name msiscsi -StartupType Automatic
    Start-Service msiscsi
    Enable-MSDSMAutomaticClaim -BusType iSCSI

    #connecting to targetportal
    New-IscsiTargetPortal -TargetPortalAddress 192.168.100.2
    #refresh the portal(s) if you added a new LUN
    Get-IscsiTargetPortal | Update-IscsiTargetPortal

    #connecting to Targets with a specific keyword (in this case "vmvol" in the IQN and which is not connected yet
    Get-IscsiTarget | Where-Object {$_.NodeAddress -like "*vmvol*" -and $_.IsConnected -eq $false} | Connect-IscsiTarget -IsPersistent $True -IsMultiPathEnabled $true | Out-Null
    #you can add an -InitiatorPortalAddress to specify the InitiatorIP as in the above example.

    • we actually have to wdiwons 2003 VMs running MSCS using the wdiwons iscsi initiator that connect directly to the SAN.the share a volume of 200G for MS SQL 2005 clustering functionality.so far so good, no problem at all .it’s implemented on prod enviroment for sharepoint.tony

Leave a Comment