are you saying the #p1= value should be the IPs from node 2 and vice versa?

Also noticed this discrepancy: -PartnerIP:"#p1=10.128.124.51:heartbeat:3260:1,10.255.255.4:heartbeat:3260:1;#p2=10.10.10.2:sync:3260:1" #p1= and #p2= ended up in the same partner list...which is probably not correct. Checking what did that...the strange thing is, the $node I supply is corr...

This piece stands out to me, but I haven't found a way to change it:

-Priority:"#p1=2;#p2=2"

Is the priority value supposed to be the same for both?

Hi Yaroslav, I'm adding the functionality I mentioned of supporting multiple heartbeat interfaces. Does the problem pop out to you from this error output? Request to SAT-SAN-V1-01.HYPERNOC.IO ( 10.128.124.50 ) : 3261 - control 0x000002772900C840 -AddPartner:"" -PartnerTargetName:"#p1=...

Thank you for all your help, Yaroslav. Can you ask someone from sales to reach out to me? The last time I checked in on pricing, we weren't yet able to afford a license with support (hence needing the free version), but I would like to check in and see if there's been any changes. Also, are you inte...

param( #StarWind node settings [string]$PrimaryNode, [string]$SecondaryNode, [ValidateRange(1,65535)] [int]$Port = 3261, #Authentication [string]$Username = "root", [string]$Password = "starwind", #LUN creation mode [ValidateSet("HA", "Flat")] [string]$LUNTyp...

Also, when you have a moment, can you tell me if there's a way from PowerShell to specify multiple heartbeat interfaces like there is in the UI Replication Manager wizard?

I'm using NotSynchronize by specifcying it as a runtime parameter. Sync and HB are IP addresses. One thing I'm wondering...should these be #p1 and #p0 instead of #p2 and #p1? [string]$PrimaryNodeSyncIPAddress = "10.10.10.1", #The IP address of the synchronization interface on the primary n...

Back on original topic....The link you shared goes to a copy of the script that's already what I'm running. See below. Before I posted, I wanted to ensure my custom script module that is far more user friendly was not the culprit, but the results are consistent between my code and your official scri...

I was a little disappointed with that change in licensing mechanism. I understand why they did it, though. If you could go from trial to free, people could get around the GUI license restriction when they occasionally make changes by requesting a trial license, using the UI, then switching back to f...

It is the Windows binary build. If you're curious to see it reproduced, I'm currently rebuilding the trial back under free and then I can show you.

I can consistently reproduce this issue. If I use PowerShell (StarWind VSAN Free) to create any type of LUN (HA or flat) once, it will work fine. Every time after the first time, it will fail with error "104 You are authenticated already." I've been able to isolate this to being a fault ei...