Issue with second path to target

[dandickson]

I have an issue with adding a second path to my iscsi target, i'm not sure if it's a limitation of the free version or something I have done wrong, here is my configuration:

Code: Select all

Node 1:

Heartbeat Channel: 192.168.9.15
Synchronization Channel: 10.255.1.15 and 10.255.2.15

Node 1:

Heartbeat Channel: 192.168.9.18
Synchronization Channel: 10.255.1.18 and 10.255.2.18

Using replication on the back-end that is handled by Starwind is working fine.

When I configure the iSCSI initiator, I have 127.0.0.1, 10.255.1.18 and 10.255.2.18 on node 1 and I have 127.0.0.1, 10.255.1.15 and 10.255.2.15 on node 2, no errors here.

When I build the connection to the target, I run through the steps, select MPIO, the Microsoft iSCSI initiator, interface is 10.255.1.15, target is 10.255.1.18 and get the desired connection.

However as there is a second path to that target, I again run through the steps, select MPIO, the Microsoft iSCSI initiator, interface is 10.255.2.15, however the only target shown is 10.255.1.18.

I have tried restarts, a reconfiguration and don't seem to be able to figure it out.

Any help is appreciated

Thanks

[Ivan (staff)]

Hello dandickson,
Thanks for the interest in StarWind solution.
Please do this simple steps to make possible connect with second IP:
1) Stop StarWind service on the first node
2) In StarWind folder open StarWind.cfg file
3) Find string <iScsiDiscoveryListInterfaces value="0"/> and modify it like that: <iScsiDiscoveryListInterfaces value="1"/>. Save the config file and close it.
4) Start StarWind vSAN service
5) Open StarWind management console and make sure all device are synchronized
6) Once all devices will be synchronized on both hosts you can perform the same steps with the second node.
7) When both StarWind.cfg files will be modified you can try to connect the iSCSI target with one more IP address.