Page 1 of 1

Problem setting ScsiDiscoveryListInterfaces value

Posted: Sun Aug 25, 2013 11:34 pm
by Caillin
We are currently evaluating Starwind Native-SAN for Hyper-V on what will become our production servers. However, I'm stuck at the very first part of the installation process.

According to the "Configuring HA Storage for Live Migration on Windows Server 2012" document, we need to find the "<!--<iScsiDiscoveryListInterfaces value="1"/> -->" line in the Starwind.cfg file and change it to "<iScsiDiscoveryListInterfaces value="1"/>"

When doing this to the config file, when we go to restart the service, it gives the "The StarWind iSCSI SAN service on the Local Computer started and then stopped." message. When I put the comments back in the line, it starts again.

Here is exactly how I have it written when it doesn't work:

By default, this value = 5 seconds. Use 0 to disable pings.-->
<<iScsiPingPeriod value="0"/>>
<!-- Allow listing of interfaces in response to SendTargets=All -->
<iScsiDiscoveryListInterfaces value="1"/>
<!--Force set of default parameters for iSCSI sessions-->
<!--<iScsiInitialR2T value="0"/>-->
<!--<iScsiImmediateData value="1"/>-->
<!--<iScsiDefaultTime2Wait value="0"/>-->
<!--<iScsiFirstBurstLength value="65536"/>-->
<!--<iScsiMaxBurstLength value="262144"/>-->
<!--<iScsiMaxReceiveDataSegmentLength value="65536"/>-->
<LocalizationDir value="Localizations"/>


I'm probably missing something obvious here....

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 3:10 am
by anton (staff)
Is there any chance you'd provide us with a StarWind and (if you have one) a crash dump?

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 3:31 am
by Caillin
What's the process of generating a crash Dump for starwind Anton?

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 6:05 am
by anton (staff)
The system would do it automatically (if the app did crash). Log is produced by StarWind either way.
Caillin wrote:What's the process of generating a crash Dump for starwind Anton?

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 7:15 am
by Caillin

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 3:49 pm
by anton (staff)
StarWind log is also a must.
Caillin wrote:Here is a link to the crash dump.

https://www.dropbox.com/s/w1j88b8kbpj0q ... shDump.zip

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Mon Aug 26, 2013 11:05 pm
by Caillin
Isn't that the starwind-20130826-091208.txt file in the Zip?

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Tue Aug 27, 2013 5:58 am
by anton (staff)
Sorry I did not bother to check the archive before asking :( We'll take a look and return ASAP. Thanks again!

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Tue Aug 27, 2013 6:16 am
by Caillin
In the meantime, I've got it all set up and benchmarking properly without that setting, so is it absolutely needed?

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Wed Aug 28, 2013 8:22 pm
by Anatoly (staff)
Callin, we`ll pass your crush dump to our R&D team and let you know about the results as soon as we will have one.
Meanwhile, could you please update to the latest version of StarWind (I see in the logs that your is a little bit outdated) and see if it helped?
I will asl oask you to provide us with Windows Application and System logs.

Thanks

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Wed Aug 28, 2013 10:44 pm
by Caillin
Sure thing Anatoly.

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Wed Aug 28, 2013 10:55 pm
by Caillin

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Wed Aug 28, 2013 11:37 pm
by Caillin
Updated version fixed the problem Anatoly. After upgrading each node, I made the same changes to the config, and this time the service started back up properly.

Thanks for the quick response.

Re: Problem setting ScsiDiscoveryListInterfaces value

Posted: Thu Aug 29, 2013 2:51 pm
by Anatoly (staff)
You are always welcome.

JFYI the problem was related to the missedition of the config file, <<iScsiPingPeriod value="0"/>> string to be more exact.