Boot from san with open-e DSS

[kbs]

Hi,

I finally managed to install an ESX Server 3.0.2. I had no Problems installing an Windows 2003 R2 Server on a DSS Lun. I use this Configuration:

DSS: QLA2340, 20GB FC LUN blocksize 512, HBA Alias
ESX: Emulex LP9002, Boot from SCSI, DSS LUN for VM

If you need more information, you are free to contact me.

[paul2kl]

Hi,

I finally managed to install an ESX Server 3.0.2. I had no Problems installing an Windows 2003 R2 Server on a DSS Lun. I use this Configuration:

DSS: QLA2340, 20GB FC LUN blocksize 512, HBA Alias
ESX: Emulex LP9002, Boot from SCSI, DSS LUN for VM

If you need more information, you are free to contact me.

Hi KBS,

I have sent you an email with a few questions to see if we can get this working properly, as there are a few of us with the same issue as myself. Would be great if we can compare notes to see if we can locate the real issue.

Paul

[kbs]

Hi,

when I installed the VM (Win2003 Server) yesterday everthing was fine. I tried to power on, power off, suspend and resume the VM and it was OK. Today I rebooted the ESX server and after powering on the VM again I had the same problems like you. This is a very strange behavior. A lot of kernel exceptions (aacraid, scsi_tgt, scst_fileio, qla2x00tgt) on the DSS and all other servers lost their fc luns. So I had to restart the dss and all other servers. I have a similar system with a Redhat Enterprise Linux and VMWare GSX Server 3. These servers even boot from the DSS SAN and have no problems. I think there are some advanced configuration parameters on the ESX. If I find the time I will try to change them maybe it helps. But actually it is problematic because DSS serves for productive systems.

[paul2kl]

Hi,

KBS yes you are seeing the same issues as me. I was able to sometimes leave it over night and it would be ok... But if i restarted ESX the same issues as you would occur. Or if i just shut down the VM's running from the LUN, and then tried to boot them 30 mins later, DSS had errors, and loads of busy retry errors on ESX. I would have to power off the DSS server and ESX server to get things back again. I am currently trying a beta of 1.37, but my inital test shows the same issues. I am going to rebuild ESX and DSS servers from scratch and then test it all again. Do you have any sugestions on which ESX settings you may wish to change, as i will try them out to see how it goes.

Thanks,

Paul

[sap]

Hi There

This thread seems to be sleeping but do any of you have any news on this?
I'm facing the exact same problem.

Serves me right. read the forum before making the plans