Powershell for a standalone LUN on VSAN

[vertigomike]

Leave root/starwind. The creds on top of the script are not the creds you use to log into the VM.
Check this out https://forums.starwindsoftware.com/vie ... NT8#p37208.

Yeah i had seen that. I wasn't sure though why i was getting the 200 error. Turns out I had fat fingered the /mnt path and once i corrected it now connects and i was able to push data. The issue i have those is i have two other servers that need to connect to the same target and its not working. Is it possible that the target created through the PS script isn't setup to allow sessions from multiple hosts. Is there a way to fix that if so? my google skills are failing me tonight as i couldn't find any info other than references to using the GUI manager which obviously isn't supported by the Free version

[yaroslav (staff)]

You are always welcome.

The issue i have those is i have two other servers that need to connect to the same target and its not working.

I don't quite follow. It looks similar to what we write here https://www.starwindsoftware.com/starwi ... 0a%20block.

Is it possible that the target created through the PS script isn't setup to allow sessions from multiple hosts.

No. The target set up with the PS script does not have this limitation.

[Michael (staff)]

Thank you for useful feedback!

[CombFiltered]

Is it possible that the target created through the PS script isn't setup to allow sessions from multiple hosts. Is there a way to fix that if so?

No. The target set up with the PS script does not have this limitation.

Yes...but kind of. I had to do some digging to figure this out, and playing around. When the target is created in the PS script, you need to add "-clustered yes". My line (under the "#create target" comment) is

Code: Select all

$target = New-Target -server $server -alias $targetAlias -devices $device.Name -clustered yes

The New-Target command help says this about the -clustered parameter: "It allows multiple concurrent iSCSI connections (yes, no)."

[yaroslav (staff)]

Is it possible that the target created through the PS script isn't setup to allow sessions from multiple hosts. Is there a way to fix that if so?

No. The target set up with the PS script does not have this limitation.

Yes...but kind of. I had to do some digging to figure this out, and playing around. When the target is created in the PS script, you need to add "-clustered yes". My line (under the "#create target" comment) is

Code: Select all

$target = New-Target -server $server -alias $targetAlias -devices $device.Name -clustered yes

The New-Target command help says this about the -clustered parameter: "It allows multiple concurrent iSCSI connections (yes, no)."

Thanks for your update.
-clustered = yes from the box. It is not in the script, yet the script I shared earlier does allow setting up the target that enables multiple connections (was tested by me and multiple users during the remote sessions). To sum up, adding it does not do any good or bad.
May I wonder what initiator you have there?