I haven't tested this fully yet but I think I have at last got to the bottom of how to configure multi-pathing for Starwind with VMware ESX. This has been giving me trouble for a while, and judging from the forum posts several others have had trouble too.
It actually happened by accident, since we are Starwind partners I've been testing it in our lab with ESX, XENserver and the MS Initiators. The other day I had to do the XEN edit to my Starwind config file in order to make the IQNs visible so I could mount them, then today I wanted to add another target to our ESX cluster. It took much longer than usual scanning but now it lists a path for each NIC I have in the Starwind server (there's four!), and will let me choose a multi-pathing policy accordingly.
I won't bother repeating the change required to the config file, just have a look at the guide to setting up Starwind for XEN.
Btw, this occurs with ESX3/3.5, I haven't tested yet on ESX4 as I only have a couple of servers running it and they are testing something else currently. However it may not be such an issue as VMware appear to have improved dynamic discovery - you can specify CHAP details per target now, rather than just on the initiator.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software