We have some issues with VVoLs work with the current StarWind build.
The issue should be fixed with the next StarWind release:
https://www.starwindsoftware.com/release-notes-build

Just to clarify, are you using the same vSwitch for Management and ISCSI traffic?

The problem can be related to the IPs you are using. You are assigning the same IP for connecting, heartbeat and synchronization.
Please check best practices.

Hi,
What StarWind build are you using?

You are welcome

Yes, MTU size should be the same on all levels, vSwitch, vmkernel and on the interfaces inside StarWind VMs.

I am telling about Discovery in ISCSI initiator properties:

Yes, one isci-target was connected, but I turned it off. But it did not help

ISCSI initiator can be in use by different service.

Hello andresha,
Did you add Target portals to Discovery? Do you have any other roles that can use ISCSI initiator?

Hi,

I'm using (and need to) a MTU of 1400. This is set in the vSwitch and within the Starwinds VSAN VM (Linux appliance)

Could you please try with a default MTU size of 1500? It could be a reason of "paths down" failures. ISCSI packets are dropping due to the maximum MTU size you made.

Hi Dan,
Could you please share the log from V2V Converter?

This option is available with paid version only.

Hi denkteich,
StarWindX is available in StarWind VSAN for vSphere. You should install Integration Component Library on the machine you are managing from.

You are right, tape redirection should be installed on the machine where tape physically attached.

Hi, You answered your question :) StarWind is active-active replication. With loopback and partner ISCSI connections you can get better performance, for example, on reading operations. MPIO policy is distributing the load between loopback and partner connections. That is expected behaviour to see tr...

Hi danswartz,
Please double-check iSER configuration you made.
Please check this KB.