Thanks I'll look for a configuration error. As mentioned, 3260 is obviously open because it's exporting a vsan. It was only when attempting to add a standalone target to that config that the standalone target failed - discoverable but attempted connection from initiator returned "service not av...

Current testing suggests the standalone target config works fine as a standalone config, but on initial testing the standalone target could not be connected to exported from a host also exporting vsan...

Any suggests, am I not being clear enough?

Hi, we've had a mostly successful test of the vsan product providing HA storage to hyper-v using the hyper-v hosts themselves to provide starwinds replicated storage. We also have some virtual hosts that export physical iSCSI targets for backup purposes. Is there any limitation that would prevent st...