ESX 4.1 loses iSCSI connection after reboot

[To-M]

Sadly the performance of Open-E DSS V6 is totally disappointing as well as the stability.

Before stating this lets take a look at the DSS log file to see if there is something else that is happening, log file can be obtained in the GUI in Status > Hardware > Log then click on the Download button. We believe you sent us an email inquiring about the features of the A/A so we can take a look your system from the log files.

[To-M]

Also you might want to try to tune your Targets as well.

1. From the console, press CTRL+ALT+W,

2. Select Tuning options -> iSCSI daemon options -> Target options,

3. Select the target in question,

4. change the MaxRecvDataSegmentLength and MaxXmitDataSegmentLength values to
the maximal required data size (check w/ the initiator to match).

maxRecvDataSegmentLen=262144
MaxBurstLength=16776192
Maxxmitdatasegment=262144
FirstBurstLength=65536
DataDigest=None
maxoutstandingr2t=8 InitialR2T=No
ImmediateData=Yes
headerDigest=None
(deprecated)Wthreads=8

Doing this will reset the iSCSI connections at each edit. Please pause any hosts connected
to the LUNS. These adjustments need to be made at each node, and at the initiators.

Did you look at this document - keep in mind that ESX 4.x MPIO is different then 5.0 and .51.
http://www.open-e.com/site_media/dow..._ESX4i_4.1.pdf

[MAFRI]

Already tried the tuning at the Open-E Storage and did same tuning for the iscsi HBA at the ESX hosts.
I sure know how to handle the Robin-Round with ESX 4.1

The log only show's the only 407 Errors since I cleared it last this must be about 12h ago.
407 cmnd_abort(1143) errors.

You offered me to send the log files via e-mail - where to send them ?

thx

[MAFRI]

Meant the Eventlog shows 407 of those erros.
Downloaded the system log.

[Gr-R]

you can send logs to pre(dash)sales at open-e dot com

[MAFRI]

Mail send