VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 2 Previous Next 20 Replies Last post: Nov 13, 2007 6:11 AM by Texiwill  

Hardware Planning posted: Nov 6, 2007 4:26 PM

Click to view dmca's profile Novice 11 posts since
Nov 6, 2007
I am new to VMWare and VMWare planning, I am trying to put together a plan for a new branch we are opening for a max of 35 people. I want all our server apps to run off VM's at this new site. I am looking for some advicce on the hardware i am planning on using. In total i can forsee 6 VM's so far and was planning the following hardware:

Servers:
2 x Dell PowerEdge 2950 (ESX Servers)
1 x Dell PowerEdge 1950 (Virtual Centre Server)

SAN:
1 x Dell MD3000i (4 x 400GB SAS Disks)
or
1 x Dell AX150 (with Fibre Channels)

Switch:
2 x Dell PowerConnect 5324 Switch

Up until the other day i was leaning towards the AX150 however i was just told today that if i wanted to leverage VMotion & HA (which i do), then i would also need to invest in a fibre switch as the direct fibre ('loop') attachment to a AX150 from the two PowerEdge servers is not supported for HA. Is this true??

I realise that the MD3000i is not currently supported by VMWare but my understanding is that it will be in December of this year. Does anyone know if the MD3000i supports HA??

Also the switch which i have mentioned, is it overkill for this solution. Would a simple Dell PowerConnect 2724 switch do the job just as well?

Re: Hardware Planning

1. Nov 6, 2007 6:24 PM in response to: dmca
Click to view ejward's profile Master 863 posts since
Sep 23, 2005
How much memory in the 2950's? The more, the better. CPU is really not important. I've got a density of about 14 VM's per 2950 with 16GB of RAM. For a SAN, we use fiber now but are moving to iSCSI. In testing, the Vmware iSCSI software initiator is giving us the same performance as our 2GB fiber. And .... we don't have to buy $1000 fiber cards. Our new iSCSI device is Equallogic and as of yesterday, Dell just bought them. I'm not sure what that says about all the EMC stuff Dell sells with the Dell name on it. I believe the AX150 supports iSCSI so, I would imagine you could use it for HA and Vmotion without having to buy a fiber switch. If you are going to use HA, why not run Virtual Center as a VM? With just a couple of ESX servers and a few VM's, you won't have performance issues.

Re: Hardware Planning

2. Nov 6, 2007 8:48 PM in response to: dmca
Click to view Dave.Mishchenko's profile Guru 8,943 posts since
Nov 15, 2005

You'll probably want to wait on the MD3000i to be supported for VMware before you get one. You can get HA/DRS to work, but as you can see in this thread you have to jump through some hoops to get it to work - http://communities.vmware.com/message/772741.

As mentioned VirtualCenter will run fine in a VM - http://www.vmware.com/pdf/vi3_vc_in_vm.pdf

Have you considered just sticking with local storage and not using shared storage. You would loose HA, but you would also eliminate the MD3000i or something else as a single point of failure. You could just go with local storage and then replicate the VMs from one host to another. If you lost one host, you could simply restart the VMs on the other host.


Re: Hardware Planning

3. Nov 7, 2007 5:01 AM in response to: Dave.Mishchen…
Click to view ejward's profile Master 863 posts since
Sep 23, 2005
Dave.Mishchenko wrote:

Have you considered just sticking with local storage and not using shared storage. You would loose HA, but you would also eliminate the MD3000i or something else as a single point of failure. You could just go with local storage and then replicate the VMs from one host to another. If you lost one host, you could simply restart the VMs on the other host

You could also save some money by not having to buy Enterprise Edition. You can squeeze a whole lot of storage into a 2950 with SAS drives (300GB x 6 drives). Or, if you wait until the next version of ESX (Due out in a month or so I think) you can use serial ATA drives and squeeze 6 x 750GB into a 2950.

Re: Hardware Planning

4. Nov 7, 2007 5:38 AM in response to: ejward
Click to view Texiwill's profile Guru 10,205 posts since
Jan 13, 2004
Hello,

Hardware truly depends on what you are trying to do... How many networks you have to deal with
  • Generally 6 NIC Ports are necessary for full redundancy and security for a basic install (2 for SC, 2 for vMotion, 2 for VMs)
  • Throw in iSCSI or NFS and another 2 NIC Ports should be used for full redundancy and security.
  • Local vs Remote Storage depends if you want to use vMotion or Not. How much failover do you need.
  • How many VMs will be used by these 35 people? This will tell you how much memory and CPU you need as well as network. Do you need more network to handle the bandwidth.

Have you run some tests on the existing setup somwhere? Do you have the existing utilization numbers to help you decide on how much of everything you need? You may find you need a bigger box in which to place more network or even a larger amount of disk, etc. Or a different design to handle the hardware you have chosen.

Best regards,
Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

Re: Hardware Planning

6. Nov 7, 2007 10:02 AM in response to: dmca
Click to view ejward's profile Master 863 posts since
Sep 23, 2005

The current version of ESX doesn't support installing on SATA drives. If you try to configure a Vmware 2950 on Dell's site with SATA drives, it will tell you.

Re: Hardware Planning

7. Nov 7, 2007 10:33 AM in response to: dmca
Click to view Texiwill's profile Guru 10,205 posts since
Jan 13, 2004
Hello,

I would bump up your NIC to 6x1GB ports (for full redundancy/performance/security) and your local RAID5 to 4 disks (3 + 1 Spare), I would also consider using the same hardware SAS or SATA at each site so that parts are pretty easy to stockpile and ship as necessary. I would also have enough local space just in case the SAN fails and the network link to the backup site fails. Plan in as much redundancy as you can afford.

Best regards,
Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

Re: Hardware Planning

9. Nov 7, 2007 5:46 PM in response to: dmca
Click to view ejward's profile Master 863 posts since
Sep 23, 2005
I certianly sounds like a good plan. Currently, ESX will not recognize SATA drives. Dell won't sell you a server with SATA drives if you buy Vmware through them. If you're getting Vmware somewhere else, don't get SATA drives in the servers. The next version of ESX (v3.5) does work with SATA. I've currently got 4 Dell servers with SATA drives running the beta. I have no idea when this is being released. I think the beta is over and they now have a release canidate. So, a real release can't be too far away. This isn't Microsoft we're talking about. :^0

Re: Hardware Planning

10. Nov 8, 2007 4:34 AM in response to: dmca
Click to view pyosifov's profile Enthusiast 51 posts since
Aug 25, 2007
Actually you don't need to put all that money to SAN if you don't really need it.NAS or iSCSI would do the trick for you.SAN is an expensive solution for such a small organization.Of course it is the best solution but the most expensive as well.For VMotion and HA to work you only need shared storage,no matter SAN, NAS or iSCSI.You should plan some extra resources on your physical machines in case of a hardware problem.

Re: Hardware Planning

11. Nov 8, 2007 5:04 AM in response to: pyosifov
Click to view ejward's profile Master 863 posts since
Sep 23, 2005

Our Vmware rep says that there are very few new deployments of Vmware that use fiber attached storage. Since v3, it's all iSCSI now. At Vmworld this year the same was true. There was very little talk of fiber attached storage. It was all iSCSI.

Re: Hardware Planning

12. Nov 8, 2007 6:41 AM in response to: dmca
Click to view Texiwill's profile Guru 10,205 posts since
Jan 13, 2004
Hello,

I think you are on the proper track. As for the restoration directly onto the PE2950, yes, that is one possibility. I like to, as part of my backup strategy, place a copy of the VM directly on a VMFS on the the local storage. This way you do not need to restore if the iSCSI server has issues. Just boot the local storage back up. Backup strategy could be:

  • Use local vcbMounter to copy the VM from the Remote storage to the local VMFS.
  • Perform normal backup mechanism

This has the advantage of not needing to restore from tape in case of failure. Going with 6 pNIC is a good choice. I would place your Storage (iSCSI network) in this situation on the vSwitch for your Service Console while not the highest level of performance, the SC must participate in the iSCSI network so it has access to it no matter what so it is generally acceptable from a security perspective. This however could affect performance of the VMs during backups as the SC is also your backup channel. With only 6 pNICS you have to make some choices somewhere. I would still shoot for 8 ports perhaps using 4 Port Intel MT or Intel VT cards. Offloading your iSCSI IO is a good thing to do if you can.

I think many new sales of ESX use iSCSI, but there are still A LOT of SAN based solutions out there and more coming on board, currently it is still the fastest IO solution if you look at just the raw numbers. That will change when 10G is available but I think SAN will run 10G as well as iSCSI so it may just be a dead heat. But that is in the future some when....

Best regards,
Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

Message was edited by: Texiwill

Re: Hardware Planning

14. Nov 11, 2007 5:27 PM in response to: dmca
Click to view ejward's profile Master 863 posts since
Sep 23, 2005

I think the idea is to put all your iSCSI traffic on it's own switch. There's ways to optimize a switch for iSCSI traffic that you would not do for regular network traffic.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities