indicates that ESX 3.5i is supported with an MD3000 (in single server mode, which is all we're going to use it for). However, I can't find any information anywhere on how to setup an ESX server with this thing. There is info on Windows and Linux using the modular disk storage manager software, but nothing on an ESX 3.5i server.
Can someone point me in the right direction on how to get this thing running with our ESX 3.5i installation? Thanks.
My reply is assumed on the usage of iSCSI from MD3000i to your ESX hosting servers.
If so, then it is pretty straight forward --- config your ESX network settings, tells it where the iSCSI target is, provided your iSCSI terget is configured properly, then you should see your LUNs. I would goto VMware supprt for documentations --- they have a VERY good list of docs.
I am testing ESX 3.5 using Openfiler and it was extrememly easy --- I can only imagine this would be a breeze for you, too.
I would like to point out ESX 3.5 does not support Jumbo Frame for iSCSI. So you are limited to the traditional dainty MTU size. This means you will still struggle if you host >=8 heavy VM servers. It will still run but don't expect much from the Gbit port.
This is actually sold based on just a regular MD3000 connected to a PERC 6/E. This is what my business account people at Dell set me up with based on discussion of what we were going to do. Will the MD3000 as a direct attached storage to a single machine not work? If so, they have some explaining to do and they're going to take this thing back. Guess I'm calling them on Monday regardless.
That's the item as listed in the details that was put into our PowerEdge 2950 III that we just ordered. The cable hooks up fine to the external port on the SAS 6E. If it only supports the 5E, though, I guess we'll have to figure some things out here (like getting a PERC5E SAS card.
I will be talking with our account rep today about this as this is what they put together for me for our VMware solution. I still need to figure otu as well if the MD3000 (not MD3000i) will work for this as a single server solution.
The MD3000 is supported with ESX 3.5 or 3.5i with only a single SAS hba connected with a single cable to one raid controller in the MD3000.
The MD3000 is only supported connected to a SAS/5e controller. This is a basic SAS controller with no RAID intelligence, as all of the RAID is handled by the controllers in the MD3000 chasis.
Even though the ports on a PERC6/e or PERC5/e have the same SAS connector as the SAS/5e they will not work with the MD3000. The PERC6/e and PERC5/e will work with the MD1000 which has basic EMM I/O modules and the raid is then handled by the PERC controller.
-cjtompsett
Message Edited by cjtompsett on 01-23-2008 12:03 AM
Thanks for the info. I have talked with my account team and they're still gathering information to get back with me, but they were leaning towards the need to switch from the 6E back to the 5E. I'll pass this information along and maybe we'll push that forward as our solution fairly quickly. I know in my more extensive reading post-purchase that what you said seems to ring most true as I haven't read anything that says the 6E and MD3000 will match up--5E is required.
Thanks for the help and hopefully I'll iron this thing out pretty quickly.
Note that the person above referred to this "not" being a PERC, but a SAS 5/E controller. The PERC is "not" used on an MD3000 - only a SAS controller. If you trade out the PERC 6 for a PERC 5 you still have the same problem, just a longer wait for being done.
guskwong
10 Posts
477
0
Posted January 19th, 2008 22:00
If so, then it is pretty straight forward --- config your ESX network settings, tells it where the iSCSI target is, provided your iSCSI terget is configured properly, then you should see your LUNs. I would goto VMware supprt for documentations --- they have a VERY good list of docs.
I am testing ESX 3.5 using Openfiler and it was extrememly easy --- I can only imagine this would be a breeze for you, too.
I would like to point out ESX 3.5 does not support Jumbo Frame for iSCSI. So you are limited to the traditional dainty MTU size. This means you will still struggle if you host >=8 heavy VM servers. It will still run but don't expect much from the Gbit port.
Thanks,
Gus