VMware Cloud Community
AlbertWT
Virtuoso
Virtuoso
Jump to solution

Best Practice and Suggestion in combining different VMHost specs into single DRS cluster ?

People,

In my HP Blade c7000 enclosure, have two different Blade Servers:

HP BL 465c G7

AMD Opteron 6172

CPU Cores: 2 sockets x 12 cores = 24 vCPU total

RAM: 96 GB

HP BL 465c G8

AMD Opteron 6378

CPU Cores: 2 sockets x 16 cores = 32 vCPU total

RAM: 256 GB

So how do I combined the two ofthose hardware types into one single DRS cluster for simplicity ?

What's the caveats or the disadvantage when combining those different Blade servers into single DRS cluster ?

Thanks in advance.

/* Please feel free to provide any comments or input you may have. */
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Take a look here some for benefits: An often forgotten VMware benefit – Pick and Mix | VMware TAM Blog - VMware Blogs

But remember that if you really need protect again hardware failure from one of your host, you must not run more VM than the host with HP BL 465C G7 can support, otherwise some VMs cannot boot in case of failover.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

4 Replies
rcporto
Leadership
Leadership
Jump to solution

Take a look here some for benefits: An often forgotten VMware benefit – Pick and Mix | VMware TAM Blog - VMware Blogs

But remember that if you really need protect again hardware failure from one of your host, you must not run more VM than the host with HP BL 465C G7 can support, otherwise some VMs cannot boot in case of failover.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Alistar
Expert
Expert
Jump to solution

Hello,

the only thing I can think of is balancing the RAM on your hosts, if the memory modules are compatible with the previous generation - but even that does not matter that much because the DRS can handle the different memory sizes pretty elegantly. Otherwise as Richardson said, keep a soft cap of your VMs to that your weakest CPU can handle, otherwise you could be facing huge ready times on failover (ie oversubscribing the CPU) which is not good.

Stop by my blog if you'd like 🙂 I dabble in vSphere troubleshooting, PowerCLI scripting and NetApp storage - and I share my journeys at http://vmxp.wordpress.com/
AlbertWT
Virtuoso
Virtuoso
Jump to solution

So how do you soft-capping means ?

at the moment they are now running on its own DRS clustway for each Blade servers.

/* Please feel free to provide any comments or input you may have. */
0 Kudos
Alistar
Expert
Expert
Jump to solution

If you know the VMs' workload and how they behave I think you can somehow count the physical core:vCPU consolidation ratio (ideally the one that will keep your CPU Ready <5% at all times) and locate that many VMs in your new cluster that would suit the worst-case scenario (ie. all of them running on the less powerful host)

Stop by my blog if you'd like 🙂 I dabble in vSphere troubleshooting, PowerCLI scripting and NetApp storage - and I share my journeys at http://vmxp.wordpress.com/