Starwind v4.0 and ESX 4 issue

[a_user]

I have been testing this as a cheap SAN solution for our development environment. We have 14 x 300gb 15k drives in an md1000 that came from our exchange server configured in raid 10 i am wanting to share between two qa/uat esx hosts. I am using version 4 of the software but am finding an issue. It seems if the san for whatever reason is restarted the esx servers will not pick it up again once its back online. I tried refreshing the storage pools as well the storage adapter. Even though the target is listed in the storage adapters I have to manually remove the iscsi target's ip, remove the static mappings and then re-add it to storage adapter and re-create the data store. This is troublesome since although the iscsi host should never need to go down you never know when you may need to restart it for something.

Anyone experienced this or have any suggestions?

Thanks

[Robert (staff)]

Hi,

I saw a similar issue a while ago (not with ESX4 yet), however, here's what I did:

1. Made sure starwind service is automatically started on windows boot-up (should be by default)
2. Also, please make sure that StarWind Box has a static IP address.

If the problem persists, please send us the log files to support@starwindsoftware.com for the deeper investigation.

Thank

[a_user]

Hi Robert,

I have submitted the log files from the iscsi target host. Hopefully they show something. It should be noted that i also tried this on an esx 3.5 server and experienced the same issues. I also used a standard windows client to map to an iscsi target presented from the starwinds host and experienced a failure to reconnect to it as well once the iscsi host had restarted and come back online.

I have verified the service is set to start automatically and it is running, likewise the machine does have a static ip configured.

[Robert (staff)]

Hi,

I believe Valery answered your request last night... Can you confirm it?

Thanks

[rguzman11]

Experiencing the same can you post the solutions please?

[Robert (staff)]

In a_user's case it was an issue with licensing.

In your case, as you have informed us via e-mail, it was related to ESX configuration.

If you experience the same, please let us know - we will investigate this and do our best to help.

Thanks

[hejdatacon]

Hi

I experiense the same problem using Starwind 4.0 and ESX 4.0. Using Windows Server 2008 Enterprise I have no problems.

Right now I am working on a customer concept for the future sale of a cheat SAN solution using Windows platform and VMWare.

I need the information on solving the ESX problem.

[Robert (staff)]

Could you please send us a note to support@starwindsoftware.com?

Thanks