iscsicpl hanging

[dpetrek1]

So we have Starwind free in 2 node / 1 virtual disk per node configuration.
Doing some testing and disconnected the nodes, both HB and sync channels.

As expected Starwind GUI telling:

"Partner Node is not ready, see Replication Manager for more Details
Device is not synchonized
Synchronization channel ... is down
Partner ... is not synchronized"

However when trying to start iscsicpl to try to mount disk locally, the GUI does not show up at all, looks like it is hanging for some reason.

So
C:\Users\Administrator>netstat -an | find "3260"
TCP 127.0.0.1:3260 0.0.0.0:0 LISTENING

So we cleaned up Micosoft ISCSI initiator registry so it starts well this time.
We have Starwind listetning on port 3260, portal should be ready for discovery, however "Discover target portal (Not responding)" happens...
Looks like Starwind portal is not allowing connection from the initiator for some reason.

Starwind log can be found here:
https://drive.google.com/file/d/1IxflLf ... sp=sharing

Whats happening?

Operating system is Windows Server 2019 Standard.

[dpetrek1]

If anyone else will run into this problem...it was an error in configuration on our side.
This had to do with trying to use single network interface but with multiple IP addresses assigned which would then be used for both sync and HB.
This was just for lab purpose, but dont do it.
Yes, minimal network requirements for SW are clearly stated in the manual

Other than this, I found out that Starwind ISCSI portal blocks connections until virtual machine (HYPER-V) running Starwind had network adapters set from "Not connected" to some(any) virtual switch. Also, local storage will not be exposed until device is in "Synchronized" state.

[yaroslav (staff)]

Glad to know that you have fixed it. Thanks for sharing your knowledge!

[anton (staff)]

== thread closed ==