New HA targets is using MS ISCSI Initiator

[WardA]

Hi Anatoly,

I absolutely will update you as soon as I have added the key. I am just waiting for an available maintenance window to do it, though, in case something bad happens. Should be either this evening or tomorrow evening.

Cheers,

Andy

[gstephenson]

I had this same problem. Today I upgraded one of my 2-node Hyper-v clusters and neither of the two servers had a transport key in the config file. Following the upgrade I added it in, one server at a time, and allowing fast-sync to complete. Seems to be working ok as of this writing.

[anton (staff)]

Looks like it's an upgrade path issue. We'll check this one and if it's our issue we'll fix it. Thank you!

[WardA]

Hi Anatoly/Anton,

I have added the transport key to the config file on both pairs of HA nodes, and everything is working fine - no MS iSCSI in sight, and all syncs happening at tasty speeds (i.e. almost instant).

Special thanks to lohelle for the confirmation of what you did on your nodes!

Cheers,

Andy

[Anatoly (staff)]

WardA, I want to inform you that we will include fix to this in next release build.

Also I want to say "Thank you" to lohelle for great assistance to our users!

[lohelle]

[Anatoly (staff)]

OK, I think I can close this topic since this case can be considered as completely closed!
Thank you everybody for the input!