How To Guy

How to Create a Virtual vSphere Lab

The best way to learn anything is by doing it. You want to learn more about VMware vSphere? Build a lab.

• By David Davis
• 03/01/2011

The best way to learn anything is by doing it. You want to learn more about VMware vSphere? Build a lab. It doesn't have to be complex or expensive, just capable. (We'll talk more about that in a minute.) Your new vSphere lab will help you in many ways:

• Improve your skills: Do things that you can't do on your production infrastructure (if you have one). Implement new features you've only read about. Break vSphere and learn how to troubleshoot it.
• Prepare for certification: Not only will your quest for the VMware Certified Professional (VCP) certification benefit from your hands-on experience, but the new VMware Certified Advanced Professional (VCAP) certifications will require it even more. I took the test recently, and I can safely say that you won't get by with just "reading" about vSphere troubleshooting.
• Proof of concept: Demonstrate what the power of vSphere advanced features, desktop virtualization or disaster recovery can do for your company. Considering enabling VMware High Availability (VMHA), Distributed Resource Scheduler (DRS) or Fault Tolerance (FT)? Test them in the lab first before enabling them in production.

Once you have a lab, you'll never want to be without it again.

Likely your first concern is the cost. This lab could be built using your existing hardware at no cost. Here are two options for building a vSphere lab:

• Option 1. Virtual vSphere Infrastructure with VMware Workstation: With a PC or laptop that you're already using, you can install the 60-day evaluation of VMware Workstation. Inside that, you can install the 60-day evaluation of VMware vSphere. The virtual lab can contain two ESXi servers, a Windows vCenter server and even a virtual iSCSI SAN by installing the free OpenFiler. The primary requirement to do this is that your PC CPU allows you to enable Intel VT or AMD-V, and you need to have a fair amount of RAM (4GB or more). The primary limitations are going to be the performance that you can get out of your desktop or laptop system (without negatively impacting the performance of your daily apps), as well as the inability to run 64-bit nested virtual machines (VMs). That means that with vCenter 4 running in 64-bit Windows (now a requirement), you'll have to run it as a VM in Workstation, not as a VM under your virtual ESXi servers. It also means that you won't be able to power on any 64-bit VMs inside an ESXi server. Still, this is an excellent option for a portable virtual infrastructure lab environment costing little or nothing.
• Option 2. Real vSphere Infrastructure with Dedicated Hardware: If you have $1,000 to $3,000 to invest in a vSphere lab, you could build a nice lab with dedicated hardware. By still using the 60-day evaluation of vSphere, the software costs would be zero. As for the dedicated hardware, I'd recommend low-end servers (I use the Dell T610) and a small SAN such as the Iomega Ix4-200D. I bought two T610s with 8GB RAM, quad-core CPUs, very little local storage (not much is required) and the Iomega SAN, all for about $3,000. With this, I run vCenter as a VM and, using the 60-day enterprise-plus vSphere license, I'm able to use all the advanced features, such as VMotion, SVmotion, VMHA, DRS, Distributed Power Management and FT. You can easily run 10 or more VMs and get decent performance.

I know a lot of pre-sales engineers and salespeople that frequently use the first option for customer demos everyday. I use the second option daily and know many VMware admins out there who do as well.

Building a virtual lab is a rewarding learning experience that will pay off, both for you and for your company in the long term. Get started learning, testing and proving the power of virtualization today!