Lab Manual
Lab Manual
Lab Manual
Manage
Lab Manual
ESXi 7 and vCenter Server 7
Copyright © 2021 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. VMware vSphere®
vMotion®, VMware vSphere® Storage vMotion®, VMware vSphere® Lifecycle Manager™,
VMware vSphere® High Availability, VMware vSphere® Enterprise Plus Edition™, VMware
vSphere® ESXi™ Shell, VMware vSphere® Client™, VMware vSphere®, VMware vSAN™,
VMware vCenter® Server Appliance™, VMware vCenter Server®, VMware View®, VMware
Horizon® View™, Not a trademarked name, VMware Verify™, VMware Host Client™, Project
Photon OS™, VMware Photon™, VMware Pivotal Labs® Navigator™, VMware ESXi™ and
VMware ESX® are registered trademarks or trademarks of VMware, Inc. in the United States
and/or other jurisdictions.
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 material is designed to be used for reference purposes in
conjunction with a 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
Typographical Conventions
• <ESXi_host_name>
www.vmware.com/education
www.vmware.com/education
Contents
v
Task 2: Add ESXi Hosts to the Inventory ............................................................................................................. 22
Task 3: View Information About the ESXi Hosts ............................................................................................... 23
Task 4: Configure the ESXi Hosts as NTP Clients ............................................................................................. 23
Task 5: Create a Folder for the ESXi Hosts ......................................................................................................... 24
Task 6: Create Folders for VMs and VM Templates ......................................................................................... 24
Lab 8 Configuring Active Directory: Joining a Domain ..................................................27
Task 1: Join vCenter Server to the vclass.local Domain ...................................................................................27
Lab 9 Configuring Active Directory: Adding an Identity Source ............................... 29
Task 1: Add vclass.local as an Identity Source..................................................................................................... 29
Lab 10 Users, Groups, and Permissions ................................................................................ 31
Task 1: View Active Directory Users........................................................................................................................ 31
Task 2: Assign Object Permission to an Active Directory User ................................................................... 32
Task 3: Assign Root-Level Global Permission to an Active Directory User ............................................ 32
Task 4: Log In as an Active Directory User ......................................................................................................... 33
Task 5: Use an Active Directory User to Create a Virtual Machine ............................................................ 33
Lab 11 Using Standard Switches ............................................................................................. 35
Task 1: View the Standard Switch Configuration ................................................................................................ 35
Task 2: Create a Standard Switch with a Virtual Machine Port Group ....................................................... 36
Task 3: Attach Virtual Machines to the Virtual Machine Port Group ........................................................... 36
Lab 12 Accessing iSCSI Storage ............................................................................................. 39
Task 1: View an Existing ESXi Host iSCSI Configuration .................................................................................. 39
Task 2: Add a VMkernel Port Group to a Standard Switch ............................................................................ 41
Task 3: Add the iSCSI Software Adapter to an ESXi Host ............................................................................. 41
Task 4: Connect the iSCSI Software Adapters to Storage ........................................................................... 42
Lab 13 Managing VMFS Datastores ...................................................................................... 43
Task 1: Create VMFS Datastores for the ESXi Host ......................................................................................... 43
Task 2: Expand a VMFS Datastore to Consume Unused Space on a LUN ............................................. 45
Task 3: Remove a VMFS Datastore........................................................................................................................ 45
Task 4: Extend a VMFS Datastore .......................................................................................................................... 46
Task 5: Create a Second VMFS Datastore .......................................................................................................... 47
Lab 14 Accessing NFS Storage .............................................................................................. 49
Task 1: Configure Access to an NFS Datastore ................................................................................................. 49
Task 2: View NFS Storage Information.................................................................................................................. 50
vi
Lab 15 Using a vSAN Datastore .............................................................................................. 51
Task 1: View a vSAN Datastore Configuration..................................................................................................... 51
Task 2: View the vSAN Default Storage Policy ................................................................................................. 53
Task 3: View a Virtual Machine on the vSAN Datastore ................................................................................. 54
Lab 16 Using VM Templates: Creating Templates and Deploying VMs .................. 55
Task 1: Create a Virtual Machine Template ........................................................................................................... 55
Task 2: Create Customization Specifications ....................................................................................................... 56
Task 3: Deploy Virtual Machines from a Template .............................................................................................57
Lab 17 Using Content Libraries................................................................................................ 59
Task 1: Create a Content Library .............................................................................................................................. 59
Task 2: Clone a VM Template to a Template in a Content Library ............................................................. 60
Task 3: Deploy a VM from a VM Template in the Content Library ............................................................. 60
Lab 18 Modifying Virtual Machines ........................................................................................ 63
Task 1: Adjust Memory Allocation on a Virtual Machine .................................................................................. 63
Task 2: Increase the Size of a VMDK File.............................................................................................................. 64
Task 3: Rename a Virtual Machine in the vCenter Server Inventory .......................................................... 65
Lab 19 vSphere vMotion Migrations ...................................................................................... 67
Task 1: Configure vSphere vMotion Networking on sa-esxi-01.vclass.local ............................................. 67
Task 2: Configure vSphere vMotion Networking on sa-esxi-02.vclass.local ........................................... 68
Task 3: Prepare Virtual Machines for vSphere vMotion Migration ............................................................... 69
Task 4: Migrate Virtual Machines Using vSphere vMotion ................................................................................71
Lab 20 vSphere Storage vMotion Migrations ....................................................................73
Task 1: Migrate Virtual Machine Files from Local Storage to Shared Storage .........................................73
Task 2: Migrate Both the Compute Resource and Storage of a Virtual Machine .................................. 74
Lab 21 Working with Snapshots ..............................................................................................75
Task 1: Take Snapshots of a Virtual Machine ........................................................................................................75
Task 2: Add Files and Take Another Snapshot of a Virtual Machine.......................................................... 76
Task 3: Revert the Virtual Machine to a Snapshot ..............................................................................................77
Task 4: Delete an Individual Snapshot .................................................................................................................... 79
Task 5: Delete All Snapshots ..................................................................................................................................... 79
Lab 22 Controlling VM Resources .......................................................................................... 81
Task 1: Create CPU Contention ................................................................................................................................. 81
Task 2: Verify CPU Share Functionality ................................................................................................................. 83
vii
Lab 23 Monitoring Virtual Machine Performance ............................................................ 85
Task 1: Create a CPU Workload ............................................................................................................................... 85
Task 2: Use Performance Charts to Monitor CPU Use .................................................................................... 86
Task 3: Remove CPU Affinity and Change CPU Shares to Normal ............................................................ 87
Lab 24 Using Alarms ................................................................................................................... 89
Task 1: Create a Virtual Machine Alarm to Monitor a Condition .................................................................... 89
Task 2: Trigger the Virtual Machine Alarm ............................................................................................................. 91
Task 3: Create a Virtual Machine Alarm to Monitor an Event ........................................................................ 92
Task 4: Trigger the Virtual Machine Alarm ............................................................................................................ 94
Task 5: Deactivate Virtual Machine Alarms .......................................................................................................... 95
Lab 25 Implementing vSphere DRS Clusters .................................................................... 97
Task 1: Create a Cluster That Is Configured for vSphere DRS ..................................................................... 97
Task 2: Modify vSphere DRS Settings ................................................................................................................... 98
Task 3: Add ESXi Hosts to the Cluster .................................................................................................................. 98
Task 4: Verify vSphere vMotion Configuration on the ESXi Hosts ............................................................. 99
Task 5: Create a Load Imbalance ............................................................................................................................. 99
Task 6: Verify Proper vSphere DRS Cluster Functionality ........................................................................... 100
Lab 26 Using vSphere HA ...................................................................................................... 103
Task 1: Configure vSphere HA in a Cluster ......................................................................................................... 103
Task 2: View Information About the vSphere HA Cluster............................................................................ 104
Task 3: Configure Network Management Redundancy ................................................................................. 104
Task 4: Test the vSphere HA Functionality ....................................................................................................... 105
Task 5: View the vSphere HA Cluster Resource Usage ................................................................................107
Task 6: Configure the Percentage of Resource Degradation to Tolerate ..............................................107
Lab 27 Using vSphere Lifecycle Manager ........................................................................ 109
Task 1: Import Update Files to the Image Depot.............................................................................................. 109
Task 2: Create a Cluster with vSphere Lifecycle Manager Activated ........................................................ 111
Task 3: Add ESXi Hosts to the Cluster .................................................................................................................. 112
Task 4: Update ESXi Hosts Using the Cluster Image .......................................................................................114
Answer Key .................................................................................................................................... 117
viii
Lab 1 Accessing the Lab Environment
1. Verify that you are successfully logged into the student desktop.
NOTE
1
Task 2: Log In to an ESXi Host with VMware Host Client
You log in to the sa-esxi-01.vclass.local ESXi host as user root to familiarize yourself with the
VMware Host Client UI.
1. From your student desktop Student-a-01, log in to SA-ESXi-01 as root using VMware Host
Client.
b. From the bookmarks toolbar, select vSphere Site-A > Host Client (SA-ESXi-01).
c. To log in, enter root for the user name and VMware1! for the password.
VMware Host Client opens with Host selected in the left pane, also called the Navigator
pane.
2. Explore the user interface by clicking objects in the Navigator pane and viewing information
about them in the right pane.
Q1. How many CPUs and how much memory does this ESXi host have?
A1. This ESXi host has 2 CPUs and 8 GB of memory.
Q4. What are the guest operating system types for the virtual machines on this
host?
A4. Microsoft Windows 10 and VMware Photon OS.
2
3. Log out of VMware Host Client.
a. From the bookmarks toolbar, select vSphere Site-A > vSphere Client (SA-VCSA-01).
2. On the Home page, select SA-VCSA-01.VCLASS.LOCAL from the drop-down menu at the
top.
This page provides information about the vCenter Server instance that you are logged into,
such as the total CPU, memory, and storage available.
The Hosts and Clusters inventory appears in the left pane, also called the navigation pane.
3
4. View the navigation pane.
The navigation pane lists the vCenter Server inventory for sa-vcsa-01.vclass.local.
You might have to expand the items in the inventory to view all the objects.
4
Lab 2 Configuring an ESXi Host
1. From your student desktop Student-a-01, log in to sa-esxi-01 as root using VMware Host Client.
a. Click the Firefox icon on the taskbar of your student desktop.
b. From the bookmarks toolbar, select vSphere Site-A > Host Client (SA-ESXi-01).
c. Log in by entering root for the user name and VMware1! for the password.
VMware Host Client opens with Host selected in the Navigator pane.
5
Task 2: Log In to the ESXi Host as an Active Directory User
You verify that you can log in to sa-esxi-01.vclass.local as the Active Directory user
esxadmin@vclass.local.
2. To log back in, enter esxadmin for the user name and VMware1! for the password.
By default, any user that is a member of the ESX Admins domain group has full
administrative access to ESXi hosts that join the domain.
IMPORTANT
In a production environment, keep SSH and vSphere ESXi Shell services deactivated.
Activate these services only if you must access the command line to troubleshoot problems.
When you finish troubleshooting, deactivate these services.
3. Scroll down the list of services to find the vSphere ESXi Shell and SSH services.
vSphere ESXi Shell is the Tech Support Mode (TSM) service, and SSH is the TSM-SSH
service. Both of these services are stopped.
6. Verify that the TSM and TSM-SSH services have a status of Running.
6
Lab 3 Creating a Virtual Machine
1. From your student desktop Student-a-01, log in to SA-ESXi-01 as root using VMware Host
Client.
a. Click the Firefox icon from the taskbar of your student desktop.
b. From the bookmarks toolbar, select vSphere Site-A > Host Client (SA-ESXi-01).
c. Log in by entering root for the user name and VMware1! for the password.
4. On the Select creation type page, verify that Create a new virtual machine is selected and
click Next.
7
5. On the Select a name and guest OS page, configure settings for your virtual machine.
Option Action
Compatibility Select ESXi 7.0 virtual machine from the drop-down menu.
Guest OS version Select Microsoft Windows 10 (64-bit) from the drop-down menu.
Click Next.
6. On the Select storage page, select the ICM-Datastore datastore and click Next.
Option Action
b. Find CD/DVD Drive 1 and select Datastore ISO file from the drop-down menu.
d. From ICM-Datastore, click the ISO folder and select the Windows 10 operating system
ISO image: en_windows_10_enterprise_ltsc_2019_x64_dvd_5795bb03.iso.
e. Click Select.
g. Verify that the Connect at power on check box is selected and click Next.
8
8. On the Ready to complete page, review the information and click Finish.
9. In the Navigator pane, select Virtual Machines and verify that your newly created VM
appears in the right pane.
10. Click the Win10-Empty virtual machine name in the right pane.
You must click the name of the VM, not just the row, to view information about the VM.
11. Review the settings under General Information, Hardware Configuration, and Resource
Consumption.
12. In the Hardware Configuration pane, expand Hard disk 1 and record the configuration
information.
• Backing __________
• Capacity __________
NOTE
In a production environment, the next step is to install an operating system in the new VM.
However, to save class and lab time, you do not install the guest operating system.
1. In the Navigator pane, right-click the Win10-Empty virtual machine and select Delete.
3. Verify that the Win10-Empty VM does not appear in the Navigator pane and the right pane.
9
10
Lab 4 Installing VMware Tools
1. From your student desktop Student-a-01, log in to SA-ESXi-01 as root using VMware Host
Client.
a. Click the Firefox icon from the taskbar of your student desktop.
b. From the bookmarks toolbar, select vSphere Site-A > Host Client (SA-ESXi-01).
c. To log in, enter root for the user name and VMware1! for the password.
3. In the right pane, right-click the Win10-Tools virtual machine and select Power > Power on.
4. When the Win10-Tools virtual machine icon shows that the VM is powered on, right-click
Win10-Tools and select Console > Open console in new tab.
5. Verify that the VM starts successfully and that you are automatically logged in to Win10-
Tools as vclass\administrator.
11
Task 2: Install VMware Tools
You install VMware Tools in the Win10-Tools VM to improve the overall performance of this VM.
NOTE
You perform the installation using the keyboard because mouse performance is suboptimal
without VMware Tools. After VMware Tools is installed in the Win10-Tools VM, mouse
performance improves substantially.
2. In the right pane, right-click Win10-Tools and select Guest OS > Install VMware Tools.
The VMware Tools ISO image is mounted on the CD/DVD drive of the Win10-Tools VM.
4. Right-click the Win10-Tools Console tab and select Reload Tab from the drop-down menu.
5. Click anywhere in the console window and press the Tab key to select the Windows Start
icon in the lower left corner of the Win10-Tools desktop.
12
7. Enter D:\ and press Enter.
a. On the Welcome to the installation wizard for VMware Tools page, press Enter to select
Next.
d. On the Ready to Install VMware Tools page, press Enter to select Install.
a. Using your mouse, navigate to the Windows system tray in the lower right to show
hidden icons.
The window shows the version of VMware Tools and indicates that the VMware Tools
service is running.
13
10. Verify that mouse performance is acceptable.
a. In the right pane of VMware Host Client, right-click Win10-Tools and select Power >
Power off.
c. Verify that the Win10-Tools VM icon indicates that the VM is powered off.
14
Lab 5 Adding Virtual Hardware
1. From your student desktop, log in to SA-ESXi-01 as root using VMware Host Client.
a. Click the Firefox icon from the taskbar of your student desktop.
b. From the bookmarks toolbar, select vSphere Site-A > Host Client (SA-ESXi-01).
c. To log in, enter root for the user name and VMware1! for the password.
a. In the right pane, right-click Photon-HW and select Power > Power on.
5. Minimize the Recent tasks pane by clicking the Minimize icon in the top-right corner of the
Recent tasks pane.
15
6. Review the Hardware Configuration pane for the virtual machine.
2. Click Add hard disk and select New standard hard disk.
3. For the new hard disk, change the disk size and disk provisioning type.
6. Expand the second new hard disk, change the disk size and disk provisioning type.
7. Click Save.
8. In the Hardware Configuration pane, verify that Hard disk 2 is a 1 GB, thin-provisioned disk,
and that Hard disk 3 is a 1 GB, thick-provisioned disk.
16
Task 3: Compare Thin-Provisioned and Thick-Provisioned Disks
You view and compare thin-provisioned and thick-provisioned virtual disk files.
Being aware of the differences between these two disk types is useful for planning your storage
needs and also for troubleshooting storage problems.
1. In the Hardware Configuration pane, view the details for Hard disk 2 and Hard disk 3.
Q1. What is the name of the virtual disk file for Hard disk 2?
A1. Photon-HW_1.vmdk
Q2. What is the name of the virtual disk file for Hard disk 3?
A2. Photon-HW_2.vmdk
Q3. On what datastore are Hard disk 2 and Hard disk 3 located?
A3. ICM-Datastore
2. Verify the size of the Hard disk 2 and Hard disk 3 virtual disk files.
The Datastores tab appears in the right pane and ICM-Datastore appears in the list.
c. In the Datastore browser window, select the Photon-HW folder and select Photon-
HW_1.vmdk.
The thin-provisioned disk uses only as much datastore space as the disk needs, in this
case, 0 bytes. The thick-provisioned disk has all its space (1 GB) allocated during
creation.
a. Select Photon-HW in the Navigator pane and in the right pane, click Shut down.
17
18
Lab 6 Adding vSphere Licenses
1. Use the vSphere Client to log in to the SA-VCSA-01 vCenter Server system as the
administrator.
a. In the bookmarks toolbar in Firefox, select vSphere Site-A > vSphere Client (SA-VCSA-
01).
a. In the vSphere Client, from the Menu drop-down menu, select Administration.
19
3. Add the vCenter Server and vSphere Enterprise Plus license keys.
b. On the Enter license keys page, enter the vCenter Server and vSphere Enterprise Plus
license keys from this link in the License keys text box.
c. Verify that both licenses are listed correctly in the text box and click NEXT.
d. On the Edit license names page, enter vCenter Server Training and ESXi
Training in the appropriate License name text boxes.
e. Click NEXT.
4. Verify that the licenses that you added appear in the list.
4. Click OK.
20
Lab 7 Creating and Managing the
vCenter Server Inventory
21
Task 2: Add ESXi Hosts to the Inventory
You add the sa-esxi-01.vclass.local and sa-esxi-02.vclass.local ESXi hosts to the vCenter Server
inventory.
2. On the Name and location page, enter sa-esxi-01.vclass.local and click NEXT.
3. On the Connection settings page, enter root as the user name and VMware1! as the
password and click NEXT.
a. If you see a security alert that the certificate store of vCenter Server cannot verify the
certificate, click YES to proceed.
4. On the Host summary page, review the information and click NEXT.
5. On the Assign license page, click the ESXi Training license key and click NEXT.
6. On the Lockdown mode page, leave the default as Disabled and click NEXT.
8. On the Ready to complete page, review the information and click FINISH.
9. Expand the Recent Tasks pane by clicking the arrows in the bottom-right corner of the
window and monitor the progress of the task.
10. Repeat steps 1 through 9 to add sa-esxi-02.vclass.local to the vCenter Server inventory.
For step 2, you enter sa-esxi-02.vclass.local on the Name and location page.
11. Verify that sa-esxi-01.vclass.local and sa-esxi-02.vclass.local appear in the navigation pane
under ICM-Datacenter.
22
Task 3: View Information About the ESXi Hosts
You view information about the ESXi host, including information about CPU, memory, storage,
NICs, and virtual machines. Knowing where to look in the UI for this information is useful for
monitoring and troubleshooting purposes.
3. Expand the Hardware pane and view the hardware details of the ESXi host.
1. In the navigation pane, select sa-esxi-01.vclass.local and click the Configure tab in the right
pane.
6. Next to NTP Service Status, select the Start NTP Service check box.
7. From the NTP Service Startup Policy drop-down menu, select Start and stop with host.
8. Click OK.
9. In the Network Time Protocol pane, verify that the NTP client is Enabled and that the NTP
service status is Running.
23
Task 5: Create a Folder for the ESXi Hosts
You create a folder named Lab Servers to group the sa-esxi-01.vclass.local and sa-esxi-
02.vclass.local ESXi hosts together.
1. In the navigation pane, right-click ICM-Datacenter and select New Folder > New Host and
Cluster Folder.
2. In the Enter a name for the folder text box, enter Lab Servers and click OK.
3. Verify that the Lab Servers folder appears in the navigation pane.
5. Verify that both hosts appear under the Lab Servers folder.
2. Create a folder for the VMs and move VMs into the folder.
a. Right-click ICM-Datacenter and select New Folder > New VM and Template Folder.
b. In the Enter a name for the folder text box, enter Lab VMs and click OK.
d. Drag the Win10-02, Win10-04, and Win10-06 virtual machines to the Lab VMs folder.
e. Verify that all three virtual machines appear under the Lab VMs folder.
a. Right-click ICM-Datacenter and select New Folder > New VM and Template Folder.
b. In the Enter a name for the folder text box, enter Lab Templates and click OK.
c. Verify that the Lab Templates folder appears in the navigation pane.
24
4. Compare the actions that you can perform on the Lab VMs folder and the Lab
Servers folder.
a. Right-click the Lab VMs folder and review the menu commands in the drop-down
menu.
c. Right-click the Lab Servers folder and review the menu commands in the drop-
down menu.
Q1. What is the difference between the menu commands for the Lab VMs folder
and the Lab Servers folder?
A1. The menu commands for the Lab Servers folder relate to host actions, whereas the menu commands for the Lab VMs folder relate to virtual machine actions.
25
26
Lab 8 Configuring Active Directory:
Joining a Domain
e. Click JOIN.
27
7. Verify that sa-vcsa-01.vclass.local successfully joined Active Directory.
8. Restart vCenter Server Appliance using the vCenter Server Appliance Management
Interface.
vCenter Server Appliance must be restarted for these changes to take effect.
a. Open a new tab in the browser.
b. From the bookmarks toolbar, select vSphere Site-A > vCenter Appliance Management
(SA-VCSA-01).
c. If a security warning appears, click Advanced and click Accept the Risk and Continue.
d. At the login screen, log in by entering root for the user name and VMware1! for the
password.
e. From the Actions drop-down menu in the top-right corner, select Reboot.
The reboot takes 10–15 minutes. During this time, the vSphere Client is unavailable.
10. In the vSphere Client tab, refresh the screen periodically until the vSphere Client login page
appears.
28
Lab 9 Configuring Active Directory:
Adding an Identity Source
5. Click ADD.
6. For the Identity Source Type, verify that Active Directory (Integrated Windows
Authentication) is selected.
8. Click ADD.
29
30
Lab 10 Users, Groups, and
Permissions
3. Under Single Sign-On in the navigation pane, select Users and Groups.
By default, the list of users for the LocalOS domain appears in the right pane.
4. In the Users pane, select vclass.local from the Domain drop-down menu.
31
Task 2: Assign Object Permission to an Active Directory User
You assign permission at the vCenter Server level to the administrator@vclass.local user.
NOTE
b. In the User/Group search box, enter admin and select Administrator from the list.
e. Click OK.
6. Verify that vclass\administrator appears in the list, is assigned the Administrator role, and is
defined in the vCenter Server object and its children.
Content libraries are located directly under the global root object. By assigning the Content
Library Administrator role to administrator@vclass.local at the global root, this user has
administrator rights for all content libraries.
3. In the Global Permissions pane, click the Add Permission icon (the plus sign).
32
4. Configure the permission settings.
b. In the User/Group search box, enter admin and select Administrator from the list.
c. From the Role drop-down menu, select Content library administrator (sample).
e. Click OK.
5. Verify that vclass.local\administrator appears in the list, is assigned the Content Library
Administrator (sample) role, and is assigned global permission.
1. In the vSphere Client, from the Menu drop-down menu, select VMs and Templates.
c. On the Select a creation type page, select Create a new virtual machine and click
NEXT.
d. On the Select a name and folder page, enter Test VM in the Virtual machine name
text box.
f. On the Select a compute resource page, expand the Lab Servers folder, select sa-esxi-
01.vclass.local, and click NEXT.
33
g. On the Select storage page, select ICM-Datastore and click NEXT.
h. On the Select compatibility page, leave ESXi 7.0 and later selected and click NEXT.
i. On the Select a guest OS page, select Linux from the Guest OS Family drop-down
menu.
j. Select VMware Photon OS (64-bit) from the Guest OS Version drop-down menu and
click NEXT.
k. On the Customize hardware page, expand the New Hard disk pane and select Thin
Provision from the Disk Provisioning drop-down menu.
l. Click NEXT.
n. Expand the Lab VMs folder in the navigation pane and verify that Test VM appears
under this folder.
a. In the navigation pane, right-click Test VM and select Delete from Disk.
c. Verify that Test VM does not appear under the Lab VMs folder.
34
Lab 11 Using Standard Switches
3. Select sa-esxi-01.vclass.local in the navigation pane and click the Configure tab in the right
pane.
5. Review the information about the vSwitch0 standard switch that is provided in the Virtual
switches pane.
Q3. Which virtual machines and templates are connected to the VM Network port
group?
A3. Photon-Hw, Photon-Template, Win10-02, Win10-04, Win10-06, and Win10-Tools.
35
Task 2: Create a Standard Switch with a Virtual Machine Port Group
You create a standard switch and a virtual machine port group on the standard switch to handle
network traffic at the host level in your vSphere environment.
1. Select sa-esxi-01.vclass.local in the navigation pane and click ADD NETWORKING in the
right pane.
2. On the Select connection type page, click Virtual Machine Port Group for a Standard
Switch and click NEXT.
3. On the Select target device page, click New standard switch and click NEXT.
4. On the Create a Standard Switch page, click the Add adapters icon (the green plus sign).
6. Review the information for the new active adapter and click NEXT.
7. On the Connection settings page, enter Production in the Network label text box and
click NEXT.
8. On the Ready to complete page, review the information and click FINISH.
9. In the Virtual switches pane, minimize the vSwitch0 pane and expand the vSwitch1 pane.
10. Verify that the Production port group is on vSwitch1 and that vmnic3 is the physical adapter.
11. Repeat steps 1 through 10 to create vSwitch1 and the Production port group on sa-esxi-
02.vclass.local.
36
f. Expand Network adapter 1 and verify that the Connect At Power On check box is
selected.
The Production port group has a status of disconnected because the VM is powered off.
a. In the navigation pane, right-click Win10-02 and select Power > Power On.
7. In Win10-02's Summary tab, verify that you are in the classic view of the vSphere Client.
a. If you see the CUSTOMIZE VIEW drop-down menu in the Summary tab, then select
Switch to classic view from the drop-down menu.
37
9. Wait for the boot process to complete.
a. In the VM's console, right-click the Windows Start icon and select Run.
b. In the Run dialog box, enter cmd and click OK to open a Command Prompt window.
c. At the command prompt, enter ipconfig /release to release the VM's current IP
address.
e. View the command's output and record the IPv4 address and the default gateway:
11. At the command prompt, enter ping 172.20.11.10 to verify that the virtual machine
is connected to the Production network.
This command pings the Production network's default gateway. Your ping should be
successful.
38
Lab 12 Accessing iSCSI Storage
3. In the navigation pane, select sa-esxi-01.vclass.local and select the Configure tab in the right
pane.
5. In the Storage Adapters pane, verify the status of the existing iSCSI software adapter.
39
6. Review the properties of the iSCSI software adapter.
• Adapter status
• Adapter name
7. Select the Devices tab and review the information in the Datastore column.
• LUN 6 (7 GB)
These LUNs should have a status of Not Consumed in the Datastore column.
The LUNs are hosted by an iSCSI provider and can be used to create datastores.
9. Select the Dynamic Discovery tab and record the iSCSI Server IP address. __________
10. Review and record information about the network port binding configuration.
b. In the Port Group column, select the IP Storage (vSwitch0) check box.
e. In the VMkernel Adapter > IP Settings tab, record the IPv4 address for vmk1.
__________
f. Click CLOSE.
40
Task 2: Add a VMkernel Port Group to a Standard Switch
You configure a VMkernel port group on vSwitch0 on sa-esxi-02.vclass.local to be used for IP
storage traffic.
4. On the Select connection type page, verify that VMkernel Network Adapter is selected and
click NEXT.
5. On the Select target device page, click Select an existing standard switch.
7. Click OK.
8. Click NEXT.
9. On the Port properties page, enter IP Storage in the Network label text box and click
NEXT.
d. Verify that the default gateway and DNS server address are set to 172.20.10.10.
e. Click NEXT.
12. Verify that vmk1, labeled IP Storage, appears in the VMkernel adapters list.
41
4. Confirm that Add software iSCSI adapter is selected and click OK.
5. In the Storage Adapters list, select the newly created iSCSI software adapter.
1. In the Storage Adapters pane, select the Dynamic Discovery tab and click Add.
2. In the Add Send Target Server window, enter 172.20.10.15 in the iSCSI Server text
box and click OK.
3. In the Storage Adapters pane, click the Network Port Binding tab.
4. Click Add.
The Rescan Storage window scans for new storage devices and new VMFS volumes by default.
7. Click OK.
8. Monitor the Recent Tasks pane and wait for the rescan tasks to finish.
• LUN 6 (7 GB)
These LUNs should have a status of Not Consumed in the Datastore column.
The LUNs are hosted by an iSCSI provider and can be used to create datastores.
42
Lab 13 Managing VMFS Datastores
a. In the navigation pane, right-click ICM-Datacenter and select Storage > New Datastore.
b. On the Type page, verify that VMFS is selected and click NEXT.
c. On the Name and device selection page, enter VMFS-2 in the Datastore name text box.
d. From the Select a host to view its accessible disks/LUNs drop-down menu, select sa-
esxi-01.vclass.local.
43
e. In the LUN list, select LUN 2 (11 GB in size).
f. Click NEXT.
h. On the Partition configuration page, move the Datastore Size slider to reduce the
datastore size by 3 GB and click NEXT.
For example, if the datastore size is 11 GB, change the size to 8 GB.
i. On the Ready to complete page, review the information and click FINISH.
4. In the navigation pane, verify that the VMFS-2 datastore appears under ICM-Datacenter.
6. In the right pane, select the Summary tab and record the value for storage capacity.
__________
b. On the Type page, verify that VMFS is selected and click NEXT.
c. On the Name and device selection page, enter VMFS-3 in the Datastore name text box.
d. From the Select a host to view its accessible disks/LUNs drop-down menu, select sa-
esxi-02.vclass.local.
g. On the Partition configuration page, accept the default (Use all available partitions) and
click NEXT.
h. On the Ready to complete page, review the information and click FINISH.
44
Task 2: Expand a VMFS Datastore to Consume Unused Space on a
LUN
You dynamically increase the capacity of the VMFS-2 datastore when more space is required by
virtual machines.
1. In the navigation pane, right-click the VMFS-2 datastore and select Increase Datastore
Capacity.
3. Scroll the window to the right and verify that Yes appears in the Expandable column.
4. Click NEXT.
5. On the Specify Configuration page, accept Use “Free Space 3 GB” to expand the datastore
from the Partition Configuration drop-down menu and click NEXT.
6. On the Ready to complete page, review the information and click FINISH.
7. When the task is completed, select the VMFS-2 datastore in the navigation pane.
8. On the Summary tab, verify that the datastore size is increased to the maximum capacity.
1. In the navigation pane, right-click the VMFS-3 datastore and select Delete Datastore.
3. Monitor the Recent Tasks pane and wait for the task to finish.
4. Verify that the VMFS-3 datastore is removed from the navigation pane.
45
Task 4: Extend a VMFS Datastore
You extend the capacity of a VMFS datastore when extra storage space is needed. You use a
second LUN to extend the size of a datastore based on the first LUN. You also rename the
VMFS datastore to make the name more descriptive.
d. On the Select Device page, select LUN 6 (7 GB) and click NEXT.
e. On the Specify Configuration page, select Use all available partitions from the Partition
Configuration drop-down menu.
f. Click NEXT.
g. On the Ready to complete page, review the information and click FINISH.
h. Monitor the Recent Tasks pane and when the task finishes, refresh the page.
b. Verify that two extent names appear in the Device Backing pane.
d. Record the new value for the total storage capacity. __________
e. Verify that the recorded value is larger than the final value in task 2, step 8.
sa-esxi-01.vclass.local and sa-esxi-02.vclass.local are in the list, indicating that this new
datastore is shared between your two ESXi hosts.
c. Click OK.
d. Verify that the datastore is renamed to Shared-VMFS.
46
Task 5: Create a Second VMFS Datastore
You use an iSCSI-shared LUN to create another VMFS datastore.
1. In the navigation pane, right-click ICM-Datacenter and select Storage > New Datastore.
2. On the Type page, verify that VMFS is selected and click NEXT.
3. On the Name and device selection page, enter iSCSI-Datastore in the Datastore
name text box.
4. From the Select a host to view its accessible disks/LUNs drop-down menu, select sa-esxi-
01.vclass.local.
5. From the LUN list, select LUN 5 (130 GB in size) and click NEXT.
7. On the Partition Configuration page, accept Use all available partitions and click NEXT.
8. On the Ready to complete page, review the information and click FINISH.
10. Select iSCSI-Datastore and in the right pane, click the Configure tab.
12. Verify that sa-esxi-01.vclass.local and sa-esxi-02.vclass.local are connected to the datastore.
47
48
Lab 14 Accessing NFS Storage
c. On the Select NFS version page, click NFS 4.1 and click NEXT.
d. On the Name and configuration page, enter NFS-Datastore in the Datastore name
text box.
g. Click the Add server icon (the green plus sign) to add the server.
Clicking the plus sign adds 172.20.10.10 to the box that appears below.
h. Click NEXT.
49
i. On the Configure Kerberos authentication page, accept the default and click NEXT.
j. On the Host accessibility page, select both the ESXi hosts and click NEXT.
k. On the Ready to complete page, verify the NFS settings and click FINISH.
4. Verify that the NFS datastore is listed in the navigation pane under ICM-Datacenter.
• Datastore type
50
Lab 15 Using a vSAN Datastore
b. Expand the Cluster Resources pane and view the number of hosts in the vSAN cluster.
c. In the right pane, click the Hosts tab to view the names of the ESXi hosts in the cluster.
51
4. View the disk group configuration on the hosts in the vSAN cluster.
c. Under the first ESXi host in the list, select the disk group.
The number of disk drives, drive types, and tier assignments are the same as the first
host.
5. View the VMkernel port configuration that is used to access the vSAN datastore.
a. In the navigation pane, select sa-esxi-04.vclass.local and, in the right pane, click the
Configure tab.
52
6. View storage capacity information for the vSAN cluster.
The Monitor tab appears and the Capacity Overview pane shows used space and free
space in the vSAN cluster.
3. In the right pane, scroll down the menu and select vSAN Default Storage Policy.
4. In the Rules tab, view the rule set for this storage policy.
5. Estimate the usable storage capacity of the vSAN default storage policy.
In the Usable capacity analysis pane, you can estimate the effective free space available
on the vSAN datastore if you deploy a VM with the specified storage policy. The policy
selected is vSAN Default Storage Policy.
Q1. Why is the policy's effective free space the value that it is?
A1. Because the storage policy uses RAID 1 (mirroring), RAID 1 provides full redundancy. A full copy of the VM is maintained and, therefore, the VM takes up twice the amount of space as a VM that is not mirrored.
53
Task 3: View a Virtual Machine on the vSAN Datastore
You power on a virtual machine on the vSAN datastore, and you familiarize yourself with the
vSAN components that make up the VM.
In the navigation pane, Photon-03 is selected and its Summary tab is displayed.
4. View the vSAN components that make up the Photon-03 virtual machine.
a. Power on Photon-03.
b. Select Photon-03 in the navigation pane.
e. Review the virtual object components that make up the virtual machine.
54
Lab 16 Using VM Templates: Creating
Templates and Deploying VMs
55
5. Move Photon-Template to the Lab Templates folder.
b. Select Lab Templates in the Move to folder window and click OK.
3. On the Name and target OS page, configure the specification name and target guest OS.
d. Click NEXT.
4. On the Computer name page, specify the computer name and the domain name.
c. Click NEXT.
c. Click NEXT.
7. On the Network page, click Use standard network settings for the guest operating system,
including enabling DHCP on all network interfaces and click NEXT.
56
8. On the DNS settings page, configure the DNS server and DNS search path.
b. Enter vclass.local in the DNS search path text box and click ADD.
c. Click NEXT.
9. On the Ready to complete page, review the information and click FINISH.
a. In the navigation pane, right-click Photon-Template and select New VM from This
Template.
b. On the Select a name and folder page, enter Photon-11 in the Virtual machine name
text box.
d. Click NEXT.
e. On the Select a compute resource page, expand ICM-Datacenter > Lab Servers and
select sa-esxi-01.vclass.local.
f. Click NEXT.
h. From the Select virtual disk format drop-down menu, select Thin Provision and click
NEXT.
i. On the Select clone options page, select the Customize the operating system and the
Power on virtual machine after creation check boxes and click NEXT.
k. On the Ready to complete page, review the information and click FINISH.
57
3. Deploy a VM from Photon-Template to sa-esxi-02.vclass.local.
a. In the navigation pane, right-click Photon-Template and select New VM from This
Template.
d. Click NEXT.
e. On the Select a compute resource page, expand ICM-Datacenter > Lab Servers and
select sa-esxi-02.vclass.local.
f. Click NEXT.
h. From the Select virtual disk format drop-down menu, select Thin Provision and click
NEXT.
i. On the Select clone options page, select the Customize the operating system and the
Power on virtual machine after creation check boxes and click NEXT.
k. On the Ready to complete page, review the information and click FINISH.
4. In the Recent Tasks pane, monitor the progress of the two virtual machine cloning tasks and
wait for their completion.
5. When the tasks are complete, verify that the VMs are placed in the inventory correctly.
a. Verify that Photon-11 and Photon-12 appear in the navigation pane under the Lab VMs
folder.
c. View Photon-11's Summary tab and verify that this VM is located on sa-esxi-
01.vclass.local.
d. View Photon-12's Summary tab and verify that this VM is located on sa-esxi-
02.vclass.local.
a. Select each virtual machine and in the Summary tab, click the Launch Web Console link.
58
Lab 17 Using Content Libraries
4. On the Name and location page, enter VM Library in the Name text box and click NEXT.
5. On the Configure content library page, verify that Local content library is selected.
7. On the Add storage page, scroll to the bottom of the list, select vsanDatastore, and click
NEXT.
8. On the Ready to complete page, review the information and click FINISH.
59
Task 2: Clone a VM Template to a Template in a Content Library
You clone virtual machines or VM templates from the vCenter Server inventory to templates in
the content library. You use the content library templates to provision virtual machines on a
cluster or host.
2. In the navigation pane, expand ICM-Datacenter > Lab Templates, right-click Photon-
Template, and select Clone to Library.
5. Enter Photon-LibTemplate in the Template name text box and click OK.
b. On the Select name and folder page, enter Photon-13 in the Virtual machine name
text box.
c. In Select a location for the virtual machine pane, select SA-Datacenter and click NEXT.
d. On the Select a compute resource page, select SA-Datacenter > SA-Compute-01 and
select sa-esxi-04.vclass.local.
e. Click NEXT.
A warning appears stating that the OVF package contains advanced configuration
options that might pose a security risk.
60
g. Click NEXT.
i. On the Select networks page, select VM Network from the Destination Network drop-
down menu and click NEXT.
j. On the Ready to complete page, review the information and click FINISH.
6. In the Recent Tasks pane, monitor the progress of the template deployment task and wait
for its completion.
9. In the navigation pane, right-click Photon-13 and select Power > Power On.
b. In the VM console window, verify that the boot process is successful and the login
prompt appears.
61
62
Lab 18 Modifying Virtual Machines
a. In the navigation pane, right-click Win10-06 and select Power > Power On.
4. In Win10-06's Summary tab, expand the VM Hardware pane and record the amount (GB) of
total memory. __________
6. In the Memory text box, enter 4500 and select MB from the drop-down menu.
The memory hot plug function is active for Win10-06. Therefore, you can add memory to
Win10-06 while it is powered on.
7. Click OK.
63
8. On the virtual machine’s Summary tab, verify that the memory size has increased.
2. On the Virtual Hardware tab, record the size (GB) of Hard Disk 1. __________
3. In the Hard disk 1 text box, increase the disk size by 2 GB and click OK.
4. View the VM Hardware pane in Win10-06's Summary tab and verify that Hard disk 1 shows
the correct disk size.
64
6. Configure the Win10-06 virtual machine’s guest operating system to detect and extend the
increased disk space.
c. If the 2 GB of unallocated space is not discovered, click Action and select Rescan Disks.
e. Click Next.
f. On the Select Disks page, verify that Disk 0 is selected in the Selected pane and click
Next.
g. On the Completing the Extend Volume Wizard page, review the information and click
Finish.
7. In the Disk Management window, verify that the local C: drive (Disk 0) is extended.
8. Record the value for the total size of the C: drive. __________
9. Compare the value with the value that you recorded in step 2.
3. Click OK.
ICM-Datastore appears in the list. This datastore is where the Win10-New VM's files are
located.
65
7. Record the name of the Win10-New virtual machine's folder. __________
When you change the name of a virtual machine, you change the name that identifies the VM
in the vCenter Server inventory, not the name of the VM’s folder or files on the datastore.
b. In the Enter the new name text box, enter Win10-06 and click OK.
a. In the navigation pane, right-click Win10-06 and select Power > Shut Down Guest OS.
66
Lab 19 vSphere vMotion Migrations
3. In the navigation pane, expand ICM-Datacenter > Lab Servers and select sa-esxi-
01.vclass.local.
7. On the Select connection type page, click VMkernel Network Adapter and click NEXT.
67
8. On the Select target device page, click New standard switch and click NEXT.
9. On the Create a Standard Switch page, click the green plus sign to add a physical adapter to
the switch.
10. Select vmnic2 for the vSphere vMotion network and click OK.
11. Review the information and click NEXT.
12. On the Port properties page, enter vMotion in the Network label text box.
d. Click NEXT.
15. On the Ready to complete page, review the information and click FINISH.
16. In the Virtual switches pane, verify that the vSwitch2 virtual switch is listed and that vSwitch2
contains the vMotion VMkernel port.
1. In the navigation pane, expand ICM-Datacenter > Lab Servers and select sa-esxi-
02.vclass.local.
5. On the Select connection type page, click VMkernel Network Adapter and click NEXT.
6. On the Select target device page, click New standard switch and click NEXT.
7. On the Create a Standard Switch page, click the green plus sign to add a physical adapter to
the switch.
8. Select vmnic2 for the vSphere vMotion network and click OK.
68
10. On the Port properties page, enter vMotion in the Network label text box.
d. Click NEXT.
13. On the Ready to complete page, review the information and click FINISH.
14. In the Virtual switches pane, verify that the vSwitch2 virtual switch is listed and that vSwitch2
contains the vMotion VMkernel port.
1. In the navigation pane, verify that the Win10-02 and Win10-04 virtual machines are powered
on.
2. Verify that Win10-02 and Win10-04 are connected to the Production network.
c. Expand the VM Hardware pane and verify that network adapter 1 is connected to the
Production network.
69
3. Open the remote console to Win10-02.
4. In the remote console, click the search icon in the Windows taskbar and enter cmd to open a
Command Prompt window.
5. When the Command Prompt window opens, enter ipconfig and record the virtual
machine’s default gateway IP address. __________
70
Task 4: Migrate Virtual Machines Using vSphere vMotion
You perform hot migrations of virtual machines residing on a shared datastore that is accessible
to both the source and the target ESXi hosts.
1. Leave the Win10-02 console open and return to the vSphere Client.
2. Migrate the Win10-02 virtual machine from host sa-esxi-01.vclass.local to host sa-esxi-
02.vclass.local.
b. On the Select a migration type page, click Change compute resource only and click
NEXT.
The sa-esxi-02.vclass.local host is the destination host to which you migrate the Win10-
02 virtual machine. The migration requirements are validated. If the validation does not
succeed, warning or error messages appear in the Compatibility pane. If errors appear,
you cannot continue with the migration until the errors are resolved.
d. Click NEXT.
e. On the Select networks page, verify that Production is selected from the Destination
Network drop-down menu and click NEXT.
f. On the Select vMotion priority page, leave Schedule vMotion with high priority
(recommended) selected and click NEXT.
g. On the Ready to complete page, review the information and click FINISH.
3. Monitor the Recent Tasks pane and verify that the Relocate virtual machine task started.
4. Return to the Win10-02 console and monitor to verify that no pings are dropped during the
migration.
5. Switch between the Recent Tasks pane and the Win10-02 console and monitor the
migration progress.
6. When the migration is complete, return to the Win10-02 console and close the Command
Prompt window to stop the ping command.
8. View Win10-02's Summary tab and verify that Win10-02 is located on the sa-esxi-
02.vclass.local host.
71
11. On the Summary tab, verify that Win10-04 is on the sa-esxi-01.vclass.local host.
12. Migrate the Win10-04 virtual machine from host sa-esxi-01.vclass.local to host sa-esxi-
02.vclass.local.
b. On the Select a migration type page, click Change compute resource only and click
NEXT.
d. On the Select networks page, verify that Production is selected from the Destination
Network drop-down menu and click NEXT.
e. On the Select vMotion priority page, leave Schedule vMotion with high priority
(recommended) selected and click NEXT.
f. On the Ready to complete page, review the information and click FINISH.
13. Monitor the Recent Tasks pane and wait for the Relocate virtual machine task to finish.
14. Verify that Win10-04 appears in the navigation pane under sa-esxi-02.vclass.local.
72
Lab 20 vSphere Storage vMotion
Migrations
3. In the navigation pane, select the Photon-11 virtual machine and verify that it is powered on.
7. On the Select a migration type page, click Change storage only and click NEXT.
9. Click NEXT.
73
10. On the Ready to complete page, review the information and click FINISH.
11. Monitor the Recent Tasks pane and wait for the Relocate virtual machine task to finish.
12. In the Related Objects pane on the Summary tab, verify that the Photon-11 virtual machine is
on ICM-Datastore.
2. In the Related Objects pane on Photon-11's Summary tab, verify that Photon-11 is on sa-esxi-
01.vclass.local and ICM-Datastore.
b. On the Select a migration type page, click Change both compute resource and storage
and click NEXT.
c. On the Select compute resource page, select ICM-Datacenter > Lab Servers > sa-esxi-
02.vclass.local and click NEXT.
e. On the Select networks page, select VM Network from the Destination Network drop-
down menu and click NEXT.
f. On the Select vMotion priority page, leave Schedule vMotion with high priority
(recommended) selected and click NEXT.
g. On the Ready to complete page, review the information and click FINISH.
4. In the Recent Tasks pane, monitor the progress of the virtual machine migration.
a. In the Related Objects pane on Photon-11's Summary tab, verify that the host is sa-esxi-
02.vclass.local and that the datastore is iSCSI-Datastore.
6. Shut down the Photon-11 VM.
a. In the navigation pane, right-click Photon-11 and select Power > Shut Down Guest OS.
74
Lab 21 Working with Snapshots
You use snapshots when you must revert to a previous virtual machine state.
75
5. Take a snapshot of Win10-02.
a. In the navigation pane, right-click Win10-02 and select Snapshots > Take Snapshot.
d. Click OK.
6. Monitor the Recent Tasks pane and wait for the task to complete.
7. Delete the CPUBUSY.VBS and IOMETER.EXE files from the Windows desktop.
a. Return to the Win10-02 VM's console tab.
b. On the desktop, drag the CPUBUSY.VBS file and the IOMETER.EXE file to the Recycle
Bin.
a. In the navigation pane, right-click Win10-02 and select Snapshots > Take Snapshot.
d. Click OK.
10. Monitor the Recent Tasks pane and wait for the task to complete.
This snapshot contains a file from which you can see how a virtual machine changes when you
revert to different snapshots in subsequent tasks.
1. Restore the CPUBUSY.VBS file from the Recycle Bin to the virtual machine's desktop.
76
2. Take a snapshot of Win10-02.
f. Click OK.
3. Monitor the task in the Recent Tasks pane and wait for its completion.
This task takes slightly longer than previous snapshots because the guest memory is also
saved.
1. In the navigation pane, right-click Win10-02 and select Snapshots > Manage Snapshots.
You should see three snapshots. The difference in icons is because you selected the
Snapshot the virtual machine’s memory check box when you took the snapshot.
3. Select the Without iometer and cpubusy snapshot and click REVERT TO.
77
4. Click OK to confirm the revert operation.
Q3. Did the Win10-02 virtual machine power off and why?
A3. Yes. The virtual machine powered off because the memory state was not preserved.
6. Power on Win10-02.
Wait for the boot process to finish. When it finishes, you are logged in as
vclass\administrator.
9. In the vSphere Client, right-click Win10-02 and select Snapshots > Manage Snapshots.
The You Are Here pointer should appear under the snapshot called Without iometer and
cpubusy.
10. In the Manage Snapshots window, select the With cpubusy snapshot and click REVERT TO.
The You Are Here pointer should appear under the snapshot called With cpubusy.
Q5. Did the virtual machine power off? Why or why not?
A5. No. The virtual machine did not power off because the memory state was preserved.
78
Task 4: Delete an Individual Snapshot
You remove a snapshot to initiate file consolidation to the parent snapshot disk.
2. In the navigation pane, right-click the Win10-02 virtual machine and select Snapshots >
Manage Snapshots.
The You are here pointer appears under the With cpubusy snapshot.
3. Select the Without iometer and cpubusy snapshot and click DELETE.
2. Right-click the Win10-02 virtual machine and select Snapshots > Manage Snapshots.
4. Click OK to confirm that you want to delete all the remaining snapshots.
Only the You are here pointer should appear in the snapshots tree.
Q1. Were all the remaining snapshots deleted from the Manage Snapshots window?
A1. Yes.
79
80
Lab 22 Controlling VM Resources
a. In the navigation pane, right-click each VM and select Power > Shut Down Guest OS.
b. On the Select a migration type page, click Change compute resource only and click
NEXT.
c. On the Select a compute resource page, select sa-esxi-01.vclass.local and click NEXT.
d. On the Select networks page, verify that Production is selected from the Destination
Network drop-down menu and click NEXT.
e. On the Ready to complete page, review the information and click FINISH.
81
5. Verify that Win10-02 is on sa-esxi-01.vclass.local.
6. Configure the Win10-02 and Win10-04 virtual machines to run only on logical CPU 1.
This affinity setting forces the Win10-02 virtual machine to run only on logical CPU 1.
d. Click OK.
IMPORTANT
CPU affinity is used mainly to create CPU contention for training purposes. The use of
this feature in a production environment is discouraged.
8. Verify that Win10-02 and Win10-04 each has a CPU shares value of Normal.
a. In the navigation pane, select Win10-02 and click the Summary tab in the right pane.
9. Start the CPUBUSY script on the Win10-02 and Win10-04 virtual machine desktops.
a. Open the Win10-02 VM web console.
b. On the desktop, right-click CPUBUSY and select Open with Command Prompt.
This script runs continuously. It stabilizes in 1–2 minutes. The script repeatedly performs
floating-point computations. The script displays the duration (wall-clock time) of a
computation, for example, I did ten million sines in # seconds.
You can use the number of seconds reported as a performance estimate. The program
should run at about the same rate in each virtual machine.
10. After 1 or 2 minutes, verify that the duration of computation value (in seconds) is similar
between Win10-02 and Win10-04.
82
Task 2: Verify CPU Share Functionality
You verify that VMs receive the correct CPU allocation during contention. CPU allocation is
based on the number of shares given to the VM.
d. Click OK.
d. Click OK.
4. In each virtual machine's Summary tab, verify that CPU shares are set to High for Win10-02
and Low for Win10-04.
If you are logged out of the console because of inactivity, log in again as vclass\administrator
with VMware1! as the password.
Q1. What is the difference in performance between the two virtual machines?
A1. Win10-04 has only one-fourth of the CPU shares that Win10-02 has. So Win10-04 receives only one-fourth of the CPU cycles of the logical CPU to which the virtual machines are pinned.
6. Close the Command Prompt window to stop the CPUBUSY script in each VM console.
This script must be stopped in each virtual machine. If the script is left running, the
performance of other labs might be affected.
83
Lab 23 Monitoring Virtual Machine
Performance
3. Verify that the Win10-02 and Win10-04 virtual machines are powered on.
4. In each VM's Summary tab, open VM web consoles for Win10-02 and Win10-04.
5. On both virtual machine desktops, right-click the CPUBUSY script file and select Open with
Command Prompt.
85
Task 2: Use Performance Charts to Monitor CPU Use
You use performance charts to monitor CPU metrics.
2. View the CPU performance chart for the Win10-02 virtual machine.
b. In the right pane, click the Monitor tab and select Advanced under Performance.
f. In the Select object for this chart pane on the right, deselect the 0 check box.
g. In the Select counters for this chart pane, verify that the Readiness and Usage check
boxes are the only boxes that are selected.
h. Click OK.
3. Open a new tab in the web browser and start a second vSphere Client instance.
a. To start the vSphere Client, select vSphere Site-A > vSphere Client (SA-VCSA-01) in
the bookmarks toolbar in Firefox.
4. In the second vSphere Client instance, repeat step 2 to view the CPU performance chart for
the Win10-04 virtual machine.
5. In the vSphere Client windows that show the CPU charts for Win10-02 and Win10-04, view
the Latest column for the Readiness metric.
6. Record the latest CPU readiness value for each virtual machine and leave the Performance
Chart windows open.
• Win10-02 __________
• Win10-04 __________
7. In each VM console, close the Command Prompt window to stop the CPUBUSY script.
This script must be stopped in each virtual machine. If the script is left running, the
performance of other labs might be affected.
86
8. In the vSphere Client windows that show the CPU charts for Win10-02 and Win10-04, view
the Latest column for the Readiness metric.
9. Wait for the chart to be updated and compare the CPU ready value with what you recorded
in step 6.
Q1. Did the CPU ready value change? If it did, what is the reason for the change?
A1. Yes. After the scripts stop, the CPU ready value decreases significantly because CPU contention does not occur.
10. Close the Win10-02 console tab, the Win10-04 console tab, and the second vSphere Client
tab.
a. In the navigation pane, right-click each VM and select Power > Shut Down Guest OS.
2. Change the CPU shares to Normal and remove CPU affinity from Win10-02 and Win10-04.
Entering 0 is not the same as deleting the value. The text box must be blank.
e. Click OK.
f. Repeat steps a through e to change the CPU shares and remove the scheduling affinity
value on Win10-04.
87
88
Lab 24 Using Alarms
a. In the navigation pane, right-click Win10-02 and select Power > Power On.
Because you are creating an alarm for the Win10-02 virtual machine object, this alarm
monitors only that object. If you set the alarm on an object higher in the vCenter Server
inventory, the alarm applies to the parent object and all relevant child objects in the hierarchy.
5. On the Name and Targets page, enter Win10-02 CPU Usage in the Alarm Name text
box.
The target type is Virtual Machine and the target object is Win10-02.
6. Click NEXT.
89
7. On the Alarm Rule 1 page, define the trigger condition.
If VM CPU Usage is above 50% for 30 seconds, then trigger the alarm and show the alarm
as Warning.
f. Click NEXT.
8. On the Reset Rule 1 page, read the rule and do not change anything.
The reset rule is to reset the alarm to Normal if the warning condition is no longer met.
9. Click NEXT.
90
12. Verify that the alarm definition is created.
a. In the navigation pane, select Win10-02 and click the Configure tab.
c. Verify that the Win10-02 CPU Usage alarm appears in the alarm list.
d. If you cannot easily find the alarm, use the filter in the Alarm Name column and search
for some or all of the alarm name.
1. Generate CPU activity in Win10-02 to trigger the Win10-02 CPU Usage alarm.
a. In Win10-02's Summary tab, click the Launch Web Console link to open the VM web
console.
The CPUBUSY script should generate enough activity to reach 50 percent CPU usage.
a. Click Win10-02's Monitor tab, and select Triggered Alarms under Issues and Alarms.
b. Wait for at least 30 seconds and refresh the Triggered Alarms pane.
c. Verify that the Win10-02 CPU Usage alarm appears in the Triggered Alarms list.
An entry states that the Win10-02 CPU Usage alarm changed from green to yellow.
91
5. Acknowledge the triggered alarm.
a. In the right pane under Issues and Alarms, click Triggered Alarms.
c. Click ACKNOWLEDGE.
The Triggered Alarms pane shows the time that the alarm was acknowledged and the
user that acknowledged the alarm.
b. Refresh the Triggered Alarms pane and verify that the Win10-02 CPU Usage alarm no
longer appears.
c. In the navigation pane, verify that Win10-02's icon does not show the warning symbol.
An entry states that the Win10-02 CPU Usage alarm changed from yellow to green.
1. In the navigation pane, select ICM-Datacenter and click the Configure tab in the right pane.
3. On the Name and Targets page, configure the alarm name and target type.
92
4. On the Alarm Rule 1 page, define the trigger condition.
The VM suspended event appears under the Power and Connection State category.
c. Click NEXT.
a. On the Reset Rule 1 page, activate Reset the alarm to green by clicking the toggle
switch.
b. Click the first drop-down menu and enter powered in the Search box.
d. Click NEXT.
93
6. On the Review page, review the alarm information.
7. Click CREATE.
a. If you cannot easily find the alarm, use the filter in the Alarm Name column and search
for some or all of the alarm name.
a. In the navigation pane, right-click Win10-02 and select Power > Suspend.
b. In the right pane, click the Monitor tab and under Issues and Alarms, select Triggered
Alarms.
c. Monitor the Recent Tasks pane and wait for the Suspend virtual machine task to
complete.
e. Verify that the VM Suspended alarm appears in the Triggered Alarms list.
3. Power on Win10-02.
a. In the navigation pane, right-click Win10-02 and select Power > Power On.
a. In the navigation pane, verify that Win10-02's icon does not show the warning symbol.
94
Task 5: Deactivate Virtual Machine Alarms
You deactivate the Win10-02 CPU Usage and the VM Suspended alarms.
If necessary, use the filter in the Alarm Name column to search for the alarm.
Perform this step on the ICM-Datacenter object because the alarm is defined on this object.
95
Lab 25 Implementing vSphere DRS
Clusters
97
4. Configure the new cluster.
c. Leave the default settings for the other options and click OK.
5. Verify that the ICM-Compute-01 cluster appears in the navigation pane under ICM-
Datacenter.
1. In the navigation pane, select ICM-Compute-01 and click the Configure tab.
With Manual mode, you can manually apply vSphere DRS recommendations.
4. Move the Migration Threshold slider to Aggressive, which is to the right side of the slider.
98
Task 4: Verify vSphere vMotion Configuration on the ESXi Hosts
You verify that a VMkernel port is configured for vSphere vMotion on sa-esxi-01.vclass.local and
sa-esxi-02.vclass.local.
1. In the navigation pane, select sa-esxi-01.vclass.local and click the Configure tab.
4. On the All tab in the lower pane, verify that vMotion appears as an enabled service.
b. On the Select a migration type page, click Change compute resource only and click
NEXT.
c. On the Select a compute resource page, select sa-esxi-01.vclass.local and click NEXT.
e. On the Select vMotion priority page, leave the default and click NEXT.
a. In the navigation pane, right-click Win10-04 and select Power > Power On.
The Power On Recommendations window opens. vSphere DRS provides you with one
or more recommendations for placing the VM when it is powered on.
b. Select the recommendation that places Win10-04 on sa-esxi-01.vclass.local and click OK.
c. In the navigation pane, right-click Win10-06 and select Power > Power On.
d. Select the recommendation that places Win10-06 on sa-esxi-01.vclass.local and click OK.
99
5. Verify that Win10-02, Win10-04 and Win10-06 are on sa-esxi-01.vclass.local.
b. In the right pane, click the VMs tab and verify that Win10-02, Win10-04 and Win10-06
are listed.
6. Open the web consoles for Win10-02 and Win10-04.
7. Start the CPUBUSY script on the Win10-02 and Win10-04 virtual machines.
a. In Win10-02's web console, right-click the CPUBUSY script and select Open with
Command Prompt.
b. In Win10-04's web console, right-click the CPUBUSY script and select Open with
Command Prompt.
2. Select ICM-Compute-01 in the navigation pane and click the Monitor tab in the right pane.
Clicking the button forces vSphere DRS to immediately evaluate the cluster and provide
recommendations instead of waiting the standard 5 minutes before generating
recommendations.
100
5. View information about the vSphere DRS cluster.
a. Click the Summary tab and expand the vSphere DRS pane.
c. Click the Information icon next to VM DRS Score to review how to interpret the VM
DRS score.
Q2. How many vSphere DRS recommendations and DRS faults are shown?
A2. The answer might vary, but you should see at least one recommendation.
Q3. Look at the DRS Score. Are Win10-02, Win10-04, and Win10-06 experiencing
serious CPU contention?
A3. Yes, they should be experiencing serious CPU contention.
f. 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. Monitor the Recent Tasks pane and wait for the virtual machine migration tasks to complete.
9. In the DRS Recommendations pane, click RUN DRS NOW to force vSphere DRS to evaluate
the cluster status.
10. Click the Summary tab and view the vSphere DRS pane.
101
11. Click the Monitor tab and select CPU Utilization under vSphere DRS.
The virtual machines should spread across the two ESXi hosts. You might need to refresh
the window.
12. In the Win10-02 and Win10-04 console tabs, stop the CPUBUSY script.
You must ensure that the CPUBUSY script is stopped in all VMs to avoid performance
problems.
It might take several minutes for the virtual machines to stabilize and the alerts to clear.
c. Click the vSphere DRS toggle button to deactivate vSphere DRS and click OK.
102
Lab 26 Using vSphere HA
3. Select ICM-Compute-01 and click the Configure tab in the right pane.
6. Monitor the Recent Tasks pane and wait for the vSphere HA configuration tasks to
complete.
7. Click the Configure tab and verify that vSphere HA is turned on.
103
Task 2: View Information About the vSphere HA Cluster
You view status and configuration information about the ICM-Compute-01 cluster. You notice
that the ESXi hosts in the cluster have only one management network port.
Q1. Does the number of protected virtual machines match the number of powered-
on virtual machines in the cluster?
A1. Yes. If both hosts are added to the cluster and no errors occur on the cluster, the number of protected VMs equals the number of powered-on VMs.
5. Under vSphere HA, select Configuration Issues and review errors or warnings that are
displayed.
You should see warning messages that each ESXi host has no management network
redundancy. Currently, each ESXi host has a single management network port. vSphere HA
still works if an ESXi host is configured with one management network port, but a second
management network port is necessary for management network port redundancy.
1. Configure a second management network port on the ESXi hosts in the cluster.
You use the vMotion VMkernel adapter as the second management network port.
a. In the navigation pane, select sa-esxi-01.vclass.local and click the Configure tab.
d. On the Port properties page, verify that the vMotion check box is selected and select
the Management check box.
104
e. Click OK.
g. Monitor the Recent Tasks pane and wait for the reconfiguration task to complete.
h. Repeat steps a through g for sa-esxi-02.vclass.local.
a. In the navigation pane, select the ICM-Compute-01 cluster and click the Monitor tab.
Q1. Do you see any warning messages about no host management network
redundancy?
A1. No, the warning messages are no longer present.
When an ESXi host outage is detected, vSphere HA automatically restarts the virtual machines
on the other ESXi hosts in the cluster.
1. In the navigation pane, select ICM-Compute-01 and click the Monitor tab.
2. Under vSphere HA, select Summary and record the name of the primary host next to
Master. __________
3. Verify that the primary host contains one or more powered-on virtual machines.
b. In the right pane, click the VMs tab and verify that Virtual Machines is selected.
c. If all the virtual machines are powered off on the primary host, power on at least one of
the virtual machines.
4. Record the name of one or more powered-on virtual machines on the primary host.
__________
6. Click the Monitor tab and select Summary under vSphere HA.
7. In the Virtual Machines pane, verify that the Protected field matches the number of
powered-on VMs within the cluster and that the Unprotected field value is 0.
105
8. Simulate a host failure by rebooting the primary host in the cluster.
Ensure that you reboot the system. Do not shut down the system.
a. In the navigation pane, right-click the primary 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.
9. View the events that occur while the vSphere HA cluster recovers from the host failure.
a. Select ICM-Compute-01 in the navigation pane and click the Monitor tab in the right
pane.
The cluster entries are sorted by time. Note the entries that appear when the host
failure was detected.
c. In the navigation pane, select the host that you rebooted and click the VMs tab in the
right pane.
Q1. Do you see the virtual machines that were running on this host (the original
primary host) and whose names you recorded earlier?
A1. No. The virtual machines previously running on this host are running on the remaining host in the cluster.
10. Monitor the original primary ESXi host in the navigation pane until it is fully running again.
It might take several minutes for the original primary host to become fully running.
106
Task 5: View the vSphere HA Cluster Resource Usage
You examine the CPU and memory resource usage information of the ICM-Compute-01 cluster.
1. In the navigation pane, select ICM-Compute-01 and click the Monitor tab in the right pane.
c. Verify that the CPU reservation is not set on the virtual machines.
a. Under Resource Allocation, select Memory and record the information for the cluster.
b. Verify that the memory reservation is not set on the virtual machines.
You must configure vSphere DRS to use this admission control option.
b. In the right pane under Services, select vSphere DRS and click EDIT.
d. From the Automation Level drop-down menu, select Fully Automated and click OK.
107
2. Configure the percentage of resource degradation to tolerate.
b. Click EDIT.
If you reduce the threshold to 0%, a warning is generated when cluster usage exceeds
the available cluster capacity.
e. Click OK.
a. In the navigation pane, select Win10-02 and in the right pane, click the Summary tab.
c. Right-click the CPUBUSY script and select Open with Command Prompt.
4. Verify that a message appears about the configured failover resources in the ICM-Compute-
01 cluster.
a. In the navigation pane, select ICM-Compute-01 and click the Summary tab in the right
pane.
You should see an informational message that says Running VMs utilization
cannot satisfy the configured failover resources on the
cluster ICM-Compute-01 in ICM-Datacenter.
5. In the Win10-02 console tab, close the Command Prompt window to stop the CPUBUSY
script.
You must ensure that the CPUBUSY script is stopped to avoid performance problems.
8. Verify that the message about the configured failover resources is not shown.
108
Lab 27 Using vSphere Lifecycle
Manager
a. In the right pane, select Import Updates from the ACTIONS drop-down menu.
b. Click BROWSE and navigate to Desktop > Class Materials and Licenses
> Downloads.
c. Double-click VMware-ESXi-7.0.0-15847920-depot.zip.
The Import Updates window opens, displaying a progress bar for Step 1 of 2.
After Step 1 completes, the window closes, and the Import updates task appears in the
Recent Tasks pane. This task represents Step 2 in the process.
109
d. Monitor the Recent Tasks pane and wait for the Import updates task to complete.
e. Verify that your uploaded image file appears in the Image Depot pane.
d. Click VENDOR ADDONS and verify that four items appear in the list.
d. Click COMPONENTS and verify that the Test VIB signing certs component and two test
components appear in the list.
110
6. View details about the images, add-ons, and components that you uploaded.
b. Select the ESXi entry in the list and review the details and components that appear to
the right.
The ESXi version, release date, category, and a full list of components are provided.
c. Click VENDOR ADDONS and select the first add-on in the list.
The add-on version, release date, category, and a list of added components are
provided.
e. Select the other add-ons in the list and review their details to the right.
The component version, release date, category, and severity are provided.
h. Select the other components in the list and review their details to the right.
2. In the navigation pane, right-click the ICM-Datacenter object and select New Cluster.
111
3. Configure the new cluster.
Option Action
Manage all hosts in the cluster with a Click the Information icon, read the information
single image provided, and close the box.
Click OK.
4. In the Recent Tasks pane, monitor the progress as the cluster is created.
6. Verify that vSphere DRS and Lifecycle Management (Manage all hosts with one image) are
listed under Selected services.
You must shut down the VMs on sa-esxi-01.vclass.local and sa-esxi-02.vclass.local because
you will be placing these hosts into maintenance mode.
a. Right-click a powered-on VM and select Power > Shut Down Guest OS.
112
2. Record the ESXi build number for sa-esxi-01.vclass.local and sa-esxi-02.vclass.local.
b. View the Hypervisor information and record the ESXi build number for sa-esxi-
01.vclass.local and sa-esxi-02.vclass.local. __________
The build number should be the same for both hosts.
b. Deselect the Move powered-off and suspended virtual machines to other hosts in the
cluster check box.
These hosts should no longer be part of the ICM-Compute-01 cluster and are still in
maintenance mode.
113
5. Take sa-esxi-01.vclass.local and sa-esxi-02.vclass.local out of maintenance mode.
You power on these VMs to demonstrate that vSphere Lifecycle Manager can update the
ESXi hosts while VMs are powered on.
a. In the navigation pane, right-click the VM and select Power > Power On.
1. In the navigation pane, select ICM-Compute-02 and click the Updates tab in the right pane.
g. Select the Test VIB signing certs check box and the vmwTestComponent3 check box
and click SELECT.
h. Verify that the components that you selected appear in the list.
i. In the Edit Image pane, click SAVE.
Several tasks are started. Saving the changes to the image automatically starts the Check
compliance of cluster with image task.
114
4. Wait for the task to complete.
5. View the Image Compliance pane and read any warning and information messages.
6. Select each host in the list and view its compliance information.
b. Verify that the host versions and image versions are different for each of the images.
7. In the Image Compliance pane, click RUN PRE-CHECK to ensure that the ICM-Compute-02
cluster is ready to remediate.
8. Wait for the precheck tasks to complete and verify that No pre-check issues
found appears in the Image Compliance pane.
9. In the Image Compliance pane, click REMEDIATE ALL to remediate the hosts in the cluster.
10. Read the information in the remediation impact summary, accept the terms of the End User
License Agreement and click START REMEDIATION.
12. Monitor the Recent Tasks pane to view the status of the individual tasks that are started
during the remediation.
vSphere DRS migrates VMs off a host before remediating the host.
The hosts are rebooted as part of the remediation. When the hosts come back online, a
second compliance check automatically runs.
13. When the remediation is complete, verify that the Image Compliance pane shows that all
hosts in the cluster are compliant.
115
116
Answer Key
117
A3. ICM-Datastore
Q4. What is the size of Photon-HW_1.vmdk?
A4. 0 Bytes
Q5. What is the size of Photon-HW_2.vmdk?
A5. 1 Gigabyte
Lab 7 Creating and Managing the vCenter Server Inventory
Q1. How many CPUs does this ESXi host have?
A1. 2 CPUs
Q2. How much memory does this ESXi host have?
A2. 8 GB
Q3. How many networks is this ESXi host connected to?
A3. One network
Q1. What is the difference between the menu commands for the Lab VMs folder and the Lab
Servers folder?
A1. The menu commands for the Lab Servers folder relate to host actions, whereas the menu
commands for the Lab VMs folder relate to virtual machine actions.
Lab 11 Using Standard Switches
Q1. Which physical adapter is vSwitch0 connected to?
A1. vmnic0
Q2. Which port groups are connected to vSwitch0?
A2. IP Storage, Management Network, and VM Network
Q3. Which virtual machines and templates are connected to the VM Network port group?
A3. Photon-Hw, Photon-Template, Win10-02, Win10-04, Win10-06, and Win10-Tools.
Lab 15 Using a vSAN Datastore
Q1. How many disks are in this disk group?
A1. Three disks.
Q2. What are the disk drive types?
A2. All three disks are flash drives.
Q3. What disk tier does each drive belong to?
A3. One 5 GB flash drive is used for the cache tier, and two 10 GB flash drives are used for
the capacity tier.
118
Q1. Why is the policy's effective free space the value that it is?
A1. Because the storage policy uses RAID 1 (mirroring), RAID 1 provides full redundancy. A
full copy of the VM is maintained and, therefore, the VM takes up twice the amount of
space as a VM that is not mirrored.
Lab 21 Working with Snapshots
Q1. Where is the You are here pointer located?
A1. Under the snapshot called With cpubusy.
Q2. Where is the You are here pointer located now?
A2. Under the snapshot called Without iometer and cpubusy.
Q3. Did the Win10-02 virtual machine power off and why?
A3. Yes. The virtual machine powered off because the memory state was not preserved.
Q4. Is either IOMETER.EXE or CPUBUSY.VBS on the desktop?
A4. No. These files were deleted before creating the snapshot called Without iometer and
cpubusy.
Q5. Did the virtual machine power off? Why or why not?
A5. No. The virtual machine did not power off because the memory state was preserved.
Q6. Is CPUBUSY.VBS on the desktop?
A6. Yes.
Q7. Is IOMETER.EXE on the desktop?
A7. No.
Q1. Did the virtual machine power off?
A1. No.
Q2. In the virtual machine console, is CPUBUSY on the desktop?
A2. Yes. The CPUBUSY file is still on the desktop because deleting the snapshot does not
change the virtual machine's current state. Deleting the snapshot removes the ability to
return to that snapshot's point in time.
Q1. Were all the remaining snapshots deleted from the Manage Snapshots window?
A1. Yes.
Q2. Is CPUBUSY on the desktop. If so, why?
A2. Yes. The current state of the virtual machine is not altered. Snapshots are consolidated
and then removed. The option to revert to those earlier points in time is no longer
available.
119
Lab 22 Controlling VM Resources
Q1. Why are the values similar?
A1. The values are similar because the CPU share allocation of Win10-02 and Win10-04 gives
them equal share of the CPU on which they are both running.
Q1. What is the difference in performance between the two virtual machines?
A1. Win10-04 has only one-fourth of the CPU shares that Win10-02 has. So Win10-04
receives only one-fourth of the CPU cycles of the logical CPU to which the virtual
machines are pinned.
Lab 23 Monitoring Virtual Machine Performance
Q1. Did the CPU ready value change? If it did, what is the reason for the change?
A1. Yes. After the scripts stop, the CPU ready value decreases significantly because CPU
contention does not occur.
Lab 25 Implementing vSphere DRS Clusters
Q1. Are any VMs experiencing resource contention?
A1. Yes. Three VMs are experiencing serious contention.
Q2. How many vSphere DRS recommendations and DRS faults are shown?
A2. The answer might vary, but you should see at least one recommendation.
Q3. Look at the DRS Score. Are Win10-02, Win10-04, and Win10-06 experiencing serious
CPU contention?
A3. Yes, they should be experiencing serious CPU contention.
Q4. Are any new recommendations listed?
A4. No.
Q5. Have the cluster and VM DRS scores improved?
A5. Yes.
Lab 26 Using vSphere HA
Q1. Does the number of protected virtual machines match the number of powered-on virtual
machines in the cluster?
A1. Yes. If both hosts are added to the cluster and no errors occur on the cluster, the number
of protected VMs equals the number of powered-on VMs.
Q2. How many datastores are used to monitor heartbeat?
A2. Two datastores. Because both datastores are shared by all the hosts in the cluster, the
datastores are automatically selected for heartbeating.
Q1. Do you see any warning messages about no host management network redundancy?
120
A1. No, the warning messages are no longer present.
Q1. Do you see the virtual machines that were running on this host (the original primary host)
and whose names you recorded earlier?
A1. No. The virtual machines previously running on this host are running on the remaining host
in the cluster.
Q2. Has the primary host changed?
A2. Yes. The secondary host is elected as the new primary host.
121