Last week, I had the pleasure of contacting Dell's technical support for help with an MD3000i that I was setting up for a client. The problem that we were having was the frequently reported "non-optimal path" issue related to MD3000i, iscsi, and mpio connection to ESX.
However, I was very disappointed to learn that Dell is currently not supporting ESX 4.1 with the MD3000i. I was told that we must downgrade to ESX 4.0, because "Support for ESX 4.1 is on the roadmap, but is not here yet."
Has anyone else heard this from Dell? I told the technical support engineer that we also tested ESX 4.0 and received the same "non optimal path" error. Dell tech support replied "a firmware update will be coming soon to fix that".
Ultimately, I was able to solve the non-optimal path issue myself, with no help from Dell.
I've run into this multiple times and have just stuck with ESX 4.0 till Dell plans to come with the new firmware with 4.1 support. I've seen odd behaviour where a server couldn't see virtual disks except if they were assigned to a single controller, even though I set it up exactly as I have always done (with 4.0) and the same way as I do for the MD3200i. So, I believe VMware changed something with the multipathing driver when they upgraded from 4.0 to 4.1 (which makes sense if you look at all the new features that VMware added for storage connectivity (if your SAN has support for them)). This change in the multipathing driver is probably why the current firmware cannot be fully trusted in a production environment till Dell releases the newer firmware.
I'm still disappointed that Dell still hasn't released a firmware compatible with such a popular hypervisor this much time after VMware released the version in question. Especially considering that their own Equallogic arrays, Dell|EMC arrays and even the PowerVault MD3200i have had support for 4.1 since the day it was released.
We ran 4.0 U2 for a short time.... I dunno, we were forced to go to 4.1 by some other system / application requirements. We are not having any issue. 4.1 is faster and the MPO seems to work better with MD3000i for us.
Looking at this, it appears to me that the problem was not with ESX 4.1 but with some other config (especially as you were able to solve it yourself). So, the real problem is that Dell support did not stick with the expected helpful nature and help with a best effort and instead blamed the unsupported OS. I can understand the pain... but at least it's all working now... right?
It seems that as of December 2010, Dell added 4.1 to the support matrix for the MD3000/MD3000i.
Earlier Dell said it was going to require a new firmware, but the new firmware didn't come out till mid January or so, so I guess in the end the previous firmware would support 4.1 anyway.
Dev Mgr
6 Operator
•
9308 Posts
•
3 Points
368
0
Posted November 14th, 2010 14:00
I've run into this multiple times and have just stuck with ESX 4.0 till Dell plans to come with the new firmware with 4.1 support. I've seen odd behaviour where a server couldn't see virtual disks except if they were assigned to a single controller, even though I set it up exactly as I have always done (with 4.0) and the same way as I do for the MD3200i. So, I believe VMware changed something with the multipathing driver when they upgraded from 4.0 to 4.1 (which makes sense if you look at all the new features that VMware added for storage connectivity (if your SAN has support for them)). This change in the multipathing driver is probably why the current firmware cannot be fully trusted in a production environment till Dell releases the newer firmware.
I'm still disappointed that Dell still hasn't released a firmware compatible with such a popular hypervisor this much time after VMware released the version in question. Especially considering that their own Equallogic arrays, Dell|EMC arrays and even the PowerVault MD3200i have had support for 4.1 since the day it was released.