Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
VS5OS_VATCLabSetupGuide.docx
Copyright © 2012 VMware, Inc. All rights reserved.
Introduction
This guide provides information that VATCs need to set up the lab environment for the VMware
vSphere: Optimize and Scale course.
This guide lists the hardware requirements, software requirements, and special configuration
instructions for the ESXi hosts, vCenter Server systems, and other servers necessary for the
hands-on lab exercises.
Each ESXi 5.1 host must meet the minimum hardware requirements:
• Shared storage: Minimum of 12GB per student ESXi 5.1 host, assuming each virtual
machine is configured with a 2GB virtual disk
(Shared storage is described in further detail in the Storage
Requirements section.)
Licensing Requirements
A vSphere 5.1 Enterprise Plus and a vCenter Server Standard license key must be available for
the students to install. Evaluation license keys are available from the periodic e-mail sent out to
all instructors, whose subject is “TRAINER DISTRIBUTION-Technical Services-60 day Evaluation
Licenses”.
1. The Management LAN - This LAN is used for the VMkernel management connections on
the ESXi host. In addition, the default port group, VM Network, must be present on this
LAN.
2. The Production LAN – This LAN is used for student virtual machines to simulate
production traffic. This configuration will use one physical NIC port from each host.
3. The vMotion LAN – This LAN is used for vMotion migrations of student virtual machines.
The networks mentioned above do not require isolation from other VATC components. Also,
the use of VLANs within physical network switches is permitted. If you do use VLANs, ensure
that the Management LAN and the Production LAN are within the same broadcast domain.
The network speed for all classroom LANs should be a minimum of 1 Gbps.
NOTE: The Auto Deploy lab requires special networking requirements. See the Auto Deploy lab
requirements section for more details.
Local Storage
Each ESXi host has a local datastore. This datastore can be used to hold the following objects:
The vApps and test virtual machines are described in further detail in the Virtual Machine
Requirements section.
VAAI-Compliant Storage
If you are using a VAAI-compliant storage array (for example, Clariion with proper Flare code),
then note the following:
NOTE: All lab exercises have been tested using the Windows vCenter Server system. Do not use
the Linux vCenter Server appliance.
Hardware requirements
The vCenter Server system can be either a physical machine or a virtual machine. If you deploy
them as virtual machines, then place the vCenter Server virtual machines on the infrastructure
host (see the Infrastructure Host Requirements section).
The Windows vCenter Server system must meet the minimum hardware requirements:
• CPU: 2 64-bit CPUs or one 64-bit dual-core processor (2.0GHz or higher Intel
or AMD processor)
• Disk space: Minimum of 15GB (minimum of 20GB if you are using Windows Server
2008 R2)
Software requirements
The Windows vCenter Server system must be installed with the following software:
• A 64-bit Windows operating system that supports vCenter Server 5.1. Choose from one
of the following operating systems:
• PuTTY
Ensure that no stored sessions exist in WinSCP. To verify this, start WinSCP. In the
WinSCP Login dialog box, click Stored sessions in the left pane. Stored sessions are
displayed in the right pane. Delete all stored sessions.
Configuration requirements
The Windows vCenter Server system must have the following configuration:
• The TCP/IP server service must be enabled using the SQL Server Configuration Manager.
• For the vCenter Server database, you can use either the default database or a remote
database, either Microsoft SQL Server 2005 or 2008. If you use a remote Microsoft SQL
Server database, then configure an ODBC connection to that database.
• Recommended: Install sysprep files in the appropriate folder on the vCenter Server
system. To find the correct folder location for your sysprep files, see Knowledge Base
article 1005593, “Sysprep file locations and versions”.
2. Create a sub-folder, naming it anything you want (for example, “vSphere 5.1 Installer”).
Place the vSphere 5.1 installation files in this folder. The installation files are needed by
the Auto Deploy lab (lab 21).
3. Download the TAR archive file, vAppTemplates.tar, from the VATC Web site,
http://vatc.vmeduc.com. Download the file to a file system that is accessible by the
vCenter Server system. You will need at least 1.8GB to hold the TAR file.
Use the program of your choice to unarchive the contents of the TAR file. For example,
use the free program named 7-Zip (see 7-Zip.org). Place the contents of the TAR file in
the Lab Files folder. The result is a Lab Files folder whose contents look like this:
Do not deploy from these OVF templates. The students will deploy from these OVF
templates when instructed to do so in the lab exercises.
The CPU-HOG and RAM-HOG vApps are described in further detail in the Virtual
Machine Requirements section.
Figure 1 is an example of what each student’s vCenter Server hierarchy should look like:
The vCenter Server system must be configured with the following inventory hierarchy:
o Six virtual machines should be displayed under each ESXi 5.1 host: Lab16_01,
Lab16_02, Test01, Test02, Win01, and Win02. These virtual machines are
described in further detail in the Virtual Machine Requirements section.
o Keep the vSphere HA admission control policy at “Host failures the cluster
tolerates.”
To deploy the vMA appliance, use one of the following two methods:
2. When you use the vSphere Client to deploy vMA as a virtual appliance, you can enter
the following URL in the "Import from URL" field of the "Deploy OVF Template" wizard:
http://www.vmware.com/go/importvma/vma4.ovf.
The only requirement for the student desktop machine is that the student be able to access
his/her vCenter Server system. Therefore, ensure that Remote Desktop Connection is available
on each student’s desktop machine.
NOTE: The vCenter Server system can also function as the student desktop machine and does so
quite nicely. It is not necessary to have a separate machine.
NOTE: If you are using a nested ESXi lab environment and two students are sharing the same
pod, you will want to use a naming convention such as the following:
Use the OVF template named MasterTestVM to deploy both test virtual machines. The OVF
template is contained in the TAR archive file, MasterTestVM.tar. This TAR file can be
downloaded from http://vatc.vmeduc.com. Download the TAR file to a file system that is
accessible to the vCenter Server system. You will need enough space on this file system to hold
the TAR file and the resulting MasterTestVM folder:
• MasterTestVM.tar: 2.3GB
Use the program of your choice to “untar” the MasterTestVM folder. For example, use the free
program named 7-Zip (see 7-Zip.org). The contents of the MasterTestVM folder look like this:
Deploy both the Test01 and Test02 virtual machines from the MasterTestVM OVF template.
Name of virtual machine Name the virtual machines Test01 and Test02.
2. After you deploy Test01 and Test02, verify that both Test01 and Test02 are configured
to have 1 CPU, 1GB memory, 1 NIC adapter of type E1000, and one virtual disk, 15GB in
size.
3. Verify that you can log in to Test01 and Test02. Log in as user root, the password is
vmware.
NOTE: Win01 and Win02 are similar to the virtual machines that get created by students in the
VMware vSphere: Install, Configure, Manage course, except named differently.
Each student’s ESXi host must contain Win01 and Win02. These virtual machines should be
configured as follows:
VM hardware version 9
Memory 384MB
3. Install Network Monitor 3.4 into Win01 and Win02. Network Monitor is needed for Lab
4, Port Mirroring. Download the installer from the Microsoft Download Center (search
for Network Monitor 3.4).
Setting Values
VM hardware version 9
Memory 2GB
The CPU and memory reservation settings for Lab16_01 were chosen to deliberately prevent the
virtual machine from powering on. The memory reservation prevents this virtual machine from
starting only if the ESXi host has 4GB of RAM.
NOTE: If your ESXi host has more than 4GB of RAM, then you will need to adjust the memory
reservation by increasing the value. The amount that you increase the reservation depends on
the amount of memory allocated to your ESXi host. The goal here is to choose a memory
reservation value that will deliberately prevent the virtual machine from powering on.
Setting Values
VM hardware version 9
Memory 1GB
For your reference, the CPU-HOG vApp was created with the following attributes:
All virtual machines start in Group 1 of the vApp and are configured to start up 5
seconds apart when the vApp is powered on.
• This vApp contains 6 virtual machines, Workload11 through Workload16. Like the CPU-
HOG vApp, these “workload” virtual machines are also diskless, and also boot from a
CD-ROM ISO image named ubcd411.iso.
All virtual machines start in Group 1 of the vApp and are configured to start up 5
seconds apart when the vApp is powered on.
To download the offline bundle and place it in the proper location, perform the following steps:
1. Download the ESXi 5.1 Offline bundle from the product download page on the VMware
Web site. The offline bundle, also called the software depot, will be used in the Auto
Deploy and Image Builder labs.
3. Rename the offline bundle ZIP file to LabDepot.zip. Move LabDepot.zip to the folder,
C:\Depot.
The Auto Deploy feature requires the use of a DHCP server. Therefore, in order for each student
team to perform the Auto Deploy lab properly, the servers of each student team must be placed
on a separate LAN.
It is only necessary to place each student team’s servers on a separate LAN for this lab only. For
all other labs, the student teams’ servers can be located on a common LAN (refer to the
Networking Requirements section).
If you are unable to create a separate LAN for each student team, another alternative is to set
up one DHCP/TFTP server for the entire class to use. The disadvantage of this alternative is that
students will not be able to perform the steps in the lab to set up the DHCP server and the TFTP
server. You, the instructor, can perform these steps as a demonstration, or you can set up the
DHCP/TFTP server as part of your lab kit deployment process.
4. vSphere PowerCLI 5.1, which is installed on each student desktop machine (see the
Student Desktop Machine requirements section)
6. A Windows system referred to as the DHCP/TFTP server (preferably other than the
vCenter Server system). This system has the following components:
a. The Windows DHCP server. Do not configure it. The students will configure and
start the DHCP server during the lab exercise.
b. A TFTP Server that is accessible from the DHCP server and the vCenter Server
system. The TFTP server that was used to create the lab is a free tool from Solar
Winds. Get the TFTP server software from the following link:
http://www.solarwinds.com/products/freetools/free_tftp_server.aspx. Install
the software onto this Windows system, but do not configure it. The students
will configure and start the TFTP server during the lab exercise.
In addition, students need to be able to access the BIOS of their ESXi host, for example, through
iLO, DRAC, or a local console. Students need this access so they can boot their ESXi host from
the network instead of from disk.
For a sample of this document, you can view the lab configuration sheet documents for the
VMware vClass environment. These lab configuration sheets are located on the VMware
vSphere: Optimize and Scale [V5.1] section of the Trainer’s Communities at
http://communities.vmware.com/community/vmtn/private/pso/vsphere/vs5/vsos5?view=docu
ments