Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
febren
- Posts: 2
- Joined: Fri Sep 29, 2017 10:25 am
Fri Sep 29, 2017 10:37 am
I’m trying to evaluate StarWind’s iSCSI target as a storage solution for some video surveillance applications. The problem is that the iSCSI initiator expects the iSCSI target to include its own IP address in the response to the SendTargets=All request during discovery. As per rfc3720 this is only optional. But my initiator seems to require it.
Is there any way that I can configure the iSCSI target in a way that it tells the initiator its own IP address during discovery?
thanks
-
Sergey (staff)
- Staff
- Posts: 86
- Joined: Mon Jul 17, 2017 4:12 pm
Fri Sep 29, 2017 4:07 pm
Hello, febren! Thank you for the question. Please find starwind.cfg file, by default located in C:\Program Files\StarWind Software\StarWind folder. You have to find <iScsiDiscoveryListInterfaces value="0"/> string and update 0 to 1. You have to stop StarWindService before updating starwind.cfg file, and start it again after you save the changes. Let me know how it goes.
-
febren
- Posts: 2
- Joined: Fri Sep 29, 2017 10:25 am
Mon Oct 09, 2017 11:59 am
Hello Sergey,
thanks for your quick help. This brings me a step further. The initiator is now able to read the IP address. But for some reason it still cannot read the LUNs.
I'll have to dig a bit deeper into the issue and will let you know about the result.
