Sample
Sample
x Cert Guide
Companion Website and Pearson Test Prep Access Code
Access interactive study tools on this book’s companion website, including practice
test software, review exercises, Key Term flash card application, a study planner, and
more!
To access the companion website, simply follow these steps:
1. Go to www.pearsonitcertification.com/register.
6. Under the book listing, click on the Access Bonus Content link.
When you register your book, your Pearson Test Prep practice test access code will
automatically be populated with the book listing under the Registered Products tab.
You will need this code to access the practice test that comes with this book. You
can redeem the code at PearsonTestPrep.com. Simply choose Pearson IT Certi-
fication as your product group and log into the site with the same credentials you
used to register your book. Click the Activate New Product button and enter the
access code. More detailed instructions on how to redeem your access code for both
the online and desktop versions can be found on the companion website.
If you have any issues accessing the companion website or obtaining your Pearson
Test Prep practice test access code, you can contact our support team by going to
pearsonitp.echelp.org.
This page intentionally left blank
VCP-DCV for vSphere 8.x
Cert Guide
$PrintCode PROOFREADER
Donna E. Mulder
Trademarks TECHNICAL EDITOR
All terms mentioned in this book that are known to be trademarks or service Joseph Cooper
marks have been appropriately capitalized. Pearson IT Certification cannot attest PUBLISHING
to the accuracy of this information. Use of a term in this book should not be COORDINATOR
regarded as affecting the validity of any trademark or service mark. Cindy Teeters
DESIGNER
Warning and Disclaimer
Chuti Prasertsith
Every effort has been made to make this book as complete and as accurate as pos-
COMPOSITOR
sible, but no warranty or fitness is implied. The information provided is on an “as
codeMantra
is” basis. The authors and the publisher shall have neither liability nor responsi-
bility to any person or entity with respect to any loss or damages arising from the
information contained in this book.
Special Sales
For information about buying this title in bulk quantities, or for special sales
opportunities (which may include electronic versions; custom cover designs; and
content particular to your business, training goals, marketing focus, or branding
interests), please contact our corporate sales department at corpsales@pearsoned.
com or (800) 382-3419.
For government sales inquiries, please contact [email protected].
For questions about sales outside the U.S., please contact [email protected].
Pearson’s Commitment to Diversity, Equity, and
Inclusion
Pearson is dedicated to creating bias-free content that reflects the diversity of all
learners. We embrace the many dimensions of diversity, including but not limited
to race, ethnicity, gender, socioeconomic status, ability, age, sexual orientation, and
religious or political beliefs.
Education is a powerful force for equity and change in our world. It has the poten-
tial to deliver opportunities that improve lives and enable economic mobility. As we
work with authors to create content for every product and service, we acknowledge
our responsibility to demonstrate inclusivity and incorporate diverse scholarship so
that everyone can achieve their potential through learning. As the world’s leading
learning company, we have a duty to help drive change and live up to our purpose to
help more people create a better life for themselves and to create a better world.
Our ambition is to purposefully contribute to a world where
■ Everyone has an equitable and lifelong opportunity to succeed through
learning
■ Our educational products and services are inclusive and represent the rich
diversity of learners
■ Our educational content accurately reflects the histories and experiences of the
learners we serve
■ Our educational content prompts deeper discussions with learners and moti-
vates them to expand their own learning (and worldview)
While we work hard to present unbiased content, we want to hear from you about
any concerns or needs with this Pearson product so that we can investigate and
address them.
Please contact us with concerns about any potential bias at
https://www.pearson.com/report-bias.html.
Contents at a Glance
Introduction xxvi
PART I: VSPHERE ARCHITECTURE, INTEGRATION, AND REQUIREMENTS
CHAPTER 1 vSphere Overview, Components, and Requirements 3
CHAPTER 2 Storage Infrastructure 31
CHAPTER 3 Network Infrastructure 91
CHAPTER 4 Clusters and High Availability 131
CHAPTER 5 vCenter Server Features and Virtual Machines 167
CHAPTER 6 VMware Product Integration 205
CHAPTER 7 vSphere Security 237
PART II: VSPHERE INSTALLATION/CONFIGURATION
CHAPTER 8 vSphere Installation 287
CHAPTER 9 Configuring and Managing Virtual Networks 331
PART III: VSPHERE MANAGEMENT AND OPTIMIZATION
CHAPTER 10 Managing and Monitoring Clusters and Resources 365
CHAPTER 11 Managing Storage 415
CHAPTER 12 Managing vSphere Security 471
CHAPTER 13 Managing vSphere and vCenter Server 515
CHAPTER 14 Managing Virtual Machines 573
CHAPTER 15 Final Preparation 613
APPENDIX A Answers to the “Do I Know This Already?” Quizzes and
Review Questions 617
Glossary 637
Index 645
ONLINE ELEMENTS:
APPENDIX B Memory Tables
APPENDIX C Memory Table Answers
APPENDIX D Study Planner
Table of Contents
Introduction xxvi
Appendix A Answers to the “Do I Know This Already?” Quizzes and Review
Questions 617
Glossary 637
Index 645
Online Elements:
Dedicated to Madison, Emma, Jaxon, Ethan, Eli, and Robbie, the six wonderful children
to whom I am blessed to be known as “Grampy.” They fill my days with joy and fun,
especially after a hard day of writing or working for their namesake, MEJEER, LLC.
—John Davis
First and foremost, I would like to dedicate this book to my loving wife, Sharyl. Without
your support, I would not be able to commit the time necessary to co-author a book.
Thank you for believing in me and allowing me to have the time for my many
endeavors. I would also like to dedicate this book to my children: Zachary, Brianna,
Eileen, Susan, Keenan, and Maura.
—Steve Baca
Acknowledgments
Thanks to my wife and best friend, Delores, who tolerates my late-night writing,
supports my recent business venture, and makes me happy every day. Thanks to my
parents, Monica and Norman Davis, who provided me with a great education and
taught me the importance of hard work. Thanks to God for placing me in an
environment with unmeasurable blessings and opportunities.
I would like to thank my co-authors and partners, Steve Baca and Owen Thomas.
Thanks to our technical editor, Joe Cooper, for his hard work and dedication.
Special thanks to Nancy Davis (executive editor) and Ellie Bru (development editor)
for coordinating everything and keeping this project moving.
—John Davis
There are so many people to acknowledge and thank for making this book possible.
First, thanks to my wife and family for supporting me while writing this book. I
would also like to thank my co-authors, John Davis and Owen Thomas, who deserve
much of the credit for this book. Thank you to the production team and editors at
Pearson, who do a tremendous amount of work from the initial planning of the book
to the final printing.
—Steve Baca
About the Technical Reviewer
Reader Services
Register your copy of VCP-DCV for vSphere 8.x Cert Guide at
www.pearsonitcertification.com for convenient access to downloads, updates,
and corrections as they become available. To start the registration process, go to
www.pearsonitcertification.com/register and log in or create an account.* Enter the
product ISBN 9780138169886 and click Submit. When the process is complete, you
will find any available bonus content under Registered Products.
*Be sure to check the box that you would like to hear from us to receive exclusive
discounts on future editions of this product.
Introduction
This book focuses on one major goal: helping you prepare to pass the VMware
vSphere 8.x Professional (2V0-21.23) exam, which is a key requirement for earning
the VCP-DCV 2023 certification. This book may be useful for secondary purposes,
such as learning how to implement, configure, and manage a vSphere environment
or preparing to take other VCP-DCV qualifying exams.
The rest of this introduction provides details on the VCP-DCV certification, the
2V0-21.23 exam, and this book.
VCP-DCV Requirements
The primary objective of the VCP-DCV 2023 certification is to demonstrate that
you have mastered the skills to successfully install, configure, and manage VMware
vSphere 8 environments. You can find the exam requirements, objectives, and other
details on the certification web portal, at http://mylearn.vmware.com/portals/
certification/. On the website, navigate to the Data Center Virtualization track and
to the VCP-DCV certification. Examine the VCP-DCV 2023 requirements based
on your qualifications. For example, if you select that you currently hold no VCP
certifications, then the website indicates that your path to certification is to gain
experience with vSphere 8.0, attend one of the following required training courses,
and pass the Professional vSphere 8.0 (2V0-21.23) exam:
■ VMware vSphere: Install, Configure, Manage [V8]
■ VMware vSphere: Optimize, Scale, and Secure [V8]
■ VMware vSphere: Troubleshooting [V8]
■ VMware vSphere: Fast Track [V8]
If you select that you currently hold a VCP-DCV 2020 or newer certification, the
website indicates that your path includes a recommendation, but not a requirement,
to take a training course.
VMware updates the VCP-DCV certification requirements each year. So, the
requirements for the VCP-DCV 2024 certification may differ slightly from VCP-
DCV 2023 certification. Likewise, VMware updates the qualifying exams. Each
year, as VMware updates the Professional VMware vSphere 8.x exam, the authors of
this book will create an appendix to supplement the original book. To prepare for a
future version of the exam, download the corresponding online appendix from the
book’s companion website and use it to supplement the original book.
Introduction xxvii
After you identify your path to certification, you can select the Professional VMware
vSphere 8.x (2V0-21.23) exam to closely examine its details and to download the
Exam Preparation Guide (also known as the exam blueprint).
■ Objective 5.13: Complete lifecycle activities for VMware vSphere with Tanzu
■ 5.13.1: Update Supervisor cluster
■ 5.13.2: Back up and restore VMware vSphere with Tanzu
Section 6: Troubleshooting and Repairing
■ Objective 6.1: Identify use cases for enabling vSphere Cluster Services (vCLS)
retreat mode
■ Objective 6.2: Differentiate between the main management services in
VMware ESXi and vCenter and their corresponding log files
■ Objective 6.3: Generate a log bundle
NOTE For future exams, download and examine the objectives in the updated exam
blueprint. Be sure to use the future Pearson-provided online appendix specific to the
updated exam.
NOTE Section 3 does not apply to the 2V0-21.23 exam, but it may be used for other
exams.
The book includes many features that provide different ways to study so you can
be ready for the exam. If you understand a topic when you read it but do not study
it any further, you probably will not be ready to pass the exam with confidence.
The features included in this book give you tools that help you determine what you
know, review what you know, better learn what you don’t know, and be well prepared
for the exam. These tools include:
■ “Do I Know This Already?” Quizzes: Each chapter begins with a quiz that
helps you determine the amount of time you need to spend studying that
chapter.
■ Foundation Topics: These are the core sections of each chapter. They explain
the protocols, concepts, and configuration for the topics in that chapter.
■ Exam Preparation Tasks: This section of each chapter lists a series of study
activities that should be done after reading the “Foundation Topics” section.
Each chapter includes the activities that make the most sense for studying the
topics in that chapter. The activities include the following:
■ Key Topics Review: The Key Topic icon appears next to the most
important items in the “Foundation Topics” section of the chapter. The
“Key Topics Review” section lists the key topics from the chapter and
their page numbers. Although the contents of the entire chapter could be
on the exam, you should definitely know the information listed for each
key topic. Review these topics carefully.
■ Memory Tables: To help you exercise your memory and memorize some
important facts, memory tables are provided. The memory tables contain
only portions of key tables provided previously in the chapter, enabling
you to complete the table or list. Appendix B, “Memory Tables,” provides
the incomplete tables, and Appendix C, “Memory Tables Answer Key,”
includes the completed tables (answer keys). These appendixes are also
provided on the companion website that is provided with your book.
■ Define Key Terms: The VCP-DCV exam requires you to learn and
know a lot of related terminology. This section lists some of the most
important terms from the chapter and asks you to write a short definition
and compare your answer to the glossary.
■ Practice Exams: The companion website contains an exam engine.
Book Organization
The chapters in this book are organized such that Chapters 1 through 7 provide in-
depth material on vSphere concepts, and Chapters 8 through 14 describe procedures
xxxvi VCP-DCV for vSphere 8.x Cert Guide
Companion Website
Register this book to get access to the Pearson IT Certification test engine and
other study materials plus additional bonus content. Check this site regularly for
new and updated postings written by the authors that provide further insight into
the more troublesome topics on the exam. Be sure to check the box indicating that
you would like to hear from us to receive updates and exclusive discounts on future
editions of this product or related products.
To access this companion website, follow these steps:
Step 1. Go to www.pearsonITcertification.com/register and log in or create
a new account.
Step 2. Enter the ISBN 9780138169886.
Step 3. Answer the challenge question as proof of purchase.
Step 4. Click on the Access Bonus Content link in the Registered Products
section of your account page to be taken to the page where your
downloadable content is available.
NOTE Keep in mind that many of the companion content files—especially image
and video files—are very large.
If you are unable to locate the files for this title by following these steps, please visit
www.pearsonITcertification.com/contact and select the Site Problems/Comments
option. Our customer service representatives will assist you.
NOTE After you register your book, your code can always be found in your account
under the Registered Products tab.
Once you have the access code, to find instructions about both the PTP web app
and the desktop app, follow these steps:
Step 1. Open this book’s companion website as shown earlier in this Introduction
under the heading, “Companion Website.”
Step 2. Click the Practice Exams button.
Step 3. Follow the instructions listed there for both installing the desktop app
and using the web app.
Note that if you want to use the web app only at this point, just navigate to
pearsontestprep.com, log in using the same credentials used to register your book
or purchase the Premium Edition, and register this book’s practice tests using the
registration code you just found. The process should take only a couple of minutes.
In addition to these three modes, you will be able to select the source of your ques-
tions. You can choose to take exams that cover all of the chapters or you can narrow
your selection to just a single chapter or the chapters that make up specific parts in
the book. All chapters are selected by default. If you want to narrow your focus to
individual chapters, simply deselect all the chapters and then select only those on
which you wish to focus in the Objectives area.
You can also select the exam banks on which to focus. Each exam bank comes com-
plete with a full exam of questions that cover topics in every chapter. You can have
the test engine serve up exams from all test banks or just from one individual bank
by selecting the desired banks in the exam bank area. There are several other cus-
tomizations you can make to your exam from the exam settings screen, such as the
time of the exam, the number of questions served up, whether to randomize ques-
tions and answers, whether to show the number of correct answers for multiple-
answer questions, and whether to serve up only specific types of questions. You can
also create custom test banks by selecting only questions that you have marked or
questions on which you have added notes.
Cover: FrameRatio/Shutterstock
Figure 5-1, Figure 5-2, Figure 5-3, Figure 5-4, Figure 8-1, Figure 10-1, Figure 10-2,
Figure 10-3, Figure 10-4, Figure 13-1, Figure 13-2: VMware, Inc.
CHAPTER 4
Table 4-1 “Do I Know This Already?” Foundation Topics Section-to-Question Mapping
Foundation Topics Section Questions
Cluster Concepts and Overview 1
Distributed Resource Scheduler (DRS) 2–4
vSphere High Availability (HA) 5–7
Other Resource Management and Availability Features 8–10
2. In vSphere 8.0, you want to configure the DRS migration threshold such that
it is at the minimum level at which virtual machine happiness is considered.
Which of the following values should you choose?
a. Level 1
b. Level 2
c. Level 3
d. Level 4
e. Level 5
3. Which of the following is not a good use for resource pools in DRS?
a. To delegate control and management
b. To impact the use of network resources
c. To impact the use of CPU resources
d. To impact the use of memory resources
4. You want to use shares to give high-priority resource access to a set of vir-
tual machines in a resource pool, without concern for the relative number of
objects in the pool compared to other pools. Which feature is helpful?
a. Limits
b. Standard shares
c. Scalable shares
d. DRS advanced settings
5. You are configuring vSphere HA in a cluster. You want to configure the cluster
to use a specific host as a target for failovers. Which setting should you use?
a. Host Failures Cluster Tolerates
b. Define Host Failover Capacity By set to Cluster Resource Percentage
c. Define Host Failover Capacity By set to Slot Policy (Powered-on VMs)
d. Define Host Failover Capacity By set to Dedicated Failover Hosts
e. Define Host Failover Capacity By set to Disabled
6. You are enabling VM Monitoring in a vSphere HA cluster. You want to set the
monitoring level such that its failure interval is 60 seconds. Which of the
following options should you choose?
a. High
b. Medium
Chapter 4: Clusters and High Availability 133
c. Low
d. Normal
9. You are configuring vSphere Fault Tolerance (FT) in a vSphere 8.0 environ-
ment. What is the maximum number of virtual CPUs you can use with an
FT-protected virtual machine?
a. One
b. Two
c. Four
d. Eight
10. You are concerned about service availability for your vCenter Server. Which of
the following statements is true?
a. If a vCenter service fails, VMware Service Lifecycle Manager restarts it.
b. If a vCenter service fails, VMware Lifecycle Manager restarts it.
c. If a vCenter service fails, vCenter Server HA restarts it.
d. VMware Service Lifecycle Manager is a part of the PSC.
134 VCP-DCV for vSphere 8.x Cert Guide
Foundation Topics
to be vMotion compatible. The clock speed, cache size, and number of cores can
differ between source and target processors. When you start a vMotion migration or
a migration of a suspended virtual machine, the wizard checks the destination host
for compatibility; it displays an error message if problems exist. By using EVC, you
can allow vMotion between some processors that would normally be incompatible.
The CPU instruction set that is available to a virtual machine guest OS is deter-
mined when the virtual machine is powered on. This CPU feature set is based on
the following items:
■ The host CPU family and model
■ Settings in the BIOS that might disable CPU features
■ The ESX/ESXi version running on the host
■ The virtual machine’s compatibility setting
■ The virtual machine’s guest operating system
EVC ensures that all hosts in a cluster present the same CPU feature set to vir-
tual machines, even if the actual CPUs on the hosts differ. If you enable the EVC
cluster setting, you can configure the EVC Mode with a baseline CPU feature set.
EVC ensures that hosts in a cluster use the baseline feature set when presenting an
instruction set to a guest OS. EVC uses AMD-V Extended Migration technology
for AMD hosts and Intel FlexMigration technology for Intel hosts to mask proces-
sor features; this allows hosts to present the feature set of an earlier processor gener-
ation. You should configure EVC Mode to accommodate the host with the smallest
feature set in the cluster.
The EVC requirements for hosts include the following:
■ ESXi 6.7 or later is required.
■ Hosts must be attached to a vCenter Server.
■ CPUs must be from a single vendor (either Intel or AMD).
■ If the AMD-V, Intel-VT, AMD NX, or Intel XD features are available in the
BIOS, they need to be enabled.
■ Check the VMware Compatibility Guide to ensure that CPUs are supported for
EVC Mode.
NOTE You can apply a custom CPU compatibility mask to hide host CPU features
from a virtual machine, but VMware does not recommend doing so.
You can configure the EVC settings by using the Quickstart > Configure Cluster
workflow in the vSphere Client. You can also configure EVC directly in the cluster
settings. The options for VMware EVC are Disable EVC, Enable EVC for AMD
Chapter 4: Clusters and High Availability 137
Hosts, and Enable EVC for Intel Hosts. You can also configure per-VM EVC, as
described in Chapter 5, “vCenter Server Features and Virtual Machines.”
If you choose Enable EVC for Intel Hosts, you can set the EVC Mode setting to
one of the options described in Table 4-2.
If you choose Enable EVC for AMD Hosts, you can set the EVC Mode setting to
one of the options described in Table 4-3.
Starting with vSphere 7.0 Update 1, EVC provides a feature for Virtual Shared
Graphics Acceleration (vSGA), allowing multiple virtual machines to share GPUs
and leverage the 3D graphics acceleration capabilities.
vSAN Services
You can enable DRS, vSphere HA, and vSAN at the cluster level. The following
sections provide details on DRS and vSphere HA. For details on vSAN, see Chapter 2.
Network-Aware DRS
In vSphere 6.5, DRS considers the utilization of host network adapters during initial
placement and load balancing, but it does not balance the network load. Instead, its
goal is to ensure that the target host has sufficient available network resources. It
works by eliminating hosts with saturated networks from the list of possible migra-
tion hosts. The threshold used by DRS for network saturation is 80% by default.
When DRS cannot migrate VMs due to network saturation, the result may be an
imbalanced cluster.
Beginning with vSphere 7.0, DRS uses a new cost modeling algorithm that is
flexible and balances network bandwidth along with CPU and memory usage.
power on. In vSphere 6.5, the new placement feature is not supported for the
following configurations:
■ Clusters where DPM, Proactive HA, or HA Admission Control is enabled
■ Clusters with DRS configured in Manual Mode
■ Virtual machines with the Manual DRS Override setting enabled
■ Virtual machines that are FT enabled
■ Virtual machines that are part of a vApp
In vSphere 6.7 and later, the new placement is available for all configurations.
DRS Rules
You can configure rules to control the behavior of DRS.
A VM–host affinity rule specifies whether the members of a selected virtual machine
DRS group can run on the members of a specific host DRS group. Unlike a virtual
machine–to–virtual machine (VM–VM) affinity rule, which specifies affinity (or
anti-affinity) between individual virtual machines, a VM–host affinity rule specifies an
affinity relationship between a group of virtual machines and a group of hosts. There are
required rules (designated by “must”) and preferential rules (designated by “should”).
A VM–host affinity rule includes the following components:
■ One virtual machine DRS group
■ One host DRS group
■ A designation of whether the rule is a requirement (“must”) or a preference
(“should”) and whether it is affinity (“run on”) or anti-affinity (“not run on”)
Chapter 4: Clusters and High Availability 143
NOTE A VM–VM rule does not allow the “should” qualifier. You should consider
these as “must” rules.
Resource Pools
Resource pools are container objects in the vSphere inventory that are used to
compartmentalize the CPU and memory resources of a host, a cluster, or a parent
resource pool. Virtual machines run in and draw resources from resource pools. You
can create multiple resource pools as direct children of a standalone host or a DRS
cluster. You cannot create child resource pools on a host that has been added to a
cluster or on a cluster that is not enabled for DRS.
You can use resource pools to organize VMs. You can delegate control over each
resource pool to specific individuals and groups. You can monitor resources and set
alarms on resource pools. If you need a container just for organization and permis-
sion purposes, consider using a folder. If you also need resource management, then
consider using a resource pool. You can assign resource settings such as shares,
reservations, and limits to resource pools.
Use Cases
You can use resource pools to compartmentalize a cluster’s resources and then use
the resource pools to delegate control to individuals or organizations. Table 4-4
provides some use cases for resource pools.
Option Description
Expandable You can enable expandable reservations to effectively allow a child resource
reservations pool to borrow from its parent. Expandable reservations, which are enabled by
default, are considered during admission control. When powering on a virtual
machine, if the resource pool does not have sufficient unreserved resources, the
resource pool can use resources from its parent or ancestors.
For example, say that in a resource pool where 8 GHz is reserved and
expandable reservations are disabled, you try to start nine virtual machines
each with 1 GHz, but the last virtual machine does not start. If you enable
expandable reservations in the resource pool, and its parent pool (or cluster) has
sufficient unreserved CPU resources, you can start the ninth virtual machine.
Limits A limit specifies an upper bound for CPU or memory resources that can be
allocated to a virtual machine or a resource pool.
You can set a limit on the amount of CPU and memory allocated to a resource
pool. The default is unlimited. For example, if you power on multiple CPU-
intensive virtual machines in a resource pool, where the CPU limit is 10 GHz,
then, collectively, the virtual machines cannot use more than 10 GHz CPU
resources, regardless of the pool’s reservation settings, the pool’s share settings,
or the amount of available resources in the parent.
Table 4-6 provides the CPU and memory share values for virtual machines when
using the High, Normal, and Low settings. For resource pools, the share values are
equivalent to those of a virtual machine with four vCPUs and 16 GB memory.
For example, the share values for a resource pool configured with normal CPU
shares and high memory shares are 4000 (that is, 4 × 1000) CPU shares and 327,680
(that is, 16 × 1024 × 20) memory shares.
NOTE The relative priority represented by each share changes with the addition
and removal of virtual machines in a resource pool or cluster. It also changes as you
increase or decrease the shares on a specific virtual machine or resource pool.
Chapter 4: Clusters and High Availability 147
Scalable Shares
In versions since vSphere 7.0, DRS provides scalable shares. The main use case for
scalable shares is a scenario in which you want to use shares to give high-priority
resource access to a set of virtual machines in a resource pool, without concern for
the relative number of objects in the pool compared to other pools. With standard
shares, each pool in a cluster competes for resource allocation with its siblings, based
on the share ratio. With scalable shares, the allocation for each pool factors in the
number of objects in the pool.
For example, consider a scenario in which a cluster with 100 GHz CPU capacity
has a high-priority resource pool with CPU Shares set to High and a low-priority
resource pool with CPU Shares set to Normal, as shown in Figure 4-1. This means
that the share ratio between the pools is 2:1, so the high-priority pool is effectively
allocated twice the CPU resources as the low-priority pool whenever CPU conten-
tion exists in the cluster. The high-priority pool is allocated 66.7 GHz, and the low-
priority pool is effectively allocated 33.3 GHz. In this cluster, 40 virtual machines
of equal size are running, with 32 in the high-priority pool and 8 in the low-priority
pool. The virtual machines are all demanding CPU resources, causing CPU conten-
tion in the cluster. In the high-priority pool, each virtual machine is allocated 2.1
GHz. In the low-priority pool, each virtual machine is allocated 4.2 GHz.
DRS Cluster
CPU Capacity = 100 GHz
32 8
VMs VMs
If you want to change the resource allocation such that each virtual machine in the
high-priority pool is effectively allocated more resources than the virtual machines
in the low-priority pool, you can use scalable shares. If you enable scalable shares
in the cluster, DRS effectively allocates resources to the pools based on the Shares
settings and the number of virtual machines in the pool. In this example, the CPU
shares for the pools provide a 2:1 ratio. Factoring this with the number of virtual
machines in each pool, the allocation ratio between the high-priority pool and the
low-priority pool is 2 times 32 to 1 times 8, or simply 8:1. The high-priority pool is
allocated 88.9 GHz, and the low-priority pool is allocated 11.1 GHz. Each virtual
machine in the high-priority pool is allocated 2.8 GHz. Each virtual machine in the
low-priority pool is allocated 1.4 GHz.
DRS Cluster
XVMs VMs
When you enable vSphere HA on a cluster, the cluster elects one of the hosts to act
as the primary host. The primary host communicates with vCenter Server to report
cluster health. It monitors the state of all protected virtual machines and secondary
hosts. It uses network and datastore heartbeating to detect failed hosts, isolation,
and network partitions. vSphere HA takes appropriate actions to respond to host
failures, host isolation, and network partitions. For host failures, the typical reac-
tion is to restart the failed virtual machines on surviving hosts in the cluster. If a
network partition occurs, a primary host is elected in each partition. If a specific host
is isolated, vSphere HA takes the predefined host isolation action, which may be to
shut down or power down the host’s virtual machines. If the primary host fails, the
surviving hosts elect a new primary host. You can configure vSphere to monitor and
respond to virtual machine failures, such as guest OS failures, by monitoring heart-
beats from VMware Tools.
NOTE Although vCenter Server is required to implement vSphere HA, the health
of an HA cluster is not dependent on vCenter Server. If vCenter Server fails, vSphere
HA still functions. If vCenter Server is offline when a host fails, vSphere HA can fail
over the affected virtual machines.
vSphere HA Requirements
When planning a vSphere HA cluster, you need to address the following
requirements:
■ The cluster must have at least two hosts, licensed for vSphere HA.
■ Hosts must use static IP addresses or guarantee that IP addresses assigned by
DHCP persist across host reboots.
150 VCP-DCV for vSphere 8.x Cert Guide
NOTE The Virtual Machine Startup and Shutdown (automatic startup) feature is
disabled and unsupported for all virtual machines residing in a vSphere HA cluster.
NOTE If multiple hosts fail, the virtual machines on the failed host migrate first in
order of priority, and then the virtual machines from the next host migrate.
Chapter 4: Clusters and High Availability 151
Heartbeats
The primary host and secondary hosts exchange network heartbeats every second.
When the primary host stops receiving these heartbeats from a secondary host,
it checks for ping responses or the presence of datastore heartbeats from the
secondary host. If the primary host does not receive a response after checking for
a secondary host’s network heartbeat, ping, or datastore heartbeats, it declares that
the secondary host has failed. If the primary host detects datastore heartbeats for
a secondary host but no network heartbeats or ping responses, it assumes that the
secondary host is isolated or in a network partition.
If any host is running but no longer observes network heartbeats, it attempts to ping
the set of cluster isolation addresses. If those pings also fail, the host declares itself to
be isolated from the network.
If you disable vSphere HA admission control, then you enable the cluster to allow
virtual machines to power on regardless of whether they violate availability con-
straints. In the event of a host failover, you may discover that vSphere HA cannot
start some virtual machines.
In vSphere 8.0, the default admission control setting is Cluster Resource Percentage,
which reserves a percentage of the total available CPU and memory resources in
the cluster. For simplicity, the percentage is calculated automatically by defining the
number of host failures to tolerate (FTT). The percentage is dynamically changed
as hosts are added to the cluster or removed from it. Another new enhancement is
the Performance Degradation VMs Tolerate setting, which controls the amount of
performance reduction that is tolerated after a failure. A value of 0% indicates that
no performance degradation is tolerated.
With the Slot Policy option, vSphere HA admission control ensures that a specified
number of hosts can fail, leaving sufficient resources in the cluster to accommodate
the failover of the impacted virtual machines. Using the Slot Policy option, when
you perform certain operations, such as powering on a virtual machine, vSphere HA
applies admission control in the following manner:
Step 1. HA calculates the slot size, which is a logical representation of memory
and CPU resources. By default, it is sized to satisfy the requirements for
any powered-on virtual machine in the cluster. For example, it may be
sized to accommodate the virtual machine with the greatest CPU reserva-
tion and the virtual machine with the greatest memory reservation.
Step 2. HA determines how many slots each host in the cluster can hold.
Step 3. HA determines the current failover capacity of the cluster, which is the
number of hosts that can fail while still leaving enough slots to satisfy all
the powered-on virtual machines.
Step 4. HA determines whether the current failover capacity is less than the
configured failover capacity (provided by the user).
Step 5. If the current failover capacity is less than the configured failover capacity,
admission control disallows the operation.
If a cluster has a few virtual machines that have much larger reservations than the
others, they will distort slot size calculation. To remediate this, you can specify an
upper bound for the CPU or memory component of the slot size by using advanced
options. You can also set a specific slot size (CPU size and memory size). The next
section describes the advanced options that affect the slot size.
Chapter 4: Clusters and High Availability 153
You can override the cluster’s settings for Restart Priority and Isolation Response
for each virtual machine. For example, you might want to prioritize virtual machines
providing infrastructure services such as DNS or DHCP.
At the cluster level, you can create dependencies between groups of virtual
machines. You can create VM groups, host groups, and dependency rules between
the groups. In the rules, you can specify that one VM group cannot be restarted if
another specific VM group is started.
The Maximum per-VM Resets setting can be used to configure the maximum
number of times vSphere HA attempts to restart a specific failing virtual machine
within the reset period.
Proactive HA
Proactive High Availability (Proactive HA) integrates with select hardware part-
ners to detect degraded components and evacuate VMs from affected vSphere hosts
before an incident causes a service interruption. Hardware partners offer a vCen-
ter Server plug-in to provide the health status of the system memory, local stor-
age, power supplies, cooling fans, and network adapters. As hardware components
become degraded, Proactive HA determines which hosts are at risk and places them
into either Quarantine Mode or Maintenance Mode. When a host enters Mainte-
nance Mode, DRS evacuates its virtual machines to healthy hosts, and the host is not
used to run virtual machines. When a host enters Quarantine Mode, DRS leaves the
current virtual machines running on the host but avoids placing or migrating virtual
machines to the host. If you prefer that Proactive HA simply make evacuation rec-
ommendations rather than automatic migrations, you can set Automation Level to
Manual.
The vendor-provided health providers read sensor data in the server and provide the
health state to vCenter Server. The health states are Healthy, Moderate Degrada-
tion, Severe Degradation, and Unknown.
156 VCP-DCV for vSphere 8.x Cert Guide
Predictive DRS
Predictive DRS is a feature in vSphere 6.5 and later that leverages the predictive
analytics of VMware Aria Operations, formerly known as vRealize Operations
(vROps), and vSphere DRS. Together, these two products can provide workload
balancing prior to the occurrence of resource utilization spikes and resource conten-
tion. Every night, Aria Operations calculates dynamic thresholds, which are used to
create forecasted metrics for the future utilization of virtual machines. Aria Opera-
tions passes the predictive metrics to vSphere DRS to determine the best placement
and balance of virtual machines before resource utilization spikes occur. Predictive
DRS helps prevent resource contention on hosts that run virtual machines with
predictable utilization patterns.
The following prerequisites are needed to run Predictive DRS:
■ vCenter Server 6.5 or later is required.
■ Predictive DRS must be configured and enabled in both vCenter Server and
Aria Operations.
■ The vCenter Server and Aria Operations clocks must be synchronized.
are used in the following order: IPMI, iLO, WOL. If a host does not support one of
these protocols, DPM cannot automatically bring a host out of Standby Mode.
DPM is very configurable. As with DRS, you can set DPM’s automation to be
manual or automatic.
NOTE Do not disconnect a host that is in Standby Mode or remove it from a DRS
cluster without first powering it on. Otherwise, vCenter Server is not able to power
the host back on.
To configure IPMI or iLO settings for a host, you can edit the host’s Power Man-
agement settings. You should provide credentials for the Baseboard Management
Controller (BMC) account, the IP address of the appropriate NIC, and the MAC
address of the NIC.
Using WOL with DPM requires that the following prerequisites be met:
■ ESXi 3.5 or later is required.
■ vMotion must be configured.
■ The vMotion NIC must support WOL.
■ The physical switch port must be set to automatically negotiate the link speed.
Before enabling DPM, use the vSphere Client to request the host to enter Standby
Mode. After the host powers down, right-click the host and attempt to power on.
If this is successful, you can allow the host to participate in DPM. Otherwise, you
should disable power management for the host.
You can enable DPM in a DRS cluster’s settings. You can set Automation Level to
Off, Manual, or Automatic. When this option is set to Off, DPM is disabled. When
it is set to Manual, DPM makes recommendations only. When it is set to Automatic,
DPM automatically performs host power operations as needed.
Much as with DRS, with DPM you can control the aggressiveness of DPM (that is,
the DPM threshold) with a slider bar in the vSphere Client. The DRS threshold and
the DPM threshold are independent of one another. You can override automation
settings per host. For example, for a 16-host cluster, you might want to set DPM
Automation to Automatic on only 8 of the hosts.
The following vSphere features are not supported for FT-protected virtual
machines:
■ Snapshots (An exception is that disk-only snapshots created for vStorage APIs
for Data Protection [VADP] backups are supported for FT but not for legacy
FT.)
■ Storage vMotion
■ Linked clones
■ Virtual Volumes datastores
■ Storage-based policy management (However, vSAN storage policies are
supported.)
■ I/O filters
■ Disk encryption
■ Trusted Platform Module (TPM)
■ Virtual Based Security (VBS)–enabled VMs
■ Universal Point in Time snapshots (a next-generation vSAN feature)
■ Physical raw device mappings (RDMs) (However, virtual RDMs are supported
for legacy FT.)
■ Virtual CD-ROMs for floppy drives backed by physical devices
■ USB devices, sound devices, serial ports, and parallel ports
■ N-Port ID Virtualization (NPIV)
■ Network adapter passthrough
■ Hot plugging devices (Note that the hot plug feature is automatically disabled
when you enable FT on a virtual machine.)
■ Changing the network where a virtual NIC is connected
160 VCP-DCV for vSphere 8.x Cert Guide
In vSphere 6.5, FT is supported with DRS only when EVC is enabled. You can
assign a DRS automation to the primary VM and let the secondary VM assume
the same setting. If you enable FT for a virtual machine in a cluster where EVC is
disabled, the virtual machine DRS automation level is automatically disabled. In ver-
sions since vSphere 6.7, EVC is not required for FT to support DRS.
To enable FT, you first create a VMkernel virtual network adapter on each host
and connect to the FT Logging network. You should enable vMotion on a separate
VMkernel adapter and network.
When you enable FT protection for a virtual machine, the following events occur:
■ If the primary VM is powered on, validation tests occur. If validation is passed,
then the entire state of the primary VM is copied and used to create the sec-
ondary VM on a separate host. The secondary VM is powered on. The virtual
machine’s FT status is Protected.
■ If the primary VM is powered off, the secondary VM is created and registered
to a host in the cluster but not powered on. The virtual machine FT Status
setting is Not Protected, VM not Running. When you power on the primary
VM, the validation checks occur, and the secondary VM is powered on. Then
FT Status changes to Protected.
Chapter 4: Clusters and High Availability 161
Legacy FT VMs can exist only on ESXi hosts running on vSphere versions earlier
than 6.5. If you require legacy FT, you should configure a separate vSphere 6.0
cluster.
NOTE Do not confuse VMware Service Lifecyle Manager with VMware vSphere
Lifecycle Manager, which provides simple, centralized lifecycle management for ESXi
hosts through the use of images and baselines.
162 VCP-DCV for vSphere 8.x Cert Guide
Review Questions
1. You are configuring EVC. Which of the following is not a requirement?
a. A vSphere cluster
b. A DRS cluster
c. CPUs in the same family
d. CPUs with the same base instruction set
2. In vSphere 8.0, you want to configure the DRS migration threshold such that
it is at the maximum level at which resource contention is considered but
virtual machine happiness is not. Which of the following values should you
choose?
a. Level 1
b. Level 2
c. Level 3
d. Level 4
e. Level 5
LAGs (link aggregation groups), 95, link aggregation groups (LAGs), 95,
350–354 350–354
LANs, virtual. See VLANs (virtual LANs) linked clones, 182, 200
latency sensitivity, VMs (virtual machines), load balancing, 359
395 DRS (Distributed Resource Scheduler),
lazy zeroed thick virtual disks, 81 140
LCM (Lifecycle Manager), 52, 219, 228, SDRS (Storage DRS), 83
318–319. See also vLCM (vSphere load-based NIC teaming, 108
Lifecycle Manager) Load-Based Teaming Daemon, 258
LDAP (Lightweight Directory Access local storage, 35
Protocol), 11, 309, 313 Lockdown Mode, ESXi, 496–497
least significant bit (LSB), 101 lockout policy, 316
legacy fault tolerance, 524 Log Assist (Skyline), 215
legacy hosts, SSL certificate verification for, log files
561 Aria for Logs, 217–218
libraries, content, 603 ESXi, 405–407, 503
adding items to, 608 limiting number of, 271
authentication, 605 log levels, 408–409
creating, 604–605 monitoring and management, 405–412
definition of, 604 system event log
deploying VMs with, 608–609 configuration, 409–410
managing VM templates in, 609 streaming events to, 401–402
overview of, 176–178 viewing, 401
permissions, 606–607 vRLI (vRealize Log Insight), 411–412
publishing, 605 vCenter Server, 407–408
subscribing to, 606 VMware Skyline, 215
synchronization options, 607 vSAN, 68
versioning, 177 logical unit numbers (LUNs), 35
License Service, 11 LSB (least significant bit), 101
licenses LUNs (logical unit numbers), 35
vSAN, 67–68, 421–422 LZ4, 58
vSphere, 8–9
LicenseSevice.Administrators group, 315 M
Lifecycle Manager (LCM), 52, 219, 228, MAC (media access control) addresses,
318–319. See also vLCM (vSphere 102–103
Lifecycle Manager) definition of, 94
Lightweight Directory Access Protocol network security policies and, 102–103
(LDAP), 11, 309, 313 MAC Address Changes option, network
line charts, 379 security policies, 103
Link Aggregation Control Protocol Machine certificate store, 244
(LACP), 95, 118–119 machine learning (ML), 601
link aggregation groups, 350–354 machine SSL certificates, 243
management 663
vSphere with Tanzu, 208–213, 521–523 vRLI (vRealize Log Insight), 411–412
vSphere+213–214 VRMS (vSphere Replication Management
VMware Remote Console (VMRC), Service), 24, 225
577–578 VRS (vSphere Replication Service), 24, 225
VMware Service Broker, 27 vSAN. See also vSphere HA
VMware Service Lifecycle Manager, benefits of, 47–48
161–162 best practices, 68
VMware Skyline, 215–216 boot devices and, 68
Skyline Advisor, 392 characteristics of, 48–50
Skyline Health, 390–391 clusters
VMware Tools, 153, 188, 189, 221 creating with Quickstart, 419
compatibility, 524 encryption in, 61, 434–437
configuration, 324 expanding, 424–426
installation, 578–580 extending across two sites, 428–430
lifecycle management, 579 managing devices in, 430–432
performance counters, 272 requirements for, 67
upgrading, 578–580 space efficiency in, 58–60, 433
virtual machine monitoring and manage- standard, 53
ment, 189, 395 stretched, 55–58
VMware vCenter Agent (vpxa), 259 two-host, 54
VMware vCloud Director, 27 compatibility, 524
VMware vCloud Suite, 27 component state, 51
VMware vSphere 8 STIG Readiness Guide, datastores
484 overview of, 43
VMware Workspace ONE Access, 222 types of, 50
VMWARE_HTTPSPROXY environment viewing, 422
variable, 578 deployment, 53–58
VMwareAccepted VIBs, 498 disabling, 423
VMwareCertified VIBs, 498 disk version, 524
VMware-I/O Vendor Program (IOVP), 75 DRS (Distributed Resource Scheduler)
VMX files, 179, 271 automation modes, 139
vmx.log.guest.level option, 579 description of, 7
vNICs (virtual NICs), 96 evacuation workflow, 141
vobd, 547 memory metric for load balancing, 140
vPMeM (Virtual Persistent Memory), 141, migration sensitivity, 143–144
458–459 network-aware DRS, 140
vPMem (Virtual PMem), 458–459 NVM (non-volatile memory) support,
vPMemDisk (Virtual Persistent Memory 141
Disk), 141, 459 Predictive DRS, 156, 374
vpxd certificate store, 244 recent enhancements, 139–142
vpxd-extension certificate store, 244 resource pools, 144–148
vpxuser, 499 rules, 142–143
vRealize Suite. See Aria Suite virtual machine distribution, 140
vSphere 689