0% found this document useful (0 votes)
147 views72 pages

Edu en Vve Lab Se

EDU-EN-VVE-LAB-SE

Uploaded by

Richie Ballyears
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
147 views72 pages

Edu en Vve Lab Se

EDU-EN-VVE-LAB-SE

Uploaded by

Richie Ballyears
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 72

VMware Virtualization Essentials

Lab Manual
vSphere 6

VMware® Education Services


VMware, Inc.
www.vmware.com/education
VMware Virtualization Essentials
vSphere 6
Part Number EDU-EN-VVE-LAB
Lab Manual
Prerelease
Copyright © 2016 VMware, Inc. All rights reserved. This manual and its accompanying materials
are protected by U.S. and international copyright and intellectual property laws. VMware products
are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a
registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
All other marks and names mentioned herein may be trademarks of their respective companies.
The training material is provided “as is,” and all express or implied conditions, representations,
and warranties, including any implied warranty of merchantability, fitness for a particular purpose
or noninfringement, are disclaimed, even if VMware, Inc., has been advised of the possibility of
such claims. This training material is designed to support an instructor-led training course and is
intended to be used for reference purposes in conjunction with the instructor-led training course.
The training material is not a standalone training tool. Use of the training material for self-study
without class attendance is not recommended.
These materials and the computer programs to which it relates are the property of, and embody
trade secrets and confidential information proprietary to, VMware, Inc., and may not be
reproduced, copied, disclosed, transferred, adapted or modified without the express written
approval of VMware, Inc.

www.vmware.com/education
C ONTENTS
Lab 1 Using vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Lab 2 Creating a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library . . . . . . . . . . 13
Lab 4 Modifying Virtual Machine Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Lab 5 Managing Virtual Machines and Using Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Lab 6 Monitoring Virtual Machine Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Lab 7 Managing Tasks, Events, and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Lab 8 Managing Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Lab 9 Using vSphere vApps, Managing Multi-Tiered Applications . . . . . . . . . . . . . . . . . . . . . . . . . 45
Lab 10 Using vSphere vMotion and Storage vMotion to Migrate Virtual Machines . . . . . . . . . . . . 49
Lab 11 Implementing a vSphere DRS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Lab 12 Using vSphere HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Answer Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

iii
iv VMware Virtualization Essentials
Lab 1 Using vSphere Web Client

Objective: Navigate and customize vSphere Web Client


In this lab, you perform the following tasks:

1. Navigate vSphere Web Client


2. Pin and Unpin Panes
3. Hide the Getting Started Tabs
4. Perform Search Operations with vSphere Web Client
5. Remove Stored Data from vSphere Web Client

Task 1: Navigate vSphere Web Client


You use VMware vSphere® Web Client to view and manage objects.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• ESXi host
• Local datastore
• Shared datastore
1. Open the Firefox Web browser and connect to the VMware vCenter Server® Appliance™
home page at https://vCenter_Server_Appliance/vsphere-client.
2. On the vSphere Web Client login page, log in as administrator@vsphere.local and enter the
vCenter Server Appliance administrator password.
3. Click Login.

1
4. In the Navigator pane, click vCenter Inventory Lists.
The Navigator pane changes to show objects related to the configured VMware vCenter
Server® instance.

Q1. What headings are listed under vCenter Inventory Lists?


1. vCenter Home, Virtual Machines, vApps, VM Templates in Folders, Content Libraries, and
various Resources

5. Under Resources, click Hosts.


The Navigator pane and contents pane change to show configured VMware ESXi™ hosts.

Q2. How many ESXi hosts are available under Hosts?


2. Two

6. In the Navigator pane, select the ESXi host defined in the class configuration handout.
7. In the contents pane, click the Related Objects tab.
8. Click Virtual Machines.
Virtual machines configured on the host appear in the contents pane.

Q3. How many virtual machines do you see?


3. Two: Win_StuA and Linux_StuA

Q4. What is the state of each virtual machine?


4. Answers vary.

9. Using the Hierarchy menu in the contents pane, navigate to the vCenter Server Appliance. s
10. In the Navigator pane, click Datastores.
The Navigator pane changes to show all of the datastores configured on the vCenter Server
Appliance. The contents pane changes to show the Datastores tab for the appliance.
11. Under Datastores, select the local datastore specified in the class configuration handout.
12. Click the Related Objects tab.
13. Click the Virtual Machines tab.

Q5. How many virtual machines do you see?


5. One: Win_StuA.

Q6. Why is this result different from the earlier virtual machine list?
6. This view shows the virtual machines configured to use this datastore as storage. The other
view showed all virtual machines configured on the ESXi host.

2 Lab 1 Using vSphere Web Client


14. At the top of the Navigator pane, click the Recent Objects icon.

A list of the most recently viewed objects appears.


15. From the list of recent objects, select the vCenter Server Appliance object.
16. In the Navigator pane, select Datastores.
17. Under Datastores, select the shared datastore.
18. Click the Related Objects tab.
19. Click the Virtual Machines tab.

Q7. How many virtual machines do you see?


7. One: Linux_StuA.

Q8. Why is this result different from the earlier virtual machine lists?
8. This view shows the virtual machines configured to use the Shared1 datastore as storage.

20. At the top of the Navigator pane, click the Recent Objects icon.
21. From the list of recent objects, select the vCenter Server Appliance.
22. In the main contents pane, click the Related Objects tab.
23. Click the Virtual Machines tab.

Q9. How many virtual machines do you see?


9. Two: Win_StuA and Linux_StuA

Q10. Why is this result different from the earlier virtual machine list?
10. All virtual machines configured on the vCenter Server Appliance appear, including virtual
machines from all hosts and all datastores.

24. Point to the Home icon and select Home to return to the vSphere Web Client Home page.

Lab 1 Using vSphere Web Client 3


Task 2: Pin and Unpin Panes
You can adjust the vSphere Web Client panes to provide more space for the contents area.
1. In the contents pane, select Hosts and Clusters.
2. Expand the data center object and click your host.
3. In the Navigator pane, click the pin icon.

The Navigator pane collapses and the contents pane expands.


4. Click the collapsed Navigator pane to expand it.

Q1. How is the view affected?


1. The Navigator pane expands when you click on it. When you click outside the pane, the
Navigator pane collapses and minimizes to the left.

5. In the Navigator pane, click the pin icon.


6. On the blue vSphere Web Client title line, open Administration@VSPHERE.LOCAL.
7. Select the Layout Settings menu.
8. Select the Recent Tasks check box.
9. Click OK to close the Recent Tasks pane.
10. Open Administration@VSPHERE.LOCAL.
11. Select the Layout Settings menu.
12. Select the Recent Tasks check box.
13. Click OK.
The Recent Tasks pane appears.
14. At the bottom of the vSphere Web Client pane, click the Recent tasks pin icon.
15. Click on the collapsed Recent Tasks pane.}

Q2. How does the view change?


2. The Recent Task pane expands.

16. Click the pin icon to repin the Recent Task pane

4 Lab 1 Using vSphere Web Client


Task 3: Hide the Getting Started Tabs
Most inventory objects have Getting Started tabs. You can hide these tabs to simplify the vSphere
Web Client user interface.
1. In vSphere Web Client, point to the Home icon and select Hosts and Clusters.
2. From the Help drop-down menu in the blue line above the contents pane, select Hide All
Getting Started Pages.

Q1. How does the contents pane change?


1. The Getting Started tab does not appear.

3. If not selected already, select your ESXi host in the Navigator pane.

Q2. In the contents pane, what tabs are available?


2. Summary, Monitor, Manage, and Related Objects

Task 4: Perform Search Operations with vSphere Web Client


You use the search function in the vSphere Web Client to find specific objects in the vCenter Server
inventory. You can save a search.
1. Point to the Home icon and select Home.
2. Click New Search in the Navigator pane.
3. Enter linux in the Search box and click Search.

Q1. What is listed in the search results?


1. The Linux virtual machines configured on the vCenter Server Appliance are listed.

4. Click Save.
5. In the Name box of the Save Search dialog box, enter searchA.
6. Click OK.
7. Point to the Home icon and select Home.
8. In the Navigator pane, click Saved Searches.
9. Click searchA to view your saved search.
10. At the top of the Navigator pane, click Home to return to the vSphere Web Client Home page.

Lab 1 Using vSphere Web Client 5


Task 5: Remove Stored Data from vSphere Web Client
You use the search function in the vSphere Web Client to find specific objects in the vCenter Server
inventory. You can save a search to use again.
1. On the blue vSphere Web Client title line, open Administrator@VSPHERE.LOCAL.
for the current vSphere Web Client session to appear.
2. Select Remove Stored Data.
3. From the User Preferences for Administrator@VSPHERE.LOCAL menu, select the Saved
Searches check box.
4. Click Clear selected data.
The vSphere Web Client interface refreshes.
5. To confirm that you have cleared the saved search, click Saved Search at the bottom of the
Navigator pane.
6. Close the vSphere Web Client.

6 Lab 1 Using vSphere Web Client


Lab 2 Creating a Virtual Machine

Objective: Create a virtual machine and install a guest


operating system and VMware Tools
In this lab, you perform the following tasks:

1. Create a Virtual Machine


2. Install a Guest Operating System on the Virtual Machine
3. Install VMware Tools on the Windows Guest Operating System
4. Install the VMRC
5. Open a Virtual Machine Console in VMRC

Task 1: Create a Virtual Machine


You can create a single virtual machine and configure it with the required hardware and software
configuration.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• ESXi host
• Shared datastore
• Repository for ISO images
• ISO filename
1. From the Firefox Web browser, open vSphere® Web Client.

7
2. On the vSphere Web Client login page, log in as administrator@vsphere.local and enter the
VMware ESXi™ administrator password.
3. Click Login.
4. In the contents pane, click Hosts and Clusters.
5. If needed, expand the Training data center and the Lab Cluster cluster to show their contents.
6. In the Navigator pane, right-click your assigned ESXi host and select New Virtual Machine >
New Virtual Machine.
The Create a New Virtual Machine wizard starts.
7. On the Select a creation type page, select Create a new virtual machine and click Next.
8. On the Select a name and folder page, enter the name of the virtual machine StuA_NVM.
9. Select Training as the location for the virtual machine and click Next.
10. On the Select a compute resource page, select your ESXi host and click Next.
11. On the Select storage page, select the shared datastore and click Next.
12. On the Select compatibility page, select ESXi 6.0 and later and click Next.
13. On the Select a guest OS page, select Microsoft Windows Server 2003 (32-bit) from the
Guest OS Version drop-down menu and click Next.
14. On the Customize hardware page, expand New Hard disk.
15. Verify that the New Hard disk is set to 8 GB.
16. Under Disk Provisioning, click Thin provision.
17. Click the black triangle next to New Hard Disk to collapse the advanced options for the New
Hard Disk.
18. Expand New CD/DVD Drive.
19. In New CD/DVD, select Datastore ISO File from the drop-down menu.
20. Expand the Shared Datastore list and click the ISO folder.
21. Select the ISO filename in your class configuration handout and click OK.
22. Select the Status Connect At Power On check box.
23. Collapse New CD/DVD and click Next.
24. On the Ready to complete page, click Finish.
25. Verify that the new virtual machine appears in the inventory.

8 Lab 2 Creating a Virtual Machine


Task 2: Install a Guest Operating System on the Virtual Machine
After a virtual machine is added to inventory, you install a guest operating system in the virtual
machine. Use the Tab and Space Bar keys to complete this task.
1. Right-click your virtual machine (StuA_NVM) and select Power > Power On.
2. Right-click the virtual machine again and select Open Console.
3. If a security error appears, perform the following steps.
a. Select I Understand the Risks.
b. Click Add Exception.
c. Click Confirm Security Exception.
4. After your virtual machine powers on, the guest operating system installation begins.
Leave the virtual machine console open and allow the installation to continue.
The installation can take 10 to 15 minutes.

Task 3: Install VMware Tools on the Windows Guest Operating System


Installing VMware Tools™ on a virtual machine provides the virtual machine with added features
and capabilities. Use the Tab and Enter keys to complete this task.
Use the following information from the class configuration handout:
• Virtual machine administrator password
1. Log in to the new virtual machine after the guest operating system installation is completed.
a. In the menu bar of the virtual machine console, click Send Ctrl-Alt-Delete.
b. Log in as Administrator, using the virtual machine administrator password.
c. Click OK.
2. Press CTRL + ALT to release the mouse from the virtual machines console.
3. Switch to the vSphere Web Client tab.
4. Install VMware Tools.
a. In the contents pane of the virtual machine, right-click your virtual machine and select
Guest OS > Install VMware Tools.
b. In the Install VMware Tools window, click Mount.
c. Switch to the console for your virtual machine.
VMware Tools adds functionality, such as mouse control, in the virtual machine console.
d. Click in the virtual machine console.

Lab 2 Creating a Virtual Machine 9


e. Accept the default values in the VMware Tools setup wizard and click Install.
f. After the installation is complete, click Finish.
g. When you are prompted to restart the system to complete the VMware Tools setup, click
Yes.
5. Close the StuA_NVM tab and return to vSphere Web Client.
6. Minimize the Firefox Web browser.

Task 4: Install the VMRC


Virtual Machine Remote Console (VMRC) opens as a standalone application for the selected virtual
machine. You can also launch more than one console to access several remote virtual machines at
the same time.
Use the following information from the class configuration handout:
• Location of the VMware Remote Console Setup file.
Install VMware Remote Console:
1. From the LabFiles folder on your student desktop, install the VMRC setup file.
2. In the VMware Remote Console Setup wizard, click Next.
3. Accept the license agreement and click Next.
4. Accept the default destination folder and click Next.
5. In the user experience settings, deselect both the check boxes and click Next.
6. In the Ready to install page, click Install.
7. When the installation is complete, click Finish.
8. Close the LabFiles folder.

Task 5: Open a Virtual Machine Console in VMRC


After installing VMRC, open a virtual machine console:
1. In vCenter Inventory Lists, navigate to and click on your StuA_NVM virtual machine.
2. Click the Summary tab.
3. Click Launch Remote Console.
4. From the VMRC drop down menu, access the virtual machine login using the ctrl+alt+del
button.
The login credentials for this virtual machine are in the class configuration handout.

10 Lab 2 Creating a Virtual Machine


5. In the StuA_NVM console, click the VMRC button
6. From the VMRC menu, select Power > Shut Down Guest.
7. Close the VMRC and return to vSphere Web Client.
8. Point to the Home icon and select Home.

Lab 2 Creating a Virtual Machine 11


12 Lab 2 Creating a Virtual Machine
Lab 3 Deploying Virtual Machines Using
Cloning, Templates, and a Content
Library

Objective: Create and deploy virtual machine clones and


templates and customize a guest operating system
In this lab, you perform the following tasks:

1. Create a Template
2. Clone a Virtual Machine to a Content Library
3. Deploy a Virtual Machine from a Preconfigured Content Library Template
4. Create a Windows Customization Specification
5. Use a Windows Guest Specification File for Cloning
6. Deploy an OVF Template
7. Export an OVF Template

Task 1: Create a Template


You can create a master copy of a virtual machine by converting a virtual machine to a template.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• Virtual machine for template creation

13
• ESXi host
1. Open VMware vSphere® Web Client.
2. In the contents pane, click VMs and Templates.
3. If the virtual machine for template creation is not powered off, right-click the virtual machine
and select Power > Shut Down Guest OS.
4. Click Yes to confirm.
5. Right-click the virtual machine, select Template > Convert to Template, and click Yes to
confirm.
The virtual machine is converted to a template with the same name.
6. In the Recent Tasks pane, verify that the task is complete.
7. In the Navigator pane, click the Hosts and Clusters icon.
8. Select your VMware ESXi™ host.
9. In the center pane, click the Related Objects tab, and then click the VM Templates in Folders
tab.
10. Verify that the virtual machine appears as a template.

Task 2: Clone a Virtual Machine to a Content Library


Use vSphere Web Client to clone a virtual machine template into the student source content library.
Use the following information from the class configuration handout:
• Assigned virtual machine to clone
• Student designation
1. In the Navigator pane, click the VMs and Templates icon.
2. In the Navigator pane, right-click your assigned virtual machine and select Clone to Template
in Library.
3. In the Clone to Template in Library window, append -Library to the template name in the
Template Name text box.
4. In the content library list, select the Student designation-source library and click OK.
5. At the bottom of the vSphere Web Client interface, observe the Recent Tasks pane.
In the Recent Tasks pan, you will see a new OVF package export task appear.
6. Point to the Home icon and select vCenter Inventory Lists.
7. Click Content Libraries.
The template appears in the Templates tab under the Related Objects tab of the content library.

14 Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library
Task 3: Deploy a Virtual Machine from a Preconfigured Content Library
Template
You use vSphere Web Client to deploy a new virtual machine from the template available in the
subscriber library.
Use the following information from the class configuration handout:
• Shared datastore name
• vCenter Server Appliance name
• Assigned ESXi host
• Student designation
1. Point to the Home icon and select Home.
2. In the left pane or in the Navigator pane, click Hosts and Clusters.
3. Expand the Training data center and the Lab Cluster cluster.
4. Right-click on your ESXi host and select New Virtual Machine > New VM from Library.
5. In the select template screen, select the Win_StuA-Library template from the student library
and click Next.
6. In the Name text box, enter Student_designation-VM03.
7. In the Select a Data Center or folder pane, select the Training data center and click Next.
8. On the Select a Resource page, select your ESXi host and click Next.
9. On the Review Details page, click Next.
10. From the Select virtual disk format drop-down menu in the Select Storage page, select Thin
provision.
11. In the Filter tab in the Select Storage page, select your shared datastore and click Next.
12. On the Select Networks page, ensure that VM Network is selected and click Next.
13. On the Ready to complete page, click Finish.
14. If the Recent Tasks pane is not visible, click Recent Tasks at the bottom of the vSphere Web
Client pane.
15. Monitor the progress and wait for the Deploy OVF package task to complete.
16. In the vSphere Web Client pane, point to the Home icon and select VMs and Templates.
17. Verify that the Student_designation_VM03 virtual machine is deployed.

Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library 15
Task 4: Create a Windows Customization Specification
You can create a Windows customization specification to customize the configuration of the
Windows virtual machines that you create.
Use the following information from the class configuration handout:
• Product key for Windows operating system
• Administrator password for Windows customization specification
• Time zone for Windows customization specification
1. In vSphere Web Client, point to the Home icon and select Home.
2. Under Monitoring in the contents pane, click Customization Specification Manager.
3. Click the Create a new specification icon.
4. On the Specify Properties page, enter CustWinStuA in the Customization Spec Name text
box and click Next.
5. On the Set Registration Information page, enter StudentA in the Name text box.
6. In the Organization text box, enter VMware and click Next.
7. On the Set Computer Name page, select Use the virtual machine name and click Next.
8. On the Enter Windows License page, enter the product key for the Windows operating system
and click Next.
9. On the Set Administrator Password page, enter and confirm the Administrator password for the
Windows customization specification and click Next.
10. On the Time Zone page, specify a time zone for this virtual machine. Use the same timezone as
used on your student desktop from the Time Zone drop-down menu.
11. Click Next.
12. On the Run Once page, click Next.
13. On the Configure Network page, click Next.
14. On the Set Workgroup or Domain page, click Next.
15. On the Set Operating System Options page, click Next.
16. On the Ready to complete page, click Finish.

16 Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library
Task 5: Use a Windows Guest Specification File for Cloning
You can use guest customization specifications to configure virtual machines that are cloned.
Use the following information from the class configuration handout:
• Virtual machine for cloning using a guest customization specification
• Virtual machine Administrator password
• Shared datastore for cloning
1. Point to the Home icon and select Home.
2. In the contents pane, click VMs and Templates.
3. If necessary, expand the elements in the Navigator pane until virtual machines and templates are
visible.
4. Right-click the virtual machine that you want to clone.
5. Use a guest customization specification and select Clone > Clone to Virtual Machine.
The Clone Existing Virtual Machine wizard starts.
6. On the Select a name and folder page, name the virtual machine CustSpec_StuA.
7. Select Training as the location for the virtual machine and click Next.
8. On the Select a compute resource page, select your ESXi host and click Next.
You might have to expand Lab Cluster cluster under Training to see your host.
9. On the Select Storage page, select Thin Provision from the Select virtual disk format menu.
10. Select the shared datastore and click Next.
11. On the Select clone options page, select the Customize the operating system and Power on
this virtual machine after creation check boxes and click Next.
12. On the Customize guest operating system page, select the guest customization specification that
you created and click Next.
13. On the Ready to Complete page, click Finish.
14. Monitor the progress in the Recent Tasks pane.
This process takes a few minutes to complete. Wait 5 minutes before moving to the next step. If
you log in to the new virtual machine too soon, you could interrupt the customization process.
15. Open the Summary tab of the virtual machine that you just created and launch the Remote
Console.
16. Observe the VMware image customization operations.

Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library 17
17. When the customization operations are complete and the login screen appears, log in to the
virtual machine as Administrator with the virtual machine Administrator password.
18. In the virtual machine console, select Start > Run.
The Run window opens on your virtual machine.
19. Enter cmd and click OK.
The Command prompt window opens in your virtual machine.
20. At the command prompt, enter hostname.
The host name that appears should match your virtual machine name.
21. At the command prompt, enter exit to close the Command Prompt window.
22. In the virtual machine desktop, select Start > Shut Down > Shut down.
23. Click OK to shut down the virtual machine.
24. Close the remote console for the virtual machine.
25. Return to vSphere Web Client.

Task 6: Deploy an OVF Template


Open Virtualization Format (OVF) template files create preconfigured virtual machines, virtual
appliances, or vApps.
Use the following information from the class configuration handout:
• Source OVF template location
• Storage for deploying the OVF template
1. Point to the Home icon and select Home.
2. In the Inventories list of the contents pane, click vCenter Inventory Lists.
3. In the Navigator pane, click vCenter Servers.
4. Right-click your vCenter Server Appliance and select Deploy OVF Template.
The Deploy OVF Template wizard starts.
5. If a security message appears, click Allow.
6. If client integration error occurs, close the browser window and reopen it.
7. On the Select source page, click Browse, navigate to Desktop, and select the LabFiles folder.
This action automatically selects Local file.
8. Select Centos_Template.ova and click Open.

18 Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library
9. Click Next.
10. On the Review details page, click Next.
11. On the Select name and folder page, name the deployed virtual machine CentOS_A.
12. Under Select a folder or data center, select Training and click Next.
13. On the Select a resource page, expand the Lab Cluster cluster. Select your ESXi host and click
Next.
14. From the Select virtual disk format drop-down menu, select Thin Provision.
15. Ensure that the shared datastore is selected and click Next.
16. On the Select storage page, select the storage for deploying the OVF template.
17. On the Setup networks page, ensure that VM Network is displayed and click Next.
18. On the Ready to complete page, select the Power on after deployment check box and click
Finish.
19. Point to the Home icon and select VMs and Templates
20. In the Navigator pane, select the virtual machine that you created.
21. Verify that the virtual machine is running.
Deploying and starting the virtual machine can take several minutes.

Task 7: Export an OVF Template


You can export an OVF template to make it available for others to use to deploy a virtual machine,
virtual appliance, or vApp that you created in their environment.
Use the following information from the class configuration handout:
• Location to export OVF template
1. Shut down the guest operating system of the virtual machine that you created using an OVF
template.
2. Right-click the virtual machine and select Template > Export OVF Template.
3. In the Name text box of the OVF Template dialog box, enter CentOS_A.
4. Click Choose.
5. Browse to the location specified on the class configuration handout to export the OVF template
and click Select Folder.

Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library 19
6. Verify that Folder of files (OVF) is selected from the Format drop-down menu and click OK.
Wait for the OVF file to be created and saved in the location specified. This process might take
a few minutes.
7. In the upper right hand corner of the browser, minimize vSphere Web Client.

20 Lab 3 Deploying Virtual Machines Using Cloning, Templates, and a Content Library
Lab 4 Modifying Virtual Machine Settings

Objective: Configure virtual machine settings


In this lab, you perform the following tasks:

1. Upgrade the Virtual Machine Hardware Version


2. Configure the Virtual Memory
3. Change the Virtual Machine Name
4. Restrict the Number of Users Accessing the Virtual Machines
5. Configure the Swap File Location

Task 1: Upgrade the Virtual Machine Hardware Version


The virtual machine hardware version determines the virtual hardware that is available to a virtual
machine. You can upgrade the hardware version of a virtual machine using VMware vSphere® Web
Client.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• Virtual machine to use for tasks 1, 2, and 3
1. Open vSphere Web Client.
2. Point to the Home icon and select VMs and Templates.
3. In the Navigator pane, expand the objects as needed and select the virtual machine to use for
tasks 1, 2, and 3 (as shown in the configuration handout).
4. In the contents pane, click the Summary tab.

21
The Summary tab includes the VM Hardware tab, which is located below the console
thumbnail. You might have to expand VM Hardware to see the virtual machine hardware
version. The compatibility listing shows the virtual machine hardware version.

Q1. What is the virtual machine hardware version?


1. ESXi 5.5 and later (virtual machine version 10)

5. If needed, shut down the virtual machine. If it is not running, skip to Step 5.
a. In the contents pane, select Actions.
b. Select Power > Shut Down Guest OS.
c. Click Yes to confirm that you want to shut down the virtual machine guest operating
system.
6. Upgrade the virtual machine’s virtual hardware version.
a. In the contents pane, select Actions > Compatibility > Upgrade VM Compatibility.
b. Click Yes to confirm upgrading virtual machine hardware.
c. Select the hardware version as ESXi 6.0 and later and click OK.
7. Verify that the hardware version for the virtual machine was upgraded.
You might have to press the screen update arrow (the curved arrow in the blue bar above the
center pane) to see the change.

Q2. What is the virtual hardware version of the virtual machine now?
2. ESXi 6.0 and later (virtual machine version 11)

Task 2: Configure the Virtual Memory


After you enable the memory hot-plug setting, you can edit the memory setting for a virtual machine
while it is powered on.
Use the following information from the class configuration handout:
• Virtual machine to use for tasks 1, 2, and 3
1. Right-click the relevant virtual machine and select Power > Power On.
2. Click the Manage tab and select Settings.
3. In the contents pane, click VM Hardware and then click Edit.
4. Expand Memory in the Edit Settings dialog box.

Q1. Can you edit the RAM text box and add more memory to the virtual machine?
1. No, the text box is dimmed.

22 Lab 4 Modifying Virtual Machine Settings


5. Click Cancel in the Edit Settings dialog box.
6. Right-click the virtual machine and select Power > Shut Down Guest OS.
7. Click Yes to confirm shutdown.
8. In the contents pane, click VM Hardware and then click Edit.
9. Expand Memory in the Edit Settings dialog box.
10. Select the Memory Hot Plug box.
11. Click OK to save your changes.
12. Power on the virtual machine.
Wait for the virtual machine to start up.
13. Edit the memory setting for the virtual machine.
a. In the contents pane, click the VM Hardware tab and click Edit.
b. Expand Memory in the Edit Settings dialog box.
Please do not change the virtual machine or the virtual machine memory settings. Making
changes could cause problems in later labs.

Q2. Can you edit the RAM text box?


2. Yes, the text box can now be edited.

Q3. What is the maximum memory recommended for this virtual machine?
3. Answers vary.

14. Click Cancel to close the Edit Settings dialog box.

Task 3: Change the Virtual Machine Name


You can change a virtual machine’s name by editing its settings.
Use the following information from the class configuration handout:
• Virtual machine to use for tasks 1, 2, and 3
1. Right-click the virtual machine to use for tasks 1, 2, and 3 and select Rename.
2. Name the virtual machine WinA.
3. Click OK.

Lab 4 Modifying Virtual Machine Settings 23


Task 4: Restrict the Number of Users Accessing the Virtual Machines
You can restrict the number of users who can access a virtual machine console at the same time.
1. Right-click virtual machine WinA and shut down the guest operating system.
2. After the virtual machine is powered off, edit its settings.
a. Right-click the virtual machine and select Edit Settings.
b. Click the VM Options tab.
c. Expand VMware Remote Console Options.
d. Under Maximum number of sessions, select the Limit the number of simultaneous
connections to this virtual machine check box.
e. In the text box, change the number of connections from 40 to 2.
f. Click OK.
3. Right click the virtual machine and click Power
4. Click Power On.
5. Click Launch Remote Console.
The VMRC console opens in a new tab.
The guest operating system state is not important and you can ignore any recovery message that
is displayed in the console.
If you click inside the console window, press Ctrl+Alt (Fn+Ctrl+Option if you are using a Mac)
to release your mouse.
6. From vSphere Web Client, click Launch Remote Console to open a second console.
A second virtual machine console opens in a new tab.
7. From the vSphere Web Console, click Launch Remote Console to open a third console.

Q1. Can you open a third console for the virtual machine?
1. No, you cannot open a third console.

Q2. What message appears?


2. Unable to connect to the MKS: Console access to the virtual machine cannot be granted
because the connection limit of 2 has been reached.

8. Close all console windows and shut down the guest operating system on the virtual machine.

24 Lab 4 Modifying Virtual Machine Settings


Task 5: Configure the Swap File Location
You can change the location of the swap file for a virtual machine when the virtual machine is
powered off.
1. Right-click virtual machine WinA and select Edit Settings.
2. In the Edit Settings dialog box, click the VM Options tab.
3. Expand Advanced.
4. Under Swap file location, click Virtual machine directory.
5. Click OK.
The default location of the swap files is Virtual machine directory.
6. Minimize the vSphere Web Client page.

Lab 4 Modifying Virtual Machine Settings 25


26 Lab 4 Modifying Virtual Machine Settings
Lab 5 Managing Virtual Machines and
Using Snapshots

Objective: Manage virtual machine power settings and


snapshots
In this lab, you perform the following tasks:

1. Edit the Startup and Shutdown Settings for Virtual Machines


2. Unregister and Register a Virtual Machine on the vCenter Server System
3. Create a Snapshot
4. Revert to a Snapshot
5. Delete a Snapshot

Task 1: Edit the Startup and Shutdown Settings for Virtual Machines
You can change startup and shutdown settings for virtual machines to automatically start and stop
with their VMware ESXi™ host.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• ESXi host
• Virtual machine for task 1
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select Hosts and Clusters.

27
3. Select your ESXi host.
4. Click the Manage tab.
5. Click the Settings tab.
6. From the Virtual Machines menu, select VM Startup/Shutdown.
7. Edit the startup and shutdown settings for virtual machines on this host.
a. Click Edit.
b. Next to System Influence, select the Automatically start and stop the virtual machines
with the system check box.
8. Set one virtual machine to override the automatic startup settings.
a. Under Per-VM Overrides, select the virtual machine for task 1.
b. Click the up arrow to move the virtual machine to the Automatic Startup list.
c. Click OK.
9. (Optional) Reboot the host to test whether the virtual machine starts with the host.
a. Right-click the host assigned to you and select Power > Reboot.
b. Enter a reason to reboot and click OK.
This reboot can take several minutes. Wait for 5 minutes and click the refresh curved arrow
in the blue bar, above the center pane, to confirm that the host has rebooted.
c. If the host does not fully reboot, right-click the host and select Connection > Connect.
d. Observe whether the virtual machine starts as the host starts up.
e. From the Summary tab of the host, you might need to reset the Host to green.
f. Point to the Home icon and select VMs and Templates.

28 Lab 5 Managing Virtual Machines and Using Snapshots


Task 2: Unregister and Register a Virtual Machine on the vCenter
Server System
You can manually unregister a virtual machine from inventory without removing its configuration
files from storage. You can then re-register the virtual machine from its configuration files.
Use the following information from the class configuration handout:
• Datastore for re-registering the virtual machine
1. Confirm which datastore the Linux_StuA virtual machine is stored in.
a. In the Navigator pane, click the virtual machine.
b. In the content pane, click the Related Objects tab.
c. Click Datastores.
d. Verify the datastore in which the virtual machine is stored.
2. In the Navigator pane, select the Linux_StuA virtual machine.
3. Remove the virtual machine from the inventory.
a. Right-click the virtual machine and select Remove from Inventory.
b. When prompted to confirm, click Yes.
4. In the Navigator pane, select the ESXi host assigned to you
5. In the contents pane, click the Related Objects tab.
6. Click the Virtual Machines tab.
7. Verify that the virtual machine that you removed from the inventory is not listed.
8. Re-register the virtual machine, using the datastore on which it was created.
a. Click the Datastores tab under Related Objects.
b. Click the datastore for re-registering the virtual machine.
c. Right-click the datastore and select Register VM.
d. Select the Shared1 datastore in the Datastores pane.
e. Select Linux_StuA in the Contents pane.
f. Verify that the Linux_StuA.vmx file appears in the Contents pane.
g. Click OK.
The Register Virtual Machine wizard starts.
h. On the Name and Location page, select the Training location and click Next.

Lab 5 Managing Virtual Machines and Using Snapshots 29


i. On the Host/Cluster page, select the Lab Cluster cluster and click Next.
j. On the Specify a Specific Host page, select your ESXi host and click Next.
k. On the Ready to Complete page, click Finish.
9. Click the Hosts and Clusters icon in the Navigator pane on the left side of vSphere Web
Client.
10. Verify that the virtual machine appears in the inventory.

Task 3: Create a Snapshot


You can create a snapshot to preserve the state of a virtual machine, so that you can return to that
state in the future.
1. Right-click the WinA virtual machine and select Power > Shut Down Power Guest OS to
power it off.
2. Click Yes to confirm the guest OS shut down.
3. Right-click the virtual machine and select Snapshots > Take Snapshot.
The Take VM Snapshot dialog box appears.
4. In the Name text box, enter a name for the snapshot: WinASnapshot1.
5. Enter a description for the snapshot and click OK.
6. Create one more snapshot and name it: WinASnapshot2.
7. Power on the virtual machine.
8. Repeat steps 1 through 4 to create a third snapshot named WinASnapshot3 with the default
Snapshot of the virtual machine’s memory box selected.
9. Repeat steps 1 through 4 again and the following two substeps to create a fourth snapshot
named WinASnapshot4:
a. De-select Snapshot the virtual machine’s memory.
b. Select Quiesce guest file system.
10. Monitor the creation of Snapshot 4 in the Recent Tasks pane.

Q1. How did the snapshot creation process differ when the virtual machine was powered
on?
1. The Snapshot of the virtual machine’s memory and Quiesce guest file system (with VMware
Tools installed) check boxes were available.

30 Lab 5 Managing Virtual Machines and Using Snapshots


Task 4: Revert to a Snapshot
You can revert to a snapshot in order to return a virtual machine to its state at the time of the
snapshot.
1. Right-click the WinA virtual machine and select Snapshots > Manage Snapshots.

Q1. Where does the You are here icon appear?


1. Under the fourth snapshot, which is the last snapshot.
2. Select the WinASnapshot2 snapshot and click Revert to.
3. Click Yes to confirm reverting to the saved snapshot.

Q2. Where does the You are here icon appear?


2. Under the third snapshot, which is now the last snapshot.

4. Click Close.
The WinA virtual machine is now powered off.

Task 5: Delete a Snapshot


You can delete a single snapshot because each one is independent of the other. Each snapshot refers
to the original vmdk file that is locked (RO) when any snapshot exists. The Delete All option
merges the selected snapshot and deletes all other snapshots, regardless of whether they precede or
follow the selected snapshot.
1. Select the virtual machine for which you took the snapshots.
2. Right-click the virtual machine and select Snapshots >Manage Snapshot.
3. In the Manage VM Snapshots window, select WinASnapshot2 and click Delete.
4. When the confirmation message appears, click Yes to confirm the deletion.

Q1. Do you see the second snapshot in the list of snapshots?


1. No, the second snapshot no longer appears.

5. To delete all the snapshots for this virtual machine, select the first snapshot and click Delete
All.
6. When the confirmation message appears, click Yes to delete all the snapshots.

Q2. Do you see any snapshots in the Snapshot Manager?


2. No, all snapshots were consolidated and the You are here message is under the virtual
machine name.

7. Click Close to exit the Manage VM Snapshots window.

Lab 5 Managing Virtual Machines and Using Snapshots 31


32 Lab 5 Managing Virtual Machines and Using Snapshots
Lab 6 Monitoring Virtual Machine
Performance

Objective: Monitor the resource use of the virtual machine


In this lab, you perform the following tasks:

1. Monitor Resource Use


2. Change the Performance Monitor View

Task 1: Monitor Resource Use


Using VMware vSphere® Web Client, you can monitor virtual machine resources such as CPU,
disk, and memory usage.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
• ESXi host
• Virtual machines for this task
1. Open vSphere Web Client.
2. Point to the Home icon and select vCenter Inventory Lists.
3. In the Navigator pane, click Hosts.
4. Select your VMware ESXi™ host.
5. Click the Related Objects tab.
6. Click the Virtual Machines tab.

33
7. Power on each of your virtual machines for this task. Press Shift and click to select all the
virtual machines and then click the power on icon.
8. Click one of the virtual machines.
9. In the contents pane for the virtual machine, click the Monitor tab.
10. Click the Performance tab.
11. Click Overview on the left side of the contents pane to view the performance charts.
Charts that display performance for CPU, memory, disk, and network appear.
You can unpin the navigation and activity panes to make viewing the charts easier.

Q1. What are the names of the charts for CPU usage?
1. Answers vary.

Q2. What are the names of the charts for memory usage?
2. Answers vary.

Q3. What are the names of the charts for disk usage?
3. Answers vary.

12. On the left side of the contents pane, click Advanced on the Performance tab to view the
advanced performance charts.
13. From the View drop-down menu, select Disk.
14. Point to one of the peaks on the chart.

Q4. What information do you see?


4. Answers vary.

15. From the View drop-down menu, select Memory.


16. Point to one of the peaks on the chart.

Q5. What information appears?


5. Answers vary.

17. From the View drop-down menu, select CPU.


18. Point to one of the peaks on the chart.

Q6. What information appears?


6. Answers vary.

34 Lab 6 Monitoring Virtual Machine Performance


Task 2: Change the Performance Monitor View
You can change the performance monitor view to show the information that you are most interested
in.
1. In the contents pane, click the left-pointing double arrow above Overview.

Q1. What does this action do to the Performance chart view?


1. It hides the Overview and Advanced buttons.

2. Click the right-pointing double arrow above the Performance tab.

Q2. What does this action do to the performance chart view?


2. It restores the Overview and Advanced buttons.

3. Shut down the guest operating system on all powered-on virtual machines for this task. Use a
method of your choice to shutdown the virtual machines.
4. Close the vSphere Web Client session.

Lab 6 Monitoring Virtual Machine Performance 35


36 Lab 6 Monitoring Virtual Machine Performance
Lab 7 Managing Tasks, Events, and
Alarms

Objective: Managing Tasks, Events, and Alarms


In this lab, you perform the following tasks:

Objective: Create and manage tasks, events, and alarms


In this lab, you perform the following tasks:

1. Schedule a Task to Create a Snapshot of a Virtual Machine


2. Create Events or Conditions to Trigger an Alarm
3. Acknowledge a Triggered Alarm

Task 1: Schedule a Task to Create a Snapshot of a Virtual Machine


You create and schedule tasks to take place at a specific time. You can create a snapshot for a virtual
machine by creating a task.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select VMs and Templates.
3. In the Navigator pane, select Student_A-VM03 virtual machine.

37
NOTE
If Student_A-03 virtual machine is not already powered on, power it on now.
4. In the contents pane, click the Manage tab.
5. Click the Scheduled Tasks tab.
The current list of scheduled tasks for the virtual machine appears, if any exist.
6. From the Schedule a New task drop-down menu, select Take Snapshot.
The Take a VM Snapshot for your_virtual_machine (scheduled) wizard starts.
7. On the Edit Settings page, name the snapshot SnpStuA-VM03.
8. Enter a description for the snapshot.
9. Click Scheduling options.
10. In the Task Name box, enter Take VM Snapshot for Student_A-VM03.
11. Enter a description for the task.
12. Under Configured Scheduler, click Change.
13. Click Schedule this action to run later and set the time for 5 minutes from the time displayed
on the clock located in the lower right corner of the student desktop.
14. Click OK and click OK again.
Wait until the scheduled time passes. If the contents pane does not change, refresh your screen.

Q1. How does the contents pane change?


1. The record for the scheduled task shows results of the last run. The chart at the bottom of the
page is populated to show the run history.

Task 2: Create Events or Conditions to Trigger an Alarm


You can create a task to trigger an alarm when a virtual machine is powered off.
1. Point to the Home icon and select Home.
2. In the contents pane, click VMs and Templates.
3. In the Navigator pane, select StudentA_VM03 virtual machine.
4. Right-click the virtual machine and select Power > Power On.
5. Right-click the virtual machine and select Alarms > New Alarm Definition.
The New Alarm Definition wizard starts.
6. On the General page, name the alarm IllegalShutDown_StuA.

38 Lab 7 Managing Tasks, Events, and Alarms


7. (Optional) Enter a description for the alarm definition.
8. In the Monitor for section, click specific event occurring on this object for example VM
Power On and then click Next.
9. Under Trigger if ANY of the following events occur on the Triggers page, click the green plus
sign.
10. From the Event drop-down menu, select VM powered off.
11. Under The following conditions must be satisfied for the trigger to fire, click the green plus
sign.
12. From the Argument drop-down menu, select VM name.
13. In the Value text box, enter Student_A-VM03.

IMPORTANT
Enter the virtual machine name exactly as it appears in the inventory list for this task to be
successful.
14. Click Next.
15. Under Specify the actions to take when the alarm state changes on the Actions page, click the
green plus sign.
16. From the Actions drop-down menu, select Power On VM.
17. Click Finish.
18. Right-click the virtual machine and select Power > Shut Down Guest OS.
19. Click Yes to confirm.
20. In the Recent Tasks pane, verify the powered off status of the virtual machine.
21. Observe the virtual machine name in the inventory.
A red stop sign appears next to the virtual machine name in the inventory.

Task 3: Acknowledge a Triggered Alarm


When an alarm has been triggered, you can acknowledge it and clear it.
1. In the Alarm list, right-click the alarm that you created in task 2 and select Acknowledge.
2. Right-click the alarm and select Reset to green.
3. Click the Manage tab.
4. Click the Alarm Definitions tab.
5. Remove the alarm definition that you created in task 2.

Lab 7 Managing Tasks, Events, and Alarms 39


6. Close the vSphere Web Client session.

40 Lab 7 Managing Tasks, Events, and Alarms


Lab 8 Managing Resource Pools

Objective: Create and verify resource pools on an ESXi


host by using vCenter Server
In this lab, you perform the following tasks:

1. Create Resource Pools


2. Verify Resource Pool Functionality

Task 1: Create Resource Pools


You use resource pools to delegate control over resources of the host or a cluster and to
compartmentalize all resources in a cluster.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select Hosts and Clusters.
3. In the navigator pane, expand the Training data center and select Lab Cluster.
4. In the contents pane, click the Manage tab and select Settings.
5. Expand Services and select vSphere DRS.
6. Click Edit.
7. Select the Turn ON vSphere DRS check box and click OK.
8. In vSphere Web Client, right-click Lab Cluster and select New Resource Pool.

41
9. Assign properties to the resource pool.

Option Action
Name Enter Fin-Test.

CPU Shares Select Low from the drop-


down menu.

All other settings Leave the default settings.

10. Click OK.


11. Right-click Lab Cluster and select New Resource Pool.
12. Assign properties to the resource pool.

Option Action
Name Enter Fin-Prod.

CPU Shares Select High from the drop-


down menu.

All other settings Leave the default settings.

13. Click OK.

42 Lab 8 Managing Resource Pools


Task 2: Verify Resource Pool Functionality
You assign virtual machines to resource pools with different resource settings to monitor and
compare the differences in their performance.
1. Point to the Home icon and select Home.
2. Click vCenter Inventory Lists.
3. Click Resource Pools in the Navigator pane.
4. In the inventory, select the Fin-Test resource pool and click the Summary tab.
5. In the Resource Settings pane, click the arrow next to CPU to expand the view.

Q1. What is the number of shares for this resource pool?


1. 2,000

6. In the inventory, select Fin-Prod and click the Summary tab.


7. View the Resource Settings pane.

Q2. What is the number of shares for this resource pool?


2. 8,000

8. In the inventory, right-click the Fin-Test resource pool and click Edit Resource Settings.
a. From the CPU Shares drop-down menu, select Normal and click OK.
b. In the Resource Settings pane, click the arrow next to CPU to expand the view.
c. Click the Refresh icon.

Q3. What is the number of shares for this resource pool?


3. 4,000

9. Repeat the last step to change CPU shares for the Fin-Prod resource pool from High to Normal.

Q4. What is the number of shares for this resource pool?


4. 4,000

10. Leave vSphere Web Client open for the next lab.

Lab 8 Managing Resource Pools 43


44 Lab 8 Managing Resource Pools
Lab 9 Using vSphere vApps, Managing
Multi-Tiered Applications

Objective: Create and manage a vApp


In this lab, you perform the following tasks:

1. Create a vApp
2. Add a Virtual Machine to a vApp
3. Set the Startup Order of the Virtual Machines in a vApp
4. Power On and Power Off a vApp
5. Clone a vApp

Task 1: Create a vApp


You create vApps in VMware vCenter Server®, where you also edit and manage them.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
1. Open the VMware vSphere® Web Client.
2. Point to the Home icon and select Hosts and Clusters.
3. In the Navigator, right-click Lab Cluster and select Settings.
4. Select vSphere DRS and click Edit.
5. From the vSphere DRS Automation drop-down menu, select Manual.

45
6. Click the arrow next to vSphere DRS Automation to expand the view and move the Migration
Threshold slider to Aggressive on the right.
7. Leave the other settings at their defaults and click OK.
8. In the Navigator pane, right-click Lab Cluster and select New vApp > New vApp.
The New vApp wizard starts.
9. On the Select a creation type page, click Next.
10. On the Select a name and location page, name the vApp vApp_StudentA.
11. Select the Training data center and click Next.
12. On the Resource allocation page, click Next.
13. On the Ready to complete page, click Finish.

Task 2: Add a Virtual Machine to a vApp


You can add individual virtual machines to vApp by dragging them to a vApp.
1. In the Navigator pane, expand LabCluster as needed to select the WinA Windows virtual
machine and drag it to the vApp that you created in task 1.
2. Expand the vApp view in the Navigator pane.
The Windows virtual machine appears in the vApp.
Click the Refresh icon to refresh vSphere Web Client if the virtual machine does not appear in
the vApp.
3. Select the Linux_StuA virtual machine and drag it to the vApp.
The Linux virtual machine appears in the vApp.

Task 3: Set the Startup Order of the Virtual Machines in a vApp


You can configure the settings for a vApp so that the virtual machines in the vApp start in a
predetermined order.
1. If the Linux_StuA and WinA virtual machines are already powered-on, power them off now.
2. Right-click the Linux_StuA virtual machine and select Power > Power On.

Q1. What message appears?


1. Virtual machine Linux_StuA is part of a vApp. To make sure the vApp works correctly, use the
power operations on the vApp instead of the power operations on the individual virtual machines.

3. Click No.
4. In the Navigator pane, select the vApp that you created in task 1.

46 Lab 9 Using vSphere vApps, Managing Multi-Tiered Applications


5. Right-click the vApp and select Edit Settings.
6. Move virtual machines to different startup groups.
a. In the Edit vApp window, click the arrow next to Start Order to show the startup order of
the vApp.
b. If WinA is not listed in group 1, click the up arrow to move the virtual machine to group 1.
c. If Linux_StuA is not listed in group 2, click the up or down arrow to move the virtual
machine to group 2.
7. Under Startup Action, verify that Operation is set to Power On.
8. Click OK.

Task 4: Power On and Power Off a vApp


You power on and power off virtual machines in a vApp by powering on and powering off the vApp
that contains them.
1. Test whether the startup order settings for the vApp are saved.
a. Right-click the vApp that you created in task 1 and select Power > Power On.
b. In the Recent Tasks pane, observe which virtual machine is powered on first.
If the startup order settings are saved, then Win_A starts first.
2. Right-click the vApp and select Power > Power Off.
Wait until the vApp has fully powered on before powering off the vApp. The Power Off option
will remain grayed out until the vApp is fully powered on.
3. Click Yes to confirm.
4. In the Recent Tasks pane, observe which virtual machine is powered off first.
5. Click the Linux machine in the vApp and drag it to your cluster.
6. Refresh vSphere Web Client and verify that the Linux machine has moved to the cluster.
7. Click the relevant Windows machine in the vApp and drag it to your cluster.
8. Refresh vSphere Web Client and verify that the Windows machine has moved to the cluster.
9. Deselect the vSphere DRS check box from the cluster settings.
a. Right click Lab cluster.
b. Click Settings.
c. Under Services, select vSphere DRS and click Edit.
d. Deselect the Turn ON vSphere DRS check box.

Lab 9 Using vSphere vApps, Managing Multi-Tiered Applications 47


Q1. Were you able to turn off vSphere DRS?
1. No, you cannot disable vSphere DRS on a cluster that contains vApps.

e. Click Cancel because you cannot proceed further.

Task 5: Clone a vApp


Just as you can clone a virtual machine, you can clone a vApp.
1. Right click the vApp that you created in task 1.
2. Select Clone > Clone.
3. Select Clone an existing vApp and click Next.
4. In the Select destination page, expand the Training data center and Lab Cluster.
5. Select your VMware ESXi™ host, and click Next.
6. In Select a name and location page, enter vApp_StudentA_Clone.
7. Select the Training data center to deploy the vApp and click Next.
8. In Select storage page, from the Select virtual disk format menu select Thin Provision.
9. Select the shared datastore, and click Next.
10. In the Resource allocation page, click Next.
11. In the Ready to complete page, click Finish.
12. In the Recent tasks pane, check the progress of vApp Cloning process.
a. The cloned vApp should be listed in the Inventory.
13. Remove the original vApp from the Inventory.
a. Right-click the vApp clone you created and select Remove from Inventory.
b. Click Yes to confirm.
14. Remove the vApp clone from the Inventory.
a. Right-click the vApp you created in task 1 and select Remove from Inventory.
b. Click Yes to confirm.
15. In the Navigator pane, right-click Lab Cluster and select Settings.
16. Select vSphere DRS and click Edit.
17. Deselect the Turn ON vSphere DRS check box.
18. Click OK.
19. In the Warning dialog box, click No.
20. Click the Home icon.

48 Lab 9 Using vSphere vApps, Managing Multi-Tiered Applications


Lab 10 Using vSphere vMotion and
Storage vMotion to Migrate Virtual
Machines

Objective: Use vSphere vMotion to migrate a virtual


machine and vSphere Storage vMotion to migrate a virtual
machine datastore
In this lab, you perform the following tasks:

1. Verify that the Virtual Machines Meet the vSphere vMotion Migration Requirements
2. Migrate a Virtual Machine with vSphere vMotion
3. Migrate Virtual Machine Files with vSphere Storage vMotion
4. (Optional) Perform a Cross-Host vSphere Storage vMotion Migration

Task 1: Verify that the Virtual Machines Meet the vSphere vMotion
Migration Requirements
Virtual machines must meet certain requirements before you use VMware vSphere® vMotion® to
migrate them.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select VMs and Templates.

49
3. If the Windows virtual machine, Student_A-VM03, is not powered off, shut down the guest
operating system on the virtual machine.
4. Right-click your Windows virtual machine and select Edit Settings.
5. Verify that Client Device is selected from the CD/DVD Drive 1 drop-down menu and that the
Connect check box is not selected.
6. Verify that Client Device is selected from the Floppy Drive 1 drop-down menu and that the
Connect check box is not selected.
7. Click OK.

Task 2: Migrate a Virtual Machine with vSphere vMotion


You can use vSphere vMotion to migrate a powered-on virtual machine to a different VMware
ESXi™ host.
Use the following information from the class configuration handout:
• Windows virtual machine
• Destination ESXi host
1. Point to the Home icon and select VMs and Templates.
2. Power on the Student_A-VM03 virtual machine.
3. Right-click the Windows virtual machine and select Migrate.
The Migrate Virtual Machine wizard starts.
4. On the Select Migration Type page, click Change Compute Resource Only and click Next.
5. On the Select a compute resource page, select your destination ESXi host and click Next.
The destination should be different than the ESXi host selected in the Power On
recommendation.
You can ignore the No guest OS heartbeats are being received warning. Causes include
incorrectly configured VMware Tools™ or by a virtual machine that have been moved recently.
This is a known vSphere behavior.
6. On the Select network page, click Next.
7. On the Select vMotion priority page, click Next.
8. On the Ready to complete page, click Finish.
9. In the Recent Tasks pane, monitor the progress of the virtual machine migration.
10. Verify that your virtual machine appears on the destination ESXi host.
a. In the Navigator pane, click the Hosts and Clusters icon at the top of the column.

50 Lab 10 Using vSphere vMotion and Storage vMotion to Migrate Virtual Machines
b. Select your destination ESXi host.
c. Click the Related Objects tab.
d. Click the Virtual Machines tab.
e. Verify that the Windows virtual machine is visible in the list of virtual machine names on
the destination ESXi host.

Task 3: Migrate Virtual Machine Files with vSphere Storage vMotion


You can use VMware vSphere® Storage vMotion® to migrate a virtual machine’s files from one
datastore to another.
Use the following information from the class configuration handout:
• Linux virtual machine
• Destination datastore
1. Point to the Home icon and select Home.
2. In the contents pane, select VMs and Templates.
3. Select your Linux virtual machine.
4. In the contents pane, click the Related Objects tab.
5. Click the Datastores tab.

Q1. Which datastore are your virtual machine’s files located on?
1. The files are stored on the Shared1 local datastore.

6. If it is not already on, power on the Linux virtual machine.


7. Right-click your Linux virtual machine and select Migrate.
The Migrate Virtual Machine wizard starts.
8. On the Select Migration Type page, click Change storage only and then click Next.
9. Select your destination datastore and click Next.
10. From the Select virtual disk format menu on the Select Datastore page, select Same format
as source.
11. On the Ready to complete page, click Finish.
12. Monitor the progress of the task in the Recent Tasks pane.
13. After the task is finished, click the Related Objects tab of the virtual machine.
14. Verify that the virtual machine is on the new datastore.

Lab 10 Using vSphere vMotion and Storage vMotion to Migrate Virtual Machines 51
15. Close all virtual machine consoles if any are open.
16. Power off all virtual machines.
17. Close vSphere Web Client.

Task 4: (Optional) Perform a Cross-Host vSphere Storage vMotion


Migration
You can use a cross-host migration in vSphere Storage vMotion to change both the ESXi host and
the datastore location for a virtual machine in the same operation.
1. Identify a virtual machine that meets the requirements for performing a cross-host vSphere
Storage vMotion migration.
Your course lecture book can help you verify the requirements.
2. Identify a datastore that contains enough free space to receive the virtual machine.
3. Perform the cross-host vSphere Storage vMotion migration of the virtual machine to the other
ESXi host in your lab environment.
4. Monitor the progress of the migration until it is completed.

52 Lab 10 Using vSphere vMotion and Storage vMotion to Migrate Virtual Machines
Lab 11 Implementing a vSphere DRS
Cluster

Objective: Implement a vSphere DRS cluster


In this lab, you perform the following tasks:

1. Create a Load Imbalance


2. Create a vSphere DRS Cluster
3. Verify Proper vSphere DRS Cluster Functionality

Task 1: Create a Load Imbalance


You create a load imbalance across the VMware ESXi™ hosts in the Lab Cluster cluster to test how
VMware vSphere® Distributed Resource Scheduler™ works.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• Virtual machine administrator password
• Virtual machine with cpubusy to clone
• Password for virtual machines with cpubusy
• Names for cpubusy virtual machine clones
• Shared datastore for cloning
• ESXi host
This lab requires three Windows virtual machines with cpubusy. One exists. You create two more
virtual machines by cloning the original virtual machine with cpubusy installed.

53
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select VMs and Templates.
3. If necessary, expand the elements in the Navigator pane until virtual machines and templates are
visible.
4. Right-click the virtual machine designated to clone and select Clone > Clone to Virtual
Machine.
The Clone Existing Virtual Machine wizard starts.
5. On the Select a name and folder page, name the virtual machine with a designated cpubusy
clone name.
6. Select Training as the location for the virtual machine and click Next.
7. On the Select a compute resource page, select the ESXi host designated for this lab and click
Next.
• You might have to expand Lab Cluster cluster under Training to see your host.
8. On the Select storage page, select Thin Provision from the Select virtual disk format menu,
then select the Shared1 datastore and click Next.
9. On the Select clone options page, select the Customize the operating system check box and
the Power on this virtual machine after creation check box and click Next.
10. On the Customize guest operating system page, select the guest customization specification
created in lab 3 and click Next.
11. On the Ready to Complete page, click Finish.
12. Repeat steps 3 to 10 for the second clone virtual machine, using the unused virtual machine
clone name.
13. Monitor the progress in the Recent Tasks pane.

IMPORTANT
Ensure that you use only these virtual machines because these systems have cpubusy loaded
onto the local desktop. Also, check that all three VMs have their file formats set to Thin
Provisioned and that they are located on the Shared datastore. Otherwise, you will not be able to
complete the tasks in this lab successfully.
14. If required, migrate the three virtual machines used for this lab to the lab designated host.
15. Power on all three of the virtual machines.
16. Start an instance of cpubusy.vbs on each of the virtual machines.

54 Lab 11 Implementing a vSphere DRS Cluster


a. In the left pane, select a virtual machine.
b. In the center pane, click Launch Remote Console on the Summary tab.
c. Log in to the virtual machine as the administrator with the password.
d. Right-click the cpubusy.vbs script on each virtual machine’s desktop and select Open
with Command Prompt.
All three virtual machines must be running cpubusy.vbs to cause vSphere DRS to
migrate virtual machines to another host.

Task 2: Create a vSphere DRS Cluster


You create a vSphere DRS cluster to balance the computing capacity among all ESXi hosts and
associated virtual machines without service interruption.
1. On the vSphere Web Client Home page, click Hosts and Clusters and expand the view of the
inventory.
2. In the inventory, right-click the Lab Cluster cluster and select Settings.
3. Select vSphere DRS and click Edit.
4. Select the Turn ON vSphere DRS check box.
5. From the vSphere DRS Automation drop-down menu, select Partially Automated.
6. Click the arrow next to vSphere DRS Automation to expand the view and move the Migration
Threshold slider to Aggressive on the right.
7. Leave other settings at their defaults and click OK.

Task 3: Verify Proper vSphere DRS Cluster Functionality


You can run vSphere DRS in either automatic mode or manual mode. In manual mode, you review
the recommendations for optimal virtual machine placement provided by vSphere DRS and decide
whether to make the changes.
1. In the inventory, click Lab Cluster and then click the Monitor tab.
2. Click the vSphere DRS tab.
3. Click Run vSphere DRS Now.
Clicking the button forces vSphere DRS to immediately evaluate the cluster and provide
recommendations instead of waiting the standard 5 minutes before generating
recommendations.
4. Click the Summary tab and click the arrow next to vSphere DRS to expand the pane.

Lab 11 Implementing a vSphere DRS Cluster 55


Q1. Does the gauge show that the load is imbalanced?
1. Yes, because all the virtual machines are running on a single host and the running cpubusy.vbs
instances create a large CPU load.

5. Click the Monitor tab and click the vSphere DRS tab.
6. Click CPU Utilization.
7. In the Sum of Virtual Machine CPU Utilization - Per Host pane, view the CPU consumption on
each ESXi host and click each of the colored boxes to view the CPU consumption of each
virtual machine.
8. Click Recommendations in the middle pane and view the vSphere DRS recommendations.
9. If new recommendations do not appear, click Run DRS Now again.
10. Click Apply Recommendations.
11. If your recommendations have expired, click Run DRS Now to generate new recommendations
and apply them.
12. Click the Tasks tab.
13. Click the Expand All icon.
14. Monitor the Migrate virtual machine subtask under Apply recommendation until completion.
15. Click the vSphere DRS tab and click the Run vSphere DRS Now tab to force vSphere DRS to
evaluate the cluster status.

Q2. Is any recommendation shown?


2. No, because all recommendations are applied.

16. Click the Summary tab and view the vSphere DRS pane.

Q3. Does the gauge show that the load is balanced?


3. Whether the gauge shows that the load is balanced or not depends on your lab environment.
Even if the cluster is still imbalanced, it is more balanced than it was before the recommendations
were applied. vSphere DRS improved the resource allocation for the virtual machines in the
cluster.

17. Click the Monitor tab and click the vSphere DRS tab.
18. Select CPU Utilization.
The virtual machines should spread across the two ESXi hosts. You can refresh the screen to see
the result.
19. Open the remote console for each virtual machine running cpubusy.
20. In the command prompt window, type Ctrl+C to stop cpubusy, then close the command
prompt window.

56 Lab 11 Implementing a vSphere DRS Cluster


21. Close the Remote console of all three virtual machines.
22. In the Navigator pane, point to Power and click Shut Down Guest OS for each of the running
virtual machines.
23. Click Yes to confirm.
24. Point to the Home icon and select Home.
25. Close the vSphere Web Console, then log out of your student desktop to complete this lab.

Lab 11 Implementing a vSphere DRS Cluster 57


58 Lab 11 Implementing a vSphere DRS Cluster
Lab 12 Using vSphere HA

Objective: Demonstrate vSphere HA functionality


In this lab, you perform the following tasks:

1. Create a Cluster Enabled for vSphere HA


2. Inspect the HA Cluster Configuration
3. Test vSphere HA Functionality
4. View the vSphere HA Cluster Resource Usage

Task 1: Create a Cluster Enabled for vSphere HA


You create a VMware vSphere® High Availability cluster to group multiple VMware ESXi™ hosts
together, to achieve higher levels of virtual machine availability than each ESXi host can provide
individually.
Students perform the steps in this task individually.
Use the following information from the class configuration handout:
• vCenter Server Appliance name
• vCenter Server Appliance administrator password
1. Open VMware vSphere® Web Client.
2. Point to the Home icon and select Hosts and Clusters.
3. Right-click Lab Cluster and select Settings.
4. In the contents pane, select vSphere HA and click Edit.
5. Select the Turn ON vSphere HA check box.
6. Expand Admission Control.

59
7. Select Define failover capacity by reserving a percentage of the cluster resources.
8. Leave the default settings for the other options and click OK.
9. In the Recent Tasks pane, monitor the progress as the cluster is created.
10. Power on all your virtual machines.

Task 2: Inspect the HA Cluster Configuration


You examine the cluster components and correct configuration issues.
1. In vSphere Web Client, point to Home and select Hosts and Clusters.
2. In the inventory, click Lab Cluster.
3. Click the Monitor tab.
4. Click the vSphere HA tab.
The vSphere HA summary information appears.
5. Notice the name of the master host and record the name of the other host (the slave host).
__________
6. Review the content and record the slave host. __________
It might take a few minutes for the vSphere Web Client to fully update.

Q1. Does the number of protected virtual machines match the number of virtual
machines in the cluster?
1. Yes, if both hosts are added to the cluster and all virtual machines on the hosts are powered
on.

7. Click Heartbeat.

Q2. How many datastores are used for heartbeating?


2. One, only the Shared1 datastore appears in the heartbeat as this is the only datastore
accessible to all hosts in the cluster.

8. Click Configuration Issues and review the errors that are listed.

60 Lab 12 Using vSphere HA


At this point, each ESXi host has a single management network port for redundancy. vSphere
HA still works if an ESXi host is configured with one management network port, but a second
management network port is necessary for redundancy.

9. In the Entity list, select esxi01.vclass.local.


10. In the contents pane, click the Manage tab, and click the Networking tab.
11. Click VMKernel Adapters and then click vMotion in the VMkernel adapter list.
12. Click the Edit Settings icon.

13. On the Port properties page, select the Management Traffic check box and click OK.
14. In the Navigator pane, right-click esxi01.vclass.local and select Reconfigure for vSphere HA.
15. In the Navigator pane, click Lab Cluster in the inventory to return to the cluster monitoring
page.
16. In the Entity list, select esxi02.vclass.local.
17. Repeat steps 7 to 14.
18. In the inventory, click Lab Clusters.

Q3. Did the previous management configuration error disappear?


3. Yes, the error management error message disappeared.

Task 3: Test vSphere HA Functionality


You set up vSphere HA to monitor the data center environment and detect hardware and guest
operating system failures. When an ESXi host outage is detected, vSphere HA automatically restarts
virtual machines on other ESXi hosts in the cluster.
1. In the inventory, select the slave ESXi host that you recorded in task 2, step 4.

Lab 12 Using vSphere HA 61


2. Click the Related Objects tab and click the Virtual Machines tab.
3. Record the name of one or more powered-on virtual machines on the slave host. __________
4. Simulate a host failure by rebooting one of the hosts in the cluster.
You must reboot the system and not shut it down.
a. Right-click the slave ESXi host and select Power > Reboot.
A warning message appears stating that you chose to reboot the host, which is not in
maintenance mode.
b. Enter Testing vSphere HA as the reason for rebooting and click OK.
5. In the inventory, click Lab Cluster.
6. Click the Monitor tab.
7. Click the Events tab.
The cluster entries are sorted by time. Notice the entries that appear when the host failure is
detected.
The initial messages from the hosts might show failures. These messages indicate that the
virtual machines on the downed host have failed. The virtual machines take 1 to 2 minutes to
successfully migrate to the new host.
The screenshot shows a list of recent events in the cluster.

8. In the inventory, select the ESXi host that is not rebooting.


9. Click the Related Objects tab and click the Virtual Machines tab.

Q1. Do you see the virtual machines that were running on the original slave ESXi host,
which you recorded in task 3, step 3?
1. Yes, the virtual machines previously running on the original slave ESXi host are running on the
remaining host in the cluster.

10. In the inventory, click Lab Cluster and then click the Monitor tab.

62 Lab 12 Using vSphere HA


11. Click the Sphere HA tab.
12. Monitor the original master ESXi host inventory until it is fully running again.
13. Click Summary in the middle pane.

Q2. Has the master host changed?


2. No. The master host role has not changed.

Lab 12 Using vSphere HA 63


Task 4: View the vSphere HA Cluster Resource Usage
You examine the CPU, memory, and storage I/O resource usage information of the cluster.
Do this task as a team. Student B should do the steps in this task.
1. On the vSphere Web Client Home page, click Hosts and Clusters and expand the view of the
inventory.
2. In the inventory, click Lab Cluster.
3. Click the Monitor tab.
4. Click the Resource Reservation tab.
5. Click CPU and record the information for the cluster.
• Total Reservation Capacity (GHz) __________
• Used Reservation (GHz) __________
• Available Reservation (GHz) __________
6. In the virtual machines pane, verify that the CPU reservation is not set on the virtual machines.
The Reservation column shows 0 (MHz).

7. Select Memory and record the information for the cluster.


• Total Reservation Capacity (GB) __________
• Used Reservation (GB) __________
• Available Reservation (GB) __________
8. In the virtual machines pane below, verify that the memory reservation is not set on the virtual
machines.
The Reservation column shows 0 (MB).

64 Lab 12 Using vSphere HA


Answer Key

Lab 1: Using vSphere Web Client


Task 1: Navigate vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1. vCenter Home, Virtual Machines, vApps, VM 7. One: Linux_StuA.
Templates in Folders, Content Libraries, and 8. This view shows the virtual machines
various Resources configured to use the Shared1 datastore as
2. Two storage.
3. Two: Win_StuA and Linux_StuA 9. Two: Win_StuA and Linux_StuA
4. Answers vary. 10. All virtual machines configured on the vCenter
5. One: Win_StuA. Server Appliance appear, including virtual
6. This view shows the virtual machines machines from all hosts and all datastores.
configured to use this datastore as storage.
The other view showed all virtual machines
configured on the ESXi host.
Task 2: Pin and Unpin Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
1. The Navigator pane expands when you click 2. The Recent Task pane expands.
on it. When you click outside the pane, the
Navigator pane collapses and minimizes to
the left.
Task 3: Hide the Getting Started Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
1. The Getting Started tab does not appear. 2. Summary, Monitor, Manage, and Related
Objects
Task 4: Perform Search Operations with vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . .5
1. The Linux virtual machines configured on the
vCenter Server Appliance are listed.

Lab 4: Modifying Virtual Machine Settings


Task 1: Upgrade the Virtual Machine Hardware Version . . . . . . . . . . . . . . . . . . . . . . . . . .21
1. ESXi 5.5 and later (virtual machine version 2. ESXi 6.0 and later (virtual machine version
10) 11)

65
Task 2: Configure the Virtual Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
1. No, the text box is dimmed. 3. Answers vary.
2. Yes, the text box can now be edited.
Task 4: Restrict the Number of Users Accessing the Virtual Machines . . . . . . . . . . . . . . .24
1. No, you cannot open a third console. 2. Unable to connect to the MKS: Console
access to the virtual machine cannot be
granted because the connection limit of 2 has
been reached.

Lab 5: Managing Virtual Machines and Using Snapshots


Task 3: Create a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
1. The Snapshot of the virtual machine’s VMware Tools installed) check boxes were
memory and Quiesce guest file system (with available.
Task 4: Revert to a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
1. Under the fourth snapshot, which is the last 2. Under the third snapshot, which is now the
snapshot. last snapshot.
Task 5: Delete a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
1. No, the second snapshot no longer appears. 2. No, all snapshots were consolidated and the
You are here message is under the virtual
machine name.

Lab 6: Monitoring Virtual Machine Performance


Task 1: Monitor Resource Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
1. Answers vary. 4. Answers vary.
2. Answers vary. 5. Answers vary.
3. Answers vary. 6. Answers vary.
Task 2: Change the Performance Monitor View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
1. It hides the Overview and Advanced buttons. 2. It restores the Overview and Advanced
buttons.

Lab 7: Managing Tasks, Events, and Alarms


Task 1: Schedule a Task to Create a Snapshot of a Virtual Machine . . . . . . . . . . . . . . . . .37
1. The record for the scheduled task shows of the page is populated to show the run
results of the last run. The chart at the bottom history.

Lab 8: Managing Resource Pools


Task 2: Verify Resource Pool Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
1. 2,000
2. 8,000
3. 4,000
4. 4,000

66 Answer Key
Lab 9: Using vSphere vApps, Managing Multi-Tiered Applications
Task 3: Set the Startup Order of the Virtual Machines in a vApp . . . . . . . . . . . . . . . . . . . .46
1. Virtual machine Linux_StuA is part of a vApp.
To make sure the vApp works correctly, use
the power operations on the vApp instead of
the power operations on the individual virtual
machines.
Task 4: Power On and Power Off a vApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
1. No, you cannot disable vSphere DRS on a
cluster that contains vApps.

Lab 10: Using vSphere vMotion and Storage vMotion to Migrate Virtual
Machines
Task 3: Migrate Virtual Machine Files with vSphere Storage vMotion . . . . . . . . . . . . . . . .51
1. The files are stored on the Shared1 local
datastore.

Lab 11: Implementing a vSphere DRS Cluster


Task 3: Verify Proper vSphere DRS Cluster Functionality . . . . . . . . . . . . . . . . . . . . . . . . .55
1. Yes, because all the virtual machines are 3. Whether the gauge shows that the load is
running on a single host and the running balanced or not depends on your lab
cpubusy.vbs instances create a large CPU environment. Even if the cluster is still
load. imbalanced, it is more balanced than it was
2. No, because all recommendations are before the recommendations were applied.
applied. vSphere DRS improved the resource
allocation for the virtual machines in the
cluster.

Lab 12: Using vSphere HA


Task 2: Inspect the HA Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
1. Yes, if both hosts are added to the cluster and 2. One, only the Shared1 datastore appears in
all virtual machines on the hosts are powered the heartbeat as this is the only datastore
on. accessible to all hosts in the cluster.
3. Yes, the error management error message
disappeared.
Task 3: Test vSphere HA Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
1. Yes, the virtual machines previously running 2. No. The master host role has not changed.
on the original slave ESXi host are running on
the remaining host in the cluster.

Answer Key 67
68 Answer Key

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy