Thank you for the info, So with the MEM 1.1.2 the hosts are already set for the correct timeout?
Is it required to configure the DiskTimeOut values in the virtual machines? We have a quite a few in a multi-tenant hosted environment and will be adding vCloud Director soon to expand upon this. This would be a huge task and I'm not even sure if I have access to all the VMs.
Is there a way to disable DelayedACK and LRO globally? We have quite a few hosts in multiple clusters. I have read in some places that this is reccomended though.
I read through some of your posts and you really seem to know your stuff with this, much appreciated.
I also have a couple other questions, currently I have a ticket in with Dell and they are trying to find it out but I'll throw the info out here too.
We're noticing a few errors that keep poping up saying
"Path redundancy to storage device naa.etcetcetcetc degraded, Path vmhba35:C3:T11:L0 is down. Affected datastores: etcetc"
Then i'll receive an message about 15 second later saying it's active again, this seems to only be happing with a single datastore and no others, even though we have multiple datastores from the same arrays connected to the same host spitting out this error.
In addtion to this we recently started getting errors that say something similar to
"Device naa.etcetcetcetc performance has deteriorated. I/O latency increased from average value of 5888 microseconds to 120037 microseconds."
I figured this had something to do with Veeam causing some extra datastore usage or the fact that I recently enabled storage i/o control on all Equallogic LUNs and it had some learning to do to find out what the average should be.
Thanks again