VSICM6 PowerPoint

3/20/2018
Course Introduction Learner Objectives (2)
Module 1 By the end of this course, you should be able to meet the following
objectives:
• Migrate virtual machines with VMware vSphere® vMotion®
VMware vSphere: • Use VMware vSphere® Storage vMotion® to migrate virtual machine storage
• Monitor resource usage and manage resource pools
Install, Configure, Manage
• Use VMware vRealize™ Operations Manager™ to identify and solve problems
through analytics and alerts
• Manage VMware vSphere® High Availability and VMware vSphere® Fault
Tolerance
• Use VMware vSphere® Replication™ and VMware vSphere® Data
Protection™ to replicate virtual machines and perform data recovery
• Use vSphere® Distributed Resource Scheduler™ clusters to improve host
scalability
• Use VMware vSphere® Update Manager™ to apply patches and perform
upgrades
• Perform basic troubleshooting of ESXi hosts, virtual machines, and vCenter
Server
VMware vSphere: Install, Configure, Manage 1-4

© 2015 VMware Inc. All rights reserved. © 2015 VMware Inc. All rights reserved.
Importance You Are Here

Administrators must have the knowledge, skills, and abilities to build and
1. Course Introduction 7. Virtual Machine Management
run a VMware vSphere® environment.
2. Software-Defined Data Center 8. Resource Management and
You must know how to install and configure VMware ESXi™ hosts and Monitoring
VMware vCenter Server™. You must also know how to manage ESXi 3. Creating Virtual Machines
hosts and virtual machines with vCenter Server. 9. vSphere HA and vSphere Fault
4. vCenter Server Tolerance
5. Configuring and Managing 10. Host Scalability
Virtual Networks
11. vSphere Update Manager and
6. Configuring and Managing Host Maintenance
Virtual Storage
12. Installing vSphere Components
VMware vSphere: Install, Configure, Manage 1-2 VMware vSphere: Install, Configure, Manage 1-5
Learner Objectives (1) Typographical Conventions

By the end of this course, you should be able to meet the following The following typographical conventions are used in this course.
objectives:
• Describe the software-defined data center
• Deploy an ESXi host and create virtual machines Monospace Filenames, folder names, path
names, and command names:
• Describe the vCenter Server architecture
Navigate to the VMS folder.
• Deploy a vCenter Server instance or VMware vCenter Server™ Appliance™
Monospace bold What the user types:
• Use vCenter Server to manage an ESXi host Enter ipconfig /release.
• Configure and manage vSphere infrastructure with VMware vSphere® Client™ Boldface User interface controls:
and VMware vSphere® Web Client
Click the Configuration tab.
• Configure virtual networks with vSphere standard switches
Italic Book titles and placeholder
• Use vSphere distributed switches to improve network scalability variables:
• Use vCenter Server to manage various types of storage • vSphere Virtual Machine
• Manage virtual machines, templates, clones, and snapshots Administration
• ESXi_host_name
• Create a vApp
• Describe and use the content library
1
3/20/2018
References VMware Education Overview

Title Location Your instructor will introduce other Education Services offerings available
https://www.vmware.com/support/pubs/vsphere to you:
vSphere Installation and Setup
-esxi-vcenter-server-6-pubs.html • Learning Paths
https://www.vmware.com/support/pubs/vsphere • On-Demand Training
vCenter Server and Host Management
-esxi-vcenter-server-6-pubs.html
• VMware Learning Zone
https://www.vmware.com/support/pubs/vsphere
vSphere Virtual Machine Administration
-esxi-vcenter-server-6-pubs.html • New Certification Framework
vSphere Networking
vSphere Security
vSphere Resource Management
vSphere Availability
vSphere Monitoring and Performance
VMware Online Resources

• VMware vSphere Blog: http://blogs.vmware.com/vsphere/
• VMware Communities: http://communities.vmware.com
• VMware Support: http://www.vmware.com/support
• VMware Education: http://www.vmware.com/education
• VMware Certifications: http://mylearn.vmware.com/portals/certification
• VMware Education and Certification Blog: http://blogs.vmware.com/education/

© 2015 VMware Inc. All rights reserved.
VCP-Core Certification Alignment

VMware vSphere: Install, Configure, Manage aligns with the VCP-Core
certification:
• The VCP-Core exam blueprint served as the basis for the design of this
course.
• You should use the VCP-Core exam blueprint as a reference when preparing
for the test.
• This course should not be used as the only resource for exam preparation.
• VMware certification details can be found at
http://mylearn.vmware.com/portals/certification/

2
3/20/2018
Software-Defined Data Center You Are Here
Module 2 1. Course Introduction 7. Virtual Machine Management

Monitoring
3. Creating Virtual Machines
9. vSphere HA and vSphere Fault
Virtual Networks
Virtual Storage

Importance Module Lessons

VMware vSphere® is based on many components with which a vSphere Lesson 1: Introduction to the Software-Defined Data Center
administrator should be familiar. You must understand the following
concepts and best practices: Lesson 2: vSphere Client
• Virtualization, VMware ESXi™, and the virtual machine Lesson 3: Overview of ESXi
• The fundamental vSphere components and how vSphere can be used

in the software-defined data center
• How VMware vSphere® Client™ and VMware vSphere® Web Client
are used to administer and manage vSphere environments
Learner Objectives
By the end of this lesson, you should be able to meet the following
objectives:
• Compare and contrast physical and virtual architectures
• Describe the benefits of using virtual machines
Lesson 1: • Describe how vSphere interacts with CPUs, memory, networks, and storage
Introduction to the Software- • Describe how vSphere fits into the cloud and the software-defined data center
Defined Data Center
2-5 VMware vSphere: Install, Configure, Manage 2-6

1
3/20/2018
Topology of a Physical Data Center Introducing the Virtual Infrastructure

Administering and maintaining a physical data center is time consuming and Virtualization enables you to run more workloads on a single server by
often inefficient. consolidating the environment so that your applications run on virtual
Applications
machines.
Operating System
Physical Host
Virtual
Machines
Hypervisor
ESXi Host
Fibre
Ethernet
Channel
Fibre
FCoE Ethernet
Storage Channel
FCoE
Storage
iSCSI NFS Local Area Fibre Channel iSCSI Storage NFS Storage Local Area Fibre Channel Storage
Storage Storage Network Storage Network
About Virtual Machines Benefits of Using Virtual Machines

A virtual machine is a software computer that, like a physical computer, Physical Machines Virtual Machines
runs an operating system and applications. Difficult to relocate: Easy to relocate:
• Moves require downtime. • Encapsulated into files.
• Specific to physical hardware. • Independent of physical hardware.
Difficult to manage: Easy to manage:
Virtual Machine Virtual Machine Components
• Require physical maintenance. • Isolated from other virtual machines.
• Operating system • Hardware failures cause downtime. • Insulated from hardware changes.
• VMware Tools™ Hardware has limitations: Provide the ability to support
• Hardware changes limit application
legacy applications.
• Virtual resources such as:
– CPU and memory support. Enable servers to be consolidated.
– Network adapters • One-to-one relationship between
– Disk controllers application and server.
– Parallel and serial ports
Physical Architecture and Virtual Architecture Physical Resource Sharing

Virtualization is a technology that decouples physical hardware from a
computer operating system and provides a solution to many of the
problems that IT staff face.
Physical Architecture Virtual Architecture

Virtual
Resources
Application
vSphere
Operating System vSphere x64
Architecture
x64 Architecture x64 Architecture Physical
Resources
2
3/20/2018
CPU Virtualization Physical and Virtualized Host Memory Usage

In a physical environment, the operating system assumes the ownership In a physical environment, the operating system assumes the ownership
of all the physical CPUs in the system. of all physical memory in the system.
CPU virtualization emphasizes performance and runs directly on the Memory virtualization emphasizes performance and runs directly on the
available CPUs. available RAM.
Application
Application
Operating System vSphere 1 GB 2 GB 8 GB
Operating System vSphere

x64 Architecture x64 Architecture
x64 Architecture x64 Architecture
Physical and Virtual Networking Physical File Systems and VMFS

Virtual Ethernet adapters and virtual switches are key virtual networking VMware vSphere® VMFS enables a distributed storage architecture,
components. allowing multiple ESXi hosts to read or write to the shared storage
concurrently.
Physical Virtual Architecture

Architecture
Application
Application
Operating System Operating System vSphere vSphere

Virtual Switch
x64 Architecture x64 Architecture x64 Architecture x64 Architecture

vSphere
x64 Architecture
Shared Storage: VMFS,
NTFS, ext4, UFS NFS, Virtual SAN
Encapsulation About the Software-Defined Data Center
VM 1 Virtual machine files are stored in directories on a In a software-defined data center, all infrastructure is virtualized, and the
VMFS or NFS datastore. control of the data center is entirely automated by software.
Software-Defined Data Center
Policy-Based Management
VM 2 and Automation Cloud Automation Cloud Operations Cloud Business
Virtualized Infrastructure Hybrid Cloud

Abstract and Pool
VMware and
vCloud Air Data Center Partners
Public Public
Clouds Clouds
Compute Abstraction = Network Abstraction = Storage Abstraction =
Server Virtualization Virtual Networking Software-Defined Storage
VM 3
Datastore: VMFS or NFS
3
3/20/2018
How vSphere Fits into Cloud Computing About Private Clouds

Cloud computing is an approach that uses the efficient pooling of an on- Private clouds are pools of resources dedicated to a single enterprise.
demand, self-managed, virtual infrastructure.
Private Hybrid Public

Cloud Internet Advantages:
Cloud Cloud
• Self-service provisioning
• Elasticity of resources
Enterprise Private Cloud • Rapid and simplified
provisioning
• Secured multitenancy
• Improved use of IT
resources
• Better control of IT
budgets
Gizmo Division Widget Division Human Sales
Resources
About Public Clouds About Hybrid Clouds

In their infrastructure public cloud service, providers host many types of IT assets are housed both internally on customer premises and in public
IT operations for multiple businesses. clouds.
Hybrid
Cloud
Advantages:
App App App
• Customer management of IT Cloud Service Provider
Loads
Loads
Loads
• Rapid and flexible Management Management

deployments Bridge
vSphere vSphere
• Efficient and cost-effective
deployments Private Public
• Secure IT assets Clouds Clouds
• Capital expenses converted
to operating expenses Use Cases
Company Company Company
A B C Disaster recovery Traffic overflow
Quick provisioning Offsite backup
Data archiving Development / QA / test
Review of Learner Objectives

You should be able to meet the following objectives:
• Compare and contrast physical and virtual architectures
• Describe the benefits of using virtual machines
• Describe how vSphere interacts with CPUs, memory, networks, and storage
• Describe how vSphere fits into the cloud and the software-defined data center
Lesson 2:
vSphere Client
VMware vSphere: Install, Configure, Manage 2-23 2-24

4
3/20/2018
Learner Objectives User Interfaces

By the end of this lesson, you should be able to meet the following You use the vSphere Web Client and the vSphere Client to interact with a
objectives: vSphere environment.
• Identify the user interfaces used with the ESXi host and VMware vCenter
Server™
• Download and install vSphere Client ESXi
• Use vSphere Client to access your ESXi hosts and vCenter Server Host
vSphere Client
vCenter
Server
Your vSphere Web Client

Desktop
Downloading vSphere Client Using vSphere Client

You use the vSphere In the vSphere Client login
Client to connect Pointing to the vCenter Server window, you enter the following
remotely to an ESXi system or the ESXi host information:
host and vCenter • Host name or IP address of ESXi
Server from a host or vCenter Server
Windows system.
• User name
Ways to download the • Password
vSphere Client:
Or you can use your Windows
• Use the VMware
session credentials.
vCenter Server
Installer.
• Download the client
from the vCenter
Server system or an
ESXi host. Internet
access is required.
Downloading the vSphere Client to a
supported Windows system
vSphere Client: Configuration Tab Viewing Processor and Memory Configuration

When you log in to an ESXi host, the vSphere Client shows the ESXi You can view processor and memory configuration information for the
host in the left pane. You use the Configuration tab to view or configure ESXi host in the Hardware list on the Configuration tab.
the host’s hardware and software settings.
5
3/20/2018
Viewing and Exporting ESXi Host System Logs Viewing Licensed Features
You can use the vSphere Client to view system logs. You export the You assign a valid license key to your ESXi host through the Licensed
system logs to an archive file and send them to VMware Support. Features link. The Licensed Features pane shows the type of license
and available features.
Lab 1: Installing vSphere Client Review of Learner Objectives

Access the student desktop and install vSphere Client You should be able to meet the following objectives:
1. Access Your Student Desktop System • Identify the user interfaces used with the ESXi host and VMware vCenter
2. Install vSphere Client Server™
• Download and install vSphere Client
• Use vSphere Client to access your ESXi hosts and vCenter Server
Learner Objectives
objectives:
• Describe ESXi host architecture
• Use the vSphere Client to access an ESXi host
• View ESXi host settings:
– Processor and memory configuration
Lesson 3: – Licensing
Overview of ESXi – DNS and routing
– Security profile
• Identify user account best practices

6
3/20/2018
About ESXi Hosts Physical and Virtual Architecture

An ESXi host has the following availability and features: The ESXi hypervisor provides a virtualization layer that abstracts the
• Available for purchase with vSphere or as a free version that can be processor, memory, storage, and networking resources of the physical
downloaded. host and allocates them to multiple virtual machines.
• High security:
– Memory hardening
vSphere Web Client vSphere Client vCLI (Scripting)
– Kernel module integrity
– Trusted platform module CIM
vSphere API/SDK (Hardware
• Small disk footprint vCenter Server
Management)
• Installable on hard disks, SAN LUNs, USB devices, SD cards, and diskless
hosts
VMM VMM VMM VMM VMM
VMware Hypervisor: VMkernel
Configuring an ESXi Host Configuring an ESXi Host: Root Access

The Direct Console User Interface (DCUI) is similar to the BIOS of a DCUI enables an administrator to configure root access settings.
computer, with a keyboard-only UI. • Set a root password (complex passwords only).
• Enable or disable lockdown mode:
– Limits management of the host to vCenter Server.
– Enabled only for hosts managed by vCenter Server.
Configuring an ESXi Host: Management Network Configuring an ESXi Host: Other Settings
The DCUI enables you to modify network settings: The DCUI enables an administrator to configure the keyboard layout,
• Host name enable troubleshooting services, view support information, and view
system logs.
• IP configuration (IP address, subnet mask, default gateway)
• DNS servers
7
3/20/2018
Network Settings: DNS and Routing Remote Access Settings: Security Profile
The DNS and Routing link enables an administrator to apply the host The security profile controls remote access to an ESXi host:
name and domain, DNS server addresses and search domains, and the • Remote clients are prevented from accessing services on the host.
default VMkernal gateway.
• Local clients are prevented from accessing services on remote hosts.
• Unless configured otherwise, daemons, such as DCUI or NTP server
processes, start and stop with the ESXi host.
Managing User Accounts Best Practices Lab 2: Configuring ESXi Hosts

Exercise care when assigning user accounts to access ESXi hosts or Configure an ESXi host
vCenter Server systems. 1. Examine the ESXi Host Hardware Configuration
• Strictly control root privileges to ESXi hosts. 2. Configure the DNS and Routing Information for an ESXi Host
• Use the vSphere Web Client to manage ESXi hosts. 3. Configure an ESXi Host to Use Directory Services
• Log in to the vCenter Server system using vCenter Server user accounts,
which can be either local or domain accounts.
Review of Learner Objectives Key Points

You should be able to meet the following objectives: • Using virtual machines solves many data center problems.
• Describe ESXi host architecture • Virtual machines are hardware independent.
• Use the vSphere Client to access an ESXi host • Virtual machines share the physical resources of the ESXi host on which they
reside.
• View ESXi host settings:
– Processor and memory configuration • A virtual machine is a set of files that is easy to transfer and back up.
– Licensing • Virtual machine files are encapsulated into a folder and placed on a datastore.
– DNS and routing • The ESXi hypervisor runs directly on the host.
– Security profile • vSphere abstracts CPU, memory, storage, and networking for virtual machine
• Identify user account best practices use.
Questions?
8
3/20/2018
Creating Virtual Machines You Are Here

Monitoring
Virtual Networks
Virtual Storage


You can create a virtual machine in several ways. Choosing the correct Lesson 1: Virtual Machine Concepts
method can help you save time and make the deployment process
manageable and scalable. Lesson 2: Creating a Virtual Machine
Learner Objectives
objectives:
• Identify the files that make up a virtual machine
• Compare virtual machine hardware version 11 to other versions
• Describe the elements of a virtual machine
• View the console of a virtual machine
Lesson 1:
Virtual Machine Concepts

1
3/20/2018
About Virtual Machine Files About Virtual Machine Virtual Hardware

A virtual machine consists of a set of related files. Up to 3 Up to 32 VMCI AHCI
2 IDE
Parallel Ports Serial/Com ports Controller Controller
Controller
Configuration file VM_name.vmx Devices 1 USB
Swap files VM_name.vswp Controller
vmx-VM_name.vswp 20 Devices
BIOS file VM_name.nvram Up to 10
Log files vmware.log NICs
VM Template file VM_name.vmtx 1 Floppy Controller
folder Raw device map file VM_name-rdm.vmdk 2 Devices
Disk descriptor file VM_name.vmdk Hardware Virtual Machine
Disk data file VM_name-flat.vmdk 3D
Suspend state file VM_name.vmss Up to 4 SCSI
Snapshot data file VM_name.vmsd Adapters
Snapshot state file VM_name.vmsn
Snapshot disk file VM_name-delta.vmdk
Up to
4 TB of RAM
15 Devices
per Adapter
Up to 128 vCPUs
Virtual Hardware Versions About Virtual Hardware Version 11

The virtual hardware version determines the operating system functions Virtual hardware version 11 provides several features and benefits.
that a virtual machine supports. Do not use a version that is higher than
supported by the VMware product. Features Benefits
xHCI controller updated to USB 3 support for Mac OS X 10.8, Windows Server 2012, and
Product Version Hardware Version version 1.0 Windows 8 operating systems.
Windows VMXNET3 driver Supports large receive offload, resulting in reduced associated
VMware ESXi™ 6 and later 11 support CPU costs by reducing network packet processing.
Enhanced NUMA feature Hot-add local memory is distributed across all NUMA nodes.
ESXi 5.5 and later 10
Support for Windows 2000 and later, Linux kernels 2.4 and later,
Guest authentication
and Solaris operating systems.
ESXi 5.1 and later 9
HGFS shared folder feature Number of reboots is reduced by installing VMware Tools™.
Hardware version 11 virtual machines can support up to 128
ESXi 5.0 and later 8 Increased vCPU capacity
virtual CPUs.
ESXi/ESX 4.0 and later 7 Increased RAM capacity Hardware version 11 virtual machines support up to 4 TB of RAM.
Increased serial port Hardware version 11 virtual machines can be configured with up
configuration to 32 serial ports.
About CPU and Memory About Virtual Disks

You can add, change, or configure CPU and memory resources to A virtual machine usually has a least one virtual disk.
improve virtual machine performance.
The maximum number of vCPUs that you can assign to a virtual machine
depends on:
• The number of logical CPUs on the host
• The host license
• The type of installed guest operating system
A virtual machine running on an ESXi 6 host can have up to 128 vCPUs.

Maximum memory size for a virtual machine depends on: Sample virtual disk definition:
Virtual disk size: 8 GB
• The host’s physical memory Datastore: MyVMFS
• The virtual machine's compatibility setting Virtual disk node: 0:0
Virtual storage adapter: LSI Logic SAS
The maximum memory size of a virtual machine Virtual disk files: Server1.vmdk and Server1-flat.vmdk
Default disk mode: Snapshots allowed
with ESXi 6 compatibility running on ESXi 6 Optional disk mode: Independent: Persistent or Nonpersistent
is 4,080 GB. Disk provisioning policy: Thick Provision Lazy Zeroed, Thick Provision
Eager Zeroed, or Thin Provision
2
3/20/2018
About Thick-Provisioned Virtual Disks About Thin-Provisioned Virtual Disks

Thick provisioning uses all the Thin provisioning enables virtual
machines to use storage space as
defined disk space at the creation
needed:
of the virtual disk:
Host • Virtual machine disks consume only Host
• Virtual machine disks consume all
the capacity needed to hold the
the capacity, as defined at creation, current files.
regardless of the amount of data in
the guest operating system file Thick Thin Thin
• A virtual machine sees the full
Thick Thin Thin
system. allocated disk size at all times.
• You can mix thick and thin formats.
Eager zeroed or lazy zeroed: Virtual Virtual
Disks • Full reporting and alerts help Disks
• Every block in an eager zeroed
manage allocations and capacity.
thick-provisioned disk is prefilled
with a zero. More efficient use of storage:
• Every block in a lazy zeroed thick- • Virtual disk allocation 140 GB
provisioned disk is filled with a zero • Available datastore capacity 100 GB
Datastores
when data is written to the block. Datastores
• Used storage capacity 80 GB
About Network Virtual Machine Configuration About Network Adapters

ESXi networking features: When you configure a virtual
machine, you can add network
• Provide communication between virtual machines on the same host,
adapters (NICs) and specify
between virtual machines on different hosts, and between virtual and
the adapter type. Whenever
physical machines
possible, select VMXNET3.
• Enable management of ESXi hosts
Supported network adapter types:
• Enable communication between VMkernel services (NFS, iSCSI, or • Flexible: Can function as either a
VMware vSphere® vMotion®) and the physical network Vlance or VMXNET adapter.
When you configure networking for a virtual machine, you select or • E1000-E1000E: High-performance adapter available for only some guest
change a network adapter type, a network connection, and whether to operating systems.
connect to the network when the virtual machine powers on. • VMXNET, VMXNET2, and VMXNET3 are VMware drivers that are available
only with VMware Tools.
• SR-IOV passthrough: Representation of a virtual function on a physical NIC
with SR-IOV support:
– Limited guest operating system support
About Miscellaneous Devices About the Virtual Machine Console

A virtual machine must have a vCPU and virtual memory. The addition of The virtual machine console provides the mouse, keyboard, and screen
other virtual devices makes the virtual machine more useful. features to control the virtual machine.
CD/DVD drive:
• Connect to CD, DVD, or ISO image.
USB 3.0:
• Smart-card readers
Floppy drive:
• Connect a virtual machine to
a floppy drive or a floppy image.
Generic SCSI devices:
• A virtual machine can be
connected to additional SCSI
adapters. vSphere Web Client
vGPUs:
• Enable a virtual machine to use
GPUs on the physical host for
high-computation activities.
vSphere Client
3
3/20/2018

• Identify the files that make up a virtual machine
• Compare virtual machine hardware version 11 to other versions
• Describe the elements of a virtual machine
• View the console of a virtual machine
Lesson 2:
Creating a Virtual Machine

Learner Objectives About Provisioning Virtual Machines

By the end of this lesson, you should be able to meet the following You can create virtual machines in several ways:
objectives: • Use the New Virtual Machine wizard to create virtual machines.
• Create, provision, and remove a virtual machine • Deploy virtual machines, virtual appliances, and vApps stored in Open Virtual
• Compare and contrast the types of virtual disk provisioning Machine Format (OVF).
• Explain the importance of VMware Tools • Use a CentOS, Linux, or Windows template in a vCloud Air catalog to create
virtual machines.
• Describe how to import a virtual appliance OVF template
• Discuss how to use VMware vCloud® Air™ to create a virtual machine from a
template
Creating Virtual Machines with the New Virtual Machine

Wizard New Virtual Machine Wizard
You can use the New Virtual Machine wizard in the vSphere Web Client
to create a virtual machine.
4
3/20/2018
Installing the Guest Operating System Deploying OVF Templates

Installing a guest operating system in your virtual machine is like You can deploy any virtual machine or a virtual appliance stored in OVF.
installing it on a physical computer.
Virtual appliances are:
• Preconfigured virtual machines
• Usually designed for a single purpose, for example, a safe browser or firewall
• Available from the VMware Solution Exchange
vSphere Web
Client
Deploying a Virtual Machine in vCloud Air About VMware Tools

vCloud Air is a secure, hybrid cloud service built on the vSphere VMware Tools is a suite of utilities that enhance the performance of the
foundation: virtual machine’s guest operating system.
• vCloud Air is available in the following infrastructure-as-a-service subscription
service types: VMware Tools benefits: VMware Tools features:
– Dedicated Cloud • Device drivers: • Shared folders between host and
– Virtual Private Cloud and Virtual Private Cloud OnDemand – SVGA display guest file systems
– Disaster Recovery – VMXNET/VMXNET3 • Copying and pasting text, graphics,
• vCloud Air includes a catalog that is populated with CentOS, Linux, and – Balloon driver for memory and files between the virtual
Windows templates that you can use to create virtual machines. management machine and the host or client
• Your organization also has its own catalog, My Catalog, which can contain your – Sync driver for quiescing I/O desktop
customized templates. • Time synchronization
• Increased graphics performance
• In vCloud Air, end users select from catalogs to add virtual machines. • Ability to shut down the virtual
• Improved mouse performance
• You can use virtual machines as desktop or workstation environments, as machine
testing environments, or to consolidate server machines to supply what the end
user sees as My Catalog.
• Go to http://vcloud.vmware.com for more information.
Removing a Virtual Machine Troubleshooting OS Installation Failures on ESX/ESXi Hosts

You can remove a virtual Problems:
machine in two ways: • The installation of a 64-bit operating system cannot start.
• Remove from the inventory: • The installation of a 64-bit operating system cannot complete.
– This type of removal unregisters
the virtual machine. • The installation of 64-bit guest operating system stops responding as Setup is
starting the Windows screen.
– The virtual machine’s files remain
on the disk. Resolutions:
– The virtual machine can later be
1. Verify that that the guest operating system you are attempting to install is fully
registered (added) to the
inventory. certified by VMware.
• Delete from disk: 2. Verify that your ESX/ESXi host meets the hardware and firmware
requirements for running 64-bit virtual machines.
– All virtual machine files are
permanently deleted from the 3. If your ESX/ESXi host uses Intel processors, verify that virtualization
virtual machine datastore. technology is enabled in the BIOS.
4. Verify that the correct guest operating system is selected.
5
3/20/2018
Troubleshooting VMware Tools Installation Problems Lab 3: Working with Virtual Machines
Problems: Create and prepare virtual machines for use
• VMware Tools installation errors before completion. 1. Create a Virtual Machine
• VMware Tools installation on a guest operating system fails to complete. 2. Install a Guest Operating System in a Virtual Machine
• Unable to complete VMware Tools for Windows or Linux installation. 3. Identify the Virtual Machine’s Disk Format and View Storage Metrics
• VMware Tools hangs when installing or reinstalling on a guest operating 4. Install VMware Tools on a Virtual Machine Installed with a Windows OS
system. 5. Prepare Your Virtual Machine for Upcoming Labs
Resolutions:
1. Verify that the guest operating system that you are trying to install VMware
Tools in is fully certified.
2. Verify that the correct guest operating system is selected.
3. Verify that the correct ISO image is being loaded.
4. Verify that the VMware Tools ISO image is not corrupted.
5. If installing on a Windows operating system, verify that you are not
experiencing problems with the Windows registry.

You should be able to meet the following objectives: • Virtual machines can be provisioned using various methods:
• Create, provision, and remove a virtual machine – You can use the Add Virtual Machine wizard in the vSphere Client or the vSphere
Web Client to create virtual machines.
• Compare and contrast the types of virtual disk provisioning – You can create a virtual machine by deploying an OVF template.
• Explain the importance of VMware Tools – You can use vCloud Air to create a virtual machine from a template.
• Describe how to import a virtual appliance OVF template • VMware Tools increases the performance of the virtual machine’s guest
• Discuss how to use VMware vCloud® Air™ to create a virtual machine from a operating system.
template Questions?
6
3/20/2018
vCenter Server You Are Here

Monitoring
Virtual Networks
Virtual Storage


VMware vCenter Server™ enables you to centrally manage multiple Lesson 1: vCenter Server Architecture
VMware ESXi™ hosts and their virtual machines. Failure to properly Lesson 2: Deploying vCenter Server Appliance
install, configure, and manage vCenter Server might result in reduced
administrative efficiency or possible ESXi host and virtual machine Lesson 3: vSphere Web Client
downtime. Lesson 4: Managing the vCenter Server Inventory
Learner Objectives
objectives:
• Discuss how ESXi hosts communicate with vCenter Server
• Identify the vCenter Server services, components, and modules
• Explain VMware Platform Services Controller™
Lesson 1:
vCenter Server Architecture

1
3/20/2018
About the vCenter Server Management Platform vCenter Server Architecture

vCenter Server is a service that acts as a central administration point for The diagram shows the supporting components for vCenter Server.
ESXi hosts and their virtual machines connected on a network.
Active Directory Domain
This service directs the actions of virtual machines and hosts.
vCenter Server
vSphere Web
Client
Manage vCenter Platform
Server and Services
Additional Controller with
Modules vCenter Single
Database Sign-On
vSphere vSphere vSphere
ESXi Host ESXi Host ESXi Host
Additional vCenter Server Services and Interfaces Platform Services Controller

vCenter Server has additional services and interfaces that provide vCenter Server includes the Platform Services Controller:
important functions.
 The Platform Services Controller includes a set of common infrastructure
PSC
services:
Platform Services
Distributed Services – VMware vCenter™ Single Sign-On™ Virtual Machine or Physical
Controller
– VMware License Server
vSphere Web Client Platform Services
Additional Services: User – Lookup Service Controller
Database • vSphere Update Manager
Server • vRealize Orchestrator
Access vSphere Third-Party – Certificate Authority
Control API Applications – Certificate Store vCenter Server
Core Services
Plug-In – VMware Directory Services
ESXi Management  Other features are installed under the vCenter Server component.
 You can install vCenter Server and the Platform Services Controller on the
same or different machines.
vCenter
Server
Database
vCenter Server Services and Functions ESXi and vCenter Server Communication
The vCenter Server group of services contains:
• vCenter Server TCP
443, 9443
• VMware vSphere® Web Client (server) TCP 443
vCenter Server
• VMware Inventory Service
vpxd
• VMware vSphere® Auto Deploy™
• VMware vSphere® ESXi™ Dump Collector
• VMware vSphere® Syslog Collector
TCP/UDP TCP/UDP
You cannot distribute these vCenter Server functions across multiple 902 902
servers. When you install the vCenter Server component, all of these
features are included.
hostd vpxa
ESXi Host
2
3/20/2018
Default vCenter Server Plug-Ins vSphere Web Client Plug-In Packages

vCenter Server is installed with a set of default plug-in components. The vSphere Web Client has several plug-in packages.
Plug-ins are applications that provide additional features and
functionalities to vCenter Server:
• VMware plug-ins: VMware vSphere® Update Manager™, VMware vCenter™
Site Recovery Manager™, and others
• Third party plug-ins: From EMC, NetApp, HP, Dell, and others

• Discuss how ESXi hosts communicate with vCenter Server
• Identify the vCenter Server services, components, and modules
• Explain VMware Platform Services Controller™ Lesson 2:
Deploying vCenter Server
Appliance

Learner Objectives vCenter Server Appliance Features

By the end of this lesson, you should be able to meet the following vCenter Server Appliance is a preconfigured, Linux-based virtual
objectives: machine:
• Discuss the vCenter Server deployment models • Runs on SUSE Linux Enterprise Server 11, Update 3
• Deploy VMware vCenter Server™ Appliance™ into an infrastructure • Can be used with ESXi 5.5 and later ESXi versions
• Add license keys to vCenter Server • Is prepackaged with a PostgreSQL embedded database:
• Configure vCenter Server settings – Suitable for environments with up to 1,000 hosts and 10,000 virtual machines
• Add hosts to vCenter Server • Supports an external Oracle database when running in an enterprise
• Is equipped with the vCenter Server Appliance console, used for
troubleshooting and configuration
• Supports centralized authentication
3
3/20/2018
vCenter Server Appliance Basics Platform Services Controller Deployment Recommendations (1)
vCenter Server Appliance is functionally Deployment Models Recommended for the Platform Services Controller
vCenter Server Appliance
equivalent to vCenter Server installed on in Enhanced Linked Mode
a Windows server: Platform Services
Controller
• vCenter Server Appliance can be
Enhanced Linked Mode with an External Enhanced Linked Mode with an External
configured with an external Platform
vCenter Server Platform Services Controller Without Platform Services Controller with vSphere HA
Services Controller. vSphere HA
• vCenter Server Appliance can be
configured as a distributed vCenter Server
instance. vCenter Server Appliance
• You can combine vCenter Server Appliance Platform Services

Controller
instances and vCenter Server systems
installed on Windows servers in the same
vCenter Server Windows
architecture. Appliance vCenter Server
• vCenter Server Appliance supports Linked vCenter vCenter
Mode. Server Server
Platform Services Controller Deployment Recommendations (2) Platform Services Controller Deployment Recommendations (3)
Deployment Models Not Recommended for the Platform Services Deployment Model Not Recommended for the Platform Services
Controller in Enhanced Linked Mode Controller in Enhanced Linked Mode
Enhanced Linked Mode with Embedded
Platform Services Controllers
External vCenter Server System Linked to an
Embedded Platform Services Controller
Combination Deployments of Both

Embedded and external Platform Services
Controllers
vCenter Server Appliance Scalability vSphere License Service

vCenter Server Appliance scales to the same capacity as vCenter Server In vSphere 6, the License Service is part of the Platform Services
installed on a Windows machine. Controller.
It delivers centralized license management and reporting functionality to
Metric Windows Appliance
vSphere and to products integrated with vSphere.
Hosts per vCenter Server System 1,000 1,000 It provides an inventory for licenses in the vSphere environment and
manages the license assignments for ESXi hosts, vCenter Server
Powered-on virtual machines per
10,000 10,000
systems, and clusters with VMware Virtual SAN™ enabled .
vCenter Server System
It manages the license assignments for products that integrate with
Hosts per cluster 64 64 vSphere.
Virtual machines per cluster 8,000 8,000
Must be Oracle or SQL for full Can be either Oracle or

Database
scalability embedded PostgreSQL
Linked Mode Yes Yes
4
3/20/2018
Preparing for vCenter Server Appliance Deployment (1) Preparing for vCenter Server Appliance Deployment (2)
Before deploying vCenter Server Appliance, you must complete several Before deploying vCenter Server Appliance, you must complete several
tasks: tasks:
• Verify that all vCenter Server Appliance system requirements are met. • When you install vCenter Server and the Platform Services Controller, you
• Prepare a vCenter Server database: must provide the fully qualified domain name (FQDN) or the static IP of the
host machine on which you are performing the install or upgrade. VMware
– Use the included PostgreSQL database.
recommends using the FQDN.
– Set up an external Oracle database.
• Before you install vCenter Server Appliance, verify that all machines on the
• For the first installation of vCenter Server Appliance, you must first deploy the vSphere network have their clocks synchronized.
Platform Services Controller and then vCenter Server.
– If you deploy vCenter Server or vCenter Server Appliance with an embedded Platform
Services Controller, this happens automatically.
– If you install vCenter Server with an external Platform Services Controller, you must
first install the Platform Services Controller and then install vCenter Server.
Deploying vCenter Server Appliance vCenter Server Appliance Installation Media

You can configure vCenter Server Appliance by using the vSphere Web vCenter Server Appliance is distributed as an ISO image, which contains
Client, the appliance shell, or the Direct Console User Interface. the following components:
You must download and install the vCenter Server Appliance installer • vCenter Server Appliance 6 data file (vcsa folder)
and the VMware Client Integration Plug-In. • Client Integration Plug-In 6 for Windows, Mac, and Linux
The Client Integration Plug-In provides access to a virtual machine’s • vCenter Server Appliance command-line installer
console in the vSphere Web Client as well as access to other vSphere • vCenter Server Appliance UI deployment Web page (index.html)
infrastructure tasks.
Connecting to the ESXi Host on Which to Deploy vCenter Server

Accessing vCenter Server Appliance Appliance
The vCenter Server Appliance ISO image contains an index.html file. In the vCenter Server Appliance Deployment wizard, you connect to the
Open this file in a supported browser to begin the installation. target ESXi host where you deploy vCenter Server Appliance.
5
3/20/2018
Specifying the Virtual Machine Name and Password for Root User Selecting the Deployment Type
Enter the vCenter Server Appliance name and set the password for the Select a deployment type based on your organization’s needs.
root user.
Configuring vCenter Single Sign-On Selecting a vCenter Server Appliance Size

Configure vCenter Single Sign-On by specifying a password, a domain Select the vCenter Server Appliance size based on the size of your
name, and a site name. vSphere inventory.
Selecting a Datastore Configuring Network Settings

From the list of available datastores, select the location where all the You must configure network settings, specify if you want to enable SSH,
virtual machine configuration files and virtual disks will be stored and, and select a Time Sync option.
optionally, enable thin provisioning.
6
3/20/2018
Using the vSphere Web Client to Log In to vCenter Server Adding License Keys to vCenter Server
After you deploy vCenter Server Appliance, log in to it by using the Assign a license to vCenter Server before its 60-day evaluation period
vSphere Web Client to manage your vSphere inventory. expires.
• Open a Web browser and enter the URL for the vSphere Web Client:
https://appliance_IP_address_or_FQDN/vsphere-client.
Configuring vCenter Server Settings Managing the vCenter Server Services

You can configure your vCenter Server system from the vSphere Web You can manage vCenter Server services by selecting Administration >
Client, including settings such as licensing, statistics collection, logging, System Configuration from the Home page and selecting Services.
and other settings.
• To access the vCenter Server system settings, navigate to the vCenter Server
system in the vSphere Web Client and click the Manage tab.
Monitoring Health and Status of Services and Nodes Across

vCenter Server Systems ESXi Host as an NTP Client
The vSphere Web Client enables you to monitor the status of all Network Time Protocol (NTP) is a
manageable services and nodes across vCenter Server systems. client-server protocol used to
synchronize a computer’s clock to a NTP
A list of default services is available in each vCenter Server instance. time reference. NTP
Server
NTP Server
NTP is important:
Server
• For accurate performance graphs
• For accurate time stamps in log
messages
• So that virtual machines have a source
to synchronize with
An ESXi host can be configured as
an NTP client. It can synchronize time
with an NTP server on the Internet or The NTP client uses
your corporate NTP server. NTP UDP over port 123 to
communicate with
Client the NTP server.
ESXi Host
7
3/20/2018
Configuring Host Time Synchronization Lab 4: Working with vCenter Server

Configure Network Time Protocol (NTP) settings for each host: Configure vCenter Server Appliance for first use
• Can be automated with host profiles 1. Access vCenter Server Appliance
2. Install vCenter Server Appliance and Host License Keys
3. Create a Data Center Object
4. Add Your ESXi Host to the vCenter Server Inventory
5. Configure Your ESXi Host as an NTP Client

• Discuss the vCenter Server deployment models
• Deploy VMware vCenter Server™ Appliance™ into an infrastructure
• Add license keys to vCenter Server
• Configure vCenter Server settings
• Add hosts to vCenter Server Lesson 3:
vSphere Web Client

Learner Objectives Accessing vSphere Web Client

By the end of this lesson, you should be able to meet the following To access the vSphere Web Client, you open a Web browser and enter
objectives: the URL for the vSphere Web Client.
• Access the vSphere Web Client
• Install the VMware Client Integration Plug-In
• Navigate the vSphere Web Client
http://appliance_IP_address_or_FQDN/vsphere-client
Download and install the

Client Integration Plug-In
for virtual machine
console access.
8
3/20/2018
vSphere Web Client Home Page Using the vSphere Web Client Navigator
The vSphere Web Client Home page appears the first time that you use You can use the
the vSphere Web Client to log in to your vCenter Server system. Navigator pane to
browse and select
The Home page has a Navigator pane on the left and Inventories,
objects in the vSphere
Monitoring, and Administration panes on the right.
Web Client inventory.
The navigator presents
a graph-based view of
the inventory, which
enables you to
navigate inventory
objects.
vCenter Server Views: Hosts and Clusters, VMs and Templates vCenter Server Views: Storage and Networks
Hosts and Clusters Inventory View Storage Inventory View
VMs and Templates Inventory View Networks Inventory View
Viewing Object Information Viewing Recent Objects

Because you can navigate to view object information and access related You can quickly navigate to the objects that you visited during your
objects, monitoring and managing object properties is easy. vSphere Web Client session.
You can revisit objects without having to search in the inventory tree.
You use the Recent Objects icon to

view objects that you visited
or created in your environment.
9
3/20/2018
Using Quick Filters Using Drag-and-Drop Functionality

You can use quick filters to find an object or a set of objects in the You can drag an inventory object to another location. This action is an
vSphere inventory by using certain display criteria. alternative way to perform tasks that are available in the context menu.
Show or hide Drag-and-drop icons

the quick filters options. indicate whether
you can move
the object.
.
Lab 5: Using vSphere Web Client Review of Learner Objectives

Navigate and customize vSphere Web Client You should be able to meet the following objectives:
1. Navigate vSphere Web Client • Access the vSphere Web Client
2. Pin and Unpin Panes • Install the VMware Client Integration Plug-In
3. Hide the Getting Started Tabs • Navigate the vSphere Web Client
4. Upgrade the Virtual Machine’s Hardware
Learner Objectives
objectives:
• Create and organize vCenter Server inventory objects
• Discuss how to create custom inventory tags for inventory objects
• Recognize how to view vCenter Server logs and events
Lesson 4:
Managing the vCenter Server
Inventory

10
3/20/2018
About Data Center Objects Organizing Inventory Objects into Folders

A virtual data center is a container for all the inventory objects required to Items in the data center can be placed into folders. Folders and
complete a fully functional environment for operating virtual machines: subfolders can be created to better organize systems.
• You can create multiple data centers to organize sets of environments.
• Each data center has its own hosts, virtual machines, templates,
datastores, and networks.
Los Angeles
Data Center
vCenter Server
File and Intel
DB AMD
Print
Paris HOST HOST HOST HOST

Toronto Los Angeles Munich
Data Center Data Center Data Center Data Center
Using Folders Adding a Host to the vCenter Server Inventory

You can use folders to group objects of the same type for easier You can add hosts under a data center object, folder object, or cluster
management. For example, permissions can be applied to folders, object. If a host contains virtual machines, those virtual machines are
enabling you to use folders to group objects that should have a common added to the inventory together with the host.
set of permissions.
Creating Custom Tags for Inventory Objects vCenter Server Events

Tags enable you to attach metadata to objects in the vSphere inventory Events are records of user actions or system actions that occur on
to make these objects more sortable. objects in vCenter Server or on a host.
You can associate a set of objects of the same type:
• Search for objects by that tag.
• Enable a business case where customers want to create groups of virtual
machines, clusters, and datastores for ease of management.
Event Type
Details of
Selected Event
11
3/20/2018
vCenter Server System Logs Lab 6: Creating Folders in vCenter Server Appliance
vSphere records events in the vCenter Server database. System log Create vCenter Server inventory objects
entries include information such as who generated the event, when the 1. Create a Host and Cluster Folder
event was created, and the type of event.
2. Create Virtual Machine and Template Folders
You can export system

logs for troubleshooting
system problems.

You should be able to meet the following objectives: • The vCenter Server architecture consists of the following components:
• Create and organize vCenter Server inventory objects – vCenter Server
• Discuss how to create custom inventory tags for inventory objects – vCenter Server database
• Recognize how to view vCenter Server logs and events – Active Directory
– Managed ESXi hosts
• vCenter Server has two types of deployment models:

– Embedded Platform Services Controller
– External Platform Services Controller
• You use the vSphere Web Client to connect to vCenter Server systems and
manage vSphere inventory objects.
Questions?
12
3/20/2018
Configuring and Managing Virtual Networks You Are Here

Monitoring
Virtual Networks
Virtual Storage
Insert Course Title Here – Prerelease ?-2


VMware ESXi™ networking features enable: Lesson 1: Introduction to vSphere Standard Switches
• Virtual machines to communicate with other virtual and physical machines Lesson 2: Configuring Standard Switch Policies
• Management of the ESXi host
Lesson 3: Introduction to vSphere Distributed Switches
• VMkernel communication on the network
Failure to properly configure ESXi networking can negatively affect virtual

machine management and storage operations.
Insert Course Title Here – Prerelease ?-3 Insert Course Title Here – Prerelease ?-4
Learner Objectives
objectives:
• Describe the virtual switch connection types
• Describe the components of a standard switch
Lesson 1:
Introduction to vSphere Standard
Switches
?-5 Insert Course Title Here – Prerelease ?-6

1
3/20/2018
Types of Virtual Switch Connections Virtual Switch Connection Examples

A virtual switch has specific connection types: More than one network can coexist on the same virtual switch. Or
• Virtual machine port groups networks can exist on separate virtual switches.
• VMkernel port:
– For IP storage, VMware vSphere® High Availability, VMware vSphere® vMotion® Management vSphere vMotion Production TestDev iSCSI
migration, VMware vSphere® Fault Tolerance, VMware Virtual SAN™, and VMware
vSphere® Replication™
– For the ESXi management network
Virtual Switch
Virtual Machine Port Groups VMkernel Ports
Production TestDev DMZ vSphere Management TestDev

Management vSphere vMotion Production iSCSI
vMotion
Virtual Switch
Virtual Switch Virtual Switch Virtual Switch Virtual Switch Virtual Switch
Uplink Ports
Types of Virtual Switches Standard Switch Components

A virtual network supports these types of virtual switches: A standard switch provides connections for virtual machines to
• Standard switches: communicate with one another, whether they are on the same host or a
– Virtual switch configuration for a single host
different host.
• Distributed switches:
VM VM VM IP Management
– Virtual switches that provide a consistent network configuration for virtual machines
as they migrate across multiple hosts
1 2 3 storage Network
VNIC VNIC VNIC VNIC
VMkernel
Test VLAN 101

Production VLAN 102
IP Storage VLAN 103
Management VLAN 104
Viewing the Standard Switch Configuration About VLANs

You can view a host’s standard switch configuration by clicking ESXi supports 802.1Q VLAN tagging.
Networking on the Manage tab. VM VM
Virtual switch tagging is one of the
tagging policies supported:
• Packets from a virtual machine are
tagged as they exit the virtual switch. VMkernel VLAN VLAN
105 106
• Packets are untagged as they return to
the virtual machine. Virtual Switch
• Effect on performance is minimal.
Physical
Display port group ESXi provides VLAN support by NIC
properties.
giving a port group a VLAN ID. Physical Switch
Delete the Trunk Port
port group.
Display Cisco Discovery

Protocol information.
2
3/20/2018
Network Adapter Properties Review of Learner Objectives

A physical adapter can become a bottleneck for network traffic if the You should be able to meet the following objectives:
adapter speed does not match application requirements. • Describe the virtual switch connection types
• Describe the components of a standard switch
Learner Objectives
objectives:
• Describe the security of a standard switch port group
• Describe the traffic shaping of a standard switch port group
• Describe the NIC teaming and failover of a standard switch port group
Lesson 2:
Configuring Standard Switch
Policies
?-15 Insert Course Title Here – Prerelease ?-16

Network Switch and Port Policies Configuring Security Policy

Policies set at the standard switch level apply to all of the port groups on Administrators can define security policies at both the standard switch
the standard switch. The exceptions are the configuration options that level and the port group level:
are overridden at the standard port group. • Promiscuous mode: Allows a virtual switch or port group to present all traffic
Available network policies: regardless of the destination.
• MAC address changes: Accept or reject inbound traffic when the MAC
• Security
address has been altered by the guest.
• Traffic shaping
• Forge transmits: Accept or reject outbound traffic when the MAC address has
• NIC teaming and failover been altered by the guest.
Policies are defined at these levels:
• Standard switch level:
– Default policies for all the ports on the standard switch.
• Port group level:
– Effective policies: Policies defined at this level override the default policies set at the
standard switch level.
3
3/20/2018
Traffic-Shaping Policy Configuring Traffic Shaping

Network traffic shaping is a mechanism for limiting a virtual machine’s A traffic-shaping policy is defined by average bandwidth, peak
consumption of available network bandwidth. bandwidth, and burst size. You can establish a traffic-shaping policy for
each port group and each distributed port or distributed port group:
Average rate, peak rate, and burst size are configurable.
• Traffic shaping is disabled by default.
• Parameters apply to each virtual NIC in the standard switch.
• On a standard switch, traffic shaping controls only outbound traffic.
Outbound Bandwidth
Peak Bandwidth
Average
Time
Burst Size = Bandwidth x Time
NIC Teaming and Failover Policy Load-Balancing Method: Originating Virtual Port ID
Administrators can edit the NIC teaming and failover policy by The diagram shows routing based on the originating port ID, called virtual
configuring specific options. port ID load balancing.
Virtual
Switch
Physical
Switch
Virtual NICs Physical NICs
Load-Balancing Method: Source MAC Hash Load-Balancing Method: Source and Destination IP Hash
The diagram shows routing based on source MAC hash. The diagram shows routing based on IP hash.
Internet
Internet
Virtual
Switch Virtual Physical
Physical Switch Switch
Switch
Virtual Physical Virtual NICs Physical NICs

NICs NICs
4
3/20/2018
Detecting and Handling Network Failure Lab 7: Using Standard Switches

The VMkernel can use link status or beaconing or both to detect a Create a standard switch and a port group
network failure. 1. View the Standard Switch Configuration
Network failure is detected by the VMkernel, which monitors the link state 2. Create a Standard Switch with a Virtual Machine Port Group
and performs beacon probing. 3. Attach Your Virtual Machine to the New Virtual Machine Port Group
VMkernel notifies physical switches of changes in the physical location of

a MAC address.
Failover is implemented by the VMkernel based on configurable
parameters:
• Failback: How the physical adapter is returned to active duty after recovering
from failure.
• Load-balancing option: Use explicit failover order. Always use the vmnic uplink
at the top of the active adapter list.

• Describe the security of a standard switch port group
• Describe the traffic shaping of a standard switch port group
• Describe the NIC teaming and failover of a standard switch port group
Lesson 3:
Introduction to vSphere
Distributed Switches
Insert Course Title Here – Prerelease ?-27 ?-28

Learner Objectives About vSphere Distributed Switches

By the end of this lesson, you should be able to meet the following A vSphere distributed switch greatly extends vSphere networking
objectives: features and centralizes vSphere management.
• List the benefits of using vSphere distributed switches • VMware vCenter Server™ owns the configuration of the distributed switch. The
• Describe the distributed switch architecture configuration is consistent across all the hosts that use it.
• Create a distributed switch • A distributed switch enhances the use of physical Ethernet NICs with a speed
of 10 Gbps or faster.
• Manage the distributed switch
The behavior of distributed switches is consistent with standard switches:
• Describe the properties of a distributed switch
• You can configure virtual machine port groups and VMkernel ports.
5
3/20/2018
Benefits of Distributed Switches Standard Switch and Distributed Switch Feature Comparison
Benefits of distributed switches over standard switches: Feature Standard Switch Distributed Switch
Layer 2 switch
• Simplify data center administration
VLAN segmentation
• Provide support for advanced features, such as private VLANs, NetFlow, and
IPv6 support
port mirroring
802.1Q tagging
• Enable networking statistics and policies to migrate with virtual machines NIC teaming
during a migration with VMware vSphere® vMotion®
Outbound traffic shaping
• Provide for customization and third-party development Inbound traffic shaping
VM network port block
Private VLANs
Load-based teaming
Data center-level management
vSphere vMotion migration over a network
Per-port policy settings
Port state monitoring
NetFlow
Port mirroring
Distributed Switch Architecture Distributed Switch Example

You create a distributed switch named VDS01. You create a port group
Management Port Management Port named Production, which will be used for virtual machine networking.
vSphere vMotion
You assign uplinks vmnic1 on host ESXi01 and vmnic1 on host ESXi02
vSphere vMotion
Port Port to the distributed switch.
Distributed Ports
and Port Groups
Distributed Switch vCenter
(Control Plane) Server Uplink
Uplink Production Port Group
Port Groups Distributed
Switch VDS01
Virtual
Hidden Virtual
Physical
Switches
(I/O Plane) Uplinks
Virtual
Physical vmnic0 vmnic1 vmnic2 vmnic0 vmnic1 vmnic2
Physical NICs
(Uplinks) ESXi01 ESXi02
Host 1 Host 2
Viewing a Distributed Switch Creating a Distributed Switch

You can view a host’s distributed switch configuration by clicking the You can create a distributed switch on a data center to handle the
Manage tab and clicking the Networking link. networking configuration of multiple hosts at the same time from a central
place.
View distributed
switch settings. Distributed switch
settings.
6
3/20/2018
Editing General and Advanced Distributed Switch Properties Migrating Network Adapters to a Distributed Switch
General settings for a distributed switch include the switch name and the For hosts associated with a distributed switch, you can migrate network
number of uplinks. adapters from a standard switch to the distributed switch.
Basic multicast filtering mode

forwards multicast traffic for virtual
machines according to the destination
multicast group MAC address.
Migrate physical or
virtual network
adapters to this
distributed switch.
Assigning a Physical NIC of a Host to a Distributed Switch Connecting Virtual Machines to a Distributed Switch
You can assign physical NICs of a host that is associated with a You connect virtual machines to distributed switches by connecting their
distributed switch to an uplink port on the host proxy switch. associated virtual network adapters to distributed port groups.
For a single virtual machine,

Manage the physical modify the network adapter
network adapters configuration of the virtual
connected to the machine.
selected switch.
For a group of virtual machines,
migrate virtual machines from a
virtual network to a distributed
switch.
Editing Distributed Port Group General Properties Editing Distributed Port Group Advanced Properties
You can edit general distributed port group settings, such as the From the advanced settings of a distributed port group, you can
distributed port group name, the port settings, and the network resource configure the per-port overriding of the policies that are set at the port
pool. group level.
7
3/20/2018
Creating a VMkernel Adapter on a Host Associated with a

About the VMkernel Networking Level Distributed Switch
The VMkernel networking layer provides connectivity to hosts and You create a VMkernel adapter on a host that is associated with a
handles the standard system traffic of VMware vSphere® vMotion®, IP distributed switch to provide network connectivity to the host and to
storage, VMware vSphere® Fault Tolerance, VMware Virtual SAN™, and handle the traffic for vSphere vMotion, IP storage, vSphere Fault
others. Tolerance logging, Virtual SAN, and others.
You can also create VMkernel adapters on the source and target
VMware vSphere® Replication™ hosts to isolate the replication data
Click Add host networking to
traffic.
start the Add Networking wizard.
TCP/IP stacks at the VMkernel level:
• Default TCP/IP stack
• vMotion TCP/IP stack Click VMkernel
• Provisioning TCP/IP stack Network Adapter.
• Custom TCP/IP stacks
Virtual Machine Communication Problem Analysis (1) Virtual Machine Communication Problem Analysis (2)
Under certain conditions, the virtual machines on the same distributed Solutions:
port group but on different hosts cannot communicate with one another.
• In the topology of the distributed switch, check which host does not have
Problems: physical NICs assigned to an active or standby uplink on the distributed port
• Virtual machines residing on different hosts and on the same port group are group. Assign at least one physical NIC on that host to an active uplink on the
unable to communicate. port group.
• Pings from one virtual machine to another fail. You cannot migrate the virtual • In the topology of the distributed switch, check the VLAN IDs of the physical
machines between the hosts by using vSphere vMotion. NICs assigned to the active uplinks on the distributed port group. On all hosts,
assign physical NICs from the same VLAN to an active uplink on the
Causes: distributed port group.
• No physical NICs on some of the hosts are assigned to active or standby
uplinks in the teaming. The failover order of the distributed port group is not
correctly configured.
• The physical NICs on the hosts assigned to the active or standby uplinks
reside on different VLANs on the physical switch. The physical NICs on
different VLANs cannot see one another and thus cannot communicate with
one another.
Physical Network Considerations Lab 8: Using vSphere Distributed Switches

Your virtual networking environment relies on the physical network Create and configure a distributed switch
infrastructure. As a vSphere administrator, you should discuss your 1. Create a Distributed Switch
vSphere networking needs with your network administration team. 2. Add the ESXi Hosts to the New Distributed Switch
The following issues are topics for discussion: 3. Examine Your Distributed Switch Configuration
• Number of physical switches 4. Migrate the Virtual Machines to a Distributed Switch Port Group
5. Prepare for the Next Lab
• Network bandwidth required
• Physical switch configuration support for 802.3ad, for NIC teaming
• Physical switch configuration support for 802.1Q, for VLAN tagging
• Physical switch configuration support for Link Aggregation Control Protocol
(LACP)
• Network port security
• Link Layer Discovery Protocol (LLDP) and Cisco Discovery Protocol (CDP)
share the following operation modes:
– Listen, broadcast, listen and broadcast, and disabled
8
3/20/2018

You should be able to meet the following objectives: • Two connection types are on a virtual switch: virtual machine and VMkernel.
• List the benefits of using vSphere distributed switches • A standard switch is a virtual switch configuration for a single host.
• Describe the distributed switch architecture • Network policies set at the standard switch level can be overridden at the port
group level.
• Create a distributed switch
• A distributed switch provides centralized management and monitoring of the
• Manage the distributed switch
networking configuration of all hosts that are associated with the switch.
• Describe the properties of a distributed switch
• You set up a distributed switch on a vCenter Server system, and its settings
are propagated to all hosts that are associated with the switch.
• Distributed port groups define how a connection is made through the
distributed switch to the network.
Questions?
9
3/20/2018
Configuring and Managing Virtual Storage You Are Here

Monitoring
Virtual Networks
Virtual Storage


Storage options give you the flexibility to set up your storage based on Lesson 1: Storage Concepts
your cost, performance, and manageability requirements.
Lesson 2: iSCSI Storage
Shared storage is useful for disaster recovery, high availability, and
moving virtual machines between hosts. Lesson 3: NFS Datastores
Lesson 4: VMFS Datastores
Lesson 5: Virtual SAN Datastores
Lesson 6: Virtual Volumes
Learner Objectives
objectives:
• Describe VMware vSphere® storage technologies and datastores
• Describe the storage device naming convention
Lesson 1:
Storage Concepts

1
3/20/2018
Basic Storage Overview Storage Protocol Overview
Boot from vSphere vSphere Raw Device

ESXi Storage
SAN vMotion
vSphere HA
DRS Mapping
Hosts Protocol Support
Support Support Support Support
Fibre ● ● ● ● ●
Channel
Datastore FCoE ● ● ● ● ●
VMFS NFS
Types iSCSI ● ● ● ● ●
NFS ● ● ●
File
System DAS ● ●
Virtual
Storage Direct Fibre Volumes
● ● ●
Technologies Attached Channel

FCoE iSCSI NAS
Virtual SAN ● ● ●
About Datastores About VMFS5

A datastore is a logical storage unit VMFS5:
that can use disk space on one • Allows concurrent access to
physical device or span several shared storage.
physical devices. • Can be dynamically expanded.
Types of datastores: • Uses a 1 MB block size, good
Host Host for storing large virtual disk Host Host
• VMware vSphere® VMFS
files.
• NFS
• Uses subblock addressing,
Datastores are used to hold virtual good for storing small files: the
machine files, templates, and ISO subblock size is 8 KB.
images. • Provides on-disk, block-level
locking.
VMFS Datastore
Datastore
About NFS About Raw Device Mapping

NFS: Virtual Disk RDM RDM enables you to
store virtual machine
• Is storage shared over the
network at the file system data directly on a LUN.
level The mapping file is
• Supports NFS version 3 and stored on a VMFS
4.1 over TCP/IP Host Host datastore that points to
the raw LUN.
.vmdk Raw
.vmdk
-flat.vmdk -rdm.vmdk LUN
NFS Datastore
VMFS or NFS VMFS NTFS/ext4
2
3/20/2018
Virtual SAN Overview About Virtual Volumes
Overview
vSphere • Native representation of VMDKs on

Virtual SAN
Virtual Volumes
SAN/NAS: No LUNs or volume management.
vSphere • Works with existing SAN/NAS systems.
PE • A new control path for data operations at the
3-64 VM/VMDK level.
• Snapshots, replications, and other operations

at the VM level on external storage.
SSD HD/SSD SSD HD/SSD SSD HD/SSD
Replication Snapshots Caching • Automates control of per-VM service levels.
• Protocol endpoint provides standard protocol

Encryption Deduplication access to storage.
Virtual SAN Aggregated Datastore
• Storage containers can span an entire array.
Storage Device Naming Conventions Physical Storage Considerations

Storage devices are identified in several ways: You should discuss vSphere storage needs with your storage
• Runtime name: Uses the convention vmhbaN:C:T:L. This name is not administration team, including the following items:
persistent through reboots. • LUN sizes
• Target: Identifies iSCSI target address and port. • I/O bandwidth
• LUN: A unique identifier designated to individual or collections of hard disk • I/O requests per second that a LUN is capable of
devices. A logical unit is addressed by the SCSI protocol or SAN protocols that
• Disk cache parameters
encapsulate SCSI, such as iSCSI or Fibre Channel.
• Zoning and masking
• Identical LUN presentation to each VMware ESXi™ host
• Active-active or active-passive arrays
• Export properties for NFS datastores

• Describe VMware vSphere® storage technologies and datastores
• Describe the storage device naming convention
Lesson 2:
iSCSI Storage

3
3/20/2018
Learner Objectives iSCSI Components

objectives:
• Describe uses of IP storage with ESXi
• Describe iSCSI components and addressing
• Configure iSCSI initiators
iSCSI Addressing iSCSI Initiators
iSCSI target name:

iqn.1992-08.com.mycompany:stor1-47cf3c25
or
eui.fedcba9876543210
iSCSI alias: stor1
IP address: 192.168.36.101
iSCSI initiator name:

iqn.1998-01.com.vmware:train1-64ad4c29
or
eui.1234567890abcdef
iSCSI alias: train1
IP address: 192.168.36.88
Setting Up iSCSI Adapters ESXi Network Configuration for IP Storage

You set up software or hardware adapters before an ESXi host can work A VMkernel port must
with a SAN. be created for ESXi to
Supported iSCSI adapter types (vmhba): access software iSCSI.
The same port can be
• Software adapter used to access
• Hardware adapter: NAS/NFS storage.
• Independent hardware adapter To optimize your
• Dependent hardware adapter vSphere networking
setup, separate iSCSI
networks from
NAS/NFS networks:
• Physical separation is
preferred.
• If physical separation is
not possible, use
VLANs.
4
3/20/2018
Creating Datastores and Discovering iSCSI Targets iSCSI Security: CHAP

Based on the environment and iSCSI initiators use
storage needs, you can create
VMFS, NFS, or virtual CHAP for authentication
datastores as repositories for purposes.
virtual machines.
By default, CHAP is not
The iSCSI adapter discovers
storage resources on the
configured.
network and determines which
ones are available for access.
ESXi supports two types
192.168.36.101:3260
of CHAP authentication:
An ESXi host supports the
following discovery methods: • Unidirectional
• Static • Bidirectional
• Dynamic, also called SendTargets SendTargets
SendTargets Request Response ESXi also supports per-
target CHAP
The SendTargets response
returns the IQN and all iSCSI Target: authentication.
available IP addresses. 192.168.36.101:3260
Multipathing with iSCSI Storage Lab 9: Accessing iSCSI Storage

Software or dependent Configure access to an iSCSI datastore
hardware iSCSI: 1. Add a VMkernel Port Group to a Standard Switch
• Use multiple NICs. 2. Configure the iSCSI Software Adapter and Connect It to the Storage
• Connect each NIC to a
separate VMkernel port.
• Associate VMkernel ports
with the iSCSI initiator.
Hardware iSCSI:
• Use two or more hardware
iSCSI adapters.
Configure port binding in the Adapter

details window of the iSCSI adapter.

• Describe uses of IP storage with ESXi
• Describe iSCSI components and addressing
• Configure iSCSI initiators
Lesson 3:
NFS Datastores

5
3/20/2018
Learner Objectives NFS Components

objectives:
NAS Device or a Directory to Share
• Describe NFS components with the ESXi Host
Server with Storage
• Describe the differences between NFS v3 and NFS v4.1 over the Network
• Configure and manage NFS datastores
192.168.81.33
192.168.81.72
ESXi Host with
VMkernel Port
NIC Mapped to
Defined on Virtual
Virtual Switch
Switch
Configuring an NFS Datastore NFS v3 and NFS v4.1

Create a VMkernel port: NFS v3: NFS v4.1:
• For better performance and security, separate it from the iSCSI network. • ESXi managed multipathing • Native multipathing and session
• AUTH_SYS (root) authentication trunking
Provide the following information:
• VMware proprietary file locking • Optional Kerberos authentication
• NFS version: v3 or v4.1
• Client-side error tracking • Built-in file locking
• NFS server names or IP addresses
• Server-side error tracking
• Folder on the NFS server, for example, /templates and /nfs_share
• Host to create the datastore on
• Whether to mount the NFS file system read-only
• Datastore name
• Authentication parameters
NFS Version Compatibility with Other vSphere Technologies NFS Dual Stack Not Supported
NFS v3 locking is not compatible with NFS v4.1:
• NFS v3 uses proprietary client-side cooperative locking. NFS v4.1 uses server-
NFS v3 NFS v4.1 side locking.
vSphere vMotion and vSphere Storage vMotion Yes Yes
Best practice:
vSphere HA Yes Yes • Configure an NFS array to allow only one NFS protocol.
vSphere Fault Tolerance Yes Yes • Use either NFS v3 or NFS v4.1 to mount the same NFS share across all ESXi
hosts.
vSphere DRS and vSphere DPM Yes Yes
• Mounting an NFS share as NFS v3 on one ESXi host and as NFS v4.1 on
Stateless ESXi and Host Profiles Yes Yes another ESXi host can lead to data corruption.
vSphere Storage DRS and vSphere Storage I/O
Yes No
Control
Site Recovery Manager Yes No
Virtual Volumes Yes No
6
3/20/2018
NFS Datastore Name and Configuration Configuring AD and NFS Servers to Use Kerberos
Before enabling Kerberos on ESXi
hosts:
• Create an account in AD for NFS v4.1
access.
– Enable Kerberos DES encryption.
– Account set to never expire.
• Configure NFS servers to use

Kerberos.
• Configure NFS server shares to grant
full access to the AD account used.
Configuring Host Authentication and NFS Kerberos

Credentials Implications of Using NFS Kerberos
Add each ESXi host to the AD domain. Configure NFS Kerberos Be aware of the UID and GID on the files:
credentials. • For NFS v3, these will be root.
• Accessing files created with NFS v3 from the NFS v4.1 Kerberos client will
result in permission-denied errors.
Use the same AD user on all ESXi hosts:
• VMware vSphere® vMotion® and other features might fail if individual hosts
use different user accounts.
• Use host profiles to automate and avoid errors.
Time must be synchronized:

VCLASS.LOCAL
• Time synchronization is required for successful Kerberos authentication.
dc.vclass.local • Configure all components to synchronize to a common Network Time Protocol
server.
Kerberos must be configured on the NFS servers and ESXi hosts before
creating an NFS datastore to use Kerberos authentication.
Configuring the Datastore to Use Kerberos Viewing IP Storage Information

You should enable Kerberos authentication when creating each You can view the details of the VMFS or NFS datastores that you
datastore. created.
7
3/20/2018
Unmounting an NFS Datastore Multipathing and NFS Storage

Unmounting an NFS datastore causes the files on the datastore to One recommended configuration
become inaccessible to the ESXi host. for NFS multipathing:
• Configure one VMkernel port.
• Use adapters attached to the same NIC NIC
physical switch to configure NIC
teaming.
• Configure the NFS server with
multiple IP addresses: Physical
– IP addresses can be on the same Switch
subnet.
• To use multiple links, configure NIC
teams with the IP hash load-
balancing policy. vmnic0 vmnic1
ESXi Host
Enabling Session Trunking and Multipathing Lab 10: Accessing NFS Storage
Multiple IP addresses are configured for each NFS v4.1 datastore. Configure access to an NFS datastore
1. Configure Access to NFS Datastores
2. View NFS Storage Information
192.168.0.203, 192.168.0.204

• Describe NFS components
• Describe the differences between NFS v3 and NFS v4.1
• Configure and manage NFS datastores
Lesson 4:
VMFS Datastores

8
3/20/2018
Learner Objectives Using VMFS Datastores with ESXi Hosts

By the end of this lesson, you should be able to meet the following Use VMFS datastores whenever possible:
objectives:
• VMFS is optimized for storing and accessing large files.
• Create a VMFS datastore
• A VMFS datastore can have a maximum volume size of 64 TB.
• Increase the size of a VMFS datastore
• Delete a VMFS datastore Use RDMs if the following conditions are true of your virtual machine:
• It is taking storage array-level snapshots.
• It is clustered to a physical machine.
• It has large amounts of data that you do not want to convert into a virtual disk.
Creating and Viewing VMFS Datastores Browsing Datastore Contents

Using the New Datastore wizard, you can create VMFS datastores on
any SCSI-based storage devices that the host discovers, including Fibre
Channel, iSCSI, and local storage devices. VMFS datastores serve as
repositories for virtual machines.
Managing Overcommitted Datastores Increasing the Size of a VMFS Datastore

A datastore becomes overcommitted when the total provisioned space of Increase a VMFS datastore’s
thin-provisioned disks is greater than the size of the datastore. size to give it more space or
possibly to improve
Actively monitor your datastore capacity:
performance.
• Alarms assist through notifications:
– Datastore disk overallocation
Ways to dynamically
– Virtual machine disk usage
increase the size of a VMFS
datastore:
• Use reporting to view space usage.
• Add an extent (LUN).
Actively manage your datastore capacity:
• Expand the datastore within
• Increase the datastore capacity when necessary. its extent.
• Use VMware vSphere® Storage vMotion® to mitigate space usage problems
on a particular datastore.
9
3/20/2018
Before Increasing the Size of a VMFS Datastore Deleting or Unmounting a VMFS Datastore
In general, before making any changes to your storage allocation:
• Perform a rescan to ensure that all hosts see the most current storage.
• Quiesce I/O on all disks involved.
• Record the unique identifier, for example, the NAA ID of the volume that you
want to expand.
Multipathing Algorithms Configuring Storage Load Balancing

Arrays provide various Path selection policies exist for:
features. Some offer active- Storage
• Scalability:
active storage processors. Array
Others offer active-passive – Round Robin:
SP A SP B Storage A multipathing
storage processors. Processors
0 1 0 1 policy that performs
vSphere 6 offers native path load balancing
selection, load-balancing, and across paths
failover mechanisms. • Availability:
Third-party vendors can – Most Recently Used

Switches (MRU)
create their own software to
be installed ESXi hosts. The – Fixed
third-party software enables
hosts to properly interact with
the storage arrays.
ESXi
Hosts
Lab 11: Managing VMFS Datastores Review of Learner Objectives

Create and manage VMFS datastores You should be able to meet the following objectives:
1. Change the Name of a VMFS Datastore • Create a VMFS datastore
2. Create VMFS Datastores for the ESXi Host • Increase the size of a VMFS datastore
3. Expand a VMFS Datastore to Consume Unused Space on a LUN • Delete a VMFS datastore
4. Remove a VMFS Datastore
5. Extend a VMFS Datastore
10
3/20/2018
Learner Objectives
objectives:
• Explain the purpose of a VMware Virtual SAN™ datastore
• Describe the architecture and requirements of Virtual SAN configuration
• Describe the steps in configuring Virtual SAN
• Explain how Virtual SAN storage policies are created and used
Lesson 5:
Virtual SAN Datastores

About Virtual SAN Virtual SAN Requirements
1 Gb or 10 Gb NIC
Network
Virtual SAN
Server on
vSphere vSphere HCL SAS/SATA: RAID
Controller controller must work in
passthrough or HBA mode.
3-64
SSD SSD SSD

Cache PCI/SAS/SATA SSD
HD/SSD HD/SSD HD/SSD At least 1
of each
Data PCI/SAS/SATA HD/SSD
Virtual SAN Aggregated Datastore
• Not every node in a Virtual SAN cluster needs local storage.

A single Virtual SAN datastore is created, using storage from multiple • Hosts with no local storage can still use distributed datastore.
hosts and multiple disks in the cluster.
Configuring a Virtual SAN Datastore Disk Groups

A Virtual SAN datastore is configured in a few steps. Disk groups are Virtual SAN Disk Groups
management constructs composed of
flash-based devices and magnetic
Create disk
Enable Virtual disks:
Set up Virtual groups
SAN on the
SAN network. (manual or
cluster. • Requires one flash device:
automatic)
– Maximum of one flash device per disk
group
• Requires one HD/SSD:
– Supports up to seven devices per disk
group
• Maximum of five disk groups per host
11
3/20/2018
Cluster Summary Tab Using Virtual SAN

In the VMware vSphere® Web Client, the Summary tab of the Virtual Capabilities define the capacity, performance, and availability
SAN cluster displays the general Virtual SAN configuration information. characteristics of the underlying physical storage. The Virtual SAN
cluster presents these capabilities to vCenter Server, where they can be
consumed by virtual machines.
Requirements outline the needs of a virtual machine.
Virtual machine storage policies specify the virtual machine requirements
so that the virtual machine can be placed appropriately on the Virtual
SAN datastore.
Capabilities VM
Create policies
presented requirements
that contain VM
from Virtual based on
requirements.
SAN. capabilities.
Objects in Virtual SAN Datastores Virtual Machine Storage Policies

In a Virtual SAN datastore, files are grouped into four types of objects: VM Storage Policy • Virtual machine storage
• Namespaces policies are built before VM
Capacity
• Virtual disks Availability
deployment to reflect the
• Snapshots Performance requirements of the
application running in the
• Swap files
VMDK virtual machine.
• The policy is based on the
Snapshot VSWP Virtual SAN capabilities.
• Select the appropriate
vSphere
policy for the virtual
Virtual SAN Cluster machine based on its
Virtual SAN Datastore requirements.
• Storage objects for the
… virtual machine are then
created that meet the policy
SSD
Hard disks SSD Hard disks
SSD
Hard disks
requirements.
Configuring Virtual Machine Storage Policies Viewing a Virtual Machine’s Virtual SAN Datastore
The consumption of Virtual SAN storage is based on the virtual
machine’s storage policy.
Mirroring
The virtual machine’s hard
disk view:
• Summarizes the total storage
size and used storage space
Storage
Object • Displays the virtual machine
storage policy
• Shows the location of disk files
on a Virtual SAN datastore
Striping
12
3/20/2018
Disk Management (1) Disk Management (2)

Disk management in vSphere Web Client: • Light LED on failures:
• Easily map the location of magnetic disks and flash-based devices. – When a solid-state disk (SSD) or a magnetic disk (MD) encounters a permanent
error, Virtual SAN automatically turns the disk LED on.
• Mark disks and control disk LEDs.
• Turn disk LED on or off:
– User might need to locate a disk, so Virtual SAN supports manually turning an SSD or
MD LED on or off.
• Marking a disk as SSD:
– Some SSDs might not be recognized as SSDs by ESXi.
– Disks can be tagged or untagged as SSDs for cache.
• Marking a disk as HDD:
– Some SSDs or MDs might not be recognized by ESXi as HDDs.
– Disks can be tagged or untagged as HDDs.
– SSDs must be marked as HDDs in order to be used for capacity.
Adding Disks to a Disk Group Removing Disks from a Disk Group

Disk groups can be expanded by adding data disks to a node and adding Individual disks can be removed from a disk group.
these disks to a particular disk group.
Data is evacuated before removing the disk. Or the host must be placed
The vSphere Web Client shows any unclaimed disk in the disk in maintenance mode.
maintenance window.
Virtual SAN Cluster Member Maintenance Mode Options Removing a Host from a Virtual SAN Cluster
Before you shut down, reboot, or disconnect a host that is a member of a To remove a host that is participating in a Virtual SAN cluster:
Virtual SAN cluster, you must place the host in maintenance mode. 1. Place the host in maintenance mode.
When you place a host in maintenance mode, you can select a specific 2. Delete the disk groups associated with the host.
evacuation mechanism. 3. Remove the host from the cluster.
When any member node of a Virtual SAN cluster enters maintenance
mode, the cluster capacity is automatically reduced because the member
node no longer contributes storage to the cluster.
Option Action
Moves enough components to ensure operational

Ensure Accessibility
integrity of objects.
Full Data Migration All components are evacuated from the host.
No action is taken, which can result in degraded

No Data Migration
objects.
13
3/20/2018

• Explain the purpose of a VMware Virtual SAN™ datastore
• Describe the architecture and requirements of Virtual SAN configuration
• Describe the steps in configuring Virtual SAN
• Explain how Virtual SAN storage policies are created and used
Lesson 6:
Virtual Volumes

Learner Objectives Next-Generation Storage

By the end of this lesson, you should be able to meet the following Next-generation storage is required to meet certain criteria.
objectives:
• Describe the benefits of software-defined storage
• Describe per-virtual machine, policy-based policy management
Lower cost of storage.
• Describe how VMDK data operations are offloaded to storage arrays through
the use of VMware vSphere® API for Storage Awareness™
Reduce manual processes
Compute around storage management.
Management Storage/Availability
Network/Security
Handle explosive data growth.
Respond to new data access and

analysis requirements.
Using the Hypervisor to Transform Storage Why Virtual Volumes

Customers have major concerns about storage.
Automate service-level
agreements through virtual
machine-centric policies.
Replication Snapshots (Policy-Based Control Plane)  “Setting up storage requires too much time.”
 “Data operations are LUN-centric. We want virtual
Virtual Machine-Level Data machine-focused operations.”
Services
Hypervisor SAN/NAS Object-Based (Virtual Data Services)
Converged Pool Pool Pool
Abstract and Pool  “We overprovision storage.”

(Virtualized Data Plane)
 “Our storage budget keeps going up.”
vSphere
 “SLAs cannot ensure predictable performance.”

 “Troubleshooting is very hard.”
x86 Servers Cloud Object
SAN/NAS
Storage
14
3/20/2018
VMDKs as Native Objects Storage Array Requirements

Virtual volumes require that the following criteria be met to function
Traditional properly:
Model
VMware vSphere • A storage array compatible with vSphere API for Storage Awareness 2.0.
• Must implement vSphere API for Storage Awareness to create the storage
Virtual volumes
provider for virtual volumes:
– Firmware
– Virtual appliance
VMDKs and – Physical appliance
VMDK Data • Use APIs to handle offloaded data services on the virtual volumes.
Operations
• Enable fine capabilities.
Offloaded to
Storage Arrays • Publish a VASA provider that runs on the array through a URL.
Replication Snapshots Caching Encryption De-duplication
Storage Administration Protocol Endpoints

The protocol endpoint is set up by the
storage administrator.
No need to configure LUNs The protocol endpoint is part of the physical vSphere
vSphere or NFS shares. storage fabric. It is treated like a LUN.
The protocol endpoint supports typical SCSI
Set up a single I/O access called and NFS commands.
a protocol endpoint, to set up
Virtual volumes are bound and unbound PE
a data path from virtual machines
to virtual volumes. to a protocol endpoint: ESXi or VMware
PE vCenter Server™ initiates
the bind and unbind operation.
Existing multipathing policies and NFS
Set up a logical entity, called
storage container, to group virtual
topology requirements can be applied.
volumes for easy management.
Storage Containers Using Virtual Volumes

In vCenter Server, the storage containers are A vendor provider is a storage provider based on vSphere API for
represented by virtual datastores: Storage Awareness that allows the array to export its capabilities and
• A storage container is configured by the storage vSphere
present them to vSphere.
administrator. A protocol endpoint is a replacement for the traditional LUN and can be
• A storage container is a logical grouping of accessed with typical NFS or SCSI methods.
virtual volumes.
Virtual Volumes datastores are created on the protocol endpoint:
• A storage container’s capacity is limited only by
the hardware capacity. • Virtual volumes are objects created on the datastore.
PE
• You must set up at least one storage container

per storage system. You can have multiple
storage containers per array.
• You assign capabilities to storage containers.
Discover protocol
Register a storage endpoints Create Virtual
provider in Volumes
vCenter Server. (iSCSI, NFS, and datastores.
so on).
15
3/20/2018
Bidirectional Discovery Process Storage-Based Policy Management (1)

Storage-based policy management helps ensure that virtual machines
receive their required performance, capacity, and availability.
Protocol Endpoint Storage Container
Per-virtual machine Policies set based External storage automates
storage policies. on application needs. control of service levels.
Storage administrator sets up a
Storage administrator sets up a
storage container of defined
protocol endpoint.
capacity and capability.
Capacity
VASA provider discovers the Performance Storage Policy-Based Management

ESXi host discovers the protocol
storage container and reports to
endpoint during a scan. Availability Virtual Data Plane: Datastore
vCenter Server.
SLAs
vSphere API for Storage Virtual Volumes

Virtual volumes are created in a
Awareness is used to bind virtual
Virtual Volumes datastore.
volumes to the protocol endpoint.
SAN/NAS
Storage-Based Policy Management (2) Review of Learner Objectives

Storage policies represent service levels demanded by virtual machines. You should be able to meet the following objectives:
• Describe the benefits of software-defined storage
• Describe per-virtual machine, policy-based policy management
• Describe how VMDK data operations are offloaded to storage arrays through
the use of VMware vSphere® API for Storage Awareness™
Key Points
• You use VMFS datastores to hold virtual machine files.
• Shared storage is integral to vSphere features such as vSphere vMotion,
vSphere HA, and vSphere DRS.
• Virtual SAN enables low-end configurations to use vSphere HA, vSphere
vMotion, and vSphere Storage vMotion without requiring external shared
storage.
• Virtual SAN clusters direct-attached server disks to create shared storage
designed for virtual machines.
• Virtual Volumes is a storage management approach that enables
administrators to differentiate virtual machine services per application.
• Key components of the Virtual Volumes functionality include virtual volumes,
VASA providers, storage containers, protocol endpoints, and virtual datastores.
Questions?

16
3/20/2018
Virtual Machine Management You Are Here

Monitoring
Virtual Networks
Virtual Storage


You must perform many cumbersome tasks when using physical Lesson 1: Creating Templates and Clones
machines. For example, you must move server storage from one storage
array to another, deploy servers with the same configuration, and Lesson 2: Modifying Virtual Machines
dynamically add resources. Lesson 3: Migrating Virtual Machines
The ability to clone and deploy virtual machines from a template enables Lesson 4: Creating Virtual Machine Snapshots
you to capture the state of a problematic virtual machine or deploy a
virtual machine from a preconfigured standard. Lesson 5: Creating vApps
VMware vSphere® enables you to migrate virtual machines and virtual Lesson 6: Working with Content Libraries
machine disks from one VMware ESXi™ host to another while the virtual
machines are running.
Learner Objectives
objectives:
• Create a template
• Deploy a virtual machine from a template
• Clone a virtual machine
• Enable guest operating system customization by VMware vCenter Server™
Lesson 1:
Creating Templates and Clones

1
3/20/2018
Using a Template Creating a Template

A template is a master copy of a virtual machine. It is used to create and Clone the virtual machine to a
provision new virtual machines. template:
• The virtual machine can be
powered on or powered off.
Convert the virtual machine to a
template:
• The virtual machine must be
powered off.
Clone a template:
• Used to create a new template
based on one that existed
previously.
Deploying a Virtual Machine from a Template Updating a Template

To deploy a virtual machine, you must provide such information as the Update a template to include new
virtual machine name, inventory location, host, datastore, and guest patches, make system changes,
operating system customization data. and install new applications:
1. Convert the template to a virtual
machine.
2. Place the virtual machine on an
isolated network to prevent user
access.
3. Make appropriate changes to the
virtual machine.
4. Convert the virtual machine to a
template.
Cloning a Virtual Machine Customizing the Guest Operating System

Cloning a virtual machine Use the Guest Operating System Customization wizard to make virtual
creates a virtual machine that machines created from the same template or clone unique.
is an exact copy of the original: Customizing a guest operating system enables you to change:
• Cloning is an alternative to • Computer name
deploying a virtual machine.
• Network settings
• The virtual machine being
• License settings
cloned can be powered on or
powered off. • Windows Security Identifier
During cloning or deploying virtual machines from a template:

• You can create a specification to prepare the guest operating systems of virtual
machines.
• Specifications can be stored in the database.
• You can edit specifications in the Customization Specifications Manager.
• Windows and Linux operating systems are supported.
2
3/20/2018
Deploying Virtual Machines Across Data Centers Lab 12: Using Templates and Clones
Virtual machine Deploy a new virtual machine from a template and clone a virtual
deployment is allowed machine
across data centers: 1. Create a Virtual Machine Template
• Clone a virtual machine 2. Create Customization Specifications
from one data center to 3. Deploy a Virtual Machine from a Template
another. 4. Clone a Powered-On Virtual Machine
• Deploy from a template in
one data center to a virtual
machine in a different data
center.

• Create a template
• Deploy a virtual machine from a template
• Clone a virtual machine
• Enable guest operating system customization by VMware vCenter Server™
Lesson 2:
Modifying Virtual Machines

Learner Objectives Modifying Virtual Machine Settings

By the end of this lesson, you should be able to meet the following You can modify a virtual
objectives: machine’s configuration in its
• Describe virtual machine settings and options Edit Settings dialog box:
• Add a hot-pluggable device • Add virtual hardware:
• Dynamically increase the size of a virtual disk – Some hardware can be added
• Add a raw device mapping (RDM) to a virtual machine while the virtual machine is
powered on.
• Remove virtual hardware:
– Only when the virtual machine
is powered off
• Set virtual machine options.
• Control a virtual machine’s
CPU and memory resources.
3
3/20/2018
Hot-Pluggable Devices Creating an RDM

The CPU hot-plug option An RDM (a -rdm.vmdk file) enables a virtual machine to gain direct
enables you to add CPU access to a physical LUN.
resources to a running virtual Encapsulating disk information in the RDM enables the VMkernel to lock
machine: the LUN so that only one virtual machine can write to it.
• Examples of hot-pluggable Items to define when creating an RDM:
devices: USB controllers,
• Target LUN: LUN that the RDM will map to
Ethernet adapters, and hard
disk devices. • Mapped datastore:
Stores the RDM file with
With supported guest the virtual machine or
operating systems, you can on a different datastore
also add CPU and memory • Compatibility mode
while the virtual machine is • Virtual device node
powered on.
Dynamically Increasing a Virtual Disk’s Size Inflating a Thin-Provisioned Disk

You can increase the size of a virtual disk that belongs to a powered-on Thin-provisioned virtual disks can be converted to a thick, eager-zeroed
virtual machine: Increases the size format.
of the existing
• The virtual disk must be virtual disk file. To inflate a thin-provisioned disk:
in persistent mode. • The virtual machine must be powered off.
• It must not contain • Right-click the virtual machine’s .vmdk file and select Inflate.
snapshots.
Dynamically increase a
virtual disk from, for
example, 2 GB to 20 GB.
Or you can use VMware vSphere® Storage vMotion® and select a thick-
provisioned disk as the destination.
Virtual Machine Options VMware Tools Options

On the VM Options tab, you can set or change virtual machine options
to run VMware Tools™ scripts, control user access to the remote
console, configure startup behavior, and more.
Customize power
button actions.
VM Display Name
Schedule VMware
.vmx File Location Tools scripts.
VM Directory
Update checks
Guest Operating
System Type
4
3/20/2018
Troubleshooting a Failed VMware Tools Installation on a

Boot Options Guest Operating System
Problems:
• VMware Tools installation errors before completion.
• VMware Tools installation fails to complete.
• Unable to complete VMware Tools for Windows or Linux installation.
• VMware Tools hangs when installing or reinstalling.
Solutions:
1. Verify that that the guest operating system that you are trying to install is fully
Delay power on. certified by VMware.
2. Verify that the correct operating system is selected.
Boot into BIOS. 3. Verify that the ISO image is not corrupted.
4. If installing on a Windows operating system, ensure that you are not
Retry after experiencing problems with your Windows registry.
failed boot.
5. If installing on a 64-bit Linux guest operating system, verify that no
dependencies are missing.
Lab 13: Modifying Virtual Machines Review of Learner Objectives

Modify a virtual machine’s hardware and add a raw LUN to a virtual You should be able to meet the following objectives:
machine • Describe virtual machine settings and options
1. Increase the Size of a VMDK File • Add a hot-pluggable device
2. Adjust Memory Allocation on a Virtual Machine • Dynamically increase the size of a virtual disk
3. Rename a Virtual Machine in the vCenter Server Inventory • Add a raw device mapping (RDM) to a virtual machine
4. Add and Remove a Raw LUN on a Virtual Machine
5. Expand a Thin-Provisioned Virtual Disk
Learner Objectives
objectives:
• Verify VMware vSphere® vMotion® requirements, including CPU constraints
and guidelines
• Perform a vSphere vMotion migration
• Perform a vSphere Storage vMotion migration
Lesson 3: • Perform a cross-host vSphere vMotion migration
Migrating Virtual Machines • Describe the major enhancements to vSphere vMotion in vSphere 6

5
3/20/2018
Migrating Virtual Machines Comparison of Migration Types

Migration means moving a virtual machine from one host, datastore, or Virtual Change Across Shared
Migration CPU
vCenter Server system to another host, datastore, or vCenter Server Type
Machine Host or vCenter Storage
Compatibility
system. Power State Datastore? Servers? Required?
Types of migrations: Host or

Different CPU
Cold Off datastore Yes No
• Cold: Migrate a virtual machine that is powered off. families allowed
or both
• Suspended: Migrate a virtual machine that is suspended.
Host or Must meet CPU
• vSphere vMotion: Migrate a virtual machine that is powered on. Suspended Suspended datastore Yes No compatibility
• vSphere Storage vMotion: Migrate a virtual machine’s files, while the virtual or both requirements
machine is powered on, to another datastore. Must meet CPU
vSphere
On Host Yes Yes compatibility
Concurrent migrations are possible: vMotion
requirements
• A maximum of 128 concurrent vSphere vMotion accesses to a single VMware
vSphere® VMFS datastore. vSphere
Storage On Datastore Yes No N/A
• A maximum of 8 concurrent cloning, deployment, or vSphere Storage vMotion vMotion
accesses to a single VMFS datastore.
Cross-host Must meet CPU
vSphere On Both Yes No compatibility
vMotion requirements
vSphere vMotion Migration How vSphere vMotion Migration Works

A vSphere vMotion migration moves a powered-on virtual machine from In the diagram, the source host is ESXi01 and the target host is ESXi02.
one host to another. The source host and the target host have access to the shared datastore
holding the virtual machine’s files.
vSphere vMotion provides these capabilities:
• Improves overall hardware use VM A VM A
• Continuous virtual machine operation while accommodating scheduled
hardware downtime
Memory ESXi-01 ESXi-02
• VMware vSphere® Distributed Resource Scheduler™ balancing virtual Bitmap
machines across hosts
vSphere
Memory
vMotion
Network
Virtual Machine
Port Group
vSphere vMotion Migration Requirements Host Requirements for vSphere vMotion Migration
A virtual machine must meet the following requirements: Source and destination hosts must have these characteristics:
• It must not have a connection to an internal standard switch: virtual switch with • Accessibility to all storage (Fibre Channel, iSCSI, or NAS) used by the virtual
zero uplink adapters. machine:
• It must not have a connection to a virtual device, such as a CD/DVD or floppy – 128 concurrent vSphere vMotion migrations per VMFS datastore
drive, with a local image mounted. • At least a 1 Gigabit Ethernet (1GigE) network:
• It must not have CPU affinity configured. – Four concurrent vSphere vMotion migrations on a 1 Gbps network
• If the virtual machine’s swap file is not accessible to the destination host, – Eight concurrent vSphere vMotion migrations on a 10 Gbps network
vSphere vMotion must be able to create a swap file accessible to the • Compatible CPUs:
destination host before migration can begin. – CPU feature sets of both the source and destination host must be compatible.
• If a virtual machine uses an RDM, the RDM and the physical disk to which it – Some features can be hidden by using Enhanced vMotion Compatibility (EVC) or
maps must be accessible by the destination host. compatibility masks.
6
3/20/2018
CPU Constraints on vSphere vMotion Migration Other Cluster Settings: EVC for vSphere DRS
Enhanced vMotion Compatibility is a cluster feature that prevents
CPU Characteristics Exact Match Required Reason vSphere vMotion migrations from failing because of incompatible CPUs.
Clock speeds, cache sizes,

Virtualized away by the
hyperthreading, and number of N/A
VMkernel.
cores
Manufacturer (Intel or AMD)
Instruction sets contain many
family and generation (Opteron4, Applicable
small differences.
Intel Westmere)
Presence or absence of SSE3, Multimedia instructions usable

Applicable
SSSE3, or SSE4.1 instructions directly by applications.
Virtualized away by the

For 32-bit VMs: N/A
VMkernel.
Virtualization hardware assist
For 64-bit VMs on Intel: Intel 64-bit with VMware
Applicable implementation uses Intel VT.
Execution-disable Guest operating system relies on

Applicable but customizable
(NX/XD bit) NX/XD bit if detected.
CPU Baselines for an EVC Cluster EVC Cluster Requirements

EVC works at the cluster level, using CPU baselines to configure all All hosts in the cluster must meet the following requirements:
processors included in the cluster enabled for EVC.
• Use CPUs from a single vendor, either Intel or AMD:
– Use Intel CPUs with Core 2 micro architecture and newer.
– Use AMD first-generation Opteron CPUs and newer.
• Be enabled for hardware virtualization: AMD-V or Intel VT

A baseline is a set of CPU
features supported by • Be enabled for execution-disable technology: AMD No eXecute (NX) or Intel
every host in the cluster. eXecute Disable (XD)
CPU Baseline Feature Set • Be configured for vSphere vMotion migration
Applications in virtual machines must be CPU ID compatible.
CPUID CPUID CPUID CPUID
X… X… X… K…
Cluster Enabled for EVC
Hiding or Exposing NX/XD Identifying CPU Characteristics

AMD No Execute (NX) and Intel Execute Disable (XD) technologies mark To identify CPU characteristics, use the server and CPU specifications or
memory pages as data-only to prevent malicious software exploits and use the VMware CPU identification utility.
buffer overflow attacks.
Choose between NX/XD security features For future CPU features,

and broadest vSphere vMotion compatibility. edit mask at the bit level.
7
3/20/2018
Checking vSphere vMotion Errors vSphere Storage vMotion in Action

When you select the host and cluster, a validation check is performed to vSphere Storage vMotion uses
verify that most vSphere vMotion requirements were met. an I/O mirroring architecture to Read/write
copy disk blocks between source I/O to virtual
disk.
and destination:
VM VM
1. Initiate storage migration. Process Process
VMkernel
2. Use the VMkernel data mover or Mirror Driver
VMware vSphere® Storage APIs
- Array Integration to copy data.
Data Mover
3. Start a new virtual machine
process.
4. Mirror I/O calls to file blocks that
are already copied to virtual disk
on the destination datastore. Storage Array
5. Cut over to the destination virtual

machine process to begin
accessing the virtual disk copy. VAAI
Source Datastore Destination Datastore
vSphere Storage vMotion Guidelines and Limitations Cross-Host vSphere vMotion

Guidelines: Cross-host vSphere vMotion migration enables a virtual machine to
• Plan the migration and coordinate with administrators. change its datastore and host simultaneously, even if the two hosts do
not have shared storage.
• Perform migrations during off-peak hours.
• This technique combines vSphere vMotion migration and vSphere Storage
• Ensure that the host has access to source datastores and target datastores. vMotion migration into a single operation
Limitations: • You can migrate between hosts and clusters without shared storage.
• Virtual machine disks must be in persistent mode or be RDMs. Layer 2 Network
ESXi ESXi
vCenter
Server
Cross-Host vSphere vMotion Migration Considerations Migration Between vCenter Server Instances
In vSphere 6, multiple changes can occur simultaneously with cross-host In vSphere 6, vSphere vMotion can migrate virtual machines between
vSphere vMotion migrations. linked vCenter Server instances. This type of migration requires:
• ESXi hosts and vCenter Server systems must be upgraded to vSphere 6.
• vCenter Server instances must be in Enhanced Linked Mode.
• Hosts must be time-synchronized.
vSphere vMotion Network
Network A Network B
ESXi ESXi
Enhanced Linked
Mode
vCenter vCenter
Server A Server B
8
3/20/2018
vSphere vMotion TCP/IP Stacks Long-Distance vSphere vMotion Migration

In vSphere 6, each host has a second TCP/IP stack dedicated to Long-distance vSphere vMotion migrations span larger networks with
vSphere vMotion migration. higher latency.
userworld hostd PING DHCP

Use cases for long-distance
User vSphere vMotion migration:
VMkernel
vSphere FT Virtual SAN NFS vSphere vMotion • Permanent migrations
• Disaster avoidance
• VMware vCenter™ Site
VMKTCP-API Recovery Manager™ and
disaster avoidance testing
Default TCP/IP vSphere vMotion TCP/IP • Multisite load balancing
• Separate Memory Heap • Separate Memory Heap • Follow-the-Sun scenario support
• ARP Tables • ARP Tables
• Routing Table • Routing Table
• Default Gateway • Default Gateway
Networking Requirements for Long-Distance vSphere vMotion

Migration Network Checks for Migrations Between vCenter Server Instances
vSphere vMotion migrations between vCenter Server instances must vCenter Server performs several network compatibility checks to prevent
connect over layer 3 connections: the following configuration problems:
• Virtual machine network: • MAC address compatibility on the destination host
– L2 connection • vSphere vMotion migration from a distributed switch to a standard switch
– Same virtual machine IP address available at destination
• vSphere vMotion migration between distributed switches of different versions
• vSphere vMotion network:
• vSphere vMotion migration to an internal network, for example, a network
– L3 connection without a physical NIC
– Secure (dedicated or encrypted)
– 250 Mbps per vSphere vMotion operation
Lab 14: Migrating Virtual Machines Review of Learner Objectives

Use vSphere vMotion and vSphere Storage vMotion to migrate virtual You should be able to meet the following objectives:
machines • Verify VMware vSphere® vMotion® requirements, including CPU constraints
1. Migrate Virtual Machine Files from the Local Storage to the Shared Storage and guidelines
2. Create a Virtual Switch and a VMkernel Port Group for vSphere vMotion • Perform a vSphere vMotion migration
Migration • Perform a vSphere Storage vMotion migration
3. Perform a vSphere vMotion Migration of a Virtual Machine on a Shared • Perform a cross-host vSphere vMotion migration
Datastore
• Describe the major enhancements to vSphere vMotion in vSphere 6
4. Perform a Cross-Host vSphere Storage vMotion Migration to a Local
Datastore
5. Prepare for the Next Lab
9
3/20/2018
Learner Objectives
objectives:
• Take a snapshot of a virtual machine and manage multiple snapshots
• Delete virtual machine snapshots
• Consolidate snapshots
Lesson 4:
Creating Virtual Machine
Snapshots

Virtual Machine Snapshots Virtual Machine Snapshot Files

Snapshots enable you to preserve the state of the virtual machine so that A snapshot consists of a set of files: the memory state file (.vmsn), the
you can repeatedly return to the same state. description file (-00000#.vmdk), and the delta file (-00000#-
delta.vmdk).
The snapshot list file (.vmsd) keeps track of the virtual machine’s
snapshots.
Taking a Snapshot Managing Snapshots

You can take a snapshot while a virtual machine is powered on, powered The Snapshot Manager enables you
off, or suspended. to review all snapshots for the active
virtual machine and act on them
A snapshot captures the state of the virtual machine: memory state, directly.
settings state, and disk state.
Actions you can perform:
Snapshots are not backups.
• Revert to a snapshot.
• Delete one or all snapshots.
committed to disk
transactions
Pending
.vmdk
10
3/20/2018
Deleting a Virtual Machine Snapshot (1) Deleting a Virtual Machine Snapshot (2)
If you delete a snapshot one or more levels above You Are Here, the If you delete the current snapshot, the changes are committed to its
snapshot state is deleted. The snap01 data is committed into the parent. The snap02 data is committed into snap01 data, and the snap02
previous state (base disk) and the foundation for snap02 is retained. -delta.vmdk file is deleted.
base disk (5GB) +

base disk (5GB)
snap01 data base disk (5GB)
snap01 delta (1GB) snap01 delta (1GB) +

snap01 delta (1GB)
snap02 delta (2GB)
snap02 delta (2GB) snap02 delta (2GB)
You are here. You are here.
Deleting a Virtual Machine Snapshot (3) Deleting All Virtual Machine Snapshots
If you delete a snapshot one or more levels below You Are Here, The delete-all-snapshots mechanism uses storage space efficiently. The
subsequent snapshots are deleted and you can no longer return to those size of the base disk does not increase. Just like a single snapshot
states. The snap02 data is deleted. deletion, changed blocks in the snapshot overwrite their counterparts in
the base disk.
base disk (5GB) base disk (5GB) +
base disk (5GB)
snap01/02 data
snap01 delta (1GB) snap01You

delta
are(1GB)
here.
snap02 delta (2GB)

You are here.
snap02 delta (2GB)

You are here.
About Snapshot Consolidation Discovering When to Consolidate

Snapshot consolidation is a method to commit a chain of snapshots to The Snapshot Manager displays no snapshots. However, a warning on
the base disks when the Snapshot Manager shows that no snapshots the Monitor > Issues tab of the virtual machine notifies the user that a
exist, but the delta files still remain on the datastore. consolidation is required.
Snapshot consolidation is intended to resolve problems that might occur
with snapshots:
• The snapshot descriptor file is committed correctly, but the Snapshot Manager
incorrectly shows that all the snapshots are deleted.
• The snapshot files (-delta.vmdk)are still part of the virtual machine.
• Snapshot files continue to expand until the virtual machine runs out of
datastore space.
11
3/20/2018
Performing Snapshot Consolidation Lab 15: Managing Virtual Machines

After the snapshot consolidation warning appears, the user can use the Perform virtual machine management tasks
vSphere Web Client to consolidate the snapshots:
1. Unregister a Virtual Machine from the vCenter Server Appliance Inventory
• Select Snapshots > Consolidate to reconcile snapshots.
2. Register a Virtual Machine in the vCenter Server Appliance Inventory
• All snapshot delta disks are committed to the base disks.
3. Unregister and Delete a Virtual Machine from the Disk
4. Take Snapshots of a Virtual Machine
5. Revert to a Snapshot
6. Delete an Individual Snapshot
7. Use the Delete All Function in the Snapshot Manager

• Take a snapshot of a virtual machine and manage multiple snapshots
• Delete virtual machine snapshots
• Consolidate snapshots
Lesson 5:
Creating vApps

Learner Objectives Managing Virtual Machines with a vApp

By the end of this lesson, you should be able to meet the following A vApp is an object in the vCenter Server inventory:
objectives: • A vApp is a container for one or more virtual machines.
• Describe a vApp • A vApp can be used to package and manage multitiered applications.
• Build a vApp
• Use a vApp to manage virtual machines
• Deploy and export a vApp
12
3/20/2018
vApp Characteristics Exporting and Deploying vApps

You can configure several Exporting the vApp as an OVF Deploying the OVF template:
template:
vApp settings by right-clicking • Deploy multitier vApps.
the vApp: • Share with others.
• Deploy OVF from VMware Virtual
• CPU and memory allocation • Use for archive purposes. Appliance Marketplace.
• IP allocation policy
You can also configure the

virtual machine startup and
shutdown order.
Lab 16: Managing vApps Review of Learner Objectives

Perform vApp management tasks You should be able to meet the following objectives:
1. Create a vApp • Describe a vApp
2. Power On a vApp • Build a vApp
3. Remove a vApp • Use a vApp to manage virtual machines
• Deploy and export a vApp
Learner Objectives
objectives:
• Describe the types of content libraries
• Recognize how to import content into a content library
• Identify how to publish a content library for external use
Lesson 6:
Working with Content Libraries

13
3/20/2018
About the Content Library Benefits of Content Libraries

A content library is a repository of OVF templates and other files that can
be shared and synchronized across vCenter Server systems.
Sharing and Consistency
Storage Efficiency
Metadata
Secure Subscription
Library Subscription Types Subscribing to vCloud Director 5.5 Catalogs

Three types of content library are available: local, published, and You can subscribe a content library to VMware vCloud Director® 5.5.
subscribed .
vCenter Server 6
Published
Local Subscribed
Local library that makes
Library of content that Library that syncs with a
content available for
you control published library
subscription Content Catalogs in
vCloud Director 5.5
On-Demand
Automatic >>>>
>>>>
The subscription process is the same
Metadata as with the published content library:
• Uses the published URL
Library Content • Immediately download all library content
Download library content only when needed • Static user name (always vcsp)
Saves storage backing space. Only metadata is retrieved. Content is downloaded as needed when
creating virtual machines or synchronizing content
and password
Publish and Subscribe Synchronization and Versioning

Interactions between the publisher and subscriber can include Synchronization is used to resolve versioning discrepancies between the
connectivity, security, an actionable files. publisher and the subscribing content libraries.
vCenter Server vCenter Server
Templates
vCenter Server vCenter Server
Other
HTTP/NFC
Transfer Service Transfer Service
Content Library Service Content Library Service Transfer Service Transfer Service
Subscribe using URL.
Content Library Service VCSP Content Library Service
Subscription URL
Password (Optional) VMware Content Subscription Protocol
14
3/20/2018
Content Library Requirements and Limitations Creating a Content Library

You can create a content library in the vSphere Web Client and populate
it with templates to use to deploy virtual machines or vApps in your
virtual environment.
Single storage backing and datastore (64 TB maximum).
Maximum 256 library Items.
Maximum 10 simultaneous synchronizations.
Synchronization occurs once every 24 hours.
License to scale based on content library usage.
Selecting Storage for the Content Library Populating Content Libraries with Content
You select storage for the content library based on the type of library you You populate a content library with templates that you can use to
are creating. provision new virtual machines.
To add templates to a content library, use one of the following methods:
• Clone a virtual machine to a template in the content library.
• Clone a template from the vSphere inventory or from another content library.
• Clone a vApp.
• Import a template from an URL.
• Import an OVF file from your local file system.
Importing Items into the Content Library Deploying a Virtual Machine to a Content Library
Your source to import items in to a content library can be a file stored on You can clone virtual machines or virtual machine templates to templates
your local machine or a file stored on a Web server. in the content library and use them later to provision virtual machines on
a virtual data center, a data center, a cluster, or a host.
Click this icon to import OVF

pages and other file types
into the content library.
15
3/20/2018
Publishing a Content Library for External Use Review of Learner Objectives

You can publish a content library for external use and add password You should be able to meet the following objectives:
protection by editing the content library settings: • Describe the types of content libraries
• Users access the library through the subscription URL that is system • Recognize how to import content into a content library
generated.
• Identify how to publish a content library for external use
Key Points
• vCenter Server provides features for provisioning virtual machines, such as
templates and cloning.
• By deploying virtual machines from a template, you can create many virtual
machines easily and quickly.
• You can use vSphere vMotion to move virtual machines while they are
powered on.
• You can use vSphere Storage vMotion to move virtual machines from one
datastore to another datastore.
• You can use virtual machine snapshots to preserve the state of the virtual
machine so that you can return to the same state repeatedly.
• A vApp is a container for one or more virtual machines. The vApp can be used
to package and manage related applications.
• Content libraries provide simple and effective management for virtual machine
templates, vApps, and other types of files for vSphere administrators.
Questions?

16
3/20/2018
Resource Management and Monitoring You Are Here

Monitoring
Virtual Networks
Virtual Storage


Although the VMkernel works proactively to avoid resource contention, Lesson 1: Virtual CPU and Memory Concepts
maximizing performance requires both analysis and ongoing monitoring.
Lesson 2: Resource Controls and Resource Pools
Lesson 3: Monitoring Resource Use
Lesson 4: Using Alarms
Lesson 5: vRealize Operations Manager
Learner Objectives
objectives:
• Discuss CPU and memory concepts in a virtualized environment
• Describe what overcommitment of a resource means
Lesson 1: • Identify additional technologies that improve memory utilization
Virtual CPU and Memory • Describe how VMware vSphere® Virtual Symmetric Multiprocessing works and
Concepts how hyperthreading is used by the VMkernel

3/20/2018
Memory Virtualization Basics Virtual Machine Memory Overcommitment

VMware vSphere® has three Virtual Machine Memory is overcommitted Host machine memory = 2 GB
layers of memory: when the combined working
Total configured VM memory = 4 GB
• Guest operating system virtual memory footprint of all virtual
memory is presented to Application
Guest OS machines exceeds that of the
Virtual Memory
applications by the operating host memory sizes. On On On Off
system.
Virtual machines do not
• Guest operating system Operating Guest OS
always use their full allocated
physical memory is presented Physical Memory
System memory. 1GB
to the virtual machine by the 1GB 1GB 1GB
VMkernel. An ESXi host transfers

• Host machine memory that is ESXi Host memory from idle virtual
managed by the VMkernel ESXi Host machines to virtual machines vmxd-*.vswp
provides a contiguous, Machine Memory that need more memory to
addressable memory space improve memory utilization. VM 1 VM 2 VM 3
that is used by the virtual .vswp .vswp .vswp
machine. Memory overhead is stored in
a swap file (.vswp).
Memory Reclamation Techniques Virtual SMP

Economize use of physical memory pages:
uni dual quad
• Transparent page sharing allows pages with identical contents to be stored VM VM VM
only once.
Deallocate memory from one virtual machine for another:
• Ballooning mechanism, active when memory is scarce, forces virtual machines vCPU vCPU vCPU vCPU vCPU vCPU vCPU
to use their own paging areas.
Virtual
Memory compression:
• Attempts to reclaim some memory performance when memory contention is Physical
high.
Thread
Host-level SSD swapping:
Core LCPU LCPU LCPU LCPU LCPU LCPU LCPU LCPU
• Use of a solid-state drive (SSD) on the host for a host cache swap file might Socket
increase performance.
Page virtual machine memory out to disk:
Single-Core Dual- Dual-Core Single- Quad-Core Single-
• Use of VMkernel swap space is the last resort due to the poor performance. Socket System Socket System Socket System
Hyperthreading CPU Load Balancing

Hyperthreading enables a core to dual
uni dual uni uni uni
execute two threads, or sets of VM VM VM VM VM
VM
instructions, at the same time.
Hyperthreading provides more scheduler
throughput.
To enable hyperthreading:
1. Verify that the host system supports
hyperthreading.
2. Enable hyperthreading in the system
BIOS.
LCPU LCPU
3. Ensure that hyperthreading for the ESXi LCPU
LCPU LCPU
LCPU
host is turned on. LCPU LCPU LCPU
LCPU
4. Hyperthreading is enabled by default. LCPU LCPU
Dual-Core Single-Socket Hyperthreaded Dual-Core,

System with Hyperthreading Dual-Socket System
3/20/2018

• Discuss CPU and memory concepts in a virtualized environment
• Describe what overcommitment of a resource means
• Identify additional technologies that improve memory utilization
• Describe how VMware vSphere® Virtual Symmetric Multiprocessing works and Lesson 2:
how hyperthreading is used by the VMkernel Resource Controls and Resource
Pools

Learner Objectives Shares, Limits, and Reservations

By the end of this lesson, you should be able to meet the following A virtual machine powers on only if its reservation can be guaranteed.
objectives:
• Assign share values for CPU, memory, and disk resources
• Describe how virtual machines compete for resources
• Create a resource pool Available Capacity Limit
• Set resource pool attributes
• Establish CPU and memory reservations and limits
Shares are used to
• Describe expandable reservations compete in this range.
Reservation
0 MHz/MB
How Virtual Machines Compete for Resources About Resource Pools

Virtual machines are resource consumers. The default resource settings A resource pool is a logical abstraction of hierarchically managed CPU
that you assign during creation work well for most machines. and memory resources.
1000 1000 1000
Number of shares. VM A VM B VM C
Root
1000 3000 1000 Resource
Pool
Change number of shares. VM A VM B VM C
Sibling
1000 3000 1000 1000 Resource
Pools Parent
Power on virtual machine. VM A VM B VM C VM D Resource
Pool
1000 3000 1000 Child
Resource
Power off virtual machine. VM A VM B VM D Pool
3/20/2018
Resource Pool Attributes Reasons to Use Resource Pools

You can create a child resource pool Use of resource pools can provide these benefits:
of any VMware ESXi™ host, • Flexible hierarchical organization
resource pool, or VMware vSphere®
Distributed Resource Scheduler™ • Isolation between pools and sharing in pools
cluster. • Access control and delegation
• Shares: Low, Normal, High, Custom • Separation of resources from hardware
• Reservations: In MHz or GHz, MB or GB • Management of sets of virtual machines running a multitier service
• Limits: • Ability to prioritize virtual machine workloads
– In MHz or GHz, MB or GB.
– Unlimited access, by default, up to
maximum amount of resource accessible.
• Reservation type:
– Expandable selected: Virtual machines and
subpools can draw from this pool’s parent.
– Expandable deselected: Virtual machines
and subpools can draw only from this pool,
even if its parent has free resources.
Resource Pool Case Study Resource Pool Example

Company X’s IT department has two internal customers: This example shows where resource attributes are set on a resource
• The Finance Department supplies two-thirds of the budget. pool.
• The Engineering Department supplies one-third of the budget.
Each internal customer has both production and test/dev virtual

machines.
You must control the resource consumption of the test/dev virtual
machines.
Engineering Pool
You must also ensure the entitled resources of the Finance Department.
CPU Shares: 1000
Reservation: 1,000 MHz
Limit: 4,000 MHz
Expandable Reservation: Yes
Eng-Test VM Eng-Prod VM
CPU Shares: 1000 CPU Shares: 2000
Reservation: 0 MHz Reservation: 250 MHz
Limit: 4000 MHz Limit: 4000 MHz
Resource Pools Example: CPU Shares Resource Pools Example: CPU Contention
In this example, the Finance resource pool has twice as many CPU Srv01
shares as the Engineering resource pool. It is entitled to twice as many All VMs below are running
on the same physical CPU.
CPU resources as the Engineering resource pool.
Standalone Host: Srv001 Engineering

Engineering Pool
pool Finance Pool
Engineering pool
(Root Resource Pool) -%33 of Physical CPU -67% of Physical CPU
Eng-Test VM Eng-Prod VM Fin-Test VM Fin-Prod VM

Engineering
Engineering Pool
pool Finance Pool
Engineering pool CPU Shares: 1000
CPU Shares: 1000 CPU Shares: 2000 CPU Shares: 2000
Engineering ~33%
11%
22%
Eng‐test gets ~33% of Engineering’s CPU
allocation: approximately 11% of the physical
Finance ~67%
CPU.
Eng-Test VM Eng-Prod VM Fin-Test VM Fin-Prod VM 45% 22%
CPU Shares: 1000 CPU Shares: 2000 CPU Shares: 1000 CPU Shares: 2000
3/20/2018
Expandable Reservation Example of Expandable Reservation (1)

Root Resource Pool eCommerce resource pools
Root Resource Pool Borrowing resources occurs
Total CPU: 10,200 MHz reserve 2,200 MHz of the 3,000
Total CPU: 10,200 MHz recursively from the ancestors of
Total Memory: 3,000 MB Total Memory: 3,000 MB MHz that the Retail pool has
the current resource pool:
reserved.
• The Expandable Reservation option Retail Pool
Retail Pool must be enabled. Power on virtual machines in the
• This option offers more flexibility but Expandable Reservation: No eCommerce Web pool.
less protection. With Expandable Reservation
eCommerce Apps eCommerce Web
eCommerce Apps eCommerce Web Expanded reservations are not Pool Pool disabled on the eCommerce Web
Pool Pool released until the virtual machine Reservation: Reservation: pool, VM3 cannot be started with
Reservation: Reservation: 1,200 MHz 1,000 MHz a reservation of 500 MHz:
1,200 MHz 1,000 MHz that caused the expansion is shut Expandable? Yes Expandable? No
Expandable? Yes Expandable? No down or its reservation is reduced. • Lower the virtual machine
VM1 VM2
reservation.
R=400 R=300
• Enable Expandable Reservation.
A mismanaged or mis-sized expandable reservation VM3 • Increase the eCommerce Web
might claim all unreserved capacity. R=500
pool’s reservation.
Example of Expandable Reservation (2) Admission Control for CPU and Memory Reservations
Root Resource Pool Enable Expandable Reservation Admission control is used to ensure that you cannot allocate resources
Total CPU: 10,200 MHz on the eCommerce Web pool. that are not available.
Total Memory: 3,000 MB
**200 MHz Used by Retail** The system considers the
resources available in the child Create a subpool Increase a pool’s
Retail Pool Power on a virtual machine.
with its own reservation. reservation.
Reservation: 3,000 MHz resource pool and its direct
**Full Reservation Used** parent resource pool.
eCommerce Apps eCommerce Web

The virtual machine’s reservation Succeed Yes Can this pool
satisfy reservation?
Pool Pool is charged against the reservation
Reservation: Reservation: for eCommerce Web. No
1,200 MHz 1,000 MHz
Expandable? Yes Expandable? Yes eCommerce Web’s reservation is
charged against the reservation No Expandable
Fail
VM4 VM5 VM1 VM2 reservation?
R=500 R=500 R=400 R=300 for Retail.
VM6 VM7 VM3 Yes. Go to parent pool.

R=500 R=500 R=500
Resource Pool Summary Tab Resource Reservation Tab

The resource pool Summary tab displays information that applies to the On the Resource Reservation tab, you can view information about a
host machine and its resources. resource pool’s CPU, memory, and storage resources.
3/20/2018
Scheduling Changes to Resource Settings Lab 17: Managing Resource Pools

You can schedule a task to change the resource settings of a resource Create and use resource pools on an ESXi host by using vCenter Server
pool or virtual machine. 1. Create CPU Contention
2. Create Resource Pools
3. Verify Resource Pool Functionality

• Assign share values for CPU, memory, and disk resources
• Describe how virtual machines compete for resources
• Create a resource pool
• Set resource pool attributes
• Establish CPU and memory reservations and limits Lesson 3:
• Describe expandable reservations
Monitoring Resource Use

Learner Objectives Performance-Tuning Methodology

By the end of this lesson, you should be able to meet the following Follow these best practices for performance-tuning your vSphere
objectives: infrastructure:
• Use the performance-tuning methodology and resource monitoring tools • Assess performance:
• Use performance charts to view and improve performance – Use appropriate monitoring tools.
– Record a numerical benchmark before changes.
• Monitor the key factors that can affect the virtual machine’s performance: CPU,
memory, disk, and network bandwidth use • Identify the limiting resource.
• Make more resources available:
– Allocate more.
– Reduce competition.
– Log your changes.
Do not make casual changes
• Benchmark again.
to production systems.
3/20/2018
Resource-Monitoring Tools Guest Operating System Monitoring Tools

Many resource and performance monitoring tools are available to To monitor performance in the guest operating system, use tools that you
administrators to use with vSphere. are familiar with, such as Windows Task Manager.
Inside the Guest OS Windows Task Manager

Perfmon DLL
Task Manager
Outside the Guest OS

VMware vCenter Server™
performance charts
VMware vRealize™ Operations™
VMware vRealize™ Hyperic™
VMware vSphere®/ESXi system logs
resxtop and esxtop
Using Perfmon to Monitor Virtual Machine Resources About Monitoring Inventory Objects with Performance Charts
The Perfmon DLL in VMware Tools™ provides virtual machine processor The vSphere statistics subsystem collects data on the resource usage of
and memory objects to access host statistics inside a virtual machine. inventory objects:
• Counters and Metric Groups
• Collection Levels and Collection Intervals
• Data Availability
Working with Overview Performance Charts Working with Advanced Performance Charts
The overview performance charts display the most common metrics for Advanced charts support data counters that are not supported in other
an object in the inventory. performance charts.
Chart
Chart Options Objects
Host’s Performance Charts Metrics Timespan
Partial Overview Panel
Chart Type
Counters Rollups Statistics Type
3/20/2018
Chart Options: Real-Time and Historical Chart Types

vCenter Server stores statistics at different specificities. Depending on the metric type and object, performance metrics are
displayed in different types of charts.
Time Interval Data Frequency Number of Samples Line chart:
• Each instance is shown separately.
Real-Time (past hour) 20 seconds 180
Past Day 5 minutes 288 Bar chart:
• Each instance is a bar in the chart.
Past Week 30 minutes 336
Pie chart:
Past Month 2 hours 360
• Each instance is a slice in a circular pie.
Past Year 1 day 365
Stacked chart:
• Graphs are stacked on top of one another.
Saving Charts Objects and Counters

You click the Save Chart icon above the graph to save performance The performance charts graphically display CPU, memory, disk, network,
chart information. and storage metrics for devices and entities managed by vCenter Server.
You can save information in these formats: Objects are instances or aggregations of devices:
• PNG
• Examples: vCPU0, vCPU1, vmhba1:1:2, aggregate over all NICs
• JPEG
• CSV
Counters identify which statistics to collect:
• Examples:
– CPU: Used time, ready time, usage (%)
– NIC: Network packets received
– Memory: Memory swapped
Statistics Type Rollup

The statistics type is the unit of measurement used during the statistics Rollup is the conversion function between statistics intervals:
interval.
• 5 minutes of past-hour statistics are converted to 1 past-day value:
– Fifteen 20-second statistics are rolled up into a single value.
• 30 minutes of past-day statistics are converted to 1 past-week value:

– Six 5-minute statistics are rolled up into a single value.
Statistics Type Description Example • Other rollup types: Minimum, Maximum
Rate Value over the current interval CPU use (MHz)

Rollup Type Conversion Function Sample Statistic
Delta Change from previous interval CPU ready time Average Average of data points CPU use (average)
Summation Sum of data points CPU ready time (milliseconds)

Absolute Absolute value, independent of interval Memory active
Latest Last data point Uptime (days)
3/20/2018
Setting Log Levels Interpreting Data from the Tools

Setting log levels enables the user to control the quantity and type of vCenter Server monitoring tools and
information logged. guest operating system monitoring
tools provide different points of view.
Examples of when to set log levels:
• When troubleshooting complex issues, set the log level to verbose or trivia.
Troubleshoot and set it back to info.
• To control the amount of information being stored in the log files.
Task Manager in
Option Description Guest Operating System
None Turns off logging
Error (errors only) Displays only error log entries
Warning (errors and warnings) Displays warning and error log entries
Info (normal logging) Displays information, error, and warning log entries
Displays information, error, warning, and verbose log

Verbose CPU Usage
entries
Chart for Host
Displays information, error, warning, verbose, and
Trivia (extended verbose)
trivia log entries
CPU-Constrained Virtual Machine Memory-Constrained Virtual Machine

If CPU usage is continuously high, the virtual machine is constrained by Check the virtual machine’s ballooning activity to determine if the virtual
CPU. However, the host might have enough CPU for other virtual machine is constrained for memory:
machines to run. • If ballooning activity is high, this state might not be a problem if all virtual
Multiple virtual machines are constrained by CPU if the following machines have sufficient memory.
conditions are present: • If ballooning activity is high and the guest operating system is swapping, then
• High CPU usage in the guest operating system the virtual machine is constrained for memory.
• Relatively high CPU ready values for the virtual machines
Single Virtual Machine CPU Usage
Memory-Constrained Host Monitoring Active Memory of a Virtual Machine

If active host-level swapping is occurring, then host memory is Monitor for increases in active memory on the host:
overcommitted.
• Host active memory refers to active physical memory used by virtual machines
and the VMkernel.
• If amount of active memory is high, this situation might lead to virtual machines
that are memory-constrained.
3/20/2018
Disk-Constrained Virtual Machines Monitoring Disk Latency

Disk-intensive applications can saturate the storage or the path. To determine disk performance problems, monitor two disk latency data
counters:
If you suspect that a virtual machine is constrained by disk access:
• Kernel command latency:
• Measure the throughput and latency between the virtual machine and storage.
– The average time spent in the VMkernel per SCSI command.
• Use the advanced performance charts to monitor:
– High numbers (greater than 2 or 3 ms) represent either an overworked array or an
– Read rate and write rate overworked host.
– Read latency and write latency • Physical device command latency:
– The average time the physical device takes to complete a SCSI command.
– High numbers (greater than 15 or 20 ms) represent a slow or overworked array.
Network-Constrained Virtual Machines Lab 18: Monitoring Virtual Machine Performance

Network-intensive applications often bottleneck on path segments Demonstrate that system-monitoring tools reflect CPU workload
outside the ESXi host: 1. Create CPU Workload
• Example: WAN links between server and client 2. Use Performance Charts to Monitor CPU Utilization
If you suspect that a virtual machine is constrained by the network: 3. Undo Changes Made to the Virtual Machines
• Confirm that VMware Tools is installed.
– Enhanced network drivers are available.
• Measure the effective bandwidth between the virtual machine and its peer
system.
• Check for dropped receive packets and dropped transmit packets.

• Use the performance-tuning methodology and resource monitoring tools
• Use performance charts to view and improve performance
• Monitor the key factors that can affect the virtual machine’s performance: CPU,
memory, disk, and network bandwidth use
Lesson 4:
Using Alarms

3/20/2018
Learner Objectives About Alarms

By the end of this lesson, you should be able to meet the following An alarm is a notification that occurs in response to selected events or
objectives: conditions that occur with an object in the inventory.
• Create alarms with condition-based triggers
Default alarms exist for various inventory objects:
• Create alarms with event-based triggers
• Many default alarms for hosts and virtual machines
• View and acknowledge triggered alarms
You can create custom alarms for a wide range of inventory objects:
• Virtual machines, hosts, clusters, data centers, datastores, datastore clusters,
networks, distributed switches, and distributed port groups
Alarm Settings Alarm Triggers

To monitor your environment, you can create and modify alarm An alarm requires a trigger.
definitions in the VMware vSphere® Web Client.
Types of triggers:
• Condition or state trigger: Monitors the current condition or state. Examples:
– A virtual machine’s current snapshot is above 2 GB in size.
– A host is using 90 percent of its total memory.
– A datastore has been disconnected from all hosts.
• Event: Monitors events. Examples:

– The health of a host’s hardware has changed.
– A license has expired in the data center.
– A host has left the distributed switch.
Configuring Condition Triggers Configuring Event Triggers

Condition or state triggers monitor metrics for a host, virtual machine, or Event triggers monitor the current state of a host, virtual machine, or
datastore. datastore.
3/20/2018
Configuring Actions Configuring vCenter Server Notifications

You can define actions that the system performs when the alarm is You must configure the email address of the sender account to enable
triggered or changes status. vCenter Server operations such as sending email notifications as alarm
actions.
Select Mail to set

SMTP parameters.
Select SNMP receivers to

specify trap destinations.
Viewing and Acknowledging Triggered Alarms Lab 19: Using Alarms

The Acknowledge Alarm feature is used to track when triggered alarms Demonstrate the vCenter Server Appliance alarm feature
are addressed. 1. Create a Virtual Machine Alarm to Monitor a Condition
2. Create a Virtual Machine Alarm to Monitor an Event
3. Trigger Virtual Machine Alarms and Acknowledge the Alarms
4. Disable Virtual Machine Alarms

• Create alarms with condition-based triggers
• Create alarms with event-based triggers
• View and acknowledge triggered alarms
Lesson 5:
vRealize Operations Manager

3/20/2018
Learner Objectives About vRealize Operations

You should be able to meet the following objectives: VMware vRealize™ Operations™
• Identify the VMware vRealize™ Operations Manager™ architecture provides intelligent operations
• Explain how to deploy and configure a vRealize Operations Manager appliance management across physical,
• Use alerts and badges to monitor the vSphere environment
virtual, and cloud infrastructures. Cloud
Operations
The suite offers the following key
benefits:
vRealize Operations:
• Intelligent operations: Improve
performance and avoid disruption • vRealize Operations Manager
with self-learning management tools. • VMware vRealize™
• Policy-based automation: Become Configuration Manager™
more efficient by automating key IT
processes with policy-based control. • vRealize Hyperic
• Unified management: Monitor and • vRealize Infrastructure Navigator
manage applications and
infrastructure from one place.
Overview of vRealize Operations About vRealize Operations Manager
vRealize Operations provides heterogeneous management capabilities. vRealize Operations Manager is the foundation of the suite and provides
visibility and insights into the performance, capacity, and health of your
Virtual and physical infrastructures are supported. Public, private, and
environment.
hybrid clouds are also supported.
vRealize Operations Manager offers the following benefits:
vRealize Operations • Comprehensive cloud operations console
Cloud Operations Console
Extensibility • End-to-end operations visibility
Integrated Management Disciplines Management • Reduced mean time to investigate and resolve issues across the entire
Packs
environment
Performance Availability Capacity Configuration Compliance
APIs
• Integrated compliance
Platform
Application Reporting/ SDK
Analytics Automation Logs
Visibility Alerting
Cloud Operations Console Operations Visibility

The vRealize Operations Manager operations console is the central point vRealize Operations Manager enables you to view details across all
of management for your environment. layers of the infrastructure.
Immediate Emerging Opportunities
Home Issues Issues to Optimize
Alerts
Environment
Content
Host memory contention is
contributing to degraded health.
Administration You can click this alert to
Coverage Across the investigate the issue.
Entire Environment
3/20/2018
Reduced Time to Investigate and Resolve Issues vRealize Operations Manager Installation Overview
Alerts reduce the mean time to investigate issues. vRealize Operations Manager can be Node
Recommendations reduce the mean time to resolve issues in the installed in the following forms:
environment. • As a virtual appliance (SLES-based) Product/Admin UI
• On a Linux (RHEL) system
• On a Windows server Collector
(REST API)
The same software stack is used for

virtual appliance, Linux, and Windows Controller
installations.
What are the
recommendations to Analytics
resolve this issue?
Persistence
Which symptoms
across the stack are
causing this problem?
Databases
Installation Prerequisites Deploying the vRealize Operations Manager Node

Before you install the software, perform the prerequisite tasks: vRealize Operations Manager consists of one or more nodes in a cluster.
• Ensure that you have adequate server capacity to deploy vRealize Operations To create nodes, follow this workflow:
Manager.
1. Download and deploy the vRealize Operations Manager virtual machine,
• Determine the vCenter Server inventory location for your node. once for each cluster node.
• Ensure that the networking requirements are met. 2. Deploy the vRealize Operations Manager from the vCenter Server system.
• Reserve a static IP address for the vRealize Operations Manager node. 3. Create a vRealize Operations Manager node by deploying an OVF.
• Determine the Network Time Protocol source for synchronizing the master
node.
• Ensure that you are using a supported Web browser version.
Types of Installations Initial Setup for a New Installation

After deploying the virtual appliance, you select the type of installation When you select New Installation, you are prompted for the following
that you want to perform: information during the initial setup phase:
• Express Installation • Password for the admin user account
• New Installation
• Certificate:
• Expand an Existing Installation – Your own certificate or the default certificate
• Node name
• NTP server name:
– If this text box is left blank, the master node uses its internal clock for timekeeping.
– The best practice is to set an external NTP server for the master node.
3/20/2018
Continuing the New Installation Viewing the Cluster

After the initial setup is complete, you are automatically logged in to the Use the administration user interface to verify that the node was added to
administration user interface, as user admin, for the first time. the cluster.
Finishing the Installation Configuring Solutions for Objects

To finish the installation, log in to any cluster data node (master node, To continue with the final steps of your new installation, you add solutions
master replica node, or data node) as user admin. for the kinds of objects that you want to monitor and manage.
Complete a one-time process to license the product or use the product
evaluation mode.
About the User Interface Major and Minor Badges

vRealize Operations Manager has the following user interfaces: With the badge identifier system, you can quickly identify good or bad
conditions in your vSphere virtual infrastructure:
• Administration interface:
– Used to perform initial setup and installation  Major badges:
– Used to perform software updates • Health
– Used only by the vRealize Operations Manager administrator • Risk
– Accessed through the URL • Efficiency
https://vRealize_Operations_Manager_name/admin
 Minor badges:
• Product user interface:
– Used to perform the following tasks:
• Workload
• Monitor the environment for health, risk, and efficiency issues. • Anomalies
• Add custom content, such as views, dashboards, and reports. • Faults
• Administer the vRealize Operations Manager instance.
– Used by all vRealize Operations Manager users
– Accessed through the URL https://vRealize_Operations_Manager_name/vcops-web-
ent
3/20/2018
About the Home Page Widgets on the Recommendations Dashboard

The home page appears when you log in. The home page provides access A widget is a pane on a dashboard that can visualize the behavior of one
to all of your dashboards. or more objects.
The dashboard provides a quick overview of the performance and The Recommendations dashboard uses the Health, Risk, Efficiency, and
condition of your virtual infrastructure. the Top Alerts widgets.
vSphere Dashboards About Inventory Trees

Prebuilt vSphere dashboards assist in monitoring resource usage and An inventory tree shows the parent-
performance of vSphere clusters, hosts, datastores, and virtual child relationships between objects:
machines.
• Object relationships are useful when
troubleshooting system issues and
finding the cause.
Inventory trees and tree types are
provided by management packs Tree Types
(solutions) when they are installed
into vRealize Operations Manager:
• For example, the VMware vSphere
solution provides several inventory
tree types related to vSphere.
Selecting an Inventory Tree Type Viewing an Object’s Details

Selecting an inventory tree type When you select an object in the navigation pane, the object’s details
enables you to see the objects appear in the center pane.
Tree
in the inventory tree instances. Type
The root of vSphere inventory
trees is the vSphere World Tree
object. Instance
vSphere World consists of all

vCenter Server instances and
Objects
their objects.
Tree
Instance
3/20/2018
About the Administration Page Lab 20: (Optional) Using vRealize Operations Manager
The Administration page Navigate the vRealize Operations Manager GUI
enables you to configure 1. Log In to the vRealize Operations Manager GUI
various aspects of vRealize 2. Navigate Dashboards and Icons
Operations Manager. 3. View the Inventory Tree and Find Objects
4. Create a CPU Report
5. View Health and Alerts of Your Environment
6. Troubleshoot a Cluster Alert
7. Troubleshoot a Virtual Machine Alert
8. View Badge Information for Analysis
9. Use a Heat Map to Identify CPU Contention
10. Create a Custom Heat Map

You should be able to meet the following objectives: • For proper resource management, vSphere has mechanisms to enable less,
• Identify the VMware vRealize™ Operations Manager™ architecture more, or an equal amount of access to a defined resource.
• Explain how to deploy and configure a vRealize Operations Manager appliance • vSphere prevents a virtual machine from consuming large amounts of a
resource and grants a guaranteed amount of a resource to a virtual machine
• Use alerts and badges to monitor the vSphere environment
whose performance is not adequate or requires a certain amount of a resource
to run properly.
• A resource pool enables you to divide and allocate resources to virtual
machines and other resource pools.
• The Performance tab enables you to monitor the performance of a host or a
virtual machine in real time or over a period of time.
• You use alarms to monitor the vCenter Server inventory and send out
notifications when selected events or conditions occur.
• vRealize Operations Manager gives you insight into the performance, capacity,
and health of the vSphere environment.
Questions?
3/20/2018
vSphere HA and vSphere Fault Tolerance You Are Here

Monitoring
9. vSphere HA and vSphere
4. vCenter Server Fault Tolerance
Virtual Networks
Virtual Storage


Most organizations rely on computer-based services like email, Lesson 1: Introduction to vSphere HA
databases, and Web-based applications. The failure of any of these
services can mean lost productivity and revenue. Lesson 2: vSphere HA Architecture
Configuring highly available, computer-based services is extremely Lesson 3: Configuring vSphere HA

important for an organization to remain competitive in contemporary Lesson 4: Introduction to vSphere Fault Tolerance
business environments.
Lesson 5: vSphere Replication and vSphere Data Protection
Learner Objectives
objectives:
• Describe the options that you can configure to make your VMware vSphere®
environment highly available
• Discuss the response of VMware vSphere® High Availability when a VMware
ESXi™ host, a virtual machine, or an application fails
Lesson 1:
Introduction to vSphere HA

1
3/20/2018
Protection at Every Level vCenter Server Availability: Recommendations

vSphere makes it possible to reduce planned downtime, Make VMware vCenter Server™ and the components that it relies on
prevent unplanned downtime, and recover rapidly from
highly available.
outages.
vCenter Server relies on these major components:
vSphere HA and vSphere Fault • vCenter Server database:
Tolerance
vSphere – Create a cluster for the database.
Storage • Authentication identity source:
Site Recovery
vSphere vMotion, vMotion
Manager – For example, VMware Center™ Single Sign-On™ and Active Directory.
vSphere DRS
NIC Teaming, – Set up with multiple redundant servers.
Storage
Multipathing Methods for making vCenter Server available:
• Use vSphere HA to protect the vCenter Server virtual machine.
vSphere Replication, Third-Party

Backup Solutions, vSphere Data Protection
Component Server Storage Data Site
About vSphere HA vSphere HA Scenarios: ESXi Host Failure

vSphere HA uses multiple ESXi hosts configured as a cluster to provide
rapid recovery from outages and cost-effective high availability for
applications running in virtual machines.
Virtual Machine A Virtual Machine B

When a host fails,
Protects against Protects against datastore Virtual Machine A Virtual Machine C Virtual Machine E
vSphere HA restarts
server failures accessibility failures the affected virtual
Virtual Machine B Virtual Machine D Virtual Machine F
machines on other
hosts.
ESXi Host ESXi Host ESXi Host
Protects virtual machines

Protects against application
against network isolation
failures
vCenter Server = vSphere HA Cluster
vSphere HA Scenarios: Guest Operating System Failure vSphere HA Scenarios: Application Failure
Application Application Application

Virtual Machine A Virtual Machine C Virtual Machine E When a virtual When an application
Virtual Machine A Virtual Machine C Virtual Machine E
VMware Tools VMware Tools VMware Tools machine stops fails, vSphere HA
Virtual Machine B Virtual Machine D Virtual Machine F sending heartbeats Application Application Application restarts the affected
VMware Tools VMware Tools VMware Tools or the virtual Virtual Machine B Virtual Machine D Virtual Machine F virtual machine on the
machine process same host.
ESXi Host ESXi Host ESXi Host crashes (vmx), ESXi Host ESXi Host ESXi Host Requires installation of
vSphere HA resets VMware Tools™.
the virtual machine.
vCenter Server = vSphere HA Cluster vCenter Server = vSphere HA Cluster
2
3/20/2018
Importance of Redundant Heartbeat Networks Redundancy Using NIC Teaming
In a vSphere HA cluster, heartbeats have these characteristics: You can use NIC teaming to create a redundant heartbeat network on
ESXi hosts.
• Heartbeats are sent between the master host and the slave hosts.
• They are used to determine whether a master host or slave host has failed. Ports or port groups used must be VMkernel ports.
• They are sent over a heartbeat network.
Redundant heartbeat networks ensure reliable failure detection.

Heartbeat network implementation:
• Implemented by using a VMkernel port marked for management.
NIC Teaming on an ESXi Host
Redundancy Using Additional Networks Review of Learner Objectives

You can also create redundancy by configuring more heartbeat
• Describe the options that you can configure to make your VMware vSphere®
networks: On each ESXi host, create a second VMkernel port on a
environment highly available
separate virtual switch with its own physical adapter.
• Discuss the response of VMware vSphere® High Availability when a VMware
ESXi™ host, a virtual machine, or an application fails
Learner Objectives
objectives:
• Describe the heartbeat mechanisms used by vSphere HA
• Identify and discuss other failure scenarios
• Recognize vSphere HA design considerations
Lesson 2:
vSphere HA Architecture

3
3/20/2018
vSphere HA Architecture: Agent Communication vSphere HA Architecture: Network Heartbeats

Datastore Datastore Datastore VMFS NAS/NFS
VMFS
FDM FDM FDM Slave Host Slave Host Master Host
vpxa hostd vpxa hostd vpxa hostd
ESXi Host (Slave) ESXi Host (Slave) ESXi Host (Master)
The master host sends periodic

heartbeats to the slave hosts so
To configure high availability, vpxd that the slave hosts know that vCenter Server
ESXi hosts are grouped into vCenter Server the master host is alive. Management Network 1
an object called a cluster. = Management Network Management Network 2
vSphere HA Architecture: Datastore Heartbeats Additional vSphere HA Failure Scenarios

• Slave host failure
VMFS VMFS NAS/NFS
Datastores are used as a • Master host failure
backup communication • Host isolation
channel to detect virtual
• Virtual machine storage failure:
Virtual Machine A Virtual Machine C Virtual Machine E machine and host heartbeats.
– Virtual Machine Component Protection
Virtual Machine B Virtual Machine D Virtual Machine F • All Paths Down
• Permanent Device Loss
Slave Host Master Host Slave Host • Network failures and isolation
Cluster Edit Settings Window
vCenter Server
Management Network 1
Management Network 2
Failed Slave Host Failed Master Host

When a slave host does not respond to the network heartbeat issued by When the master host is placed in maintenance mode or crashes, the
the master host, the master vSphere HA agent tries to identify the cause. slave hosts detect that the master host is no longer issuing heartbeats.
NAS/NFS VMFS NAS/NFS VMFS
(Lock File) (Heartbeat Region) (Heartbeat Region)
(Lock File)
File Locks File Locks
File Locks File Locks

Virtual Machine A Virtual Machine C Virtual Machine E Default Gateway
Virtual Machine B Virtual Machine D Virtual Machine F (Isolation Address)
Failed Slave Master Host Slave Host
Host Slave Host master host
Failed Master Host Slave Host
MOID: 98 MOID: 99 99
MOID: MOID: 100
vCenter Server Primary Heartbeat Network

Primary Heartbeat Network
Alternate Heartbeat Network vCenter Server Alternate Heartbeat Network
MOID = Managed Object ID
4
3/20/2018
Isolated Host Design Considerations

If the host does not observe Host isolation events can be minimized through good design:
election traffic on the management • Implement redundant heartbeat networks.
and cannot ping its default
gateway, the host is isolated. • Implement redundant isolation addresses.
If host isolation events do occur, good design enables vSphere HA to

determine whether the isolated host is still alive.

Implement datastores so that they are separated from the management
network by using one or both of the following approaches:
ESXi Host ESXi Host ESXi Host • Fibre Channel over fiber optic
• Physically separating your IP storage network from the management network
Primary Heartbeat Network

Default Gateway Alternate Heartbeat Network
(Isolation Address)
Virtual Machine Storage Failures Virtual Machine Component Protection

With an increasing number of virtual Virtual Machine Component Protection (VMCP) protects against storage
machines and datastores on each failures in a virtual machine.
host, storage connectivity issues
have high costs but are infrequent. Only vSphere HA clusters that contain ESXi 6 hosts can be used to
enable VMCP.
Connectivity problems due to:
• Network or switch failure
ESXi ESXi Runs on cluster
• Array misconfiguration
enabled for
• Power outage vSphere HA. Application
Virtual machine availability is availability and
ESXi ESXi remediation.
affected:
• Virtual machines on affected hosts are
difficult to manage.
• Applications with attached disks crash. VMCP detects
and responds to
failures.

• Describe the heartbeat mechanisms used by vSphere HA
• Identify and discuss other failure scenarios
• Recognize vSphere HA design considerations
Lesson 3:
Configuring vSphere HA

5
3/20/2018
Learner Objectives About Clusters

By the end of this lesson, you should be able to meet the following A cluster is a collection of ESXi
objectives: hosts and their associated
• Recognize the prerequisites for creating and using a vSphere HA cluster virtual machines, configured to
• Configure a vSphere HA cluster share their resources.
vCenter Server manages cluster
resources like a single pool of
resources.
Components such as vSphere
HA and VMware vSphere®
Distributed Resource
Scheduler™ are configured on
a cluster. Cluster
vSphere HA Prerequisites Configuring vSphere HA Settings

• All hosts must be licensed for vSphere HA. When you create a vSphere HA cluster or configure a cluster, you must
• A cluster must contain at least two hosts.
configure settings that determine how the feature works.
• All hosts must be configured with static IP addresses. If you are using DHCP,
you must ensure that the address for each host persists across reboots.
• All hosts must have at least one management network in common.
• All hosts must have access to the same virtual machine networks and
datastores.
• For Virtual Machine Monitoring to work, VMware Tools™ must be installed.
• Only vSphere HA clusters that contain ESXi 6 hosts can be used to enable
VMCP.
Permanent Device Loss and All Paths Down Overview vSphere HA Settings: Virtual Machine Monitoring (1)
vSphere HA uses VMCP to move virtual machines in Permanent Device You use Virtual Machine Monitoring settings to control the monitoring of
Loss and All Paths Down situations to other fully connected hosts. virtual machines.
Permanent Device Loss:
• The datastore appears as unavailable in the Storage view.
• A storage adapter indicates the operational state as loss of communication.
• All paths to the device are marked as dead.
All Paths Down:

• The datastore appears as unavailable in the Storage view.
• A storage adapter indicates the operational state as dead or error.
• All paths to the device are marked as dead.
• The vSphere Client is unable to connect directly to the ESXi host.
• The ESXi host appears as disconnected in vCenter Server.
6
3/20/2018
vSphere HA Settings: Virtual Machine Monitoring (2) vSphere HA Settings: Datastore Heartbeating
A heartbeat file is created on the selected datastores and is used in the
event of a management network failure.
vSphere HA Settings: Admission Control vSphere HA Settings: Advanced Options

vCenter Server uses admission control to ensure that: To customize vSphere HA behavior, you set advanced vSphere HA options.
 Sufficient resources are available in a cluster to provide failover To force cluster not to use the default isolation address (default gateway):
protection • das.usedefaultisolationaddress = false
 Virtual machine resource reservations are respected To force cluster to ping alternate isolation addresses:
• das.isolationaddressX = pintable address
To force cluster to wait beyond default 30-second isolation action window:
• fdm.isolationpolicydelaysec = > 30 sec
Configuring Virtual Machine Overrides Network Configuration and Maintenance

You can override the vSphere HA settings that are set on a cluster for Before changing the networking settings on an ESXi host (adding port
individual virtual machines in that cluster. groups, removing virtual switches, and so on), you must suspend the
Host Monitoring feature and place the host in maintenance mode.
This practice prevents unwanted attempts to fail over virtual machines.
7
3/20/2018
Cluster Resource Reservation Monitoring Cluster Status

The Resource Reservation tab reports total cluster CPU, memory, You can monitor the status of a vSphere HA cluster on the Monitor tab.
memory overhead, storage capacity, the capacity reserved by virtual
machines, and how much capacity is still available.
Lab 21: Using vSphere HA Review of Learner Objectives

Demonstrate vSphere HA functionality You should be able to meet the following objectives:
1. Create a Cluster Enabled for vSphere HA • Recognize the prerequisites for creating and using a vSphere HA cluster
2. Add Your ESXi Host to a Cluster • Configure a vSphere HA cluster
3. Test vSphere HA Functionality
4. View the vSphere HA Cluster Resource Usage
5. Manage vSphere HA Slot Size
6. Configure a vSphere HA Cluster with Strict Admission Control
7. Prepare for Upcoming Labs
Learner Objectives
objectives:
• List VMware vSphere® Fault Tolerance requirements and limitations
• Describe vSphere Fault Tolerance operation
Lesson 4:
Introduction to vSphere Fault
Tolerance

8
3/20/2018
vSphere Fault Tolerance vSphere Fault Tolerance Features (1)

vSphere Fault Tolerance provides instantaneous failover and continuous vSphere Fault Tolerance protects mission-critical, high-performance
availability: applications regardless of the operating system used.
• Zero downtime
vSphere Fault Tolerance:
• Zero data loss
• Supports up to four virtual CPUs
• No loss of TCP connections
• Supports up to 64 GB of memory
Instantaneous • Supports VMware vSphere® vMotion® for primary and secondary virtual
Failover machines
Fast Checkpointing • Creates a secondary copy of all virtual machine files, including disks
• Provides fast checkpoint copying to keep primary and secondary CPUs
synchronized
Primary Virtual Machine Secondary Virtual Machine
ESXi
How vSphere Fault Tolerance Works with vSphere HA and vSphere

vSphere Fault Tolerance Features (2) DRS
vSphere Fault Tolerance: vSphere Fault Tolerance works with vSphere HA and vSphere DRS.
• Supports thin-provisioned disks vSphere HA:
• Supports memory virtualization hardware assist • Is required for vSphere Fault Tolerance
• Supports Enhanced vMotion Compatibility clusters • Restarts failed virtual machines
• Is vSphere Fault Tolerance aware
vSphere DRS:
• Selects the virtual machine’s location at power-on
• Does not balance fault-tolerant virtual machines in a balanced cluster
Primary Secondary New Secondary

Machine Machine Machine
ESXi ESXi ESXi
Redundant VMDKs vSphere Fault Tolerance Checkpoint

vSphere Fault Tolerance creates two complete virtual machines. vSphere Fault Tolerance supports multiple processors.
Each virtual machine has its own .vmx configuration file and .vmdk Changes on the primary machine are not processed on the secondary
files. Each of these virtual machines can be on a different datastore. machine. The memory is updated on the secondary.
Input
ESXi ESXi
Primary Secondary
.vmx file .vmx file FT
Network
Result X
vmdk file vmdk file vmdk file vmdk file vmdk file vmdk file
Datastore 1 Datastore 2
9
3/20/2018
vSphere vMotion: Precopy vSphere vMotion: Memory Checkpoint

During a vSphere vMotion migration, a second virtual machine is created In vSphere vMotion migration, checkpoint data is the last bit of memory
on the destination host. Then the memory of the source virtual machine that keeps changing.
is copied to the destination.
VM A VM A VM A VM A
Memory Memory
Bitmap Bitmap
vSphere vMotion Memory Precopy vSphere vMotion Checkpoint Data

Network Network
Virtual Machine Virtual Machine
Port Group Port Group
Virtual Machine Virtual Machine

End User End User
vSphere Fault Tolerance Fast Checkpointing Shared Files

The SMP FT checkpoint interval is dynamic by default. It adapts to vSphere Fault Tolerance has shared files:
maximize the workload performance and can range from as small as a • shared.vmft prevents UUID change.
few milliseconds to as large as several hundred milliseconds.
• .ftgeneration is for the split-brain condition.
vmx config
Devices
Disks
VM memory
Primary Host Secondary Host
checkpoint
Fault Tolerance shared.vmft

Primary Host Network Secondary Host .ftgeneration
shared.vmft File Enabling vSphere Fault Tolerance on a Virtual Machine

The shared.vmft file, which is found on a shared datastore, is the You can turn on vSphere
vSphere Fault Tolerance metadata file and contains the primary and Fault Tolerance for a
secondary instance UUIDs and the primary and secondary vmx paths. virtual machine through
the VMware vSphere®
Web Client.
UUID-1 UUID-1
UUID-2
VM Guest OS
Ref: UUID-1
10
3/20/2018

• List VMware vSphere® Fault Tolerance requirements and limitations
• Describe vSphere Fault Tolerance operation
Lesson 5:
vSphere Replication and vSphere
Data Protection

Learner Objectives About vSphere Replication

By the end of this lesson, you should be able to meet the following vSphere Replication is an extension to vCenter Server.
objectives:
It provides hypervisor-based virtual machine replication and recovery.
• Describe VMware vSphere® Replication™
• Identify vSphere® Data Protection™ requirements
vSphere
• List vSphere Data Protection sizing guidelines Replication
• Describe vSphere Data Protection installation and configuration
• Explain how to back up and restore data with vSphere Data Protection
Source vSphere vSphere Target
vSphere Replication Appliance How Replication Works

The vSphere Replication appliance provides all the components required vSphere Replication enables replication of a virtual machine from a
to perform vSphere replication. source site to a target site, monitoring and managing the status of the
replication, and recovering the virtual machine at the target site.
vSphere Replication
Appliance
Included with Replication

Standard OVF Delivered with the Between
Most vSphere
Virtual Appliance vSphere Platform Two Sites
Editions
11
3/20/2018
Steps for Full Recovery About vSphere Data Protection

vSphere Replication integrates with Volume 1. Right-click and vSphere Data Protection is a robust, easily deployed, disk-based backup
Shadow Copy Service through VMware Tools. select Recover. and recovery solution.
vSphere Data Protection
2. Select a target
folder.
3. Select a target
resource.
4. Click Finish.
Validates your choices as you go
vSphere Data Protection Requirements and Architecture vSphere Data Protection Deployment and Configuration
vSphere Data Protection requires vCenter Server, either the Windows vSphere Data Protection is deployed using vSphere Web Client from a
implementation or vCenter Server™ Appliance™. prepackaged Open Virtualization Archive (OVA) file.
vSphere Data Protection Components vSphere Data Protection: Configuring the UI to Run in Maintenance Mode
Creating and Editing a vSphere Data Protection Backup Job Performing Restores with vSphere Data Protection
You create and edit a backup job on the Backup tab of the vSphere Data You can restore an entire virtual machine from the Restore tab in the
Protection UI in the vSphere Web Client. vSphere Data Protection UI:
• The administrator can browse the list of protected virtual machines and select
one or more restore points.
Creating a Custom Retention Policy • Individual VMDKs can also be restored.
12
3/20/2018

You should be able to meet the following objectives: • vSphere HA restarts virtual machines on the remaining hosts in the cluster.
• Describe VMware vSphere® Replication™ • Hosts in vSphere HA clusters have a master-slave relationship.
• Identify vSphere® Data Protection™ requirements • You implement redundant heartbeat networks either with NIC teaming or by
• List vSphere Data Protection sizing guidelines creating additional heartbeat networks.
• Describe vSphere Data Protection installation and configuration • vSphere Fault Tolerance provides zero downtime for applications that must be
• Explain how to back up and restore data with vSphere Data Protection available at all times.
• vSphere Replication can be used to protect virtual machines as part of a
disaster recovery strategy.
• vSphere Replication is the only hypervisor-based replication solution that
operates at the individual VMDK level, enabling replication between datastores
hosted on any storage.
• vSphere Data Protection is a backup and recovery solution from VMware.
Questions?
13
3/20/2018
Host Scalability You Are Here

Monitoring
Virtual Networks
Virtual Storage

Importance Learner Objectives

As you scale your VMware vSphere® environment, you must be aware By the end of this module, you should be able to meet the following
of the vSphere features and functions that will help you manage the objectives:
hosts in your environment. • Describe the functions of a VMware vSphere® Distributed Resource
Scheduler™ cluster
• Create a vSphere DRS cluster
• View information about a vSphere DRS cluster
• Remove a host from a vSphere DRS cluster
vSphere DRS Cluster Prerequisites vSphere DRS Cluster Settings: Automation Level
vSphere DRS works best when the virtual machines meet VMware Configure the automation level for the initial placement of virtual
vSphere® vMotion® migration requirements. machines and dynamic balancing while virtual machines are running.
To use vSphere DRS for load balancing, the hosts in the cluster must be
part of a vSphere vMotion migration network.
• If not, vSphere DRS can still make initial placement recommendations.
To use shared storage, configure all hosts in the cluster: Automation Level Settings
• Volumes must be accessible by all hosts.
• Volumes must be large enough to store all virtual disks for your virtual
machine.
Migration threshold guides selection
of virtual machines for migration.
1
3/20/2018
Other Cluster Settings: Swap File Location for vSphere DRS vSphere DRS Cluster Settings: Virtual Machine Affinity
Store the virtual machine’s swap file with the virtual machine or in a vSphere DRS affinity rules
specified datastore. specify that selected virtual
VMware recommends that you store the swap file in the same directory machines be placed either
as the virtual machine. on
the same host (affinity) or on
separate hosts (anti-affinity).
Affinity rules:
• Use for multi-virtual machine
systems where virtual
machines communicate Options:
heavily with one another. • Keep Virtual Machines Together
• Separate Virtual Machines
Anti-affinity rules: • Virtual Machines to Hosts
• Use for multi-virtual machine

systems where load balance
or high availability is desired.
vSphere DRS Cluster Settings: DRS Groups vSphere DRS Cluster Settings: VM-Host Affinity Rules
DRS groups are used in A VM-Host affinity rule:
defining VM-Host affinity • Specifies an affinity
rules. relationship between a virtual
machine DRS group and a
Types of DRS groups:
host DRS group
• A group of virtual machines
• Is either a required rule or a
• A group of hosts preferential rule
A virtual machine can belong
to multiple virtual machine
DRS groups.
A host can belong to multiple
host DRS groups.
Other options:
Must run on hosts in group,
Must Not run on hosts in group,
Should Not run on hosts in group
VM-Host Affinity Rule: Preferential VM-Host Affinity Rule: Required

A preferential rule is softly enforced and can be violated if necessary. A required rule is strictly enforced and can never be violated.
Example: Separate virtual machines on different blade systems. Example: Enforce host-based ISV licensing.
vSphere DRS Cluster vSphere DRS Cluster
Group A Group A
Group B
X X X X
Blade Chassis A Blade Chassis B ISV-Licensed
2
3/20/2018
vSphere DRS Cluster Settings: Automation at the Virtual Machine

Level Adding a Host to a Cluster
You can customize the automation level for individual virtual machines in When adding a host or moving a host into a vSphere DRS cluster, you
a cluster to override the automation level set on the entire cluster. can keep the resource pool hierarchy of the existing host.
• If vSphere DRS is not enabled, host resources pools are lost.
For example, add sc-quail04 to Lab Cluster.
When adding the host, choose to create a

resource pool for this host’s virtual
machines and resource pools.
Viewing vSphere DRS Cluster Information Viewing vSphere DRS Recommendations

The cluster Summary tab provides information specific to vSphere DRS. The DRS tab displays information about the vSphere DRS
recommendations made for the cluster, the faults that occurred in
Clicking the vSphere DRS link on the Monitor tab displays CPU and applying such recommendations, and the history of vSphere DRS
memory utilization per host. actions.
Refresh recommendations.
Apply a subset of
recommendations.
Apply all
recommendations.
Monitoring Cluster Status Maintenance Mode and Standby Mode

View the inventory hierarchy for the cluster state. To service a host in a cluster, for example, to install more memory, or
You can view the cluster’s Tasks and Events tabs for more information. remove a host from a cluster, you must place the host in maintenance
mode:
• Virtual machines on the host should be migrated to another host or shut down.
• You cannot power on virtual machines or migrate virtual machines to a host
entering maintenance mode.
• While in maintenance mode, the host does not allow you to deploy or power on
a virtual machine.
When a host is placed in standby mode, it is powered off:
• This mode is used by VMware vSphere® Distributed Power Management™ to
optimize power usage.
3
3/20/2018
Removing a Host from the vSphere DRS Cluster Improving Virtual Machine Performance Methods
Before removing a host
from a vSphere DRS
cluster, consider the
following issues: Fine
Use network
• The resource pool traffic shaping.
hierarchy remains with the
cluster. Modify the virtual
• Because a host must be in machine’s CPU and memory
maintenance mode, all reservations.
virtual machines running on
Modify the resource pool’s CPU and
that host are powered off.
memory limits and reservations.
• The resources available for
the cluster decrease. Broad Use NIC teaming.
Use storage multipathing.
Use a vSphere DRS cluster.
Using vSphere HA with vSphere DRS Lab 22: Implementing a vSphere DRS Cluster
Reasons why VMware vSphere® High Availability might not be able to Implement a vSphere DRS cluster
fail over virtual machines: 1. Create a Load Imbalance
• vSphere HA admission control is disabled. 2. Create a vSphere DRS Cluster
• Required VM-Host affinity rule prevents vSphere HA from failing over. 3. Verify Proper vSphere DRS Cluster Functionality
• Sufficient aggregated resources exist, but they are fragmented across hosts. 4. Create, Test, and Disable a VM-VM Affinity Rule
5. Create, Test, and Disable an Anti-Affinity Rule
In such cases, vSphere HA uses vSphere DRS to try to adjust the cluster
6. Create, Test, and Disable a VM-Host Affinity Rule
by migrating virtual machines to defragment the resources.

You should be able to meet the following objectives: • vSphere DRS clusters provide automated resource management for multiple
VMware ESXi™ hosts.
• Describe the functions of a VMware vSphere® Distributed Resource
Scheduler™ cluster • vSphere DRS works best if the virtual machines meet vSphere vMotion
migration requirements.
• Create a vSphere DRS cluster
• View information about a vSphere DRS cluster Questions?
• Remove a host from a vSphere DRS cluster
4
3/20/2018
vSphere Update Manager and Host Maintenance You Are Here

Monitoring
Virtual Networks
Virtual Storage


Over time, your VMware vSphere® environment might undergo changes Lesson 1: Introducing vSphere Update Manager and Patch
in its hardware or software configuration, or in the form of software Management
updates or patches.
Lesson 2: Host Profiles
From a manageability and scalability perspective, you should implement
changes to your vSphere environment in an orderly, controlled, and
systematic fashion.
Learner Objectives
objectives:
• Describe VMware vSphere® Update Manager™ functionality
• List the steps to install vSphere Update Manager
• Use vSphere Update Manager create and attach a baseline
Lesson 1:
Introducing vSphere Update
Manager and Patch Management

1
3/20/2018
About vSphere Update Manager vSphere Update Manager Capabilities

vSphere Update Manager enables centralized, automated patch and vSphere Update Manager enables cross-platform upgrade from VMware
version management for VMware ESXi™ hosts, virtual machine ESX® to ESXi.
hardware, VMware Tools™, and virtual appliances.
Automated patch downloading:
vSphere Update Manager reduces security risks:
• Begins with information-only downloading.
• Reduces the number of vulnerabilities.
• Is scheduled at regular configurable intervals.
• Eliminates many security breaches that exploit older vulnerabilities.
vSphere Update Manager reduces the diversity of systems in an Creation of baselines and baseline groups
environment: Scanning:
• Makes management easier.
• Inventory systems are scanned for baseline compliance.
• Reduces security risks.
Remediation:
vSphere Update Manager keeps machines running more smoothly:
• Inventory systems that are not compliant can be automatically patched.
• Patches include bug fixes.
• Makes troubleshooting easier. Reduces the number of reboots required after VMware Tools updates
vSphere Update Manager Components Requirements for Installing vSphere Update Manager
vSphere Update Manager includes several components and requires vSphere Update Manager has the following installation requirements:
network connectivity with VMware vCenter Server™. • vSphere Update Manager must be installed on a Windows 64-bit machine.
vSphere Update Manager server component: • The vSphere Update Manager server requires an SQL Server or an Oracle
• Install on the same computer as Windows vCenter Server or on a different
database.
computer. • vCenter Server must be installed.
Client components: • Update Manager 6 is compatible only with vCenter Server 6.
• vSphere Update Manager Client runs on the desktop: You can install the vSphere Update Manager server and vSphere Update
– Use the vSphere Update Manager Client to perform patch and version management Manager Client only on Windows machines.
of the vSphere inventory.
• Update Manager tab in the VMware vSphere® Web Client plug-in:
– Use to view scan results and compliance states for vSphere inventory objects.
Database:
• Use to store and organize server data.
Installing vSphere Update Manager Configuring vSphere Update Manager Settings

To use vSphere Update Manager, you must ensure that your vCenter You can modify the vSphere Update Manager configuration only if you
Server 6 is already installed, and complete the following tasks: have the correct privileges:
1. Create and prepare a database. • Network Connectivity Settings
2. Install the vSphere Update Manager server. • Download Settings
3. Install the vSphere Update Manager Client. • Proxy Settings

• Checking for Updates (Download Schedule) Settings
4. Enable the vSphere Update Manager plug-in for the vSphere Web
Client. • Notification Check Schedule Settings
• Virtual Machine Settings
• Host and Cluster Settings
2
3/20/2018
Baseline and Baseline Groups Creating and Editing Patch or Extension Baselines
A baseline consists of one or more patches, extensions, or upgrades: You can create custom patches, extensions, and upgrade baselines to
• vSphere Update Manager includes two default dynamic patch baselines and meet the needs of your specific deployment by using the New Baseline
three upgrade baselines. wizard:
A baseline group consists of multiple baselines: • Create a fixed patch baseline:
• Can contain one upgrade baseline per type and one or more patch and – Fixed baselines consist of a set of patches that do not change as patch availability
extension baselines. changes.
• Create a dynamic patch baseline:
– Dynamic baselines consist of a set of patches that meet certain criteria.
• Create a host extension baseline:

– Extension baselines contain additional software for ESXi hosts. This additional
software might be VMware software or third-party software.
• Filter patches or extensions in the New Baseline wizard:
– When you create a patch or extension baseline, you can filter the patches and
extensions available in the vSphere Update Manager repository to find specific
patches and extensions to exclude or include in the baseline.
Attaching a Baseline Scanning for Updates

To view compliance information and scan objects in the inventory against Scanning evaluates the inventory object against the baseline or baseline
baselines and baseline groups, you must first attach baselines and group.
baseline groups to these objects.
You can attach baselines and baseline groups to objects in the vSphere
Update Manager plug-in to the vSphere Web Client: the Update
Manager tab.
Viewing Compliance for vSphere Objects Remediating Objects

You can review compliance information for the virtual machines, virtual You can remediate virtual machines, templates, virtual appliances, and
appliances, and hosts against baselines and baseline groups that you hosts:
attach.
• You can perform the remediation immediately or schedule it for a later date.
• Host remediation runs in different ways, depending on the types of baselines
that you attach and whether the host is in a cluster or not.
• For ESXi hosts in a cluster, the remediation process is sequential by default.
• Remediation of hosts in a cluster requires that you temporarily disable cluster
features such as VMware vSphere® Distributed Power Management™ and
VMware vSphere® High Availability admission control.
3
3/20/2018
Patch Recall Notification Lab 23: Using vSphere Update Manager

At regular intervals, vSphere Update Manager contacts VMware to Install, configure, and use vSphere Update Manager
download notifications about patch recalls, new fixes, and alerts: • Install the vSphere Update Manager Server
• Notification Check Schedule is selected by default. • Install vSphere Update Manager
• Modify the Cluster Settings
On receiving patch recall notifications, vSphere Update Manager takes
the following actions: • Configure vSphere Update Manager
• Create a Patch Baseline
• Generates a notification in the notification tab
• Attach a Baseline and Scan for Updates
• No longer applies the recalled patch to any host:
• Stage the Patches onto the ESXi Hosts
– Patch is flagged as recalled in the database.
• Remediate the ESXi Hosts
• Deletes the patch binaries from its patch repository
vSphere Update Manager does not uninstall recalled patches from ESXi
hosts. It waits for a newer patch and applies that patch to make a host
compliant.

• Describe VMware vSphere® Update Manager™ functionality
• List the steps to install vSphere Update Manager
• Use vSphere Update Manager create and attach a baseline
Lesson 2:
Host Profiles

Learner Objectives About Host Profiles

By the end of this lesson, you should be able to meet the following Host profiles provide an automated and centrally managed mechanism
objectives: for host configuration and configuration compliance.
• Describe the host profiles workflow
• Identify how to create a host profile
• Recognize how to apply a host profile to an ESXi host or cluster
• Use host profiles to perform remediation on an ESXi host
4
3/20/2018
Host Profiles Workflow Creating a Host Profile

The host profile workflow starts with the concept of a reference host. The You create a host profile by extracting the designated reference host’s
reference host serves as the template from which the host profile is configuration.
extracted:
1. Set up and configure the reference host.
2. Create a host profile from the reference host.
3. Attach other hosts or clusters to the host profile.
4. Check the compliance of the added hosts to the host profile. If all
hosts are compliant with the reference host, they are correctly
configured.
5. Apply the resulting recommendations to the hosts.
Attaching a Host Profile to a Host or Cluster Checking Compliance

After creating a host profile from a reference host, you attach the host or You can confirm the compliance of a host or cluster to its attached host
cluster to the host profile. profile and determine which configuration parameters on a host are
different from those specified in the host profile.
Remediating an ESXi Host Review of Learner Objectives

In the event of a compliance failure, use the remediate function to apply You should be able to meet the following objectives:
the host profile settings onto the host. • Describe the host profiles workflow
This action changes all host profile-managed parameters to the values • Identify how to create a host profile
contained in the host profile attached to the host. • Recognize how to apply a host profile to an ESXi host or cluster
• Use host profiles to perform remediation on an ESXi host
5
3/20/2018
Key Points
• vSphere Update Manager reduces security vulnerabilities by keeping systems
up to date and by reducing the diversity of systems in an environment.
• Host profiles encapsulate the host configuration and help you manage the host
configuration.
Questions?

6
3/20/2018
Installing vSphere Components You Are Here

Monitoring
Virtual Networks
Virtual Storage
12. Installing vSphere
Components


By understanding the options in deploying VMware vCenter Server™ Lesson 1: Installing ESXi
and VMware ESXi™ hosts, you can select deployment options that best
fit the enterprise. Lesson 2: Installing vCenter Server
Learner Objectives
objectives:
• Describe how to install ESXi interactively
• Describe other methods of ESXi installation
• Identify the basic requirements for a boot-from-SAN configuration
Lesson 1:
Installing ESXi

1
3/20/2018
ESXi Hardware Prerequisites Information for Installing ESXi

Processor: 64-bit x86 CPU:
Installation Required or Default
Comments
• Requires at least two cores. Option Optional Selection
Keyboard layout Required U.S. English
• ESXi supports a broad range of x64 multicore processors.
Required for The vSphere Web Client can use either the host
• Requires NX/XD bit to be enabled for the CPU in the BIOS. Host name
static IP settings
None
name or the IP address to access the ESXi host.
Must be at least 5 GB if you install the components
Memory: 4 GB RAM minimum Install location Required None
on a single disk.
Keyboard
One or more Ethernet controllers: layout
Required U.S. English
• Gigabit, 10 Gigabit, and 40 Gigabit Ethernet controllers are supported. VLAN ID Optional None VLAN ID range: from 0 through 4094.
IP address Optional DHCP
Disk storage: Calculated based on IP
Configure a static IP address or use DHCP to
configure the network.
Subnet mask Optional
address
• A SCSI adapter, Fibre Channel adapter, converged network adapter, iSCSI IP address, subnet mask, gateway, and DNS
Based on IP address and
adapter, or internal RAID controller Gateway Optional
subnet mask network settings can be changed after installation.
• A SCSI disk, Fibre Channel logical unit number (LUN), iSCSI disk, or RAID Primary DNS Optional
Based on IP address and Secondary DNS server can also be defined
subnet mask
LUN with unpartitioned space: SATA, SCSI, or Serial Attached SCSI
Root password Optional None Must contain from 8 through 40 characters
Installing ESXi Other ESXi Installation Options

You must have the ESXi ISO file on CD, DVD, or USB flash drive media. In addition to using an interactive installation procedure to install ESXi,
Boot from the media to start the ESXi installer. the following options are available:
• Scripted ESXi installation:
Select a volume that is not formatted with VMware vSphere® VMFS.
– The script contains the host configuration settings.
– The script must be stored in an accessible location such as HTTP, HTTPS, FTP, NFS,
CD, or USB.
Select a volume that – A PXE boot installation is possible.
is not formatted with • Automatic ESXi installation with VMware vSphere® Auto Deploy™:
VMFS.
– The ESXi host loads the image directly into the host memory.
– The ESXi installation can be either stateful or stateless.
– PXE boot is used to contact an autodeploy server.
– vSphere Auto Deploy uses host profiles.
• Remote management applications:

– Install ESXi on hosts in remote locations with third-party management applications.
Booting from SAN Review of Learner Objectives

ESXi can be booted from SAN: You should be able to meet the following objectives:
ESXi
• Supported for Fibre Channel SAN • Describe how to install ESXi interactively
• Supported for iSCSI and Fibre Channel over Ethernet • Describe other methods of ESXi installation
for certain qualified storage adapters • Identify the basic requirements for a boot-from-SAN configuration
SAN connections must be made through a

switched topology unless the array is certified for
direct-connect.
The ESXi host must have exclusive access to its
own boot LUN.
Use different LUNs for VMFS datastores and boot
partitions.
Boot LUN
2
3/20/2018
Learner Objectives
objectives:
• Choose between a distributed configuration and an embedded configuration,
based on your requirements
• Choose between a Windows-based installation and an appliance, based on
your requirements
Lesson 2: • Identify the basic requirements for a vCenter Server installation
Installing vCenter Server

Overview of the vSphere Installation Process Platform Services Controller

VMware vSphere® is a sophisticated product with multiple components vCenter Server includes the Platform Services Controller.
to install and set up. To ensure a successful vSphere deployment, follow
The Platform Services Controller includes a set of common
this sequence of required tasks:
infrastructure services:
1. Read the vSphere release notes.
• VMware vCenter™ Single Sign-On™
2. Verify that your system meets vSphere hardware and software requirements. Virtual Machine or Physical
• VMware License Server
3. Install ESXi 6 on your ESXi hosts.
• Lookup Service
4. (Optional) Set up a Syslog server for remote logging. Platform Services
• Certificate Authority Controller
5. Prepare databases.
• Certificate Store
6. Synchronize clocks on the vSphere network with a network time server. vCenter Server
7. Configure vCenter Server administrator user accounts.
8. Deploy VMware Platform Services Controller™.
9. Install vCenter Server.
© 2015 VMware Inc. All rights reserved. © 2015 VMware Inc. All rights reserved. 1
6
Other vCenter Server Functions and Services Choosing Your Configuration

vCenter Server provides other functions and services as part of the You choose between the following major options when you plan your
vSphere system: vCenter Server installation:
• vCenter Server • Single system or distributed?
• VMware vSphere® Web Client (server) • Windows server-based or virtual appliance?
• VMware Inventory Service Virtual Machine or Physical • Embedded database or external database?
• vSphere Auto Deploy • Physical server or virtual machine?
Platform Services
• VMware vSphere® ESXi™ Dump Collector Controller
• VMware vSphere® Syslog Collector
vCenter Server
3
3/20/2018
When to Use a Windows Server or a Virtual Appliance Choosing a Single System or a Distributed System
Should you use a Windows server or a virtual appliance? Consider the following options when you install a single (embedded)
Virtual appliance advantages: system or a distributed system:
• A virtual appliance is much easier to install and configure. • In a single system all components are installed on one server:
• No operating system license is required. – Much simpler to install.
– Much simpler to manage.
• All configuration is done through a GUI.
– The user interface calls a single system deployment an embedded deployment.
• vCenter Server running on a virtual appliance can scale to the same loads as a
vCenter Server installed on a Windows server • In a distributed system you have multiple servers:
– You can have different components on different servers.
vCenter Server system running on a Windows server advantages:
– A distributed system can handle higher loads and provide more fault tolerance if it is
• Better for administrators who are more comfortable with Windows. configured correctly.
• More options for external database support. – The user interface calls a distributed deployment an external install.
• Configuration is done through a GUI, but individual components appear as
Windows services.
Both the Windows and the virtual appliance types of installation appear
the same and operate the same in the vSphere Web Client, with identical
functionality.
vCenter Server in an Embedded Install Distributed vCenter Server System Configuration

All services bundled with the Platform Services Controller are deployed The services included with the Platform Services Controller and vCenter
on the same host as vCenter Server. Server are deployed on different physical servers or virtual appliances.
Optional Additional Embedded Servers You first must deploy the Platform Services Controller on one virtual
machine or physical server and then deploy vCenter Server on another
virtual machine or physical server.
Virtual Machine or Physical Virtual Machine or Physical
After a deployment method is selected, it cannot be undone.
Platform Services VMDir
Platform Services
Controller Controller
Replication Virtual Machine or Physical Virtual Machine or Physical
Platform Services VMDir Platform Services

vCenter Server vCenter Server Controller Replication Controller
• A single server with an embedded Platform Services Controller is suitable for Virtual Machine or Virtual Machine or Virtual Machine or Virtual Machine or
deployments with eight or fewer ESXi host instances. Physical Physical Physical Physical
• The Platform Services Controller supports data replication. vCenter Server vCenter Server vCenter Server vCenter Server
The green arrows represent VMDir replication.
Choosing an Installation Method vCenter Server Appliance Benefits

You must determine which vCenter Server installation method meets the VMware vCenter Server™ Appliance™ has many benefits:
needs of your organization: • Simplified installation and setup.
• A virtual appliance is much easier to install and configure: • Contains all of the necessary services, such as vCenter Single Sign-On and
– No operating system license is required. the License Service, which can be shared between multiple vCenter Server
– All configuration is done through a GUI. instances.
• vCenter Server Appliance and Windows-based vCenter Server have the same • The VMware vFabric® Postgres embedded database supports larger
functionality. Both can be used to manage large environments. environments than databases embedded in previous vCenter Server Appliance
versions.
• Support for both IPv4 and IPv6 connectivity (no mixed mode deployments).
4
3/20/2018
vCenter Server Appliance Features Installing vCenter Server on a Windows Server

vCenter Server Appliance is a preconfigured Linux-based virtual Instead of using a virtual appliance, you can install vCenter Server on
machine, which is optimized for running vCenter Server. Microsoft Windows Server 2008 SP2 or later:
• vCenter Server Appliance runs on SUSE Linux Enterprise Server 11, Update 3. 1. Validate vCenter Server hardware and software requirements.
• vCenter Server Appliance can be used with ESXi 5.5 and ESXi 6. 2. Choose a vCenter Server database.
• Prepackaged with a VMware vFabric® Postgres database embedded – Embedded vFabric Postgres database
database: – External database
– Suitable for environments with up to 1,000 hosts and 10,000 virtual machines. 3. Install vCenter Server and the infrastructure services.
– Also supports Oracle 11g R2 11.2.0.4 and Oracle 12c as external databases. – Embedded Platform Services
• Equipped with the vCenter Server Appliance console for troubleshooting and – External Platform Services Controller
configuration.
• Supports vSphere Web Client.
• Supports connections by either IPv4 or IPv6 addresses.
User Account for Running vCenter Server vCenter Server Windows Host Requirements
You can use the Microsoft Windows built-in system account or a user At installation, when you select the deployment model, the preinstallation
account to run vCenter Server: checker determines whether the Windows server on which you install
• User (administrator) account: vCenter Server meets the minimum hardware requirements.
– With this account, you can enable Windows authentication for SQL Server.
– This account provides more security.
• Microsoft Windows built-in system account: vCenter Server with an vCenter Server with an External
– This account has more permissions and rights on the server than the vCenter Server Embedded Platform Platform Services Controller
system needs. Services Controller
– This account can contribute to security problems.
vCenter Platform Services
Property
• The virtual appliance has a built-in administrator account (root). Server Controller
Memory 8 GB 8 GB 2 GB
Disk Space 17 GB 17 GB 4 GB
Number of
2 2 2
CPUs
Supported External Databases for vCenter Server 6 on

Supported Operating Systems for vCenter Server 6 Windows
Windows operating systems supported by vCenter Server 6: Databases that are tested and supported for vCenter Server 6 as
external databases:
• Microsoft Windows Server 2008 SP2 64-bit
• Microsoft SQL Server 2008 R2 SP1
• Microsoft Windows Server 2008 R2 64-bit
• Microsoft SQL Server 2008 R2 SP2
• Microsoft Windows Server 2008 R2 SP1 64-bit
• Microsoft SQL Server 2012
• Microsoft Windows Server 2012 64-bit
• Microsoft SQL Server 2012 SP1
• Microsoft Windows Server 2012 R2 64-bit
• Microsoft SQL Server 2014
• Oracle 11g R2 11.2.0.4
• Oracle 12c
5
3/20/2018
Before Installing vCenter Server Installing vCenter Server and Its Components
Before beginning the vCenter Server installation, ensure that the You use the VMware vCenter Installer to install vCenter Server.
following prerequisites are met:
• Ensure that vCenter Server hardware and software requirements are met.
• Ensure that the vCenter Server system belongs to a Microsoft Windows
domain rather than a workgroup.
• Create a vCenter Server database, unless you plan on using the embedded
Embedded
vFabric Postgres database: Deployment
– If you create a database, you must also create a 64-bit data source name.
• Obtain and assign a static IP address and a host name to the vCenter Server
system:
– The name should be resolvable by DNS.
Distributed
– If you plan to use IPv6, the name should be resolvable in IPv6 by DNS. Deployment
• Create any administrator accounts that are needed.
Required Information vCenter Server Installation Demonstration

The VMware vCenter Installer prompts you for the listed parameters. Your instructor will run a demonstration of the vCenter Server installation
on a Windows server.
Parameter Description
System name of the local

Must be a fully qualified domain name.
system
Either create a vCenter Single Sign-On domain or join
Single sign-on domain
an existing domain. User name and password required.
License key Evaluation or valid license key.

Default database or remote database connection
Database information
information.
System account information User for running the vCenter Server service.
Destination folder Software location.
Ports used for communicating with client interfaces and

Ports
managed hosts.

You should be able to meet the following objectives: • ESXi installation requires little configuration during installation.
• Choose between a distributed configuration and an embedded configuration, • vCenter Server consists of the Platform Services Controller and vCenter
based on your requirements Server Appliance.
• Choose between a Windows-based installation and an appliance, based on • You can install vCenter Server in distributed or embedded configurations.
your requirements
• You can use either an external database or an embedded database.
• Identify the basic requirements for a vCenter Server installation
• You can install vCenter Server on a Windows system or configure vCenter
Server Appliance.
• vCenter Server installed on Windows operating systems can run on physical
machines or virtual machines.
Questions?

VSICM6 PowerPoint

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VSICM6 PowerPoint

Uploaded by

Copyright:

Available Formats

3/20/2018

Course Introduction Learner Objectives (2)

VMware vSphere: Install, Configure, Manage 1-4

Importance You Are Here

Learner Objectives (1) Typographical Conventions

References VMware Education Overview

VMware Online Resources

VMware vSphere: Install, Configure, Manage 1-8

VCP-Core Certification Alignment

VMware vSphere: Install, Configure, Manage 1-9

Software-Defined Data Center You Are Here

Module 2 1. Course Introduction 7. Virtual Machine Management

VMware vSphere: Install, Configure, Manage 2-2

Importance Module Lessons

• The fundamental vSphere components and how vSphere can be used

2-5 VMware vSphere: Install, Configure, Manage 2-6

Topology of a Physical Data Center Introducing the Virtual Infrastructure

About Virtual Machines Benefits of Using Virtual Machines

Physical Architecture and Virtual Architecture Physical Resource Sharing

Physical Architecture Virtual Architecture

CPU Virtualization Physical and Virtualized Host Memory Usage

Operating System vSphere 1 GB 2 GB 8 GB

Operating System vSphere

Physical and Virtual Networking Physical File Systems and VMFS

Physical Virtual Architecture

Operating System Operating System vSphere vSphere

x64 Architecture x64 Architecture x64 Architecture x64 Architecture

Encapsulation About the Software-Defined Data Center

Software-Defined Data Center

Virtualized Infrastructure Hybrid Cloud

Datastore: VMFS or NFS

How vSphere Fits into Cloud Computing About Private Clouds

Private Hybrid Public

About Public Clouds About Hybrid Clouds

• Rapid and flexible Management Management

Review of Learner Objectives

VMware vSphere: Install, Configure, Manage 2-23 2-24

Learner Objectives User Interfaces

Your vSphere Web Client

Downloading vSphere Client Using vSphere Client

vSphere Client: Configuration Tab Viewing Processor and Memory Configuration

Lab 1: Installing vSphere Client Review of Learner Objectives

2-35 VMware vSphere: Install, Configure, Manage 2-36

About ESXi Hosts Physical and Virtual Architecture

VMM VMM VMM VMM VMM

VMware Hypervisor: VMkernel

Configuring an ESXi Host Configuring an ESXi Host: Root Access

Managing User Accounts Best Practices Lab 2: Configuring ESXi Hosts

Review of Learner Objectives Key Points

Creating Virtual Machines You Are Here

Module 3 1. Course Introduction 7. Virtual Machine Management

VMware vSphere: Install, Configure, Manage 3-2

Importance Module Lessons

3-5 VMware vSphere: Install, Configure, Manage 3-6

About Virtual Machine Files About Virtual Machine Virtual Hardware

Virtual Hardware Versions About Virtual Hardware Version 11

About CPU and Memory About Virtual Disks

A virtual machine running on an ESXi 6 host can have up to 128 vCPUs.

About Thick-Provisioned Virtual Disks About Thin-Provisioned Virtual Disks

About Network Virtual Machine Configuration About Network Adapters

About Miscellaneous Devices About the Virtual Machine Console

Review of Learner Objectives

VMware vSphere: Install, Configure, Manage 3-19 3-20

Learner Objectives About Provisioning Virtual Machines