Bah didn't see that, we've had odd issues like this before on that Core box. It didn't save the network settings until I rebooted.
So now that they are correct, I step through and create with the following settings:
New Partner Host : 192.168.12.3
New Partner Management Port : 3261
New Partner Authentication : Use default credentials
New Partner Username : root
Second target name : iqn.2008-08.com.starwindsoftware:192.168.12.3-cluster20328secondnode
Mark as non-optimized path for ALUA : No
Partner Image : My Computer\F\clusterdisk1.img
Create new : No
Cache mode : wb
Cache size : 7168
Then get:
Add partner node failed!
Failed: operation cannot be completed.
I tried a few different settings and didn't get anywhere so I deleted the unsynched device (secondary node - primary node still has device and target), and tried to create a new one through this same set of options and I get the same error.
The only thing that stand out in the logs:
2/28 10:40:00.215 1690 Sw: *** MountTarget: Failed to log in to target(iqn.2008-08.com.starwindsoftware:192.168.12.3-cluster20328secondnode). Error message: Failed to log in to target. Status: Target not found(515)
.
If I created a target on the second server with that name then I can't step through the wizard as it says the target already exists. So the error doesn't seem really helpful.
edit again:
2/28 10:51:15.033 b14 HA: CHADevice::AddPartner: unable to process command. AddPartner_i() failed with error code 87.
This code mean anything?
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software