- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Automate Windows iSCSI Connections
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-13-2013 02:39 PM
05-13-2013 02:39 PM
Re: Automate Windows iSCSI Connections
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-14-2013 11:45 AM
05-14-2013 11:45 AM
Re: Automate Windows iSCSI Connections
Just wanted to update the forum with what my issue was. I just rebooted the host and it fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-12-2013 10:45 AM
06-12-2013 10:45 AM
Re: Automate Windows iSCSI Connections
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.
---
$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]}
}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-10-2013 02:11 AM
07-10-2013 02:11 AM
Re: Automate Windows iSCSI Connections
Hey Adam,
Did the update with Least Queue Depth change ever get released ?
Thanks
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-27-2013 11:04 AM
08-27-2013 11:04 AM
Re: Automate Windows iSCSI Connections
Hey Adam,
I get the following message when I try to run in Windows 2003 R2. New to PowerShell so any help would do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-27-2013 02:37 PM
08-27-2013 02:37 PM
Re: Automate Windows iSCSI Connections
Never mind. Installed PowerShell 2.0 and it ran successfully; however, it made double amount of persistent connection for each volume.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-27-2013 03:49 PM
08-27-2013 03:49 PM
Re: Automate Windows iSCSI Connections
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2013 09:09 AM
12-09-2013 09:09 AM
Re: Automate Windows iSCSI Connections
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-09-2018 02:22 AM
07-09-2018 02:22 AM
Re: Automate Windows iSCSI Connections
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
Rajesh Balakrishnan
I am a HPE Employee
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP