PowerCLI: Configured Maximums – Storage

Title: PowerCLI: Configured Maximums – Storage

Author(s): (VIRTU-AL) Alan Renouf

Target Audience: Technical - Intermediate

Current Revision:

First Published: 17 March 2010

Products: VMware, Powershell

UID: XD10217

Posted Wed, 17/03/2010 - 07:22 by xtravirt

Use PowerCLI to check how many hosts should be in a cluster or how many datastores should be set as a maximum before it starts impacting performance

Punchy Text:

Use PowerCLI to check how many hosts should be in a cluster or how many datastores should be set as a maximum before it starts impacting performance

Alan Renouf is a community peer for VMware PowerCLI, Virtu-Al.Net. In 2009, he was named a vEXPERT by VMware. Alan's main focus is to teach and help other VMware admins automate their VMware infrastructures and make their lives easier through automation.
www.virtu-al.net.

With vSphere introduced some new maximum’s which we not only have to memorise for the exams but also have to keep in mind when designing and using your infrastructure.

In the back of your mind when adding a new host to a cluster you should always be thinking, how many hosts should be in this cluster ? or when adding another LUN to your clustered hosts, how many datastores should I have as a maximum before it starts impacting my performance and how many paths are supported ?

The answer to these questions (in my case anyway) is to use PowerCLI to check them

I will of course add these to the next version of vCheck so they are automatically checked for but in the meantime here are some quick one-liners to check your infrastructure against the configured maximums for storage, I will add more as I write them:

Virtual machines per volume: 256 Maximum: