Академический Документы
Профессиональный Документы
Культура Документы
Contents
Page 1 of 85
Objective 7.1 – Create and Configure VMware Clusters .................................................................................................. 49
Objective 7.2 – Enable a Fault Tolerant Virtual Machine ................................................................................................. 54
Objective 7.3 – Create and Configure Resource Pools ..................................................................................................... 57
Objective 7.4 – Migrate Virtual Machines ........................................................................................................................ 60
Objective 7.5 – Backup and Restore Virtual Machines ..................................................................................................... 63
Section 8 – Perform Basic Troubleshooting and Alarm Management.................................................................................. 65
Objective 8.1 – Perform Basic Troubleshooting for ESX/ESXi Hosts ................................................................................. 65
Objective 8.2 – Perform Basic Troubleshooting for VMware FT and Third-Party Clusters............................................... 67
Objective 8.3 – Perform Basic Troubleshooting for Networking ...................................................................................... 69
Objective 8.4 – Perform Basic Troubleshooting for Storage ............................................................................................ 70
Objective 8.5 – Perform Basic Troubleshooting for HA/DRS and VMotion ...................................................................... 71
Objective 8.6 – Create and Respond to vCenter Connectivity Alarms ............................................................................. 74
Objective 8.7 – Create and Respond to vCenter Utilization Alarms ................................................................................. 76
Objective 8.8 – Monitor vSphere ESX/ESXi and Virtual Machine Performance ............................................................... 78
Appendix A – Configuration Maximums ............................................................................................................................... 82
Appendix B – CLI.................................................................................................................................................................... 84
Appendix C – Sources ............................................................................................................................................................ 85
Page 2 of 85
Section 1 – Plan, Install and Upgrade VMware ESX/ESXi
Objective 1.1 -- Install VMware ESX/ESXi on local storage
Identify minimum hardware requirements
o 64-Bit Server (AMD Opteron, Intel Xeon, or Intel Nehalem)
Up to 64 logical CPUs (cores or hyperthreads)
o 2GB RAM; 1TB Max
o 1+ Network Controller (Broadcom NetXtreme 570x & Intel Pro 1000); 10Gb supported
o 1+ SCSI adapter , Fibre Channel adapter, iSCSI adapter, or Internal RAID controller
o 1+ SCSI disk, Fibre Channel LUN, iSCSI disk, or RAID LUN with unpartitioned space
ATA & IDE (ESX only; cannot store VMs), SAS, SATA, SCSI, SANs
ESXi: 5GB disk
Page 3 of 85
Perform a custom installation
o Customize storage layout for given situations
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_vc_installation_guide.pdf#pag
e=61
Choose Advanced Setup
/boot Ext3 1250MB (1.25GB) [Boot Partition]
/ Ext3 5000MB (5GB) [Root Partition]
(none) Swap 600MB [Swap Partition for Service Console]
/var/log Ext3 2000MB (2GB) [Log File Partition]
(none) Vmkcore 100MB [Vmkcore Partition for dump files]
/boot and vmkcore are physical partitions. /, swap, /var/log, and all the optional partitions are
stored on a virtual disk called esxconsole-<system-uuid>/esxconsole.vmdk. The virtual disk is
stored in a VMFS volume.
Note: The service console must be installed on a VMFS datastore that is resident on a host's
local disk or on a SAN disk that is masked and zoned to that particular host only. The name of
the service console file: esxconsole.vmdk Size: 1200MB
Configure ESXi from the direct console
o Boot from DVD or Log into the console and Press F2
Page 4 of 85
Manage ESX/ESXi licensing
o Compare/Contrast VMware vSphere editions
ESXi:
Page 5 of 85
Objective 1.2 – Upgrade VMware ESX/ESXi
Plan a VMware vSphere upgrade
o Backup/Restore ESX/ESXi host configuration
vCenter’s Host Profiles
ESX: File-based & Image-based Service Console backup/restore methods
ESXi: vicfg-cfgbackup --server <ESXi-host-ip> --portnumber <port_number> --protocol
<protocol_type> --username < username> --password <password> -s <backup-filename>
Recovery CD / Repair option on the CD
Note: Before you upgrade an ESX host, back up:
Page 6 of 85
Understand VMware ESX/ESXi upgrade scenarios
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_upgrade_guide.pdf
o Host Update Utility
Graphical utility for standalone hosts. This utility is intended for small deployments with fewer
than 10 ESX/ESXi hosts and without vCenter Server or vCenter Update Manager.
Note: Can only be used to upgrade ESX and perform automated host compatibility checks.
o Update Manager
Robust software for upgrading, updating, and patching clustered hosts, virtual machines, and
guest operating systems.
Page 7 of 85
Objective 1.3 – Secure VMware ESX/ESXi
Identify default security principles
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf#page=163
o ESX uses the Pluggable Authentication Modules (PAM) structure for authentication when users access
the ESX host using the vSphere Client. The default installation of ESX uses /etc/passwd authentication as
Linux does, but you can configure ESX to use another distributed authentication mechanism.
By default, passwords are set to never expire.
The default minimum number of days between password changes is 0.
The default number of days in advance of password expiration that a reminder is sent is 7.
The minimum password length is set to nine. This means that the user must enter at least eight
characters if they use only one character class (lowercase, uppercase, digit, or other). The
password length algorithm allows shorter passwords if the user enters a mix of character
classes.
Understand Service Console firewall operation
o By default, all incoming connections to the service console port of an ESX server are blocked. A firewall
on the ESX Server checks all incoming traffic and allows only traffic explicitly allowed in the firewall
configuration. The firewall can be configured in two ways, from the command line and from the vCenter
GUI.
o http://www.vmadmin.co.uk/index.php/resources/35-esxserver/51-esxfirewallcmd
o Service Console Security Level
High (default): Incoming ports blocked by default; Outgoing ports blocked by default
Medium: Incoming ports blocked by default; Outgoing ports not blocked by default
Low: Incoming ports not blocked by default; Outgoing ports not blocked by default
o Opening/Closing ports in the firewall using the vSphere Client
Select ESX Host Configuration tab Security Profile Properties
ESX Console (not in Blueprint guide):
Page 8 of 85
Determine applications needed for accessing the service console in a given scenario
o To access the service console there are roughly two options: (1) From the local terminal (monitor,
keyboard); (2) Remote using a SSH (Secure Shell) Client. Linux and Mac have a SSH client by default.
For Windows, Putty is a favored client for accessing SSH Servers.
Before you can access a VMware ESX server with a remote client you need to explicitly allow access.
Also, an account needs to be created. Remote root access is disabled by default, but can be enabled.
This however is not a best practice!!! The most secure way is to log in as a regular user and use sudo to
execute privileged commands.
Page 9 of 85
Objective 1.4 – Install VMware ESX/ESXi on SAN Storage
Configure LUN Masking
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_san_cfg.pdf#page=83
o LUN Masking is used to hide certain LUNs for the ESX hypervisor. All LUNs presented to the OS are
under normal circumstances visible (assuming the LUNs are presented on the storage array). When
installing ESX on a LUN you want to be sure you only see the partition you want to install ESX on,
otherwise you risk overwriting valuable VMFS partition with VM’s. Hiding LUNs during installation is
typically done on your storage array.
o esxcli corestorage claimrule add -r <claimrule_ID> -t <type> <required_option> -P <MASK_PATH>
Prepare SAN
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_san_cfg.pdf#page=33
o Fibre Channel SAN:
1. Connect the FC and Ethernet cables, referring to any cabling guide that applies to your setup.
2. Configure the storage array:
a) From the SAN storage array, make the ESX host visible to the SAN.
o If you are using VMotion, DRS, or HA, make sure that both source and target
hosts for virtual machines can see the same LUNs with identical LUN IDs.
b) From the SAN storage array, set up the ESX host to have the WWPNs of the host’s FC
adapters as port names or node names.
c) Create LUNs.
d) Assign LUNs.
e) Record the IP addresses of the FC switches and storage arrays.
f) Record the WWPN for each SP and host adapter involved.
3. Configure the HBA BIOS for boot from SAN.
4. Boot your ESX system from the ESX installation CD.
CAUTION! If you use scripted installation to install ESX in boot from SAN mode, you need to
take special steps to avoid unintended data loss.
o iSCSI SAN:
1. Connect network cables, referring to any cabling guide that applies to your setup.
2. Configure the storage system so that the ESX system has access to the assigned LUN. This could
involve updating ACLs with the IP addresses, iSCSI names, and the CHAP authentication
parameter you use on the ESX system. On some storage systems, in addition to providing access
information for the ESX host, you must also explicitly associate the assigned LUN with the host.
3. Ensure that the LUN is presented to the ESX system as LUN 0. The host can also boot from LUN
255. On storage systems that present volumes as multiple targets rather than multiple LUNs,
the volumes are always presented as LUN 0.
4. Ensure that no other system has access to the configured LUN.
5. Record the iSCSI name and IP addresses of the targets assigned to the ESX host.
Page 10 of 85
6. You must have this information to configure your iSCSI HBA.
Page 11 of 85
o Enable BIOS
1. Enter the BIOS Fast!UTIL configuration utility:
a) Boot the server
b) While booting the server, press Ctrl+Q
2. Perform the appropriate action depending on the number of HBAs.
3. In the Fast!UTIL Options page, select Configuration Settings and press Enter.
4. In the Configuration Settings page, select Host Adapter Settings and press Enter.
5. Set the BIOS to search for SCSI devices:
a) Set the BIOS to search for SCSI devices.
b) Press Enter to toggle the value to Enabled.
c) Press Esc to exit.
o Select the Boot LUN
1. Use the cursor keys to select the first entry in the list of storage processors.
2. Press Enter to open the Select Fibre Channel Device page.
3. Use the cursor keys to select the chosen SP and press Enter.
a) If the SP has only one LUN attached, it is selected as the boot LUN, and you can skip to
Step 4.
b) If the SP has more than one LUN attached, the Select LUN page opens. Use the arrow
keys to position to the selected LUN and press Enter.
4. Press Esc twice to exit.
5. Press Enter to save the setting.
Page 12 of 85
Objective 1.5 – Identify vSphere Architecture and Solutions
Differentiate VMware platform products and editions
o Datacenter Products
VMware vSphere 4
VMware ESXi
VMware Server
o Management Products
VMware vCenter Server
VMware vCenter Server Heartbeat
VMware vCenter Orchestrator
VMware vCenter Site Recovery Manager
VMware vCenter Lab Manager
VMware vCenter Lifecycle Manager
VMware vCenter Converter
VMware vCenter Chargeback
VMware vCenter ConfigControl
VMware CapacityIQ
VMware vCenter AppSpeed
o Desktop products
VMware View 4
VMware ThinApp
VMware ACE
VMware Workstation
VMware Fusion (Mac)
VMware Player
Understand the various datacenter solutions (View, SRM, Lab Manager, etc.)
o Site Recovery Manager
VMware Site Recovery Manager is a pioneering disaster recovery management and automation solution
for VMware vSphere 4. Site Recovery Manager accelerates recovery by automating the recovery
process and simplifies management of disaster recovery plans by making disaster recovery an integrated
element of managing your VMware virtual infrastructure. Site Recovery Manager also ensures reliable
recovery by eliminating complex manual recovery steps and enabling non-disruptive testing of recovery
plans.
o VMware Server Heartbeat
VMware vCenter Server Heartbeat delivers high availability and disaster recovery for VMware vCenter
Server and all of its components – including the database and licensing server—with failover across the
LAN or WAN. The software supports physical-to-virtual (P2V), physical-to-physical (P2P) and virtual-to-
virtual (V2V) failover, ensuring consistent operation of VMware vSphere when VMware vCenter Server is
threatened by unplanned or planned downtime.
Page 13 of 85
o VMware Lab Manager
vCenter Lab Manager allows IT to provide non-IT users with on-demand access to shared virtual
resources. Application owners, development and testing teams, support and training organizations can
create, deploy and reconfigure multi-tier system configurations in seconds. Self-service management
with policy-based access control reduces administrative burden and infrastructure management costs,
and empowers businesses to deliver new or updated applications rapidly and with greater agility.
VMware vCenter Lab Manager streamlines application development and testing by giving every
engineer the equivalent of his or her own personal datacenter.
o Life Cycle Manager
VMware vCenter Lifecycle Manager provides a service catalog of virtual machine configurations to
automate provisioning tasks and standardize the way virtual machines are requested, deployed and
decommissioned. Lifecycle Manager helps IT administrators deploy virtual infrastructure more broadly,
gain more control and visibility, and optimize resource utilization for greater ROI.
o VMware Converter
VMware Converter reduces the amount of time spent on migrating to a virtual infrastructure by
enabling fast, reliable and non-disruptive conversions from physical to virtual machines, and from older
virtual machines to newer formats.
o VMware View
VMware allows you to use your virtual infrastructure to host desktops. Users can access their virtual
desktops from a wide variety of devices thick, thin or mobile—without any performance degradation.
Page 14 of 85
Section 2 – Configure ESX/ESXi Networking
Objective 2.1 – Configure Virtual Switches
Page 15 of 85
Create/Delete Virtual Switches
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf#page=18
1. Select ESX host
2. Select the Configuration tab
3. Click Networking Add Networking
4. Select Virtual Machine
5. Select the appropriate NICs
6. Enter a Name and optional VLAN ID
Page 16 of 85
Modify vSwitch security policy and VLAN settings
1. Select the Configuration tab
2. Click Networking
3. Click Properties next to an existing vSwitch
4. Select the vSwitch Click Edit
5. Select the Security tab
6. Adjust the security settings
Configure VMotion
o To configure VMotion, you need to add a VMkernel Port to one of your vSwitches. To add a VMkernel Port,
you can use the Create Port Groups section described earlier. Once the port group is added, you enable
VMotion:
1. Select ESX host
2. Select the Configuration tab
3. Click Networking
4. Click Properties next to an existing vSwitch
5. Select the VMotion port group click Edit
6. Make sure the VMotion checkbox is checked
Page 17 of 85
Objective 2.2 – Configure vNetwork Distributed Switches
Understand ESX Host and port maximums for dvSwitches (Enterprise Plus license only)
o A vNetwork Distributed Switch (dvSwitch) is a virtual switch that spans multiple ESX hosts. Unlike the
previously covered vSwitch (ESX local host switch), a dvSwitch has one configuration for all ESX hosts and
allows for new features like network statistics that VMotion along with the host. dvSwitches are created
and managed by the vCenter server.
Maximums
http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf#page=6
Virtual network switch ports per host (vDS and vSS ports): 4096
Distributed port groups per vCenter: 512
Distributed virtual network switch ports per vCenter: 6000
Distributed switches per vCenter: 16
Hosts per distributed switch: 64
Page 18 of 85
Objective 2.3 – Configure VMware ESX/ESXi Management Network
Page 19 of 85
Section 3 – Configure ESX/ESXi Storage
Objective 3.1 – Configure FC SAN Storage
o LUN Masking is an authorization process that makes a Logical Unit Number available to some hosts and
unavailable to other hosts. Usually, LUN masking is performed at the SP or server level.
Configure LUN masking
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_san_cfg.pdf#page=83
o esxcli corestorage claimrule add -r <claimrule_ID> -t <type> <required_option> -P
<MASK_PATH>
Page 20 of 85
Scan for new LUNs
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_san_cfg.pdf#page=55
1. Select ESX host
2. Select the Configuration tab
3. Click Storage Adapters Rescan
Page 21 of 85
Objective 3.2 – Configure iSCSI SAN Storage
Page 22 of 85
o If needed, enable Jumbo Frames. Jumbo Frames must be enabled for each vSwitch through the vSphere
CLI. Also, if you use an ESX host, you must create a VMkernel network interface enabled with Jumbo
Frames. (http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.pdf#page=35)
Configure Dynamic/Static Discovery
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.pdf#page=35
1. Select a ESX host
2. Select the Configuration tab
3. Select Storage Adaptors
4. Select the iSCSI Initiator Properties
5. Click the Dynamic Discovery or Static Discovery tab and add a server or target
Page 23 of 85
Identify iSCSI addressing in the context of the host
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.pdf#page=10
o iSCSI Name: Identifies a particular iSCSI element, regardless of its physical location. The iSCSI name can
use IQN or EUI format.
o IQN (iSCSI qualified name). Can be up to 255 characters long and has the following format:
Page 24 of 85
Objective 3.3 – Configure NFS Datastores
Page 25 of 85
Objective 3.4 – Configure and Manage VMFS Datastores
o Only extents with free space immediately after them are expandable. As a result, rather than adding the
new extent, you can grow the existing extent so that it fills the available adjacent capacity. An extent
can be grown any number of times, up to 2TB minus 512B.
o You can add a new extent to any existing VMFS datastore. A datastore can have up to 32 extents.
o A VMFS can have a maximum volume size of 64TB minus 16K .
Page 26 of 85
Objective 3.BONUS – Understanding Storage Device Naming
In the vSphere Client, each storage device, or LUN, is identified by several names, including a friendly name, a
UUID, and a runtime name.
o Name: A friendly name that the ESX host assigns to a device based on the storage type and
manufacturer. You can modify the name using the vSphere Client. When you modify the name of the
device on one host, the change takes affect across all hosts that have access to this device.
o Identifier: A universally unique identifier assigned to a device. Depending on the type of storage,
different algorithms are used to create the identifier. The identifier is persistent across reboots and is
the same for all hosts sharing the device.
Example: naa.6090a02830bb6189f8ab9429000010e8
o Runtime Name: The name of the first path to the device. The runtime name is created by the host, is
not a reliable identifier for the device, and is not persistent.
Example: vmhba33:C0:T5:L0
The runtime name has the following format: vmhba#:C#:T#:L#, where
vmhba# is the name of the storage adapter. The name refers to the physical adapter on the
host, not to the SCSI controller used by the virtual machines.
C# is the storage channel number. Software iSCSI initiators use the channel number to show
multiple paths to the same target.
T# is the target number. Target numbering is decided by the host and might change if there is a
change in the mappings of targets visible to the host. Targets that are shared by different ESX
hosts might not have the same target number.
L# is the LUN number that shows the position of the LUN within the target. The LUN number is
provided by the storage system. If a target has only one LUN, the LUN number is always zero (0).
Page 27 of 85
Section 4 – Install and Configure vCenter Server
Objective 4.1 – Install vCenter Server
Page 29 of 85
Install additional modules
o vCenter Guided Consolidation:
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_vc_installation_guide.pdf#page=115
vCenter Guided Consolidation enables you to migrate from physical servers to virtual infrastructure
using a wizard that identifies physical servers for consolidation, converts them to virtual machines, and
places them onto ESX/ESXi hosts.
o vCenter Update Manager:
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_vc_installation_guide.pdf#page=116
Using vCenter Update Manager, you can orchestrate steps of an upgrade process sequentially, based on
compliance baselines at the host, virtual machine, and datastore level.
ESX host upgrade per cluster: 1
ESX host remediation per VUM server: 8
Virtual machine remediation per ESX host: 5
o vCenter Converter:
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_vc_installation_guide.pdf#page=117
Using vCenter Update Manager, you can orchestrate steps of an upgrade process sequentially, based on
compliance baselines at the host, virtual machine, and datastore level.
Concurrent import/export tasks (assumes no load on vCenter Server system): 16
Page 30 of 85
Objective 4.2 – Manage vSphere Client plug-ins
Page 31 of 85
Objective 4.3 – Configure vCenter Server
Identify the vCenter Server managed ESX Hosts and Virtual Machine maximums
o ESX: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf#page=3
ESX hosts on 32-bit vSphere: 200
VMs on 32-bit vSphere (powered on / registered): 2000 / 3000
ESX hosts on 64-bit vSphere: 300
VMs on 64-bit vSphere (powered on / registered): 3000 / 4500
Linked vCenter Servers: 10
Concurrent vSphere Clients (32 / 64 bit): 15 / 30
ESX hosts per datacenter: 100
Concurrent Storage VMotions (Host / Datastore): 2 / 4
Concurrent operations per vCenter: 96
o VM: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf
CPUs (Virtual SMP): 8
RAM: 255GB
Swap file size: 255GB
SCSI adapters: 4
SCSI targets per SCSI adapter: 15
SCSI targets: 60
Disk size: 2TB minus 512B
NICs: 10
Concurrent remote console connections to a virtual machine: 40
Page 32 of 85
Use Datacenters and Folders to organize the environment
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=72
o Datacenters can represent physical or logical datacenters in your IT environment. Please note that you
cannot use VMotion to live migrate VMs from one Datacenter to another. For both folders and
datacenters, it is possible to set user rights to allow or disallow certain user actions.
Configure/Use Scheduled Tasks
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=283
o Home Management Scheduled Tasks
o Note: The vSphere Client must be connected to a vCenter Server system to schedule tasks.
o Note: After a scheduled task is created, it will be performed even if the user no longer has permission to
perform the task.
Configure/Use Resource Maps
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=231
Use Storage Reports/Storage Maps
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=227
o Reports and Maps are updated every 30 minutes
View/Manage Events
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=289
o Home Management Events
Configure vCenter Server settings
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=46
o Administration vCenter Server Settings
Configure vSphere Client settings
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=38
o Edit Client Settings
Page 33 of 85
Objective 4.4 – Configure Access Control
o VMware recommends several best practices for creating users and groups in your vSphere environment:
Use vCenter Server to centralize access control, rather than defining users and groups on
individual hosts.
Choose a local Windows user or group to have the Administrator role in vCenter Server.
Create new groups for vCenter Server users. Avoid using Windows built-in groups or other
existing groups.
Define vCenter predefined roles and their privileges
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=214
o No Access, Read Only, Administrator, Virtual Machine Administrator, Virtual Machine Power User,
Virtual Machine User, Resource Pool Administrator, VMware Consolidated Backup User,
Datastore Consumer, Network Consumer, Datacenter Administrator
Page 34 of 85
Assign roles to users and groups
1. Select an Object (e.g. VM, Datacenter, Host, Folder)
2. Select the Permissions tab
3. Right click and select Add
4. Select the role you would like to assign in the right pane
5. Select the local or AD user / user group you would like to assign
Page 35 of 85
Section 5 – Deploy and Manage Virtual Machines and vApps
Objective 5.1 – Create and Deploy Virtual Machines
Page 36 of 85
o Determine Virtual Disk type
VMDK (New or Existing) (Thin Provisioned Format or Thick Format)
Raw Device Mapping (Virtual or Physical Mode)
Virtual: Allows the RDM to behave as if it were a virtual disk, so you can use such
features as snapshotting, cloning, and so on.
Physical: Allows the guest operating system to access the hardware directly. Physical
compatibility is useful if you are using SAN-aware applications on the virtual machine.
However, a virtual machine with a physical compatibility RDM cannot be cloned, made
into a template, or migrated if the migration involves copying the disk.
o Install/Upgrade/Configure VMware Tools
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=122
1. Right click a VM in the vCenter client
2. Select Guest Install/Upgrade VMware Tools
3. Select either Interactive Tools Installation or Automatic Tools Upgrade
Create/Convert templates
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=167
o Right click the VM and choose Template Clone to Template (can be done when VM is powered on) or
Convert to Template (only available when VM is off, VM will be converted to template.).
Page 37 of 85
Deploy a virtual machine using VMware vCenter Converter Enterprise
o Perform Hot Clone: http://www.vmware.com/pdf/vsp_vcc_41_admin_guide.pdf#page=11
o Perform Cold Clone: http://www.vmware.com/pdf/vsp_vcc_41_admin_guide.pdf#page=13
o Perform System Reconfiguration:
http://www.vmware.com/pdf/vsp_vcc_41_admin_guide.pdf#page=18
o During the conversion process, physical disks are typically resized to conserve space on the datastore
while providing room for growth on the resultant virtual disk. The following formula is used to resize
converted disks: amount of space used on physical disk * 1.25 = resultant virtual disk size. Virtual disks
are set to a size of 4GB or larger.
o Cloning Modes:
Disk-Based Cloning: vCenter Converter supports disk-based cloning for cold cloning and for
importing existing virtual machines. Disk-based cloning transfers all sectors from all disks, and
preserves all volume metadata. The destination virtual machine receives the same volumes of
the same type as the volumes of the source virtual machine. Disk-based cloning supports all
basic and dynamic disks.
Volume-Based Cloning: vCenter Converter supports volume-based cloning for hot and cold
cloning and for importing existing virtual machines. In volume-based cloning, all volumes in the
destination virtual machine are basic volumes, regardless of the type in the corresponding
source volume. Volume-based cloning is performed at the file level or block level, depending on
your size selections. (If size is smaller than original volume, File Level is used. If size is the same
or larger, Block Level is used.)
Page 38 of 85
o One important metric displayed in the Analysis tab is the Confidence metric. During the analysis phase,
performance data about each selected system is collected. This data is used to find a host with
resources that match the collected data to determine a recommendation for each candidate. The
recommendation indicates how well suited, based on the collected data, a candidate is to a particular
virtual machine host system. Confidence refers to the reliability of the recommendation and it is a
function of the duration of the analysis. Recommendations based on longer periods of analysis – and
therefore more performance data – receive a higher level of confidence.
Page 39 of 85
Objective 5.2 – Manage Virtual Machines
Configure/Modify virtual machines
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=142
o You can configure virtual machines using two tools in the vSphere Client: the Virtual Machine Properties
editor and the Add Hardware wizard. These dialog boxes also allow you to control advanced virtual
machine configuration options. You can also upgrade the virtual hardware of a virtual machine or
convert virtual disks from thin to thick using these dialog boxes.
o Add/Hot Add virtual machine hardware
http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=157
1. Right click a VM and select Edit Settings
2. Click the Add button to add additional hardware
It is possible to add / modify certain aspects / remove some types of hardware while the VM is
running. This is called Hot Add. The limitations depend of the type of guest OS you are using.
You can Hot Add the following types of hardware:
USB Controller
Ethernet Adaptor
Hard Disk
SCSI Device
Page 41 of 85
Objective 5.3 – Deploy vApps
Determine whether a vApp is appropriate for a given situation
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=103
o A vApp is a container, like a resource pool, and can contain one or more virtual machines. In addition, a
vApp also shares some functionality with virtual machines. A vApp can power on and power off, and can
also be cloned. vApps can be created on folders, hosts, resource pools, DRS-enabled clusters, and within
other vApps.
o The vApp metadata resides in the vCenter Server's database, so a vApp can be distributed across
multiple ESX/ESXi hosts. This information can be lost if the vCenter Server database is cleared or if a
standalone ESX/ESXi host that contains a vApp is removed from vCenter Server. You should back up
vApps to an OVF package in order to avoid losing any metadata.
Build a vApp
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=104
o Right click on a Cluster and select New vApp
-or- File New vApp
Export vApps
o File Export Export OVF Template
Page 42 of 85
Clone a vApp
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=111
o Right click a vApp and select Clone (the vApp has to be shut down for this option to be selectable)
-or- Inventory vApp Clone
Page 43 of 85
Section 6 – Manage Compliance
Objective 6.1 – Install, Configure and Manage VMware vCenter Update Manager
Determine installation requirements and database sizing
o http://www.vmware.com/pdf/vsp_vum_40_admin_guide.pdf#page=21
o http://www.vmware.com/support/vsphere4/doc/vsp_vum_40_sizing_estimator.xls
Windows XP SP2, Sever 2003 or Server 2008
MS SQL or Oracle (dedicated DB recommended)
Two or more logical cores, each with a speed of 2GHz
2GB RAM. When VUM is installer on the same server as vCenter Server a minimum of 4GB of
RAM is needed.
Preferably a Gigabit connection, but 10/100Mb will suffice
Create baselines
o http://www.vmware.com/pdf/vsp_vum_40_admin_guide.pdf#page=51
o Home Solutions and Applications Update Manager Baselines and Groups tab
o Baselines contain a collection of one or more patches, service packs and bug fixes, or upgrades. Baseline
groups are assembled from existing baselines and might contain one upgrade baseline per type and one
or more patch baselines or a combination of multiple patch baselines. When you scan hosts, virtual
machines, and virtual appliances, you evaluate them against baselines and baseline groups to determine
their level of compliance.
Page 44 of 85
Attach baselines to vCenter inventory objects
o http://www.vmware.com/pdf/vsp_vum_40_admin_guide.pdf#page=61
o Select Object Update Manager tab Click Attach
o Although you can attach baselines and baseline groups to individual objects, it is more efficient to attach
them to container objects, such as folders, hosts, clusters, and datacenters. Attaching a baseline to a
container object transitively attaches the baseline to all objects in the container.
Page 45 of 85
Analyze compliance information from a scan
o http://www.vmware.com/pdf/vsp_vum_40_admin_guide.pdf#page=69
o Update Manager scans objects to determine how they comply with baselines and baseline groups you
attach. You can review compliance by examining results for a single virtual machine, virtual appliance,
template, or ESX/ESXi host or for a group of virtual machines or hosts.
Page 46 of 85
Objective 6.2 – Establish and Apply ESX Host Profiles
Create/Delete Host Profiles (Enterprise Plus license only)
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf#page=207
o Home Management Host Profiles Click Create Profile
o Host profiles eliminates per-host, manual, or UI-based host configuration and maintain configuration
consistency and correctness across the datacenter by using host profile policies. These policies capture
the blueprint of a known, validated reference host configuration and use this to configure networking,
storage, security, and other settings on multiple hosts or clusters. You can then check a host or cluster
against a profile’s configuration for any deviations.
Page 47 of 85
Apply Host Profiles
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf#page=212
o Note: The host must be in maintenance mode before a profile is applied to it.
o Home Inventory Hosts and Clusters Right-click the Host and select Host Profile Apply Profile
o -or- From the Host Profiles list, select the Profile Hosts and Clusters tab Click Apply Profile
Page 48 of 85
Section 7 – Establish Service Levels
Objective 7.1 – Create and Configure VMware Clusters
Create new cluster
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_availability.pdf#page=19
1. Home Inventory Hosts and Clusters
2. Right-click a Datacenter and select New Cluster
3. Complete the New Cluster wizard
o All virtual machines and their configuration files must reside on shared storage. So that you can power
on the virtual machines using different hosts in the cluster, the hosts must be configured to access that
shared storage.
o Each host in a VMware HA cluster must have a host name assigned and a static IP address associated
with each of the virtual NICs. Hosts must be configured to have access to the virtual machine network.
VMware recommends redundant network connections for VMware HA.
For ESX, set up redundant service console networking.
For ESXi, set up redundant VMkernel networking.
Page 49 of 85
Enable/Configure VM Monitoring
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_availability.pdf#page=23
o Right-click a Cluster Select Edit Settings VMware HA Click VM Monitoring
o After failures are detected, VMware HA resets virtual machines. This helps ensure that services remain
available. To avoid resetting virtual machines repeatedly for nontransient errors, by default virtual
machines will be reset only three times during a certain configurable time interval. After virtual
machines have been reset three times, VMware HA makes no further attempts to reset the virtual
machines after any subsequent failures until after the specified time has elapsed. You can configure the
number of resets using the Maximum per-VM resets custom setting.
o Occasionally, virtual machines that are still functioning properly stop sending heartbeats. To avoid
unnecessarily resetting such virtual machines, the VM Monitoring service also monitors a virtual
machine's I/O activity. If no heartbeats are received within the failure interval, the I/O stats interval (a
cluster-level attribute) is checked. The I/O stats interval determines if any disk or network activity has
occurred for the virtual machine during the previous two minutes (120 seconds). If not, the virtual
machine is reset. This default value (120 seconds) can be changed using the advanced attribute
das.iostatsInterval.
o You can configure the level of monitoring sensitivity. Highly sensitive monitoring results in a more rapid
conclusion that a failure has occurred. Low sensitivity monitoring results in longer interruptions in
service between actual failures and virtual machines being reset. Select an option that is an effective
compromise for your needs:
High Failure Interval: 30 seconds Reset Period: 1 hour
Medium Failure Interval: 60 seconds Reset Period: 24 hours
Low Failure Interval: 120 seconds Reset Period: 7 days
Page 50 of 85
o Rules: You can control the placement of virtual machines on hosts within a cluster, by using DRS affinity
and antiaffinity rules. If two rules conflict, the older one will take precedence, and the newer rule is
disabled.
An affinity rule specifies that two or more virtual machines be placed on the same host.
An antiaffinity rule is limited to two virtual machines, and it requires that these two virtual
machines not be placed on the same host.
o Power Management: The VMware Distributed Power Management (DPM) feature allows a DRS cluster
to reduce its power consumption by powering hosts on and off based on cluster resource utilization.
VMware DPM monitors the cumulative demand of all virtual machines in the cluster for memory and
CPU resources and compares this to the total available resource capacity of all hosts in the cluster. If
sufficient excess capacity is found, VMware DPM places one or more hosts in standby mode and powers
them off after migrating their virtual machines to other hosts.
Page 51 of 85
Configure swap file location
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=31
o Right-click a Cluster Select Edit Settings Click Swapfile Location
o By default, the swap file (.vswp) is created in the same location as the virtual machine's configuration
file. A swap file is created by the ESX/ESXi host when a virtual machine is powered on and deleted when
it is powered off. If this file cannot be created, the virtual machine cannot power on.
Store the swapfile in the same directory as the virtual machine: Stores the swapfile in the
same directory as the virtual machine configuration file
Store the swapfile in the datastore specified by the host: Stores the swapfile in the location
specified in the host configuration. If the swapfile cannot be stored on the datastore that the
host specifies, the swapfile is stored in the same folder as the virtual machine.
Page 52 of 85
Analyze HA admission control
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_availability.pdf#page=13
o vCenter Server uses admission control to ensure that sufficient resources are available in a cluster to
provide failover protection and to ensure that virtual machine resource reservations are respected.
o Including VMware HA, there are three types of admission control:
Host: Ensures that a host has sufficient resources to satisfy the reservations of all virtual
machines running on it.
Resource pool: Ensures that a resource pool has sufficient resources to satisfy the reservations,
shares, and limits of all virtual machines associated with it.
VMware HA: Ensures that sufficient resources in the cluster are reserved for virtual machine
recovery in the event of host failure.
o Admission control imposes constraints on resource usage and any action that would violate these
constraints is not permitted. Examples of actions that could be disallowed include:
Powering on a virtual machine.
Migrating a virtual machine onto a host or into a cluster or resource pool.
Increasing the CPU or memory reservation of a virtual machine.
Determine use cases for DRS automation levels and migration thresholds
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=49
Page 53 of 85
Objective 7.2 – Enable a Fault Tolerant Virtual Machine
Identify FT restrictions
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_availability.pdf#page=34
o Snapshots. Snapshots must be removed or committed before Fault Tolerance can be enabled on a
virtual machine. In addition, it is not possible to take snapshots of virtual machines on which Fault
Tolerance is enabled.
o Storage VMotion. You cannot invoke Storage VMotion for virtual machines with Fault Tolerance turned
on. To migrate the storage, you should temporarily turn off Fault Tolerance, and perform the storage
VMotion action. When this is complete, you can turn Fault Tolerance back on.
o DRS features. A fault tolerant virtual machine is automatically configured as DRS-disabled. DRS does
initially place a Secondary VM, however, DRS does not make recommendations or load balance Primary
or Secondary VMs when load balancing the cluster. The Primary and Secondary VMs can be manually
migrated during normal operation.
o Physical Raw Disk mapping (RDM). If you want to use Raw Disk Mapping (RDM) for your virtual disks,
only virtual RDMs are supported.
o vCPU: Only single processor VMs are supported
o Virtual Disks: No thin provisioned disks (auto upgraded to thick disk)
o Physical/Remote Devices: No support for virtual devices backed by a physical or remote device (USB,
Sound, CD-ROM, Floppy, etc.)
Page 54 of 85
Cases where high availability might be provided through custom clustering solutions, which are
too complicated to configure and maintain.
o Another key use case for protecting a virtual machine with Fault Tolerance can be described as On-
Demand Fault Tolerance. In this case, a virtual machine is adequately protected with VMware HA during
normal operation. During certain critical periods, you might want to enhance the protection of the
virtual machine. You can use On-Demand Fault Tolerance to protect the virtual machine during a critical
time period and return the resources to normal during non-critical operation.
Set up an FT network
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_availability.pdf#page=36
o On each host that you intend to add to a VMware HA cluster, you must configure two different
networking switches so that the host can also support VMware Fault Tolerance. Multiple gigabit
Network Interface Cards (NICs) are required. For each host supporting Fault Tolerance, you need a total
of two VMkernel gigabit NICs: one dedicated to Fault Tolerance logging and one dedicated to
VMotion. The VMotion and FT logging NICs must be on different subnets. Additional NICs are
recommended for virtual machine and management network traffic.
1. Select a ESX host
2. Select Configuration tab
3. Select Networking Add Networking
4. Select VMkernel
5. Select Create a Virtual Switch
6. Select Use this port group for VMotion or Use this port group for fault tolerance logging
7. Provide an IP address and Subnet mask
o To enable Fault Tolerance for a host, VMware recommends that you complete this procedure twice,
once for each port group option to ensure that sufficient bandwidth is available for Fault Tolerance
logging.
Test an FT configuration
o There are two built-in methods to test FT. Right-click the VM and choose either:
Test Failover: Primary and Secondary VMs switch roles
Test Restart Secondary: After restarting it, you can check its consistency compared to the
original
Page 56 of 85
Objective 7.3 – Create and Configure Resource Pools
Determine Resource Pool requirements for a given situation
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=35
o Resource pools allow you to delegate control over resources of a host (or a cluster), but the benefits are
evident when you use resource pools to compartmentalize all resources in a cluster. Create multiple
resource pools as direct children of the host or cluster and configure them. You can then delegate
control over the resource pools to other individuals or organizations.
o Using resource pools can result in the following benefits:
Flexible hierarchical organization
Isolation between pools, sharing within pools
Access control and delegation
Separation of resources from hardware
Management of sets of virtual machines running a multitier service
Page 57 of 85
Create Resource Pools
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=37
o File New Resource Pool (or click New Resource Pool in the Commands panel of the Summary tab).
vCenter Server creates the resource pool and displays it in the inventory panel. A yellow
triangle appears if any of the selected values are not legal values because of limitations on total
available CPU and memory.
o Note: If a host has been added to a cluster, you cannot create child resource pools of that host. You can
create child resource pools of the cluster if the cluster is enabled for DRS.
Page 58 of 85
Describe resource pool hierarchy
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=35
o A resource pool can contain child resource pools, virtual machines, or both. You can create a hierarchy
of shared resources. The resource pools at a higher level are called parent resource pools. Resource
pools and virtual machines that are at the same level are called siblings. The cluster itself represents the
root resource pool. If you do not create child resource pools, only the root resource pools exist.
o Each child resource pool owns some of the parent’s resources and can, in turn, have a hierarchy of child
resource pools to represent successively smaller units of computational capability.
Page 59 of 85
Objective 7.4 – Migrate Virtual Machines
Identify compatibility requirements
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=187
o ESX Hosts:
Each host must be correctly licensed for VMotion.
Each host must meet shared storage requirements for VMotion.
Configure hosts for VMotion with shared storage to ensure that virtual machines are
accessible to both source and target hosts.
Each host must meet the networking requirements for VMotion.
VMotion requires a Gigabit Ethernet (GigE) network between all VMotion-enabled
hosts. Each host enabled for VMotion must have a minimum of two Ethernet adapters,
at least one of which must be a GigE adapter.
Note: vCenter's CPU compatibility checks compare the features available on the source and
target host CPUs. A mismatch in user-level features blocks migration.
o Restrictions:
You cannot use migration with VMotion to migrate virtual machines using raw disks for
clustering purposes.
You cannot use migration with VMotion to migrate a virtual machine that uses a virtual device
backed by a device that is not accessible on the destination host.
You cannot use migration with VMotion to migrate a virtual machine that uses a virtual device
backed by a device on the client computer.
Migrations with VMotion are not allowed unless the destination swapfile location is the same as
the source swapfile location. In practice, this means that virtual machine swapfiles must be
located with the virtual machine configuration file.
You cannot migrate a virtual machine with snapshots with Storage VMotion.
Page 60 of 85
o Migration with Storage VMotion: Moving the virtual disks or configuration file of a powered-on virtual
machine to a new datastore. Migration with Storage VMotion allows you to move a virtual machine’s
storage without any interruption in the availability of the virtual machine.
Understand/Apply
o Migration with VMotion allows virtual machine working processes to continue throughout a migration.
The entire state of the virtual machine as well as its configuration file, if necessary, is moved to the new
host, while the associated virtual disk remains in the same location on storage that is shared between
the two hosts. After the virtual machine state is migrated to the alternate host, the virtual machine runs
on the new host.
The state information includes the current memory content and all the information that defines and
identifies the virtual machine. The memory content includes transaction data and whatever bits of the
operating system and applications are in the memory. The defining and identification information
stored in the state includes all the data that maps to the virtual machine hardware elements, such as
BIOS, devices, CPU, MAC addresses for the Ethernet cards, chip set states, registers, and so forth.
When you migrate a virtual machine with VMotion, the new host for the virtual machine must meet
compatibility requirements in order for the migration to proceed.
o Migration with VMotion happens in three stages:
When the migration with VMotion is requested, vCenter Server verifies that the existing virtual
machine is in a stable state with its current host.
The virtual machine state information (memory, registers, and network connections) is copied
to the target host.
The virtual machine resumes its activities on the new host.
o If any error occurs during migration, the virtual machines revert to their original states and locations.
Page 61 of 85
Migrate a virtual machine using VMotion
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=197
1. Right-click a VM
2. Select Migrate
3. Select Change Host
4. Set the Cluster to migrate to
5. Select the appropriate Resource Pool
6. Select the Priority (High Priority migration is the default and is recommended. High Priority reserves the
resources the VM needs on the source and destination hosts before the migration begins)
Page 62 of 85
Objective 7.5 – Backup and Restore Virtual Machines
Describe different back-up/restore procedures and strategies
o File Level
Use traditional backup software running inside a virtual machine. Backups run within a virtual
machine allow for traditional full, incremental, and differential backups.
Use VMware Consolidated Backup (VCB). Provides the same flexibility of running traditional full,
incremental, and differential backups in a Windows virtual machine but avoids the
disadvantages of running a backup agent in the virtual machine.
o Image Level
Use VMware Converter
Use VMware Consolidated Backup (VCB)
Use the VMware Data Recovery appliance
Use a third-party product
Create/Delete/Restore Snapshots
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=203
o Inventory Virtual Machine Snapshot Snapshot Manager
-or- Inventory Virtual Machine Snapshot Take Snapshot
-or- Right-click the virtual machine and select Snapshot Take Snapshot
o Note: While snapshots do provide a "point in time" image of the disk that backup solutions can use,
snapshots should not be used for your own virtual machine backups. Large numbers of snapshots are
difficult to manage and take up large amounts of disk space. Backup solutions, like VMware Data
Recovery, use the snapshot mechanism to "freeze" the state of a virtual machine and make a copy.
However, the Data Recovery backup method has additional capabilities that mitigate the limitations of
snapshots.
Page 63 of 85
Install Backup and Recovery Appliance
o http://www.vmware.com/pdf/vdr_10_admin.pdf#page=11
o VMware Data Recovery uses a plug-in to the VSphere Client and a backup appliance to store backups to
destinations such as hard disks. You can store backups on any virtual disk supported by ESX. You can
use technologies such as storage area networks (SANs) and network attached storage (NAS) devices.
Data Recovery also supports Common Internet File System (CIFS) based storage such as SAMBA.
1. File Deploy OVF Template
2. Select Deploy from File, and then browse to VmwareDataRecovery.ovf
3. Review and accept the OVF details and EULA
4. Select the Location, Host, and Cluster for the appliance
5. Select a Datastore to store the virtual machines files
o The default credentials for logging into the appliance, via the console, are Username: root, Password:
vmw@re. Use the passwd command to change the password for the root account to a strong password
of your choosing.
Page 64 of 85
Section 8 – Perform Basic Troubleshooting and Alarm Management
Objective 8.1 – Perform Basic Troubleshooting for ESX/ESXi Hosts
Understand general ESX Server troubleshooting guidelines
o -
esxcfg-vswitch -l (Provides a list of the current virtual switch configurations. Check that
the uplink adapter configured for the service console is connected to the appropriate
physical network.)
esxcfg-nics -l (Provides a list of the current network adapters. Check that the uplink
adapter configured for the service console is up and that the speed and duplex are both
correct.)
The wrong NIC was chosen for the Service Console during the install
esxcfg-vswitch -L <new vmnic> <service console vswitch> (Changes the uplink for the
service console.)
Routing is not configured
There is no Default Gateway defined for the Service Console Network
The Firewall on ESX does not allow you to connect
Page 65 of 85
Monitor ESX Server system health
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=81
o Hosts and Clusters Choose Host Hardware Status tab
o You can use the vSphere Client to monitor the state of host hardware components, such as CPU
processors, memory, fans, and other components. You can monitor a host’s health status either by
connecting the vSphere Client directly to a host, or by connecting to a vCenter Server system. You can
also set alarms to trigger when the host health status changes.
o When you connect the vSphere Client directly to a host, you can view the health status from the host’s
Configuration tab.
o When you are connected to a host through vCenter Server, you must use the Hardware Status tab
rather than the Configuration tab to monitor the host health.
Understand how to export diagnostic data
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=66
When connected to vCenter:
1. File Export Export System Logs -or- Administration Export System Logs
2. Select the ESX host(s) you would like to export log files from
3. Choose a location to download the logs to
When connect directly to an ESX host:
1. File Export Export System Logs
2. Choose a location to download the logs to
o When you export log file data, the vm-support script creates a file of the selected data and stores it in a
location you specify. The default file type is .txt if no other extension is specified. The file contains Type,
Time, and Description.
Page 66 of 85
Objective 8.2 – Perform Basic Troubleshooting for VMware FT and Third-Party Clusters
Analyze and evaluate VM population for maintenance mode considerations
o Virtual machines cannot run when a host is in maintenance mode. To ensure a consistent user
experience, vCenter Server migrates virtual machines to other ESX/ESXi hosts within a cluster before the
host is put in maintenance mode. All remaining hosts in the cluster must have enough resources
available to handle the increased load.
Page 67 of 85
o Other Fault Tolerance Troubleshooting Issues:
Hardware Virtualization Must Be Enabled
Compatible Secondary Hosts Must Be Available
Secondary VM on Overcommitted Host Degrades Performance of Primary VM
Very Large Virtual Machines Can Prevent Use of Fault Tolerance
Secondary VM CPU Usage Appears Excessive
Page 68 of 85
Objective 8.3 – Perform Basic Troubleshooting for Networking
Verify VM is connected to the correct port group
1. Select the VM
2. Select the Summary tab
3. The associated Port Groups as listed under the Resources section
Page 69 of 85
Objective 8.4 – Perform Basic Troubleshooting for Storage
Identify storage contention issues
o Use the Disk performance graphs (Performance tab) to examine disk usage and potential congestion for
each ESX host.
o Verify that the initiator name is a qualified iSCSI name and matches the storage system setup
o If CHAP is configured, ensure that it is enabled on the ESX/ESXi host and matches the storage system
setup
o Verify that the Dynamic Discovery addresses are correct
o Ensure that the subnet mask and gateway address are set correctly on the iSCSI storage and the iSCSI
initiator in the ESX/ESXi host.
o Ensure that the iSCSI adaptor is enabled and the port (3260) is allowed through the ESX firewall
o The software iSCSI initiator in ESX/ESXi requires that a VMkernel network port have access to the iSCSI
storage. The software initiator uses the VMkernel for data transfer between the ESX/ESXi system and
the iSCSI storage.
Page 70 of 85
Objective 8.5 – Perform Basic Troubleshooting for HA/DRS and VMotion
Explain the requirements of HA/DRS and VMotion
o All Hosts in an HA Cluster must have access to the same shared storage locations used by all virtual
machines on the cluster. This includes any Fibre Channel, iSCSI, and NFS datastores used by virtual
machines.
o All Hosts in a HA cluster should have an identical virtual networking configurations (vSwitches, Port
Groups, etc.). Port Group naming is CASE SENSITIVE -- NAMES MUST BE IDENTICAL ACROSS ALL HOSTS!
o Each Host in a HA cluster must have a host name assigned and a static IP address associated with each of
the virtual NICs. All hosts in an HA cluster must resolve the other hosts using DNS names.
o A Gigabit Ethernet NIC with a VMkernel port defined and enabled for VMotion on each host
o CPUs must be from the same vendor, must be in the same family, and must share a common set of CPU
instruction sets and features.
Per-VM CPU Identification (CPUID) Masking and/or Cluster level EVC can be enabled to help get
around this limitation
You can use VMware’s bootable CPU Identification (CPUID) utility to boot a server and
determine what CPU features it supports
o VMs:
Must not be connected to any physical device (e.g. CD/DVD) or internal-only virtual switch
Must not have its CPU affinity set to a specific CPU
Must not have a physical mode RDM
Page 71 of 85
Verify the service console network functionality
o http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=
1003728
o http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003
486&sliceId=1&docTypeID=DT_KB_1_1&dialogID=52680897&stateId=0%200%2052682475
o Ping each Host, by name, from the vCenter server
o Ping each Host and vCenter from ESX: ping <server>
o Ping each Host and vCenter from ESXi: vmkping <server>
The vmkping command sources a ping from the local VMkernel port
Interpret the DRS Resource Distribution Graph and Target/Current Host Load Deviation
o Select the Cluster Summary tab
Target/Host deviation is located under the section VMware DRS
Target Host Load Standard Deviation: A value derived from the migration threshold
setting that indicates the value under which load imbalance is to be kept.
Current Host Load Standard Deviation: A value indicating the current load imbalance in
the cluster. This value should be less than the target host load standard deviation
unless unapplied DRS recommendations or constraints precluded attaining that level.
Click View Resource Distribution Chart
CPU: If the VM is receiving the resources it’s entitled to, the box is green. If the box is
not green for an extended time, you might want to investigate what is causing this
shortfall.
Memory: The virtual machine boxes are not color-coded, because the relationship
between consumed memory and entitlement is often not easily categorized.
Page 72 of 85
Troubleshoot HA redundancy issues
o For redundancy, you should have 2 or more NICs attached to your VMotion network. Each NIC should
be connected to a separate physical switch.
o Select an ESX host Select the Configuration tab Networking
Verify the status of each NIC on your VMotion port group
Page 73 of 85
Objective 8.6 – Create and Respond to vCenter Connectivity Alarms
List vCenter default connectivity alarms
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=263
o Cannot Connect to Network: Monitors network connectivity on a vSwitch.
o Cannot Connect to Storage: Monitors host connectivity to a storage device.
o Host Connection and Power State: Monitors host connection and power state.
o Host Connection Failure: Monitors host connection failures.
o Host Connection State: Monitors host connection state.
o Host Storage Status: Monitors host connectivity to storage devices.
vSphere Update 1 added the following:
Network Connectivity Lost (replaces “Cannot Connect to Network”): Monitors network connectivity on
a vSwitch.
Network uplink redundancy degraded: Monitors network uplink redundancy degradation on a
virtual switch.
Network uplink redundancy lost: Monitors loss of network uplink redundancy on a virtual
switch
For a given alarm, analyze and evaluate the affected virtual infrastructure components
o Using vCenter, you can evaluate the status of and troubleshoot all components
Page 74 of 85
Create a vCenter connectivity alarm
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=252
o You create an alarm by using the Alarm Settings dialog box. You can open this dialog box by selecting
the object in the inventory and using any of the following methods:
Select File New Alarm
Select Inventory <object_type> Alarm Add Alarm
Right-click the object and select Alarm Add Alarm
Select the Alarms tab Click the Definitions button Right-click in the pane, and select New
Alarm
Select the object in the inventory and press Ctrl+A
o Note: After an alarm is created, it will be enabled even if the user who created it no longer has
permissions.
Page 75 of 85
Objective 8.7 – Create and Respond to vCenter Utilization Alarms
List vCenter default utilization alarms
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=263
o Datastore Usage on Disk: Monitors datastore disk usage.
o Host CPU Usage: Monitors host CPU usage.
o Host Memory Usage: Monitors host memory usage.
o Virtual Machine CPU Usage: Monitors virtual machine CPU usage.
o Virtual Machine Memory Usage: Monitors virtual machine memory usage.
Page 76 of 85
For a given alarm, analyze and evaluate the affected virtual infrastructure resource
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=258
1. Select the Object
2. Click the Performance tab
3. If advanced graphing is required, click Advanced
a. Select the appropriate item from the Switch To dropdown box
b. If needed, click Chart Options to modify the selected graph
o http://communities.vmware.com/docs/DOC-9279
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_resource_mgmt.pdf#page=79
ESX: esxtop -a -b <filename>
ESX or ESXi: resxtop --server <host name or IP>
Page 77 of 85
Objective 8.8 – Monitor vSphere ESX/ESXi and Virtual Machine Performance
Identify critical performance metrics (e.g., CPU ready, queue depth, etc.)
o http://communities.vmware.com/docs/DOC-9279
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=277
o CPU Usage, CPU Ready
o Memory Usage, Memory Balloon, Memory Active, Memory Swap In Rate, Memory Swap Out Rate
o Disk Usage, Disk Read Rate, Disk Write Rate
o Network Usage, DroppedTx, DroppedRx
o VMware Tools includes a library of functions called Perform DLL. This DLL allows you to access key host
statistics inside a guest VM. You access these functions via the Windows Performance Monitor or WMI.
Page 78 of 85
If multiple VMs are being constrained by memory, then not only will you see high ballooning
activity and the guest OS paging, you will also see the VM itself being swapped in and out by the
VMkernel.
o Memory Active: Amount of memory actively used, as estimated by VMkernel. Active memory is based
on the current workload of the virtual machine or host.
If amount of active memory is continuously high, this could lead to VMs that are memory-
constrained.
If CPU utilization is continuously high, then the VM is constrained by CPU. However, the
host might have enough CPU for other VMs to run.
Multiple VMs are constrained by CPU if there is high CPU utilization in the guest OS and
there are relatively high CPU ready values for the VMs.
Host: Actively used CPU of the host, as a percentage of the total available CPU. Active CPU is
approximately equal to the ratio of the used CPU to the available CPU.
available CPU = # of physical CPUs × clock rate
100% represents all CPUs on the host. For example, if a four-CPU host is running a virtual
machine with two CPUs, and the usage is 50%, the host is using two CPUs completely.
o It is a good idea to periodically monitor the CPU usage of the host. This can be done through the
vSphere Client or by using esxtop or resxtop. Below we describe how to interpret esxtop data:
If the load average on the first line of the esxtop CPU Panel is equal to the number of physical
processors in the system, this indicates that the system is overloaded.
The usage percentage for the physical CPUs on the PCPU line can be another indication of a
possibly overloaded condition. In general, 80% usage is a reasonable ceiling and 90% should be
a warning that the CPUs are approaching an overloaded condition. However, organizations will
have varying standards regarding the desired load percentage.
Page 79 of 85
Explain network metrics (usage, packet drops, etc.)
o http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf#page=348
o Network Usage: Sum of the data transmitted and received during the collection interval.
o DroppedRx: Number of receive packets dropped during the collection interval.
o DroppedTx: Number of transmit packets dropped during the collection interval.
Dropped network packets indicate a bottleneck in the network.
Page 80 of 85
o Advanced performance charts enable you to see data point information for a plotted metric, export
chart data to a spreadsheet, and save chart data to a file. You can customize the advanced chart views.
Note: You cannot view datastore metrics in the advanced charts. They are only available in the overview
charts.
You can view CPU, memory, disk, and network statistics for an object in the advanced
performance charts. These charts support additional data counters not supported in the
overview performance charts.
Page 81 of 85
Appendix A – Configuration Maximums
http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf
vSwitch
Virtual network switch ports per host (vDS and vSS ports): 4096
Port groups per standard switch: 512
Virtual network switch ports per standard switch: 4088
Standard switches per host: 248
Distributed Switch
Virtual network switch ports per host (vDS and vSS ports): 4096
Distributed port groups per vCenter: 512
Distributed virtual network switch ports per vCenter: 6000
Distributed switches per vCenter: 16
Hosts per distributed switch: 64
Virtual Machines
Page 82 of 85
vCenter
Hosts (32‐bit OS server): 200
Powered‐on virtual machines (32‐bit OS server): 2000
Registered virtual machines (32‐bit OS server): 3000
Concurrent vSphere client connections (32‐bit OS server): 15
ESX
Volume size: 64TB minus 16K
Extents size: 2TB minus 512B
Extents per volume: 32
Volumes per host: 256
Virtual machines per volume: 256
LUN ID: 255
HBAs per host: 8
Targets per HBA: 256
Logical processors per host: 64
Virtual CPUs per host: 512
Virtual CPUs per physical core: 20 (25 in vSphere U1)
Size of RAM per host: 1TB
RAM allocated to service console: 800MB (300MB min)
Page 83 of 85
Appendix B – CLI
Change Service Console NIC: esxcfg-vswitch -L <new vmnic> <service console vswitch>
Page 84 of 85
Appendix C – Sources
http://www.vmware.com
http://www.b3rg.nl/vcp-4.0.html
http://www.simonlong.co.uk/blog/vcp-vsphere-upgrade-study-notes/
Page 85 of 85