topic Re: Automate Windows iSCSI Connections in Array Setup and Networking

Automate Windows iSCSI Connections

aherbert23 — Thu, 21 Feb 2013 17:16:54 GMT

This script will work on Windows Server 2003, 2008, 2008R2, and 2012 with the native software iSCSI initiator. Any Nimble volumes accessible to the server will be mapped with all possible paths.

NOTE!

By default PowerShell scrips are disabled from running. You must set the PowerShell ExecutionPolicy to from Restricted to at least AllSigned. Please see this MS KB for more information : Using the Set-ExecutionPolicy Cmdlet Also it may be necessary to run this script from a PowerShell session launched with Administrator privileges.

Re: Automate Windows iSCSI Connections

edayeh69 — Mon, 04 Mar 2013 18:18:25 GMT

This script is great to use with customers/partners that bring up MPIO setup as a potential blocker to our solution. Great work Adam!

Re: Automate Windows iSCSI Connections

Nick_Dyer — Wed, 06 Mar 2013 11:22:50 GMT

Nice work Adam - it works every time.

Only question I have is if it would be possible to automate the failover policy to Least Queue Depth vs the Round Robin it defaults to?

A blog available on the web seems to have found a way to do this... Connecting MPIO iSCSI Targets via Powershell… and a bit of dirty VBscript.

Re: Automate Windows iSCSI Connections

aherbert23 — Thu, 07 Mar 2013 15:27:13 GMT

Absolutely, it's very possible. I have an update that I'll post soon and that will be a part of it.

Re: Automate Windows iSCSI Connections

smurthy110 — Tue, 16 Apr 2013 03:36:26 GMT

Thanks for the Script. Does this script automatically detect the Initiators and Nimble Target and maps them or we manually need to key in the parameters?

Re: Automate Windows iSCSI Connections

Nick_Dyer — Tue, 16 Apr 2013 07:24:58 GMT

Hey Sathish,

The script will automatically detect the Nimble volumes presented and will map/MPIO them for you. Give it a go on a windows VM - works perfectly!

Re: Automate Windows iSCSI Connections

Hakanl10 — Thu, 18 Apr 2013 15:52:54 GMT

When using this script, you would first have to define allowed connections to the Nimble volume through the web interface, right?

Re: Automate Windows iSCSI Connections

Nick_Dyer — Thu, 18 Apr 2013 15:56:14 GMT

Hi Hakan,

If i'm reading your question right - yes you have to configure your access control list correctly in the Nimble GUI/CLI for your host before you run the script on said host.

Re: Automate Windows iSCSI Connections

Hakanl10 — Thu, 18 Apr 2013 17:26:06 GMT

That's exactly what I meant. Thanks

Re: Automate Windows iSCSI Connections

Mon, 13 May 2013 21:14:05 GMT

Adam,

I'm trying to run my script. I ran the Set-ExecutionPolicy RemoteSigned and then i tried launching the NimbleMPIO script but get this. Any suggestions?

Re: Automate Windows iSCSI Connections

aherbert23 — Mon, 13 May 2013 21:39:23 GMT

This could be one of two things.

Try starting PowerShell as an administrator. You will need to right click on the PowerShell icon and select "Run as Administrator."
If you are using a hardware dependent iSCSI card (eg Broadcom) and using it as the initiator instead of the Windows software iSCSI initiator. Use the normal network interfaces for IP connectivity instead of the hardware iSCSI initiator and it would fix this issue.

Re: Automate Windows iSCSI Connections

Tue, 14 May 2013 18:45:37 GMT

Just wanted to update the forum with what my issue was. I just rebooted the host and it fixed the issue.

Re: Automate Windows iSCSI Connections

nschoonover110 — Wed, 12 Jun 2013 17:45:28 GMT

I found a bug in that script. The LoadBalancePolicy should be set to 4 and not 2 as is used in their script. Here's the corrected script.

---

$MPIOPolicy = (“Non-Selected”,”Failover Only”,”Round Robin”,”Round Robin with Subset”,”Least Queue Depth”,”Weighted Paths”,”Least Blocks”)

$Policies = get-wmiobject -namespace ROOT\WMI -class DSM_QueryLBPolicy_V2

foreach($Policy in $Policies){

$Instance = $Policy.InstanceName

$objShare = Get-WmiObject -Namespace ROOT\WMI -Class DSM_LB_Operations | where{$_.InstanceName -eq $Instance}

$InParams = $objShare.GetMethodParameters(“DsmSetLoadBalancePolicyALUA”)

Write-Host Current Policy is $MPIOPolicy[$policy.LoadBalancePolicy.LoadBalancePolicy] for $policy.InstanceName$policy.LoadBalancePolicy.LoadBalancePolicy = 2

$InParams.LoadBalancePolicy = $Policy.LoadBalancePolicy

$Inparams1 = $InParams.LoadBalancePolicy

$Inparams1.LoadBalancePolicy = 4

$Inparams.LoadBalancePolicy = $Inparams1

$outparams = $objShare.DsmSetLoadBalancePolicy($inparams.LoadBalancePolicy)

If ($outparams.Status = 2){Write-Host Policy Set to $MPIOPolicy[$Inparams1.LoadBalancePolicy]}

}

Re: Automate Windows iSCSI Connections

rfenton4 — Wed, 10 Jul 2013 09:11:11 GMT

Hey Adam,

Did the update with Least Queue Depth change ever get released ?

Thanks
Rich

Re: Automate Windows iSCSI Connections

jjackson72 — Tue, 27 Aug 2013 18:04:21 GMT

Hey Adam,

I get the following message when I try to run in Windows 2003 R2. New to PowerShell so any help would do.

Re: Automate Windows iSCSI Connections

jjackson72 — Tue, 27 Aug 2013 21:37:42 GMT

Never mind. Installed PowerShell 2.0 and it ran successfully; however, it made double amount of persistent connection for each volume.

Re: Automate Windows iSCSI Connections

alex_goltz — Tue, 27 Aug 2013 22:49:38 GMT

Hey Adam,

Is this script something I could use to do a daily VSS snapshot (clone and mount) for an additional SQL server that needs less resources and privileges?

Thanks,

Alex

Re: Automate Windows iSCSI Connections

HenriAZ — Mon, 09 Dec 2013 17:09:04 GMT

I am having a problem with this script on a Windows 2008R2 server. I have downloaded the script twice and unzipped it, but keep getting the same error about the hash of the file not matching the digital signature. I am running Powershell as Administrator. Is there a security problem with the NimbleMPIO.ps1 script available for download?

PS C:\Users\hprudhommeadm\Documents\NimbleMPIO.ps1> .\NimbleMPIO.ps1

File C:\Users\hprudhommeadm\Documents\NimbleMPIO.ps1\NimbleMPIO.ps1 cannot be loaded. The contents of file C:\Users\hprudhommeadm\Documents\NimbleMPIO.ps1\NimbleMPIO.ps1 may have been tampered because the hash of the file does not match the hash stored in the digital signature. The script will not execute on the system. Please see "get-help about_signing"

for more details..

At line:1 char:17

+ .\NimbleMPIO.ps1 <<<<

+ CategoryInfo : NotSpecified: (:) [], PSSecurityException

+ FullyQualifiedErrorId : RuntimeException

Thanks,

Henri

Re: Automate Windows iSCSI Connections

B_Rajesh — Mon, 09 Jul 2018 09:22:43 GMT

Hi Henri,

You may have to change the execution policy for PowerShell. Get the following help to get more information in order to decide what to select - "help about_Execution_Policies".

Try below PowerShell command:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned