StarWind Software

Hallo,
we have a HA with 5.8 Starwind Servers on Win2k8R2 SP1.
MPIO installed. For iSCSI traffic there are 2 x dual-Ports dedicated, can see all the ipv4 in the StarWind managent console.

Problem is - from one Hyper-V iSCSI initiator we can see all target interfaces (adapted starwind.cfg with iSCSIDiscovery item) -> BUT from the other Hyper-V iSCSI initiator only one of the four interfaces / ip is listed in the connect box.

I know you suggest to use Quick Connect and hope Microsoft MPIO does it job correctly, but I prefer to manually connect and manage the sessions.

1. What is the MPIO "hardware id" from the StarWind Service(s)?? At the moment we just see one entry.

2. Any idea what the error could be. All interfaces are ping-able and seem to work correctly. Firewall are shut off.

Could it be, that 2 of 4 interfaces where configured and added to a later time?

Greetings from Germany
Raymond

Hi,
I found my error, was a unvisable sign in the iSCSIDiscovery row of the starwind.cfg....

Another request for the next versions would be, if we had the option to configure in the management console,
which interfaces should be used for dedicated iscsi and/or mpio, then I could stay with the "quick connect" solution, without having to turning on all interfaces on (iSCSIDiscovery thing).

THX
Raymond

I`m sorry, I`m not 100% sure that I get all right - your request is the ability to choose what NIC will be used for iSCSI or not iSCSI via our Management Console?