Escolar Documentos
Profissional Documentos
Cultura Documentos
o
)
o o o o o o
!~
o
.J
)
vmware
c
(J
CopyrlghtfTrademark
Copyright 2010 VMware, Inc. Ali rights reserved. This manu al and its accompanying materials are protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at htlp://www.vmware.com/go/ patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. Ali other marks and names mentioned herein may be trademarks of their respective companies. The training mate rial is provided "as is," and ail express or implied conditions, representations, and warranties, including any implied warranty of merchantability, fitness for a particular purpose or noninfringement, are disclaimed, even if VMware , Inc., has been advised of the possibility of such claims. This training mate rial is designed to support an instructor-Ied training course and is intended to be used for reference purposes in conjunction with the instruetor-Ied training course. The training material is not a standalone training tool. Use of the training material for self-study without class atlendance is not recommended. These mate rials and the computer programs to which it relates are the property of, and embody trade secrets and confidential information proprietary to, VMware, Ine. , and may not be reproduced, copied , disclosed, transferred, adapted or modified without the express writlen approval of VMware, Inc. education@vmware.com
c
c
c
c c c c
o o o o o o o o
()
1 AI:::SLt::
ut-
vUN 1 t::NTS
()
Lab 1: Configuring VMware ESXi .................... . ..................... . ... 1 Lab 2: Installing VMware vCenter Server ........ . ...... . . . .................. . . . .. 7 Lab3: UsingVMwarevCenterServer ... . ... . ... . ..... . . . . . . . .. . .. . ... . . . .. .... 15 Lab 4: Standard Virtual Switches . . ................... . .................... .. .. 23 Lab 5: (Optional) Designing a Network Configuration ...... . ..................... . .. 27 Lab 6: Accessing IP Storage .. .. ... " ........................................... 31 Lab 7: Managing VMware vStorage VMFS Datastores ...... . .................... .. . .37 Lab 8: Working with Virtual Machines .............. . .. . .................. . .. . . .43 Lab 9: Using Templates and Clones .................. .... . . .............. . ..... 55 Lab 10: VMware vCenter Converter ......... . . . ...... ... ............ . .... . .. . . .63 Lab 11: Modifying a Virtual Machine . .... . ............ . ..................... . .. 73 Lab 12: Managing Virtual Machines ............ . ... ... ... . . . .. . .. . . . .... . ... ... 79 Lab 13: Access Control ............................ ... . . ................ . ... 87 Lab 14: Resource Pools .. . .. .. .............................................. 95 Lab 15: Monitoring Virtual Machine Performance ........ ... . . ..................... 99 Lab 16: Using Alarms ....... . ............................................. 103 Lab 17: VMware Data Recovery .................... .. ................... . .. . . 109 Lab 18: Working with Host Profiles ......................................... . .. 115 Lab 19: vNetwork Distributed Switches ................ . ........................ 121 Lab 20: Migrating Virtual Machines ..... . . . ... . ...... . . .. ................. ... . 127 Lab 21: VMware Distributed Resource Scheduler .... . .... . ................... . . .. . 133 Lab 22: VMware Distributed Power Management ............................... . .. 141 Lab 23: Using VMware High Availability ............. .. .. . ................ . . ... 147 Lab 24: Working with Slot Sizes and Admission Control. .... .. ...................... 151 Lab 25: (Optional) Configuring VMware High Availability Network Redundancy ........... 159 Lab 26: Configuring VMware Fault Tolerance ......... . . . .. . ............... . . .. .. 165 Lab 27: VMware vCenter Update Manager ...................................... 169
o o o
) VMware vSphere 4.1: Install, Configure, Manage
o o o o
o
"--J
n
c
c c
Il
VMware vSphere 4.1: Install, Configure, Manage
()
o o
(~
Lab 1
o o o o o o
c)
()
'0
" U
Your student virtual machine name NTP server Domainname Preferred DNS server
)
)
Lab 1
Configuring VMware ESXi
o o o o o o o c
c c
3. Enter the host name ofyour ESXi host, which you recorded in "Preparing for the lab." 4. Type the user name root and enter the ESXi host root password that you recorded in "Preparing for the lab." Click Login. 5. Select the check box Install this certificate and do not display any security warnings for "<host_name>" and click Ignore to proceed.
Secutlty
Wiltllllly '.
c
c c
2
Lab 1 Configuring VMware ESXi
o o o o o o o o o o o o o o o
J
6. If a VMware Evaluation Notice window appears stating when your evaluation license will expire, click OK. The vSphere Client Home page is displayed.
7. Click the Inventory icon. 8. Expand your ESXi host in the inventory. Verify that there is a student virtual machine for you in the inventory. You recorded its name in "Preparing for the lab." In the screenshot, two student virtual machines are present on the ESXi host sc-rat06.vmeduc.com: one for you and one for your partner, who shares an ESXi host with you.
ah
VM-for-StudentB
When you are connected to a host through VMware vCenter Server, you use the Hardware Status tab to monitor the host health. 2. In the Hardware list, select Processors. View the processor mode!, processor speed, and other information about your ESXi host processors.
Lab 1
3. In the Hardware list, select Memory. View the total physical memory and how much memory is used by the system and by the virtual machines.
o o o o c o
c
c c
(~
Field/setting
Domain
Value
Verify that the domain name matches the value that you recorded in "Preparing for the lab." If the domain name does not match, enter the domain name that you recorded in "Preparing for the lab."
c
c c
4
Lab 1 Configuring VMware ESXi
o o o o o o o o o o o o o
)
)
Field/setting
Use the following DNS server address
Value
Enter the preferred DNS and altemate DNS server address information that you recorded in "Preparing for the lab." Click the Routing tab. Verify that the IP address for the VMkemel default gateway matches the value that you recorded in "Preparing for the lab." If the default gateway is not defined, enter the IP address that you recorded in "Preparing for the lab."
Default Gateway
5. Verify that the DNS and Routing pane lists the information that you added.
Field/setting
General NTP Settings
Value
Accept the default and select NTP Settings. Click Add. In the Add NTP Server dialog box, enter the NTP server name that you recorded in "Preparing for the lab." Select the check box and click OK.
5. Click OK to exit the Time Configuration dialog box. 6. Verify that the Time Configuration pane lists the NTP server that you added. 7. In the vSphere Client menu bar, select File> Exit to close the vSphere Client. Both student A and student B should do this step.
()
o o o o o o c
o
c c c
6
Lab 1 Configuring VMware ESXi
c c
o o o o o o o o o o o o o o o
)
Lab2
Lab 2
Your default database UNC user name UNC user password Location of vCenter Server installation software
o o o
o
o o
o
ide"i
For the rest of the lab, you will work together as a team that consists of student A and student B. Student A and student B will altemate to do the remaining tasks. Read the instructions carefully to determine which team member does the task.
1. From your vCenter Server system desktop, select Start > Programs > Administrative Tools > Data Sources (ODBC). 2. Click the System DSN tab and click Add. 3. Select the SQL Native Client driver. 4. Click Finish.
o o o o o o c
c c
Lab 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
)
5. When prompted by the Create a New Data Source to SQL Server wizard, enter the following values.
Field/setting
Name
Value
Enter the ODBC DSN that you recorded in "Preparing for the lab." Type vCenter Server Database. Enter the host name of the SQL Server to connect to that you recorded in "Preparing for the lab." Ifyou see more than one SQL server in the list, make sure that you enter the correct SQL server name.
Description Server
Enter the name that you recorded in "Preparing for the lab." The UNC user account you logged in with appears in the Login ID field.
Connect to SQL Server to obtain default settings for the additional configuration options Change the default database to
Select the check box and set the default database to the value that you recorded in "Preparing for the lab." Make sure that you select your assigned database (and not the mas ter database, for example).
6. Click Test Data Source. If the test does not complete successfully, back up in the ODBC wizard and verify the information that you entered.
7. Click OK to retum to the ODBC Microsoft SQL Server Setup dialog box.
Lab2
8. Click OK to retum to the ODBC Data Source Administrator dialog box. Verify that your new data source appears in the list of system DSNs. 9. Click OK to close the ODBC Data Source Administrator dialog box.
o o o o o o o o
o
ExPlore media
Utlllty
Agent prc-upO@de Cbad<
3. Click the vCenter Server link. 4. When prompted by the installation wizard, enter the following values. Field/setting Choose Setup Language Value Select the setup language that you recorded in "Preparing for the lab" and click OK. Click Next.
Lab 2 Installing VMware vCenter Server
c c c
c
Welcome Page 10
o o o o o o o o o o o o o o o o
Field/setting
End-User Patent Agreement License Agreement
Value
Click Next. Select 1 agree to the terms in the Iicense agreement and click Next. Type VMware s tudent. Type VMware. Click Next. Leave blank (you will install the license key in lab 3) and click Next. Ifyou did not do task 2, select Install a Microsoft SQL Server 2005 Express instance and click Next. Ifyou did task 2, select Use an existing supported database, select the DSN created in task 2, and click Next. In the second Database Options dialog box, type Administrator in Database Username. In Database Password, enter the Administrator password that you recorded in "Preparing for the lab" and click Next. If a warning appears about reinitializing the database, select Replace my existing data base with an empty one. Ifyou are installing vCenter Server for the first time, you will not see this warning.
Database Options
vCenter Server Service Destination Folder vCenter Server Linked Mode Options Configure Ports vCenter Server JVM Memory Ready to Install the Program
Lab 2
Select Use SYSTEM Account and click Next. Accept the default and click Next. Accept the default and click Next.
Accept the defaults and click Next. Accept the default and click Next.
Click Install.
11
o o o
1. Go to the location of the vCenter Server installation software, which you recorded in "Preparing for the lab."
2. Start the VMware vCenter Installer. Ifyou are not sure how to do this, see task 3, step 2.
3. In the VMware vCenter Installer window, click vSphere Client to start the installation wizard.
4 . When prompted by the installation wizard, enter the following values.
o o o
o
Field/setting
Setup Language
Value
Select the setup language that you recorded in "Preparing for the lab" and click OK. Click Next. Click Next. Select 1 agree to the terms in the Iicense agreement and click Next. Type VMware s tuden t . Type VMware. Click Next. Accept the default and click Next. Click Install.
User Name Organization Destination Folder Ready to Install the Pro gram
o o o o o
o c
5. When the installation is complete, click Finish. 6. Close the VMware vCenter Installer window.
c
Lab 2 Installing VMware vCenter Server
12
o o o o o o o o o o o o o o o
C)
7. Log in to the vCenter Server with the vSphere Client. a. Double-click the vSphere Client icon on your vCenter Server system.
b. In the vSphere Client login dialog box, enter your vCenter Server system IF address or host name in IP addresslName and select the Use Windows session credentials check box. c. Click Login. d. Select Install this certificate and do not display any security warnings for "<host_name>" to prevent this warning from being displayed in the future. e. Click Ignore to proceed with the connection.
f. Click OK when the VMware Evaluation Notice window appears, warning that your
evaluation license expires within 60 days. 8. Verify that the Hosts and Clusters inventory view is displayed. 9. In the vSphere Client menu bar, select File> Exit to close the vSphere Client. 10. Log out of the vCenter Server system.
Lab 2
13
o o o o o o o
c
c
o
c
c
c c
14
Lab 2
Installing VMware vCenter Server
o o o
() Lab 3
o o o o o o o o o o o
)
15
Task 1: Log in to the vCenter Server system from your desktop virtual machine
In this task, you will log in to your desktop virtual machine and you will use the VMware vSphere Client to log in to your vCenter Server system. Students assigned to a single ESXi host should do the steps in this task individually. 1. Ask your instructor how to access your desktop virtual machine, whose name you recorded in "Preparing for the lab." For example, your instructor might have you use Remote Desktop Connection to access your desktop virtual machine. 2. Log in to your desktop virtual machine with the domain administrator user name and password that you recorded in "Preparing for the lab." 3. Using the vSphere Client, log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 4. Go to Home> Inventory > Hosts and Clusters.
@ ve-GOOSfOb - v~phere ClIent
o o o
o
1>
ms
o o o o o
o c o
Idelii
For the rest of the lab, you will work together as a team that consists ofstudent A and student B. Student A and student B will altemate to do the remaining tasks. Read the instructions carefully to determine which team member does the task.
16
Lab 3
()
o
()
o o
o
o o o o o o
()
Field/setting
Host
Value
Enter the fully qualified domain name (FQDN) ofyour ESXi host, which you recorded in "Preparing for the lab."
M".. tU'
Use the FQDN, not the short name or the IP address, to identify your ESXi host. Failure to use the FQDN will cause problems in future labs. Username Password Typeroot. Enter the ESXi host root password that you recorded in "Preparing for the lab." When you click Next, a security alert appears stating that vCenter Server is unable to verify the authenticity ofthe specified host. Click Yes to proceed. Host Summary Verify the information and click Next.
o
)
)
Lab 3
17
Field/setting
Assign License
Value
Select Evaluation Mode (No License Key) and click Next. You will add licenses later on in the labo Do not enable lockdown mode. Click Next. Select your Training datacenter and click Next. Review the configuration summary and click Finish.
()
o
Cl
3. In the Recent Tasks pane at the bottom of the vSphere Client, monitor the progress of the task. After the task is finished, expand the Lab Servers folder and verify that your ESXi host appears in the inventory. 4. Select your ESXi host in the inventory and click the Summary tab. View information about the ESXi host, such as its datastores, networks, number ofNICs and CPUs, and memory usage. 5. Click the Hardware Status tab and view the status ofyour ESXi host's hardware.
o o o
o
c c o o c
C
18
o o o o o o o o o o o o o o o
6. How does the list ofinventory objects differ between the Hosts and Clusters view and the VMs and Templates view?
7. Select your student virtual machine, whose name you recorded in "Preparing for the lab." Drag it to your TemporaryVMs folder. 8. Select your team member's student virtual machine, whose name your team member recorded in "Preparing for the lab." Drag it to your TemporaryVMs folder.
id"i
Ifyou are working alone and there is another virtual machine on your ESXi host that is not being used by another student, drag it to your Temporary VMs folder. Remain logged in to your desktop virtual machine and leave the vSphere Client open.
1
_
t1 B
Il
~ Qj
V~~i. Ymtkic.
I~ ~&
_
~ I !nventory
1 6ft
B.oles aessions
ljI
fr
qtl
~;
Server set\:ings
2. In the Product list, exp and Evaluation Mode and expand No License Key. Your ESXi host and your vCenter Server system are in the list. 3. Click the Manage vSphere Licenses link in the upper-right corner. 4. When prompted by the Manage vSphere Licenses wizard, enter the following values.
Lab 3
19
Field/setting
Add Lieense Keys
Value
ln Enter new vSphere lieense keys (one per line), enter the vCenter Server license key and the vSphere Enterprise license key. You recorded these keys in "Preparing for the lab."
l1li
Include the hyphens: XXXXX-XXXXX-XXXXX-XXXXXXXXXX. (The text box forces you to enter a hyphen every five characters.) ln Enter optionallabel for new lie en se keys, type VMware Training Licenses and click Add Lieense Keys. Click Next. Assign Lieenses ln the ESX tab, your ESXi host is an unlicensed asset. The Product colurnn on the right shows that your ESXi host has no license key. Assign the license to your host by clicking the 25character vSphere 4 Enterprise Plus license key. Click the vCenter Server tab. ln the vCenter Server tab, your vCenter Server system is an unlicensed asset. The Product column on the right shows that your vCenter Server system has no license key. Assign the license to your host by clicking the 25-character vCenter Server 4 Standard license key. Click Next. Remove Lieense Keys Confirm Changes Click Next. Click Finish.
o c
Cl
c
c
c c
20
o o o o o o o o
o
s,_
Oln5t:5'lCes
iii
50CPUs 50 CPUs
Remain logged in to your desktop virtual machine and leave the vSphere Client open for the nextlab.
o o o o o
()
)
Lab 3
21
o o
o
o o o o
o
o o
c
22
Lab 3
Using VMware vCenter Server
o o o
()
Lab4
o
()
o o o o o o o o o
1. View the current standard virtual switch configuration. 2. Create a standard virtual switch. 3. Verify that your virtual machine has proper access to the Production network.
Lab 4
23
1. If the vSphere Client is not already active, use it to log in to your VMware vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters. 3. In the VMware vCenter Server inventory, select your VMware ESXi host and click the Configuration tab. 4. In the Hardware list, select Networking. You see that a standard virtual switch was created when this host was installed. The virtual switch is named vSwitchO. It contains a VMkernel port named Management Network and a virtual machine port group named VM Network. You have one or more virtual machines connected to VM Network.
o o o o o o
o
1. Click the Add Networking link. 2. When prompted by the Add Networking wizard, enter the following values.
c
o
Field/setting
Connection Type Network Access
Value
Keep the default. Select Create a virtual switch. Select the check box for the vmnic for the Production network, which you recorded in "Preparing for the lab." Click Next.
Connection Settings
In Network Label, type Production. Keep the default for the VLAN ID. Click Next.
c
c
Ready to Complete
Click Finish.
3. Verify that the virtual switch for the Production network appears in the Networking pane.
24
Lab 4
o o o
()
Task 3: Verify that your virtual machine has proper access to the Production network
In this task, you will verify that your virtual machine can access the Web over the Production network. Students should do the steps in this task individually. 1. Go to Home> Inventory > Networking. 2. Expand the Networking inventory view. 3. Put your virtual machine on the Production network: a . Select VM Network and click the Virtual Machines tab. The virtual machine that you recorded in "Preparing for the lab" appears. b. Select your virtual machine and drag it to the Production virtual switch. 4. Select Production in the inventory and click the Virtual Machines tab. 5. Open a console to the virtual machine. Right-click your virtual machine and select Open Console.
o o o o o o
()
idili
Depending on how your virtual machine is configured, you might have to wait for system customizations to finish before the virtual machine can fmish booting. 6. Verify that your virtual machine can access the Web: a. In Internet Explorer, go to http://www.vmware.com. b. Verify that you can access the Web site. Ifyou are unable to access the Web site, you might have to renew the virtual machine IP address. Do one of the following actions: Reboot the virtual machine. Log in to the guest operating system and open a Command Prompt window (Start > Run). Type cmd. At the command prompt, type ipconfiq Irelease and then type ipconfiq Irenew. c. Exit Internet Explorer.
o o o o
d. Close the virtual machine's console. Remain logged in to your desktop system and leave the vSphere Client open for lab 6.
Lab 4
25
(J
l
o
(J
o c c
c: c
26
Lab 4
Standard Virtual Switches
o o o o o o o o o o o o
()
Lab5
o o o
.U.ili
This lab can be done separately by each member in the ESXi team.
Lab 5 (Optional) Designing a Network Configuration
27
(J
Component
Networking requirements Web-based applications implemented by using four virtual machines arranged as foIlows :
o c
c
VMI and VM2: Web servers, and NAT clients ofVM3 VM3: front end for the Web servers. Acts as a NAT router for the back-end virtual machines VM4: a test box, used to test intrusion detection systems and virus-protection software, among other applications
o o
CJ
IP-based storage
ANAS, used to hold running virtual machines for the test virtual machines only (storage for the production virtual machines is provided by a SAN) Four physical network adapters: one lOOMbps and three GigE cards Two physical switches and four external LANs, each named to indicate its purpose. A single physical switch is configured to handle traffic for three networks, which are implemented as VLANs. One physical switch is dedicated to the management LAN, which, by company policy, must be physicaIly separate from aIl other networks. The management LAN is used by VMware vCenter Server.
Physical NICs
External networks
c
C~
c
28
Lab 5 (Optional) Designing a Network Configuration
o o o o o o o o o o o o o o o o
There is no single correct answer. In fact, there are many reasonable solutions. The point ofthis lab is not to come up with the one "right" answer. Rather, this lab encourages a discussion of the advantages and disadvantages of different solutions.
.. ' _____ .... _____ _... _______ ... ... - ____ _.... f<"~~J<-,....~., . - ____ " "" ..... ___ .. " __
\,J ,,\.. ""
~ ""
ri ~-.-
<"0
~).",-
T ..s v, ,'4.)
virtual machines
VM
VM
VMkernel
100
Mbps
,- 1
Lab 5
29
CJ
o o
o
o
o
o
o o
c
c
c c
30
Lab 5
o o o o o o o o o o o o o o o
o
Lab6
Accessing IP Storage
Objective: Configure access to an iSCSI and NFS datastore
In this lab, you will perfonn the following tasks:
1. Create a VMkemel port on a standard virtual switch. 2. Configure the iSCSI software adapter. 3. Configure access to an NFS datastore. 4. View iSCSI and NFS storage infonnation.
o
o o
o
o
o
Value
Select VMkernel. Type IP Storage. Leave the default. Leave deselected. Leave deselected.
Field/setting
Connection Types Network Label VLAN ID (Optional) Use this port group for vMotion Use this port group for Fault Tolerance logging Use this port group for management trame Use the following IP settings
o o
o
o o
Leave deselected.
Leave selected.
o o o
Lab 6 Accessing IP Storage
32
o o o o o o o o o o o o o o o o
Field/setting
IP Address
Value
Enter the VMkernel port's IP address, which you recorded in "Preparing for the lab." Enter the VMkernel port's subnet mask, which you recorded in "Preparing for the lab." Verify that the correct VMkernel gateway address is entered and click Next. If the VMkernel gateway address is incorrect, click Edit and enter the VMkernel default gateway address that you recorded in "Preparing for the lab."
SubnetMask
Summary
Click Finish.
8. After the VMkernel port is created, click Close to dismiss the vSwitch Properties dialog box. 9. Verify that the VMkernel port named IP Storage appears in the Networking pane.
33
8. Select the Enabled check box and click OK. 9. Monitor task completion in the Recent Tasks pane at the bottom of the VMware vSphere Client. Wait for the task to complete. 10. Verify that the General tab displays the iSCSI initiator name and a status ofEnabled. Leave the Properties dialog box open. 11. Click the Dynamic Discovery tab and click Add. 12. Enter the name of the iSCSI target that you recorded in "Preparing for the lab." 13. Leave the port set to 3260 and click OK. 14. Monitor the Recent Tasks pane and wait for the task to complete. 15. Verify that the iSCSI target's name and port number are listed in the Send Targets panel and click Close. 16. When you are prompted to rescan the ho st bus adapter, click Yeso Wait for the rescan task to complete. 17. Select the iSCSI software adapter from the Storage Adapters list and view the Details pane. Record the values for the following fields to verify that a logical unit number was found.
o
(J
o o
Field/setting
Connected target Deviees Paths
I
0
Value
A
0"-
f.-~,x. (~~~s:~
dD"'C
e~ >)r.,.\NG}~iv:,~
In this task, you will create an NFS datastore. Students assigned to a single ESXi host should work together to complete this task. Student A should do the steps in this task. 1. Click the Configuration tab ofyour ESXi host. 2. In the Hardware list, select Storage. 3. In the Datastores list, select Add Storage. 4. When prompted by the Add Storage wizard, enter the following values.
c c
c
34
o o o o o o o o o o o o o o o
)
Field/setting
Storage Type
Value
Select Network File System and click Next. Enter the NFS server host name or IP address that you recorded in "Preparing for the lab." Enter the NFS share name that you recorded in "Preparing for the lab." Select the check box. Type nfs_library and click Next. Click Finish.
Server
Folder
co ... ..,.J:.c-)
2. In the list of reports, select Show ail SCSI :eattls: Verify that the iSCSI adapter that you added earlier appears in the list. You might have to click the Update link in the upper-right corner.
Show ail SCSI Paths ...
Show ail Virtual Machines show ail Datastores Show ail SCSI Volumes (lUNs) Show ail SCSI Paths Show ail SCSI Adapters Show ail SCSI Targets (Array Ports) Show ail NAS Mounts
35
3. Select Show ail SCSI Targets (Array Ports) from the list of reports. View information about your iSCSI storage. 4. Select Show ail NAS Mounts from the list of reports. View information about your NFS storage. 5. View the contents of the NFS datastore: a . Click the Configuration tab ofyour ESXi host. b. Right-click the NFS datastore and select Browse Datastore. c. Click the / folder in the upper-left pane. You should see several files and directories, including ISO images for use in future labs. d. Close the Datastore Browser. Remain logged in to your desktop virtual machine and leave the vSphere Client open for the next labo
o
(J
o o c c c
c
c
c c
(.J
36 Lab 6 Accessing IP Storage
o o o o o o o o o o o o
()
Lab 7
o o
37
Student A LUN ID Student B LUN ID Learn from your instructor which logical unit numbers (LUNs) contain VMware vStorage VMFS volumes that should not be removed or reformatted. Record the LUNs or VMFS volumes that should not be touched:
M,.. tUi
These LUNs are accessible by aIl VMware ESXi hosts and should not be touched unless you are instructed to.
c
)
c c
1. In the View list of the Storage Views tab, select Show ail Datastores. View the information for each datastore, such as the capacity and free space. 2. Click datastore 1 to go to the Datastores inventory view. The Show aIl Virtual Machines report is displayed. It lists aIl virtual machines that reside on this datastore.
c
l
c
38
Lab 7 Managing VMware vStorage VMFS Datastores
o o o
o
1. In the inventory, right-click datastore 1 and select Rename. 2. Type Local-##, where ## is the number ofyour ESXi ho st. For example, for an ESXi host that ends in 06, the name of the datastore is Local-06. 3. Verify that the new datastore name appears in the inventory.
o o
o
Field/setting
Select host
Value
Expand the inventory hierarchy and click your ESXi host. Click Next. Select DisklLUN and click Next. Click your assigned LUN ID, which you recorded in "Preparing for the lab," and click Next. Review the CUITent disk layout and click Next. Type Private-##, where ## is the number of the LUN ID that you recorded in "Preparing for the lab." For example, for a LUN ID of2l, the VMFS datastore name is Private-21. Click Next.
o o
o
o
o o o o
Maximum me size
Lab 7
39
Field/setting
Capacity
Value
Deselect the Maximum Capacity check box and reduce the LUN size by a half. For example, if the current disk size is 10GB, change the size to 5GB. (You will increase this VMFS datastore to its maximum size in the next task.) Click Next.
o o
Ready to Complete
Click Finish.
3. Monitor the progress in the Recent Tasks pane and wait for the task to complete. 4. Verify that yOuf new VMFS datastore appears in the datastore inventory. 5. Select yOuf Private-## datastore in the inventory. 6. Click the Summary tab and record the value for Capacity: ~ 1 4- S
o o o o o
o
1. Click the Configuration tab. Your ESXi host is displayed and selected. 2. Click the Properties link in the Datastore Details pane. 3. In the Properties dialog box, click Increase. 4. When prompted by the Increase Datastore Capacity wizard, enter the following values.
Field/setting
Extent Deviee
Value
Select your assigned LUN ID that you recorded in "Preparing for the lab." This LUN should read Yes in the Expandable colurnn. Click Next.
Review the current disk layout. Notice the free space available on the LUN (under Prirnary Partitions) and click Next.
Lab 7 Managing VMware vStorage VMFS Datastores
40
o o o o o o o o o o o o o o o
()
Fleld/setting
Value
Capacity
Leave the Maximize capa city check box selected and click Next. Review the information for accuracy and click Finish.
Ready to Complete
5. After the task is complete, verify that the datastore size was increased to the maximum capacity ) / 1- S &6 . (Jess space for system overhead). 6. Click Close to dismiss the datastore Properties dialog box.
Lab 7
41
Field/setting
Value
Extent Device
Select the LUN ID that is assigned to yoUf lab partner, which was recorded in "Preparing for the lab." Review the current disk layout. Leave the Maximize capacity check box selected. Click Finish.
Ready to Complete
7. When the task completes, verify that two extents are displayed in the Extents pane. If necessary, click Refresh in the Properties dialog box. 8. Close the Properties dialog box. 9. In the Datastore Details pane, record the new value for Total Formatted Capacity: 1 (Cr6 . It should differ from the value recorded in step 4.
o o o o o o
o o o
0 0
:1.'
10. Remove this VMFS datastore: a. Right-click yOUf Private-## datastore and select Delete. b. Click Yes to confirm datastore deletion. c. Verify that the datas tore was removed from the inventory. Allow yOUf lab partner to do the steps in this task. Remain logged in to yOUf desktop virtual machine and leave the vSphere Client open for the next labo
o
o c
42
Lab 7
Managing VMware vStorage VMFS Datastores
o o o o o o o o o o o o o o o o
LabB
Lab 8
43
Shared datastore for virtual machines Guest operating system version Repository for ISO images Path to virtual appliance OVF file Virtual appliance import datastore Virtual machine Administrator password Name of iSCSI datastore
o
o o
o
o
o o
c
c
c
c
Field/setting
Configuration Name (ofvirtual machine)
Value
Custom Name the new virtual machine with your fust name, followed by the number of your VMware ESXi host and a sequence number, starting with 1. For example, Greg has an ESXi host named goose06. The name of his virtual machine is Greg06-I. The Lab VMs foider is selected for you. Expand the view and select your ESXi host
44
0 0
Value Select your Local-## datastore. Keep the default. Recorded in "Preparing for the lab" Recorded in "Preparing for the lab" Select 1. To ensure that you are configuring 384MB ofmemory (not GB), select MB from the drop-down menu and type 384 in the space provided. Select 1. Select Production from the drop-down menu. Keep the default. Leave selected. Keep the default. Keep the default. Type 2GB. Select the check box.
0
()
0 0 0 0
NIC 1 Adapter Connect at Power On SCSI Controller Disk Disk Size Allocate and commit space on demand (Thin Provisioning) Support c1ustering features such as FauIt Tolerance Location Virtual Deviee Node
0
0
0
0 0
Leave unselected.
Lab8
45
Field/setting
Mode - Independent Ready to Complete
Value
Leave unselected. Select the Edit the virtual machine settings before completion check box and click Continue. The Virtual Machine Properties dialog box appears.
o
) ()
5. In the Hardware list, select New CD/DVD (adding). 6. Select Datastore ISO file. 7. Click Browse and go to the repository for ISO images that you recorded in "Preparing for the lab." 8. Click Open. 9. Select the ISO image that corresponds to the guest operating system that you selected during virtual machine creation and click OK. 10. In the Virtual Machine Properties dialog box, select the Connect at power on check box. 11. Click Finish to save the changes. 12. Verify that the new virtual machine appears in the inventory. 13. In the inventory, select the virtual machine that you created and click the Summary tab. Record the following information.
Virtual machine 1
o o o o o c o o
c c c
1. Right-click the virtual machine that you created in task 1 and select Power> Power On. 2. Right-click the virtual machine again and select Open Console.
46
o o
() ()
3. Do an unattended installation of the Windows guest operating system. After your virtual machine powers on, it begins to install the guest operating system. The installation should take 10-15 minutes.
4. Complete tasks 3-5 while this virtual machine is installing. Leave the virtual machine's console
open so that you can monitor it periodically.
o o o
()
1. Go to Home> Inventory > VMs and Templates. 2. Right-click your TemporaryVMs folder and select New Virtual Machine. 3. When prompted by the Create New Virtual Machine wizard, enter the following values.
Field/setting
Configuration Name
Value
Custom Name the new virtual machine, starting with iSCSIVM, followed by the number of your ESXi host. For example, for an ESXi host named goose06, the virtual machine name is iSCSIVM-06. Your TemporaryVMs folder is selected for you. Select your ESXi host. Select the iSCSI datastore. Select 7. Select Linux. Select Other Linux (32-bit). Select 1. Type 128MB.
o o o
()
Inventory Location
HostlCluster Datastore Virtual Machine Version Guest Operating System Version Number of virtual processors Memory
o
()
Lab 8
47
Field/setting
How many NICs do you want to connect NIC 1 Network
Value
Select 1. Select Production from the drop-down menu. Keep the default. Deselect the check box. Keep the default. Select Do not create disk. This virtual machine will boot from a CDROM ISO image. Select the Edit the virtual machine settings before completion check box and click Continue.
o
l
(J
Ready to Complete
o o c o
c
4. In the Hardware list, select New CDIDVD (adding). 5. Select Datastore ISO File. 6. Click Browse and go to the repository for ISO images that you recorded in "Preparing for the lab." 7. Click Open. 8. Select the ISO image named dsl. iso. 9. Select the Connect at power on check box.
10. Click Finish to save the changes. 11 . Verify that the new virtual machine appears in your TemporaryVMs folder. Do not power on the virtual machine.
c
c
48
Lab 8
o o o o o o o o o o o
()
1. In the vCenter Server inventory, select your ServerVMs folder. 2. In the vSphere Client menu bar, select File> Deploy OVF Template. The Deploy OVF Template wizard appears. 3. When prompted by the Deploy OVF Template wizard, enter the following values.
Field/setting
Source
Value
Enter the path to the virtual appliance OVF file that you recorded in "Preparing for the lab" and click Browse. Select the OVF file in the folder. Click Next.
Click Next. TypeVDR-## (where ## is the number ofyour ESXi host). The ServerVMs folder is selected for you. Expand the inventory. Select your ESXi host and click Next. If a waming message appears about the appliance's operating system, click Yes to continue.
o o o o
Datastore
Select the datastore for virtual appliance import that you recorded in "Preparing for the lab." Keep the default. Keep the default.
49
Field/settlng
Properties Ready to Complete
Value
Keep the default. Click Finish.
4. Wait for the deployment to complete. A pop-up window shows you the status of the deployment process. When the deployment has completed successfully, click Close. 5. Verify that your Data Recovery appliance (VDR-##) is in your ServerVMs folder. Do not power on the appliance. You will use it in a later labo
1. In the Lab VMs folder, right-click the <your_ name>##-l virtual machine in the inventory and select Edit Settings. 2. In the Hardware list, select Hard disk 1. 3. Under Disk Provisioning, identify the VMDK type. What type ofVMDK has been provisioned? :Ch ;'"
4. Click Cancel to close the Virtual Machines Properties dialog box. 5. In the LabVMs folder, select the <your_name>##-l virtual machine and click the Summary tab. 6. In the Resources panel, click the Refresh Storage Usage link to update the Provisioned Storage and Used Storage metrics. Record the new values in the following table.
o o o o o o o o o o o
Virtual machine 1
G~
c
C
Lab 8 Working with Virtual Machines
Compare these values to the values listed in task 1, step 13. Verify that values difIer. Although a 2GB virtual VMDK has been configured for this virtual machine, the storage space consumed
50
o o o o o o o o o o o o o o o o
by the VMDK is a fraction of the total disk space. The used storage space will increase dynamically as the virtual machine is used.
Task 6: Install VMware Tools into a virlual machine installed with a Windows operating system
In this task, you will install VMware Tools into the guest operating system. Students should do the steps in this task individually. 1. Retum to the console of the virtual machine where the Windows guest operating system is installing. Check to see whether the installation has fini shed. If the installation has not finished, wait for it to complete before proceeding. 2. In the icon bar of the virtual machine console window, click Connectldisconnect the CD/DVD devices of the virtual machine (the right-most icon). 3. Select CD/DVD Drive 1 > Disconnect from datastore image. Click Yes to confirm that you want to disconnect the device. 4. From the virtual machine console, log in to the guest operating system: a. In the menu bar of the virtuaJ machine console, select VM > Guest > Send Ctrl+AIt+Del. b. In the Windows login screen, log in as user Administrator with the virtual machine Administrator password that you recorded in "Preparing for the lab." 5. Install VMware Tools into the Windows guest operating system: a . In the menu bar of the virtual machine console, select VM > Guest > Install/Upgrade VMware Toois.
Ifyou are unable to move the pointer to the menu bar, press Ctrl+Alt to release the pointer from the virtual machine console. b. Read the warning message that appears and click OK. c. Click anywhere in the virtual machine console window to give mouse focus to your virtual machine. d. The VMware Tools installation wizard starts. On the welcome page, click Next. e. On the Setup Type page, leave Typical selected and click Next.
f. Click Install to start the installation. Over the span of several seconds, several windows are
displayed.
51
6. Ifyou see a pop-up window infonning you that hardware acceleration is not enabled, click Yes and do steps 6a-6c. Ifyou do not see the pop-up window, go to step 7. a. In the Display Properties dialog box, click the Settings tab and click the Advanced button. Vou might have to move the VMware Tools Installation wizard to the side so that you can see the Display Properties dialog box. b. Click the Troubleshoot tab. Drag the Hardware Acceleration bar from None to Full. Click OK. c. Click OK to exit the Display Properties dialog box. 7. Click Finish to exit the VMware Toois Installation wizard. 8. When prompted to restart the virtual machine, click Yeso 9. After the virtual machine reboots, log in as user Administrator. 10. Verify that the movement ofyour pointer in the virtual machine console is smoother. Leave the virtual machine console open.
o o o
o
o
o o
Task 7: Enable time synchronization between a virtual machine and an ESXi host
In this task, you will configure VMware Tools to synchronize the time between the virtual machine and the ESXi host. Students should do the steps in this task individually. 1. In the virtual machine console, notice the time, which is displayed in the notification area. 2. In the notification area, right-click the VMware Toois icon and select Open VMware Tools. 3. Select the Time synchronization between the virtual machine and the ESX Server check box and click OK. 4. Go to Home> Inventory > Hosts and Clusters. 5. Select your ESXi host from the inventory and click the Configuration tab. 6. Click the Time Configuration link. 7. Compare the time in the virtual machine and the ESXi host time. If they do not match, you might have to adjust your virtual machine's time zone. Vou might also need to adjust the clock for daylight saving time.
o o
0
c c c
52
()
In this task, you will connect to the ClassFiles-vSphere. iso image file and copy its contents to your Windows virtual machine's desktop. This ISO image contains files needed for future labs. Students should do the steps in this task individually.
1. Connect ClassFiles-vSphere. iso to your virtual machine's CD-ROM drive: a. In the icon bar of the virtual machine console window, click the Connect/disconnect the CD/DVD devices of the virtual machine icon (the right-most icon). b. Select CD/DVD Drive 1 > Connect to ISO image on a datastore.
()
c. Select Classfiles-vSphere. iso and click OK. 2. View your virtual machine console. If autorun does not open the CD-ROM, use Windows Explorer and go to the CD-ROM drive (0:). 3. Copy the file cpubusy. vbs from the CD-ROM drive (0:) to the virtual machine's desktop. You will use this file in a later labo 4. Extract the files from the executable extpart. exe (to be used in a later lab): a. On the CD-ROM, double-click the file extpart. exe.
o
()
( )
o
C )
b. In the WinZip Self-Extractor dialog box, click Unzip. Two files are unzipped to the path C: \dell \ExtPart. Click OK. c. Click Close to close the WinZip Self-Extractor dialog box. 5. Disconnect from the Classfiles-vSphere. iso on the CD-ROM drive: a. Right-click the virtual machine in the inventory and select Edit Settings. b. In the Hardware list, select CD/DVD Drive 1.
()
c. Select Client Deviee and click OK. d. Close the virtual machine console. 6. Log out ofyour vSphere Client session (File> Exit.) 7. Log out ofyour desktop virtual machine.
()
o
Lab 8 Working with Virtual Machines
53
()
c c
c
c c
c c
c
c c c
c
c
54
Lab 8
Working with Virtual Machines
o o o o o o o o o o o o o o o
)
Lab9
1. Configure guest operating system customization on a vCenter Server system. 2. Create a template. 3. Deploya virtual machine from a template. 4. Clone a virtual machine that is powered on.
Lab 9
55
Your domain administrator password Shared datas tore for virtual machines Windows product ID Virtual machine Administrator password
Id-Iii
In lab 2, your instructor told you how to access your vCenter Server system, for example, by using Remote Desktop Connection.
c
c
C
2. Find the Windows Sysprep CAB file, whose location you recorded in "Preparing for the lab." 3. Right-click the Windows sysprep CAB file WindowsServer2003-KB892778-SP1DeployTools-x86-ENU and select Open. 4. In Windows Explorer, open the Sysprep tools installation folder that you recorded in "Preparing for the lab." 5. Copyall files from the CAB file to the Sysprep tools installation folder. Vou will receive a warning for each file whose publisher is not verified. Click Save for each file. 6. Close all Windows Explorer windows. 7. Log out ofyour vCenter Server system.
C
C
c
(~
c
c
56
Lab 9
Using Templates and Clones
o o o
o
1. Log in to your desktop virtual machine with the domain administrator user name and password that you recorded in "Preparing for the lab."
iU"i
In lab 3, your instructor told you how to access your desktop virtual machine, for example, by using Remote Desktop Connection.
o o o o o o o o o o o o
2. Using the VMware vSphere Client, log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 3. In the vSphere Client, go to Home> Inventory > VMs and Templates. 4. Expand your Lab VMs folder. In this folder, you have a virtual machine named <your_ name>##-l. 5. Right-click the virtual machine and select Template > Clone to Template. 6. When prompted by the Clone Virtual Machine to Template wizard, enter the following values.
Field/setting
Template Name
Value
Name the template with your first name, followed by the word "Template" (for example, GregTemplate). Select the Training datacenter. Select your ESXi host.
Template Inventory Location Host or Clnster on which to store template Datastore for the template Disk Format Ready to Complete
7. Monitor the progress of the cloning task in the Recent Tasks pane at the bottom of the vSphere Client.
57
8. When the clone-to-template operation is finished, notice how the icon of the template differs from a virtual machine icon.
o
~
.)
l1li
Vou can also view the template from the Rosts and Clusters inventory view: Switch to the Rosts and Clusters inventory view, select yOuf datacenter or host, and click the Virtual Machines tab.
Field/setting
Name
c
c c c
Value
Name the new virtual machine with your first name, followed by the number ofyour ESXi host and a sequence number. For example, Greg has an ESXi host named goose06. The name of his second virtual machine is Greg06-2. Select your LabVMs folder. Select your ESXi host.
Inventory Location Host or Cluster to run this virtual machine Datastore for the virtual machine
c
c
Select the shared datastore for virtual machines that you recorded in "Preparing for the lab." Keep the default. Select Customize using the Customization wizard.
c
c
c c
58
Lab 9 Using Templates and Clones
o o o
o
3. When prompted by the vSphere Client Windows Guest Customization wizard, enter the following values. Field/setting Name Organization NetBIOS Name ProductKey Value Type VMware student. Type VMware. Select Use the virtual machine name. Type the Windows product ID that you recorded in "Preparing for the lab." Leave selected. Keep the default. Enter the virtual machine Administrator password that you recorded in "Preparing for the lab." Leave unselected.
o o o o
o
Automatically log on as tbe administrator TimeZone RunOnce Network Workgroup or Domain Generate New Security ID (SID) Save tbis customization specification for later use Name (of customization specification)
Select your time zone. Keep the defaults. Keep the default. Keep the defaults. Keep the default. Leave selected.
o o o o o o
o
Description
59
Field/setting
Ready to Complete (vSphere Client Guest OS Customization wizard) Ready to Complete (Deploy Template wizard)
Value
Click Finish.
o
o
Select the Power on this virtual machine after creation check box and click Finish.
4. In the Recent Tasks pane at the bottom of the vSphere Client, monitor the progress of the cloning and customization. 5. When the task completes, open a virtual machine console to yOuf new virtual machine. 6. Verify that the virtual machine was created properly. Check the following: complete its tasks, which includes a reboot of the system. You can log in to the guest operating system as Administrator with the virtual machine Administrator password that you recorded in "Preparing for the lab." l....-\k. J..<. VMware Toois is installed with time synchronization configured. The cpubusy. vbs file is on the desktop. 7. Close the virtual machine console. Do not shut down the virtual machine.
c
l
~ ~EP V>v (' The virtual machine booted up successfully. Wait at least two minutes for Sysprep to )"{GSSc. \ ~
. : yc<..v"'Y
,..,ti\1
n
~
.J '~
.).y--"> f
"Je"'-
c
c
Field/setting
Name
Value
Name the new virtual machine with yOuf first name, followed by the number of yOuf ESXi host and a sequence number. For example, Greg has an ESXi host named goose06. The name ofhis third virtual machine is Greg06-3. Select yOuf LabVMs folder.
c c
c
Inventory Location
c
c,
60
Lab 9
o o o o o o o o o o o o o o o o
Field/setting
Host or Cluster on which to run this virtual machine Datastore
Value
Select your ESXi hosto
Select the shared datas tore for virtual machines that you recorded in "Preparing for the lab." Keep the default. Select Customize using an existing customization specification. Select the customization specification with your name from the Iist. Leave the Use the Customization Wizard to temporarily adjust the specification before deployment check box unselected.
Ready to Complete
Select the Power on this virtual machine after creation check box and click Finish.
3. Monitor the task in the Recent Tasks pane. Allow the task to run. Check the result during the next labo 4. Exit the vSphere Client. 5. Log out of yOuf desktop virtual machine.
Lab 9
61
(J
o c c c c
c
c
c
c
c
62 Lab 9
c c
o o o o o o o o o o o o o o o o
Lab 10
63
Sysprep tools installation folder Your desktop virtual machine name Your domain administrator user name Your domain administrator password IP address of the <your_name>##-3 virtual machine Import task user name Import task user password Shared datastore for virtual machines
c c
c c
c
c
yClntJr uW,d
'"'dt_
Utliity
c c
Lab 10
VMware vCenter Converter
64
o o o o o o o o o o o o o o o
CJ
4. Click the vCenter Converter link in the VMware vCenter Installer. 5. When prompted by the vCenter Converter installation wizard, enter the following values.
Field/setting
Setup Language
Value
Select the setup language that you recorded in "Preparing for the lab" and click OK. Click Next. Click Next. Select 1 accept the terms in the License Agreement and click Next. Accept the default value and click Next. If an error message about free space appears, click OK.
Destination Folder
Enter your vCenter Server system name, the user named Administrator, and Administrator's password, which you recorded in "Preparing for the lab." Leave the port set to 80. If an untrusted SSL certificate message appears, click Yes to continue.
Verify that either the fully qualified domain name (FQDN), IP address, or system name of the vCenter Server system is selected and click Next. Click Install.
Ready to Install
65
7. Click Exit to close the VMware vCenter Installer. 8. Ifyou are student A, log out of the vCenter Server system. Ifyou are working alone, remain logged in to the vCenter Server system.
()
o
Cl
1. Log in to the desktop of your vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. Right-click the Windows Sysprep CAB file WindowsServer2003-KB892778-SPlDeployTools-x8 6-ENU and select Open. You recorded its location in "Preparing for the lab." 3. In Windows Explorer, open the Sysprep tools installation folder that you recorded in "Preparing for the lab."
Idlii
The foIder that vCenter Converter uses for the Windows Sysprep files is difIerent from the guest operating system customization folder that vCenter Server uses for operations like cloning and deploying from a template. 4. Copy aIl files from the CAB file to the Sysprep tools installation folder. You will receive a warning for each file whose publisher is not verified. Click Save for each file. 5. Close aIl Windows Explorer windows. 6. Log out of the vCenter Server system.
o c c c
1. Log in to your desktop virtual machine with the domain administrator user name and password that you recorded in "Preparing for the lab."
Id"i
In lab 3, your instructor told you how to access your desktop virtual machine, for example, by using Remote Desktop Connection.
(~
(~
66
Lab 10
o o o o o o o o
o
2. Using the VMware vSphere Client, log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 3. In the menu bar of the vSphere Client, select Plug-ins > Manage Plug-ins. The Plug-in Manager appears. 4. Under Available Plug-ins, next to the entry for vCenter Converter, click the Download and Installlink. 5. When the download completes, enter the following values.
Field/setting
Setup Language
Value
Select the setup language that you recorded in "Preparing for the lab." Click Next. Click Next. Select 1 accept the terms in the License Agreement and click Next. Click Install.
Ready to Install
6. Click Finish when the installation completes. 7. Verify that the vCenter Converter plug-in has a status of Enabled in the Plug-in Manager.
o o o o o o o
Idili
If the status does not refresh, you might need to exit the vSphere Client and log in again. 8. In the Plug-In Manager, click Close.
67
3. Open a console to the system to clone and log in with the import task user name and password that you recorded in "Preparing for the lab."
4. From the desktop of the system to clone, select Start > Run.
7. Click Stop.
8. Close the Services window. 9. Close the console of the system to clone.
1. Right-c1ick your ESXi host in the inventory and select Import Machine.
2. When prompted by the Import Machine wizard, enter the following values.
o o o o o o o
Field/setting
Select Source Type Powered-on machine - IP address or name User name
Value
Select Powered-on machine. Enter the IP address of the <your_name>##-3 virtual machine. Enter the import task user name that you recorded in "Preparing for the lab." Enter the import task user password that you recorded in "Preparing for the lab." Select Windows and click View Source Details.
c c o c
c c
c c
Password
OS Family
68
Field/setting
Uninstall VMware vCenter Converter Agent
Value
Leave Automatically uninstall the files when import succeeds selected and click Yes to continue. Review the infonnation in the Machine Details window and click Close. Click Next.
0 0 0
()
Leave at default. For the new virtual machine name, type Rot<your_name>##, where ## is the number of your ESXi ho st. For example, Greg has an ESXi host named goose06. The name ofhis virtual machine is Hot-Greg06. Select the shared datas tore for virtual machines that you recorded in "Preparing for the lab." Select version 7 and click Next. Verify that the virtual machine name is Hot<your_name>##, where ## is the number of your ESXi host. Verify that the folder destination is set to Training.
0
0 0
Datastore
0
0 0
Option - Data to Copy Option - Deviees
Verify that the copy type is volume-based. Verify that Processors is set is 1. Verify that Disk Controller is set to Preserve Source. A warning indicates that the source machine is running with 1ess than the minimum recommended memory for this operating system. The conversion process will adjust the memory value to 512MB for you.
0
0 0 0
Option - Networks
Lab 10 VMware vCenter Converter
69
Field/setting
Option - Services
Value
Click Edit. Find Print Spooler in the list. Note the current status.
o o
o
To fmd this service easily, click the Service column to sort the services in alphabetical order. Click the Destination services tab. Find Print Spooler in the list. In the Startup Mode column, change the value to Disabled. Option - Advanced Options Click Edit and select the following options: Power on destination machine Power off source machine Leave ail options in Post-conversion processing at their default values. Option - Throttling Scroll down in the Options pane to see the throttling option in the list. Click Edit and verify the following: CPU throttling is set to None. The Network bandwidth throttling check box is not selected. Click Next. Summary Verify ail information and click Finish.
o o o o o o o
3. In the Recent Tasks pane, monitor the progress of the Import Machine task. 4. When the task completes, verify that the machine was converted properly. Check the following: The destination virtual machine boots up completely. The source virtual machine is powered down.
70
Lab 10
o o o o
\J
t~
System memory is set to 512MB on the cloned system. Vou can log in to the guest operating system as user Administrator. The
cpubusy. vbs
5. Select Start > Run and type services. msc in the box. 6. When the Services window appears, find Print Spooler in the list and verify that Startup Type is set to Disabled. 7. Close the Services window. 8. Close the console of the clone. Leave the vSphere Client open for the next labo
o o o
)
o
() ()
o o o
Lab 10 VMware vCenter Converter
71
o o o o o o o o
o
o
C)
c
c
72
Lab 10
VMware vCenter Converter
o o o o o o o o o o o o o o o o
Lab 11
Lab 11
73
c c
C
c
c c c
d. Use Windows Explorer to open the folder C: \dell \ExtPart foIder. e . Double-click the extpart . exe file.
f. In Volume to extend, type C: .
g. In Size to exp and the volume, type 2048 (to extend the volume by 2,048MB).
c c
L
74
Lab 11
o o o o o o o o o o o o o o o o
h. On the virtual machine desktop, double-click My Computer to verify that the C: drive was extended. Record the value for total size ofthe C: drive. . Does it differ from step 9c?_ _ __
"411UUI
Renaming a virtual machine in the inventory does not change the name of the virtual machine files on the datastore. For example, if the virtual machine Hot-Greg02 is renamed to Greg02-7 in the vCenter Server inventory, the files on the datastore are still named Hot-Greg02.
Lab 11
75
To rename a virtual machine and ail files belonging to the virtual machine, you must renarne the virtual machine in the inventory and use VMware Storage vMotion to move the virtual machine to a different datastore. For this task, you will rename only the virtual machine. 3. Drag <your_narne>##-4 to your TemporaryVMs folder.
c
c
Task 4: Add a raw LUN to a virtual machine and verity that the guest operating system can see it
In this task, you will add a raw logical unit number (LON) to a virtual machine that is powered on. You will also verify that the gue st operating system can see the new virtual disk. Students should do the steps in this task individually. 1. Add a raw LUN to the <your_ name>##-2 virtual machine: a. In the inventory, right-click the <your_narne>##-2 virtual machine and select Edit Settings. The Virtual Machine Properties dialog box appears. b. In the Virtual Machine Properties dialog box, click Add. c. When prompted by the Add Hardware wizard, enter the following values.
c
o
o
o
Fleld/setting
Deviee Type Select a Disk Select Target LUN
Value
Select Hard Disk. Select Raw Deviee Mappings. Select your assigned LUN, which you recorded in "Preparing for the lab." Keep the default. Select Virtual. Leave the defaults. Click Finish.
c
c c
d. When a new entry for the hard disk appears in the Hardware list with the word "(adding)" next to it, click OK to add the raw LUN. 2. In the inventory, right-click the <your_narne>##-2 virtual machine that you created and select Rename. Change the name to <your_name>##-2-RDM.
76
Lab 11
3. View the <yoUf_name>##-2-RDM virtual machine files: a. In the inventory, select the <your_name>##-2-RDM virtual machine and click the Storage Views tab. b. Click the Update link.
c. In the drop-down menu, select Show ail Virtual Machine Files. d. Verify that a new virtual machine file named <your _ name>U-2 _l-rdm. vrndk exists. 4. Verify that the guest operating system can see the new disk: a. Open a console to the virtual machine and log in as user Administrator, with the password that you recorded in "Preparing for the lab."
o o
)
b. Select Start > Programs > Administrative Toois > Computer Management. c. Click Disk Management. d. Verify that Disk 1 is listed. Disk 1 is the raw device mapping. You can now use the guest operating system utilities to format the drive. In this lab, do not format the drive. e. Close the Computer Management window.
f. Close the virtual machine console.
o
)
allocated to it when it was created. Students should do the steps in this task individually. 1. View storage information for the virtual machine named <your_name>##-3: a. In the inventory, select the virtual machine named <your_name>##-3. b. Click the Summary tab and record the storage information found in the Resources panel. Provisioned Storage Not-shared Storage Used Storage Datastore
()
2. Inflate the thin-provisioned virtual disk:
)
)
a. Go ta Home> Inventory > Datastores. b. Right-click the datastore that you recorded in step 1 and select Browse Datastore.
Lab 11 Modifying a Virtual Machine
77
c. Open the folder for the virtual machine named <your_name>##-3. d. Right-click the <your _ name>U-3. vrndk file and select Inflate. Wait for the operation to finish. e. Close the Datastore Browser. 3. Go to Home> Inventory > VMs and Templates. 4. In the vCenter Server inventory, select the virtual machine named <your_name>##-3. 5. Click the Summary tab. 6. Record the storage information found in the Resources panel and verify that the disk is now fully allocated. Provisioned Storage Not-shared Storage Used Storage Leave the vSphere Client open for the next labo
o o o o o o o
c
c c
c c
78
Lab 11
(~
o o o o o o o o o o o o o o o o
Lab 12
Lab 12
79
o o
c
o o o
c c
c c
1. If the VMware vSphere Client is not already active, use it to log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > VMs and Templates. 3. In your TemporaryVMs folder, select <your_name>##-4 (where ## is the number ofyour VMware ESXi host) and click the Summary tab. 4. From the Datastore column in the Resources panel, record the VMFS datastore name where the k; a tol;s A 1..virtual machine resides: 1 5. Right-click <your_ name>##-4 and select Remove from Inventory.
'm,II1 t.h 1
Do not select Delete from Disk. That operation is not recoverable. 6. Click Yes to confirm the removal and verify that <your_ name>##-4 no longer appears in the inventory. 7. Go to Home> Inventory > Datastores. 8. Right-click the VMFS datastore on which <your_name>##-4 is located (the name that you recorded in step 4) and select Browse Datastore. 9. In the Datastore Browser, find the foIder containing the files for <your_name>##-4. The folder is named with the original virtual machine name: Hot-<your_name>##. 10. Open the fol der with the original virtual machine name (Hot-<your_ name##. Select the foIder name in the left pane to view the virtual machine files. Leave the Datastore Browser open.
c
80
Lab 12 Managing Virtual Machines
o o o o o o o o o o o o o o o
Field/setting
Name & Location
Value
Type <your_name>##-S, where ## is the number of your ESXi host. In the Inventory Location pane, select your TemporaryVMs folder.
3. Verify that the virtual machine was placed back in the inventory: a . Close the Datastore Browser. b. Go to Home> Inventory > VMs and Templates. c. Verify that <your_name>##-5 appears in your TemporaryVMs folder.
tu
2. Right-click <your_name>##-5 and select Delete from Disk. 3. Click Yes to confirm the deletion and verify that <your_name>##-5 no longer appears in the inventory. 4. Go to Home> Inventory > Datastores.
81
5. Right-click the VMFS datastore on which <your_name>##-5 is located and select Browse Datastore.
6. Verify that the virtual machine files no longer exist. The folder would have been named with the original virtual machine name: Hot-<your_name>##. 7. Close the Datastore Browser. 8. Go to Home> Inventory > VMs and Templates.
9. In the TemporaryVMs folder, power off any virtual machines that you own. Coordinate with your lab partner to power off the iSCSIVM-## virtual machine, where ## is the last two digits of your ESXi host. If you are working alone, power off aH virtual machines in this folder.
10. In the TemporaryVMs folder, right-click each virtual machine that you own and select Delete from Disk. Coordinate with your lab partner to delete from disk the iSCSIVM-## virtual machine. Ifyou are working alone, delete from disk ail virtual machines in the TemporaryVMs folder.
o o o c o
o
o o
G
Power On.
2. Right-click the virtual machine and select Snapshot > Take Snapshot. 3. When prompted by the Take Virtual Machine Snapshot wizard, enter the following values.
Field/setti ng
Name Description Snapshot the virtual machine's memory Quiesce guest file system (Needs VMware Toois installed)
Value
Type<your name> Base Image. Type Wi th cpubusy. vbs. Leave selected. Leave unselected.
4. Click OK and monitor the task in the Recent Tasks pane. 5. Right-click the virtual machine and select Open Console.
c c c
Managing Virtual Machines
82
Lab 12
o o o o o o o o o o o o
()
6. Log in as user Administrator with the virtual machine Administrator password that you recorded in "Preparing for the lab."
7. Drag the cpubusy. vbs file to the Recycle Bin. To completely remove the cpubusy. vbs file, empty the Recycle Bin (right-click the Recycle Bin icon and select Empty Recycle Bin).
Field/setting
Name Description Snapshot the virtual machine's memory Quiesce guest file system (Needs VMware Toois installed)
Value
Type<your_name> Snapshot 2. Type Wi thout cpubusy. vbs. Leave selected.
Leave unselected.
10. Click OK and monitor the task in the Recent Tasks pane. 11. After the task has completed, right-click the virtual machine and select Snapshot > Snapshot Manager.
12. Select each snapshot in the snapshot hierarchy and view its name and description.
o o o
83
5. Go to the virtual machine's console. Log in to the virtual machine and verify that the cpubusy. vbs file is on the desktop. 6. Reopen the Snapshot Manager. Click Delete Ali to delete aIl ofyour snapshots. 7. Click Yes to confirm the deletion. 8. Verify that aIl snapshots were removed from the Snapshot Manager. 9. Close the Snapshot Manager. 10. Close the virtual machine console.
o c c
(J
1. In your Lab VMS folder, verify that the <your_ name>##-l virtual machine is powered on. If it is not, power it on. 2. Select <your_ name>##-l and click the Summary tab. 3. Under Datastore in the Resource panel, verify that the virtual machine is on the Local-## datastore. 4. Right-click the virtual machine in the inventory and select Migrate. 5. When prompted by the Migrate Virtual Machine wizard, enter the following values.
o
c
o
o
Field/setting
Select Migration Type Select Datastore
Value
Leave at default. Select the VMFS datastore to migrate to, which you recorded in "Preparing for the lab." Keep the default. Click Finish.
c
Lab 12 Managing Virtual Machines
84
o o o o o o o o o o o o o o o
()
7. After the task is finished, click the Summary tab of<your_name>##-l to verify that your virtual machine is on the new datas tore. Leave the vSphere Client open for the next labo
Lab 12
85
()
o o
(J
c
c
c
c
(-.....
L
86
Lab 12
Managing Virtual Machines
o o o
o
Lab 13
o o o o o o o o o o o o
Access Control
Objective: Manage user access permissions
In this lab, you will perform the following tasks: 1. Configure an ESXi host to use directory services.
2. Use Active Directory accounts to verify proper access to your ESXi host.
3. Create a custom role in vCenter Server.
Access Control
87
1. Use the VMware vSphere Client to log in to yOuf VMware vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab."
2. Go to Home> Inventory > Hosts and Clusters.
3. Select your ESXi host in the inventory and click the Configuration tab.
4. Under Software, click the Authentication Services link. 5. Click the Properties link.
6. In the Directory Services Configuration dialog box, enter the following values.
Field/setting
User Directory Service Domain Settings
Value
Select Active Directory. Enter the Active Directory domain name that you recorded in "Preparing for the lab" and click Join Domain. Enter your domain administrator user name (without the domain name) and the domain administrator password that you recorded in "Preparing for the lab." Click Join Domain.
o o o o o c o
c
c c
L
Join Domain
88
(~
()
o o o o o o o o o o o
)
)
Task 2: Use Active Directory accounts to verify proper access to your ESXi host
In this task, you will verify that privileged and nonprivileged directory services accounts have proper access to your ESXi host. Students should do the steps in this task individually.
1. Use the vSphere Client to log directly in to your ESXi host with the nonprivileged domain user name and password that you recorded in "Preparing for the lab." Was the login successful? Why or why not?
~~v
-7
2. Use the vSphere Client to log in to your ESXi host, this time with the domain administrator user name and password that you recorded in "Preparing for the lab." Was the login successful? Why or why not?
ri. V
---'>
3. Go to Home> Administration> Roles. 4. In the Roles column, click Administrator. What users and groups are assigned the Administrator role?
(-"r~_h .. ",
("C>o
\t..S
.
lC" ...
J-.';"s
1--
O-C.VI
5. Log out of the ESXi host (File> Exit).
v (?C'-'><r
89
Prlvilege category
Datastore Network Resource Virtual machine> Configuration
Privilege name
Allocate space Assign network Assign virtual machine to resource pool Addnew disk Add or remove device Memory
o
o o o
AlI privileges. Select Interaction to include aIl privileges in this subcategory. Createnew
o o o o
0
0
1. Go to Home> Inventory > VMs and Templates. 2. Select the TemporaryVMs folder. 3. Click the Permissions tab. 4. Right-click in the white space and select Add Permission. The Assign Permissions dialog box appears. 5. Click Add. 6. From the drop-down menu in the Domain panel, select the Active Directory domain that you recorded in "Preparing for the lab."
o
0 0
..J
90
o
o
7. In the search field of the Users and Group panel, enter the user name of the nonprivileged domain account that you recorded in "Preparing for the lab." Do not include the login domain in the entry. Click Search.
o o o o o o o o o o
()
8. When the search completes, select the nonprivileged domain user name in the Users and Groups panel and click Add.
9. Click OK to continue. 10. In the Assigned Role panel, select the Virtual Machine Creator - <your_ name> role. 11. Leave the Propagate to Child Objects check box selected and click OK. Verify that the permission appears in the Permissions tab. 12. Go to Home> Inventory > Hosts and Clusters. 13. Select your ESXi host in the inventory and click the Permissions tab.
14. Add the permission (as in steps 4-11). 15. Go to Home> Inventory > Datastores.
16. Select the datastore for domain users that you recorded in "Preparing for the lab" and click the Permissions tab.
1. Use the vSphere Client to log in to your vCenter Server system with the nonprivileged domain user name and password that you recorded in "Preparing for the lab."
2. Go to Home> Inventory > VMs and Templates. Notice that TemporaryVMs is the only folder that you see.
o
()
3. Right-click your TemporaryVMs folder and select New Virtual Machine. 4. When prompted by the Create New Virtual Machine wizard, enter the following values.
91
Field/setting
Virtual Machine Configuration Name
Value
Select Custom.
o
o o o o
Type <your_name>-Temp, where <your_name> is your fIfst name (for example, Brian-Temp). Your TemporaryVMs folder is selected for you. Select your ESXi host. Select the datastore for nonprivileged users that you recorded in "Preparing for the lab." Notice that the other datastores do not appear in the list. Leave the default. Leave the default. Leave the default. Leave the default. Leave the default. Select Production from the drop-down menu for NIC 1. Notice that the VM Network port group does not appear in the list. Leave the default. Notice the available options and leave the default. In Capacity, type 2GB. Select the Allocate and commit space on demand (Thin Provisioning) check box. Leave the default. Click Finish.
Virtual Machine Version Guest Operating System Version CPUs Memory Network
o o o
o
o
o
o o
G
c
92
Lab 13 Access Control
o
o o o o o o
()
6. After the task is complete, verify that the virtual machine was created successfully. As you completed the wizard, did you notice how only those inventory objects on which you assigned permissions were available for the user to select?_ _ _ __
Id"i
Only one ESXi host is in the inventory, so it is the only host on which a virtual machine can be created. If there were more than one ESXi host managed by vCenter Server, you would be able to see the entire effect of the permission that you applied. 7. Right-click yOUf virtual machine in the inventory. Familiarize yourselfwith the options that the role does not permit. For example, the Delete from Disk option is unavailable. 8. Exit the vSphere Client. 9. Use the vSphere Client to log in to the vCenter Server system with the ~n administrator user name and password that you recorded in "Preparing for the lab." 10. In the inventory, right-click the virtual machine <your_name>-Temp and select Delete from Disk. Leave the vSphere Client open for the next labo
o o o
()
()
Lab 13 Access Control
93
(J
o o
c c c
c c
(~
c
94
Lab 13 Access Control
() () ()
Lab 14
o o o o o o
()
Resource Pools
Objective: Create and use resource pools on an ESXi host
In this lab, you will perfonn the following tasks:
1. Create CPU contention. 2. Create a resource pool named Fin-Test. 3. Create a resource pool named Fin-Prod. 4. Verify resource pool functionality.
o o o
()
)
95
4. In each virtual machine, start three instances of the cpubusy. vbs script (on the virtual machine's desktop) by right-clicking the script and selecting Open with Command Prompt. This script runs continuously. Allow it to run for a minute or two to stabilize. This script repeatedly does floating-point computations. It also displays how long it took to do the computation (wall-clock time). Example:
l did three million sines in 2 seconds!
c
)
Use the number of seconds reported as a performance estimate. Vou should tind that the program runs at approximately the same rate in each virtual machine. 5. In the inventory view, right-click the <your_name>##-l virtual machine and select Edit Settings. 6. In the virtual machine Properties dialog box, click the Resources tab. 7. Click Advanced CPU. 8. In the Scheduling Affinity pane, type 2 in the space provided. The virtual machine will ron only on processor 2. Click OK.
c
c c
CPU affinity is used mainly to create CPU contention for training purposes. Use ofthis feature in a production environment is strongly discouraged. 9. Repeat steps 5-8 to set the scheduling affinity for the other virtual machine, <your_name>##-3. Force it use the same processor as the tirst virtual machine (processor 2). Allow cpubusy. vbs to run for a minute or two.
L
96
Lab 14 Resource Pools
o o o o o o o o o o o o o o o
)
Type Fin-Test. Select Low from the drop-down menu. Leave the defaults.
4. ClickOK.
Type Fin-Prod. Select High from the drop-down menu. Leave the default.
4. ClickOK.
Lab 14
Resource Pools
97
..,
)
1. Select Fin-Test in the inventory and click the Summary tab. View the CPU Resource Settings 7.,.og~ panel. Record the number of shares for this resource pool:
2. Select Fin-Prod and click the Summary tab. View the Resource Settings panel. Record the number of shares for this resource pool: 5(00 QI
3. Drag <your_ name>##-l to the Fin-Prod resource pool. 4. Drag <your_name>##-3 to the Fin-Test resource pool.
5.
c~
View the results of cpubusy. vbs in each virtual machine console. Is there a difference in performance between virtual machines? Why or why not?
CI.
~ ..,
c
(.-
6. Wait for your team member to reach this step. When ready, have one member in your team change CPU shares of the Fin-Test resource pool from Low to Normal. Leave CPU shares at High for the Fin-Prod resource pool.
7. Let the scripts run for a few seconds and compare the performance of the script in each virtual
machine. Ifthere is contention for CPU, you should notice a difference in performance between ~ 1\ ") -Q 5- the virtual machines.
.. ') A 1.-- /((. 'K-<. 8. Wait for your team member to reach this step. When ready, have one member in your team change CPU shares of the Fin-Prod resource pool from High to Normal.
9. Stop the cpubusy. vbs script in each virtual machine. Press Ctrl+C in the cpubusy window. 10. Minimize the virtual machine consoles. You will use them in the next labo
98
o o o o o o o o o o o o o o o o
Lab 15
1. Create CPU contention. 2. Use vCenter Server to monitor CPU utilization. 3. Undo changes made to your virtual machines.
Lab 15
99
o o o
o o o
o o
o o o o
(J
100
Lab 15
o o o o o o o o o o o o o o o
)
8. ClickOK. 9. Click the Popup Chart icon to display the CPUlReal-time graph for this virtual machine in a separate window.
10. Select <yoUT_name>##-3 in the inventory and click the Performance tab. 11 . Configure the CPU Performance graph for <yoUT_name>##-3 and select the same chart options as you did in steps 3-8. 12. Click the Popup Chart icon to display the CPU/Real-time graph for this virtual machine in a separate window. 13. In the Performance Chart window for each virtual machine, point to the end of the Hne graph to view the current CPU ready value.
Lab 15
101
14. Record the current CPU ready value for each virtual machine.
o
o
o
o
scripts in each virtual machine. Press Ctrl+C in each cpubusy window.
Make sure that this script is stopped in each virtual machine. If this script is still running, it will affect the next labo 16. In the Performance Chart window for each virtual machine, point to the end of the line graph to view the current CPU ready value. Did the Ready value change? Why or why not?
-"";>
o o
o
l ,, --\ e. _
>
1 . Close the Performance Chart windows. 2. Close the virtual machine consoles. 3. Remove the scheduling affinity value from <your_name>##-l : a. Right-click the <your_name>##-l virtual machine in the inventory and select Edit Settings. b. Click the Resources tab.
C.
o o o o
Click Advanced CPU and deI ete the value 2 from the field in the Scheduling Affinity pane.
d. Click OK. 4. Repeat step 3 on <your_name)##-3. Leave the vSphere Client open for the next labo
c
Monitoring Virtual Machine Performance
102
Lab 15
o o o o o o o o o o o o o o o
Lab 16
Using Alarms
Objective: Demonstrate the vCenter Server alarm feature
In this lab, you will perform the following tasks:
1. Create a virtual machine alarm that monitors for a condition. 2. Create a virtual machine alarm that monitors for an event. 3. Trigger virtual machine alarms and acknowledge them. 4. Disable virtual machine alarms.
Lab 16
Using Alarms
103
1. If the VMware vSphere Client is not already active, use it to log in to yOuf VMware vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 2. Go to Rome> Inventory > Rosts and Clusters. 3. Select the <yoUf_name##-l> virtual machine in the inventory and click the Alarms tab. 4. Click Definitions. Notice that the virtual machine inherited alarms defined at the vCenter Server level. 5. Right-click anywhere to the right of the list ofalarms and select New Alarm. The Alann Settings dialog box appears. 6. In the General tab, enter the following values.
o o o o c o
c
Field/setting
Alarm na me Description Alarm Type - Monitor
Value
TypeVM CPU Usage - <your_name>. Leave blank. Select Virtual Machines and select Monitor for specifie conditions or state, for ex ample, CPU usage, power state. Leave selected.
c
c
7. Click the Triggers tab and click Add. 8. Add the following trigger.
c
c
Trigger setting
Trigger Type Condition Warning
Value
Select VM CPU Usage (%). Select Is above. Double-click the current value and type 25.
c
Lab 16 Using Alarms
104
o o o o o o o o o o o o o o o o
Trigger setting
Value
Condition Length
Select for 30 sec from the dropdownmenu. Type 50. Leave the default (5 minutes).
9. Leave Trigger if any of the conditions are satisfied selected. 10. Do not change anything in the Reporting tab. 11 . Click the Actions tab. 12. Click Add. 13. Configure the following action settings.
Action setti ng Value
Action
Click the space below the Action header and select Suspend VM from the list. Leave as is. (This column does not apply to this action.) Select Once from the list. Change the setting from Once to no value. Leave blank. Leave blank.
14. Click OK. 15. Verify that your alarm appears in the list of alarms. It should appear at the end of the list.
Lab 16
Using Alarms
105
o
o c
c
o
Field/setti ng
Alarm name Description Alarm Type - Monitor
Value
TypeVM Suspended - <your_name>. Leave blank. Select Virtual Machines and select Monitor for specifie events occurring on this object, for example, VM powered On. Leave selected.
o c
c
4. Click the Triggers tab. 5. Click Add. 6. Double-click the trigger in the Event column to display a drop-down menu with a list of triggers. Enter the following values.
Trigger setting
Event Status
Value
Select VM suspended (near the end of the list). Keep the default.
c c
c
7. In the Conditions column, click the Advanced link. The Trigger Conditions dialog box appears. 8. Click Add. 9. In the Argument column, select Change tag and select VM name from the list. 10. In the Operator column, leave equal to selected.
c
Lab 16 Using Alarms
106
o o o o o o o o o o o o o o o
)
11. Click the area under the Value colurnn. Type <your_ name>## -1 as the virtual machine name, where <your_name> is your first name and ## is the number ofyour VMware ESXi hosto The virtual machine name is case-sensitive. 12. Click OK. 13. Without making changes in either the Reporting tab or the Actions tab, click OK. Verify that your alarm appears in the list ofalarms. It should appear at the end of the li st.
Id'''i
Your VM CPU Usage alarm appears briefly in the Triggered Alarms pane, so you might not see this alarm if you were not viewing the pane at the time the alarm was triggered. But you should see your VM Suspended alarm after the virtual machine is suspended. 4. Verify that your VM Suspended alarm is triggered. You should see an entry for this alarm in the Triggered Alarms pane. The Acknowledged and Acknowledged By fields are blank. 5. Right-click your VM Suspended alarm and select Acknowledge Alarm. The Acknowledged and Acknowledged By fields are now populated. 6. Power on the suspended virtual machine by right-clicking the virtual machine in the inventory and selecting Power> Power On. 7. In the virtual machine console, press Ctrl+C in the command window to stop cpubusy. vbs. 8. Close the virtual machine console. 9. In the Alarms tab, right-click your VM Suspended alarm and select Reset Alarm to Green. In the inventory, verify that the red alert icon is removed from the virtual machine.
Lab 16
Using Alarms
107
o
()
1. Disable your VM Suspended alarm: a. Select the Training datacenter in the inventory and click the Alarms tab. b. Click Definitions. c. Locate your VM Suspended alarm in the list and right-click it. Select Edit Settings. d. In the General tab, deselect the Enable this alarm check box and click OK. 2. Disable your VM CPU Usage alarm: a. Select your the <your_name>##-l virtual machine in the inventory and click the Alarms tab. b. Click Definitions. c. Right-click your VM CPU Usage alarm and select Edit Settings. d. In the General tab, deselect the Enable this alarm check box and click OK. 3. Log out ofyour vSphere Client session (File> Exit).
(J
o
o o
C~
c:
c
c
108
Lab 16 Using Alarms
o o o o o
o
Lab 17
o o o o o o o o o
Lab 17
109
o
)
1. If you have not already done so, log in to your desktop virtual machine with the domain administrator user name and password that you recorded in "Preparing for the lab." For example, in your lab environment, you might use Remote Desktop Connection to access your desktop virtual machine. 2. From the desktop, select Start > Run and enter the location of the Data Recovery plug-in installer, which you recorded in "Preparing for the lab." 3. Drag the VMwareDataRecoveryPlugin .msi file to your desktop. 4. Right-click the VMwareDataRecoveryPlugin. msi installer and select Install. The VMware Data Recovery Setup wizard appears. If a security waming appears, click Run. 5. In the VMware Data Recovery wizard, click Next. 6. When prompted by the wizard, enter the following values.
Field/setting
Welcome page VMware Data Recovery Information License Agreement Confirm Installation
Value
Click Next. Click Next. Click 1 Agree and click Next. Click Next.
7. After the installation completes, click Close. 8. If your vSphere Client is open, close it. Reopen the vSphere Client and log in to your VMware vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 9. In the menu bar, select Plug-ins > Manage Plug-ins.
(
110 Lab 17 VMware Data Recovery
o o o o o o o o o o o
o
()
1. Go to Home> Inventory > VMs and Templates. 2. Expand your ServerVMs folder. Tbe Data Recovery appliance named VDR-## is in tbis folder. You imported VDR-## in lab 8. 3. Add a destination bard disk to tbe Data Recovery appliance: a. Right-click the VDR-## virtual machine and select Edit Settings. The Virtual Macbine Properties dialog box appears. b. In the Hardware tab, click Add. c. When prompted by the Add Hardware wizard, enter the fo11owing values.
Field/setti ng
DeviceType Select a Disk Create a Disk
Value
Select Hard Disk and click Next. Keep the default and click Next. Type 10 to change disk capacity to 10GB. Under Disk Provisioning, select Allocate and commit space on demand (Thin Provisioning). Leave a11 other options at default values and click Next.
4. View tbe Hardware tab and verify tbat the network adapter is connected to the Production network. If it is not, modify the network adapter connection. 5. Click OK to apply the changes.
o o o
6. Right-click the Data Recovery virtual appliance and select Power> Power On. Wait for it to boot. 7. Click the Data Recovery appliance's Summary tab. Record the IP address ofthis virtual machine: /\"AL . Afa . ;{o . t-~A
111
o o
(J
()
1. Go to Home> Solutions and Applications> VMware Data Recovery. 2. Expand the vCenter Server inventory and select your Data Recovery virtual appliance named VDR-## (where ## is the last two digits ofyour assigned ESXi host). 3. In the Data Recovery window, click Connect. 4. In the Set vCenter Server Credentials dialog box, enter your domain administrator password, which you recorded in "Preparing for the lab," and click OK. The Getting Started wizard appears.
~J 5.
Field/setting
Credentials
Value
Verity that your domain administrator user name and password (hidden with asterisks) are displayed. Click Next. Click the disk drive (added in task 2) and click Format. When the waming message appears, click OK to format the volume. Click Next.
o o c
c c
Backup Destinations
Configuration complete
View the configuration information. Deselect the Create a new Backup job after completion check box and click Close.
c
c:
(~
(~
1. Ifyou are not connected to the Data Recovery appliance, connect to the appliance: a. Go to Home> Solutions and Applications> VMware Data Recovery. b. Expand the vCenter Server inventory and select your Data Recovery virtual appliance named VDR-## (where ## is the last two digits ofyour assigned ESXi host). c. In the Data Recovery window, click Connect. 2. Click the Backup tab.
112
o o o o o o o o o o o o o o o
)
3. Click the New link. The Backup Job wizard appears. 4. When prompted by the Backup Job wizard, enter the following values.
Fleld/setting
Name Virtual Machines
Value
Type Backup for <your_name>##-3 and click Next. Expand the inventory and select the <your_name>##-3 check box. Click Next.
Select /SCSI-O: 1/ and click Next. Click the Select Alllink and click Next. Set Retention Policy to Custom. In More Policy Details, type 2 to change the number of most recent backups to retain. Leave the rest of the fields at their defaults and click Next. Verify the backup job information and click Finish.
Ready to Complete
5. Wait for the backup job to finish by monitoring the status in the Reports tab. Do not proceed to the next task until the backup has completed.
1. Go to Home> Inventory > Hosts and Clusters. 2. Right-click the <your_name>##-3 virtual machine and select Power> Shut Down Guest. 3. When the virtual machine has powered off, right-click it in the inventory and select Delete fromDisk. 4. Go to Home> Solutions and Applications> VMware Data Recovery. 5. In the Data Recovery pane, click the Restore tab. 6. Select the check box next to the <your_name>## -3 virtual machine. A check mark should appear next to the virtual machine name and in each inventory container above the virtual machine. 7. Click the Restore link.
Lab 17 VMware Data Recovery
113
8. When prompted by the Virtual Machine Restore wizard, enter the following the values.
Field/setting
Source Selection Destination Selection Ready to Complete
Value
Select the <yoUf_name>##-3 virtual machine and click Next. Leave the default and click Next. Click Restore.
.......,
)
9. In the Reports tab, monitor the progress of the restore. The restore is complete when no running tasks appear in the Running Tasks panel of the Restore tab. After the restore operation has completed, the virtual machine is restored to the original inventory location. 10. Go to Home> Inventory > Hosts and Clusters. 11. Verify that yOuf virtual machine is restored to the original location in the inventory and that it is poweredon.
(~) "-..,
c
c
c
l
114 Lab 17 VMware Data Recovery
()
o o o o o o o o o o o o o o
)
Lab 18
Lab 18
115
Task 1: Add a second ESXi host to the team vCenter Server system
In tbis task, the ESXi team with the higher-nwnbered ESXi host will remove their host from their vCenter Server instance and add it to the team vCenter Server instance. This task should be done only by the ESXi team working on the higher-nwnbered ESXi host. Student A should do the steps in this task. The ESXi team working on the lower-numbered ESXi host should start with task 2. 1. If it the VMware vSphere Client is not already active, use it to log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters. 3. Remove your ESXi host from the inventory: a . Right-click yOuf ESXi host in the inventory and select Remove. b. Click Yes to confirm the removal. 4. Exit the vSphere Client. 5. Add the ESXi host to the team vCenter Server system: a. Open the vSphere Client. Log in to the team vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." b. Go to Home> Inventory > Hosts and Clusters. c. Expand the inventory. d. Right-click the Lab Servers folder in the inventory and select Add Host. e. When prompted by the Add Host wizard, enter the following values.
c c c c
L
Field/setting
Host na me
Value
Enter the fully qualified host name of the highernwnbered ESXi host. Type root. Enter the fOot password and click Next. If a security alert appears, click Yeso View the information.
Username Password
Host Summary
116
o
()
Field/setting
Assign License
Value
Select the vSphere 4 Enterprise Plus license key. Ifyou see a warning message that the license key that you selected is part of another vCenter Server inventory, click Use key. Leave the default. Select the Training datacenter. Review the configuration summary and click Finish
o
(]
Lockdown Mode Virtual Machine Locadon Ready to Complete
o o o o o o o
()
6. Monitor the progress of the task in the Recent Tasks pane. After the task is finished, your ESXi host appears in the Lab Servers folder in the inventory. 7. Go to Home> Inventory > VMs and Templates. 8. Move virtQal machines <student_name>##-l, <student_name>##-2-RDM, and <student name>##-3 to the LabVMs folder.
iU'''i
The templates that were created using the higher-numbered ESXi host do not appear in the VMs and Templates inventory view. The templates would have to be registered (added into the inventory) with the lower-numbered ESXi host. In this lab, do not necessary to register the templates. Remain logged in to the vCenter Server system of the lower-numbered ESXi team. 9. Before going to task 3, wait for your partner ESXi team to complete task 2.
o o o
1. Ifthe vSphere Client is not already active, use it to log in to your vCenter Server system with the domain administrator user name and password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters. 3. Select the lower-numbered ESXi host in the inventory and click the Configuration tab. 4. In the Hardware list, select Networking. 5. Click the Add Networking link.
Lab 18 Working with Host Profiles
117
6. When prompted by the Add Network wizard, enter the foUowing values.
Field/setting
Connection Type Network Access
Value
Click Virtual Machine. Deselect aU check boxes. No vmnic adapter should be selected.
Type Internal Virtual Machine Network.
Click Finish.
c-=
7. Verify that the new virtual switch is displayed in the Networking pane. 8. Before going to task 3, wait for your partner ESXi team to complete task 1.
~.
c c c
Field/setting
Select Creation Method Specify Reference Host
Value
Click Create Profile from existing host and click Next. Expand the inventory view and click the lowernumbered ESXi host. Click Next.
118
o o o o o o o o o o
()
Field/setting
Profile Details
Value
Type Add InternaI vSwi tch. No description is necessary. Click Next.
Ready to Complete
Click Finish.
To shut down multiple virtual machines at the same time, sort the list of virtual machines by state so that aIl the powered-on virtual machines are sequential in the list. Select the frrst powered-on virtual machine. Rold down the Shift key and click the last powered-on virtual machine in the list. Right-click the last powered-on virtual machine in the list and select Power > Shut Down Guest. 5. Right-click the higher-numbered ESXi host in the vCenter Server inventory and select Enter Maintenance Mode. 6. Click Yes to confrrm the action. 7. Go to Home> Management> Host Profiles. 8. Right-click the Add InternaI vSwitch host profile and select Attach HostlCluster. 9. Expand the inventory and select the higher-numbered ESXi host. 10. Click Attach and click OK. 11 . Select the Add Internai vSwitch host profile.
(J
o o o
f)
Lab 18
119
12. In the Add Internai vSwitch pane, click the Hosts and Clusters tab. 13. Select the ESXi host and click the Check Compliance Now link. Review the compliance failures.
Do this lab as a cluster team. Student A from the lower-numbered ESXi host team should do the steps in this task. 1. Go to Home> Management> Host Profiles. 2. Select the Add InternaI vSwitch hast profile. 3. Click the Hosts and Clusters tab.
rk Nv<-" _ ..so r L--,,r J.." "Q,Ao-" ' .~' . . " te",~A:.-,,\ ':' v 4. Select the ESXi host and click the Apply Profile link. ~ .., ~> '~ ..J/',..__Jr.ftc:. ~ .>e~v,u.. '/
~)<7... e~
12..)- r q;,,:!A
........
....)
5. When prompted for the credentials of a user with permission to join the domain, enter the domain administrator user name and password that you recorded in "Preparing for the lab." 6. Review the configuration changes to be applied and click Finish. 7. In the Recent Tasks pane, monitor the process as it applies changes on the host. 8. In the Hosts and Clusters tab, watch for the ESXi host to change to Compliant. 9. Go to Home> Inventory > Hosts and Clusters. 10. Click the Configuration tab. 11. Click the Networking link. 12. Verify that the internaI virtual switch was created. 13. Take the higher-numbered host out of maintenance mode and power on its virtual machines: a. Right-click the higher-numbered hast in the inventory and select Exit Maintenance Mode. b. Click the Virtual Machines tab. c. Select aH virtual machines in the list. d. Right-click the last virtual machine in the list and select Power> Power On. Leave the vSphere Client open for the next labo , C~
c c
c
c
120
o o o o o o o o o o o o o o o
)
Lab 19
Lab 19
121
o o o o o o o o
o
Task 2: Create a distributed virtual switch for the virtual machine network
In this task, you will create a distributed virtual switch named Production for virtual machine networking. Do this lab as a cluster team. Student A from the lower-numbered ESXi host team should do the steps in this task. 1. Go to Home> Inventory > Networking. 2. Expand the inventory view. 3. Right-click the Training datacenter and select New vNetwork Distributed Switch. 4. When prompted by the Create vNetwork Distributed Switch wizard, enter the following values.
o o o
(~
Field/setting
Distributed Switch Version Name Number of dvUplink Ports
122
Value
Select vNetwork Distributed Switch Version 4.1.0. Type vDS-Ol. Type 2.
Lab 19 vNetwork Distributed Switches
o o o o o o o o o o o o o o o
Field/setting
When do you want to add hosts and their physical adapters to the new vNetwork distributed switch? Host/Physical adapters
Value
Click Add now
Expand the inventory for both ESXi hosts and select the vrnnic for the Production network that you recorded in "Preparing for the lab." Click the View details link to view more information about the vrnnic.
Click Finish.
5. Verify that the following objects appear in the inventory: the distributed virtual switch vDS-O l and the uplink port group vDS-O I-DVUplinks-### (where ### is a number assigned by vCenter Server).
13
GP
13
!n Training
vc-koala01.vmeduc.com
123
Field/setting
Name
Value
Type Production-<your_ name> for the port group name, where <your_name> is your first name. Leave aIl other fields at their default value and click Next. Click Finish.
-'
Ready to Complete
4. Verify that the port group was created in the inventory. 5. Identify use cases for creating multiple port groups to access the same vmnic.
c
c
("
6. Go to Home> Inventory > Hosts and Clusters. 7. Select your ESXi host from the inventory and click the Configuration tab. 8. Click the Networking link. 9. Click the vNetwork Distributed Switch button. 10. Click the information icon to the right ofvDS-Ol to show distributed virtual switch configuration details. 11. In the vDS-OI-DVUplinks pane, expand dvUplinkl to show the vmnic in use for vDS-Ol. 12. Find the name ofyour port group and click the information icon to the right of the port group name. This operation shows details about port group configuration.
(,
c
c
124
o o o
o
Field/setting
Source Network Destination Network
Value
Select Production. Select Production-<your_name> (vDS-Ol). Click Show Virtual Machines.
4. Select the check box next to each virtual machine that is named after you and click OK. 5. Monitor the task in the Recent Tasks pane. Wait for the task to complete. 6. In the inventory, select your port group and click the Virtual Machines tab. 7. Verify that the virtual machines were migrated to the destination network.
o o o o o o o o
J
Task 5: Verify that your virtual machine has proper access to the Production network
In this task, you will verify that your virtual machine can access the Web over the Production network. Students do the steps in this task individually. 1. In the Virtual Machines tab ofthe Production-<your_name> port group, right-click one of the virtual machines that you own and select Open Console. 2. Log in to the guest operating system as Administrator with the password that you recorded in "Preparing for the lab." 3. In Internet Explorer, go to http://www.vmware.com. 4. Verify that you can access the Web site. 5. Exit Internet Explorer. 6. Close the virtual machine's console. Leave the vSphere Client open for the next labo
o o
)
Lab 19 vNetwork Distributed Switches
125
c c c
126
Lab 19
o o o o o o o o o o o o o o o
)
Lab 20
Lab 20
127
(J
(J
1. If the VMware vSphere Client is not already active, use it to log in to the team vCenter Server system with your domain administrator user name and password. Vou recorded this information in "Preparing for the lab."
2. Go to Home> Inventory > Hosts and Clusters.
3. Select your ESXi host in the inventory and click the Configuration tab.
c c c
c
Field/setting
Connection Type Network Access
Value
Click VMkernel. Select the vmnic for the vMotion network that you recorded in "Preparing for the lab."
Network Label
Type vMotion.
Select the Use this port group for vMotion check box.
c c
c
IP Address
Enter the vMotion IP address that you recorded in "Preparing for the lab." Enter the vMotion subnet mask that you recorded in "Preparing for the lab." Confirm the settings and click Finish.
SubnetMask
Summary
8. Verify the configuration information for the new virtual switch in the Networking panel.
128
Lab 20
o o o
o
1. Go to Home> Inventory > Hosts and Clusters. 2. Select each ESXi host and click its Summary tab. 3. View the Processor Type infonnation to verify that the CPUs are compatible. 4. Click your ESXi host's Configuration tab. 5. Verify that a vMotion port group exists and that it is configured with a speed and duplex of 1000Mb, Full Duplex: a. Click the Networking link. b. Click the Virtual Switch button. A vMotion port group should exist and it should be a VMkemel port. c. Click the Properties link next to the vMotion virtual switch. d. Click the Network Adapters tab. In the pane to the right, the configured speed and duplex should be 1000Mb, Full Duplex. e. Click Close to close the vSwitch Properties dialog box. 6. Verify that both ESXi hosts have access to the same shared datastore: a. Select the Lab Servers folder and click the Maps tab. b. In the Map Relationships panel, select Custom Map from the drop-down menu. c. Under Host Options, select the Host to Datastore check box. Deselect the Host to VM check box. d. Under VM Options, deselect every check box. e. Click Apply Relationships. Both ESXi hosts should have access to the same shared datastore for virtual machines, which you recorded in "Preparing for the lab." 7. Verify that both ESXi hosts have access to the same networks: a. Under Host Options, deselect the Host to Datastore check box and select the Host to Network check box. b. Under VM Options, dese!ect every check box. c. Click Apply Relationships. Both ESXi hosts should have access to the same networks.
o o o o o o
()
o o o o
()
Lab 20
129
1. Go to Home> Inventory > VMs and Templates. 2. In your LabVMs folder, right-click the <your_name>##-2-RDM virtual machine and select Edit Settings. 3. Verify that the virtual machine's floppy drive is not connected to a local device and does not have an image in a local datastore defined: a. In the Hardware Iist, verify that the Summary column for Floppy Drive 1 shows Client Deviee. b. If the Summary column does not show Client Deviee, select Floppy Drive 1 in the list and click Client Deviee. 4. Verify that the virtual machine's CDIDVD Drive 1 is not connected to a local device and does not have an image in a local datastore defmed: a. In the Hardware list, verify that the Summary column for CDIDVD Drive 1 shows Client Deviee. b. If the Summary column does not show Client Device, select CDIDVD Drive 1 in the li st and click Client Deviee to remove existing connections. 5. In the Hardware list, find Network Adapter 1. Verify that the virtual machine is either disconnected from the network or connected to a network accessible by the destination ESXi ho st (your partner's ESXi host). 6. Check the Hardware list for hard disks that are of type Mapped Raw LUN (and that are not accessible by the destination host): a. Ifyou have such a disk, select the mapped raw LUN and click Remove. b. In the Removal Options panel, leave the default Remove from virtual machine. 7. Verify that CPU affinity is not set: a. Click the Resources tab and select Advanced CPU. b. If the Scheduling Affinity field displays a number, delete the number. 8. Click OK to apply aH virtual machine changes.
o o c c
o
o
c c c
c
c
130
Lab 20 Migrating Virtual Machines
o o o o o o o o
o
Field/setting
Select Migration Type Select Destination
Value
Select Change hosto Expand the inventory view and select the ESXi host ofyoUf partner team. The migration requirements will be validated. If the validation does not succeed, you will receive warning or error messages and will be unable to continue with the migration until the errors are resolved.
o o o o o o
)
One reason that the validation might not succeed is if the virtual machine's disk is not on the shared datastore. Ifthis is the case, use Storage vMotion to migrate the disk to the shared datastore first and then retry the vMotion migration. Select Resource Pool vMotion Priority Ready to Complete Select the ESXi host name. Select High priority (Recommended). Click Finish.
4. In the Recent Tasks pane, monitor the progress of the virtual machine migration. 5. Verify that yOuf virtual machines appear under yOuf partner team's ESXi host in the inventory.
Lab 20
131
o o o
o
Field/setting
Select Migration Type Select Destination
Value
Click Change hosto Expand the inventory view and select the lower-numbered ESXi host. The migration requirements will be validated. If the validation does not succeed, you will receive waming or error messages and will be unable to continue with the migration until the errors are resolved.
o
o
o o
o
2. Right-click <yoUf_name>##-1 in the inventory and select Power> Shut Down Guest. 3. Right-click <your_name>##-2-RDM in the inventory and select Power> Shut Down Guest. 4. After <your_name>##-2-RDM shuts down, right-click it in the inventory and select Remove from Inventory. 5. Click Yes to confirm the removal. Leave the vSphere Client open for the next labo
o
0
c c:
132
Lab 20 Migrating Virtual Machines
o o o o o
o
Lab 21
o
o
o o o o o o o
CJ
133
1. If the VMware vSphere Client is not already active, use it to log in to the team vCenter Server system with yOuf domain administrator user name and password. Vou recorded this information in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters. 3. Right-click the Training datacenter and select New Cluster. 4. When prompted by the New Cluster wizard, enter the following values.
Field/setting
Name Cluster Features Automation level Migration threshold
Value
Type Lab Cluster. Select Turn On VMware DRS. Click Manual. Drag the slider ail the way to the right to Aggressive. Leave the default. Leave the default. Leave the default.
c
c
c
c c c
(~
5. Verify that the cluster appears in the Rosts and Clusters inventory view.
134
Lab 21
o o
o
o
o
o o o o o o
()
6. Select Lab Cluster in the inventory and click the Summary tab. 7. View the general information and DRS information. Wait for your partner ESXi team to add their host to the ORS cluster. 8. Verify that you have two ESXi hosts in your ORS cluster.
1. Go to Home> Inventory > VMs and Templates. 2. Apply the ORS recommendation when a virtual machine is powered on: a. Verify that your <your_ name>##-l virtual machine is powered off. If it is not, shut it down. b. Right-click <your_name>##-l and select Power> Power On. With ORS running in manual mode, when a virtual machine is powered on ORS will recommend a ho st on which to place the virtual machine.
o o o
C.
When prompted with a host recommendation, select the check box for the lower-numbered ESXi host and click Power on.
Lab 21
135
3. Generate CPU activity in your virtual machines: a . Open a console to <your_ name>##-l and log in as Administrator with the virtual machine Administrator user name and password that you recorded in "Preparing for the lab." b. Run the cpubusy. vbs script by right-clicking the script on the desktop and selecting Open with Command Prompt. Let the script run continuously. 4. Wait for all the members ofyour cluster team to complete step 3. 5. Go to Home> Inventory > Hosts and Clusters. 6. Select Lab Cluster in the inventory and click the Summar 7. 8. Click the View Resource Distribution Chart link. This chart displays the CPU or memory use per host. Point to each colored square. You see information on how much of the entitled resource (CPU or memory) each virtual machine is using. 9. Close the chart window. 10. Click the DRS tab. 11. Click the Run DRS link in the upper-right corner to refresh the view. It normally takes 3-5 minutes to see migration recommendations.
(J
o
(J
c
(j
c c c
c c
C
M'in.Ui
Do not apply recommendations until everyone on your team can see the effect. 2. When at least two recommendations appear, click Apply Recommendations. 3. Monitor the migrations in the Recent Tasks pane and wait for each virtual machine migration to complete. 4. Click the Virtual Machines tab. 5. Sort the virtual machines by ESXi host on which they reside. To do this, click the Host column heading. Identify the virtual machines that each ESXi host is running. 6. Click the Summary tab. View the VMware DRS panel. Is your ~ed or imbalanced? (Allow approximately 5 minutes for DRS to evaluate the state of the cluster.)
136
Lab 21
o o o o o o o o o o o o o o o
()
7. Click the View Resource Distribution Chart link to confinn load distribution.
9. Stop each instance of the cpubusy. vbs script in each virtual machine by pressing Ctrl+C in each cpubusy window.
10. Close aIl virtual machine consoles.
1. Verify that each virtual machine that you own is mnning on a different ESXi hosto If the virtual machines that you own are running on the same ESXi host, choose one to migrate to the other ESXi host in the cluster before you go to step 2. Ifyou have one virtual machine on each ESXi host in the cluster, no action is necessary.
2. Right-click Lab Cluster in the inventory and select Edit Settings. The Lab Cluster Settings dialog box appears.
3. In the left pane, select VMware DRS > Rules and click Add.
4. Enter the following values in the Rule dialog box. Close the Lab Cluster Settings dialog box when you are done.
Value
Type Colocate <your_first_name> Ws. Select Keep Virtual Machines Together. Click Add.
In the Virtual Machines dialog box, select the check box next to each of the virtual machines that you own named <Y0uf_ name>##-#.
Click OK.
5. In the Rule dialog box, click OK. 6. Click OK to close the Lab Cluster Settings dialog box.
Lab 21
137
7. Click the Lab Cluster DRS tab. If the view is not Recommendations, click Recommendations. Wait for a DRS recommendation to appear for your virtual machine.
ideili
Wait for everyone in your cluster team to complete step 7. Do step 8 as a cluster team. Student A from the lower-numbered ESXi host should do step 8. 8. Click Apply Recommendations and monitor the Recent Tasks pane as the recommendation is applied. The virtual machines associated with your affinity mIe will be migrated to one of the two hosts in the DRS cluster. Students should do steps 9-13 individually. 9. Click the Virtual Machines tab. 10. Click the Host column heading to sort the virtual machines by ESXi host on which they reside. The virtual machines that you own should be running on the same ESXi host. 11. Right-click Lab Cluster in the inventory and select Edit Settings. 12. In the left pane, select VMware DRS > Rules. 13. Deselect the affinity mie that you created to disable it.
0
CJ
0
C 0
c
c c
To delete an affinity rule, you select the rule and click Remove. For this lab, keep the rule disabled. Leave the Lab Cluster Settings dialog box open for the next task.
c
c
138
Lab 21
o o o o o o o o o o o o o o o
Value
TypeSeparate <your_first_name> VMS. Select Separate Virtual Machines. Click Add.
In the Virtual Machines dialog box, select the check box next to each of the virtual machines that you own named <Y0uf_ name>##-#.
Click OK.
3. In the Rule dialog box, click OK. 4. Click OK to close the Lab Cluster Settings dialog box. 5. Click the Lab Cluster DRS tab. The default view should be Recommendations. If it is not, click the Recommendations button. 6. Click the Run DRS link to make DRS evaluate the state of the cluster and make recommendations. A recommendation to separate yOuf virtual machines should appear. If it does not appear, check the rules that you created to verify the accuracy of inputs from step 2.
1d," i
Wait for everyone in yOuf cluster team to complete step 6. Do step 7 as a cluster team. Student B from the lower-numbered ESXi host team should do step 7. 7. Click Apply Recommendations. 8. Monitor the Recent Tasks pane as the recommendations are applied. The virtual machines with anti-affinity rules applied to them will be migrated to another ESXi host in the cluster. Students should do steps 9-15 individually. 9. Click the Virtual Machines tab. 10. Click the Host column heading to sort the virtual machines by ESXi host on which they reside. The virtual machines you own should be running on the different ESXi hosts.
Lab 21
139
11. Right-c1ick Lab Cluster in the inventory and select Edit Settings: 12. In the left pane, select VMware DRS > Rules. 13. Deselect the anti-affinity mIe that you created to disable it. Click OK. 14. Press Ctrl+C in each cpubusy window to stop the 15. Close the virtual machine console. 16. Log out ofyour vSphere Client session (File> Exit.) 17. Log out ofyour desktop virtual machine.
cpubusy. vbs
(J
o
(J
c
c c
(~
c
140
Lab 21
()
o
C)
Lab22
o o o o o o o
;,')
'-J
()
Lab 22
141
Intelligent Platfonn Management Interface/ Integrated Lights-Out (IPMI/iLO) user name IPMIIiLO user password Baseboard management controller (BMC) IP address of the lower-numbered ESXi host BMC MAC address of the lower-numbered ESXi host BMC IP address of the higher-numbered ESXi host BMC MAC address of the higher-numbered ESXi host
o
()
Task 1: Log in to your vCenter Server system and start the vSphere Client
In this task, you will log in to the desktop of your vCenter Server system. Then you will use the VMware vSphere Client to log in to the team vCenter Server system with the Administrator account. Students should do the steps in this task individually. 1. Log in to the desktop ofyour vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. Use the vSphere Client to log in to the team vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab."
o o o o o o
o
(...J
142
Lab 22 VMware Distributed Power Management
o o o
()
Field/setting
IPMIIiLO user Dame IPMIIiLO user password BMC IP Address BMC MAC Address
Value
See "Preparing for the lab." See "Preparing for the lab." See "Preparing for the lab." See "Preparing for the lab."
o o o o o o o o o o o
)
1. Right-click Lab Cluster in the inventory and select Edit Settings. The Lab Cluster Settings dialog box appears. 2. Select the Turn on VMware HA check box. 3. In the left pane, select VMware HA. 4. Click Percentage of cluster resources reserved as failover spare capacity and type 50. 5. Do not click OK. 6. In the left pane, select VMware DRS and click FuUy Automated. 7. In the left pane, select Power Management. 8. Click Automatic. 9. Set DPM Threshold to Aggressive by moving the slider bar aH the way to the right. 10. Click OK. 11 . Read the warning in the Confirm Enable Power Management window and click OK. 12. Monitor the Recent Tasks pane. The cluster will configure the ESXi hosts for VMware High Availability before processing VMware DPM requests. Wait for these tasks to complete before going to the next task.
Lab 22
143
(J
o o
id"i
Migrate only virtual machines named <yoUf_name>##-#. If other virtual machines exist on the higher-numbered ESXi host, do not migrate them.
C.
When prompted by the Migrate Virtual Machine wizard, enter the fo11owing values.
Field/setting
Select Migration Type Select Destination
Value
Select Change host. Expand the inventory view and select the lower-numbered ESXi host. Migration requirements are validated. If the validation does not succeed, you will receive waming or error messages and will be unable to continue with the migration until the errors are resolved.
c
{
' ........
2. Ifthere are virtual machines that are still powered on on the higher-numbered ESXi host, shut down these virtual machines. 3. Select the lower-numbered ESXi host in the inventory. 4. Click the Virtual Machines tab. Shut down a11 virtual machines on this host.
\
....
144
Lab 22
()
5. Allow everyone in the cluster team to monitor the Recent Tasks pane. After the last virtual machine is shut down, verify that the host automatically tries to enter standby mode. Did the host enter standby mode? If not, what can you check to obtain more information to help you diagnose the problem?
o o o o o o o o o o
)
It will take several minutes for the ESXi host to enter standby mode. After the lower-numbered ESXi host has entered standby mode, notice that the virtual machines have been migrated back to the higher-numbered ESXi host. In general, if sufficient excess capacity is found, VMware DPM places one or more hosts in standby mode after migrating their virtual machines to other hosts.
1. Select the higher-numbered ESXi host in the inventory and click the Virtual Machines tab. 2. Power on one of the <yOUf_ name>##-# virtual machines that you powered off earlier. 3. Allow everyone in the cluster team to monitor the Recent Tasks pane. Did the lower-numbered ESXi host exit standby mode? What condition caused the host to exit standby mode?
145
6. Click OK. 7. On both ESXi hosts, power on only the virtual machines named <student_name>##-#. Leave ail other virtual machines powered off. Leave the vSphere Client open for the next labo
o o o o o
o
o
o
r~
-..,
\ .....J
(
146 Lab 22
VMware Distributed Power Management
o o o
()
Lab23
o o o o o o
() ()
o o
)
Lab 23
147
o
(J
o
(~
c c
\il 1 III
l
En.~ . __._.... _
sc-goos.o7.vmtduCot_ sc-goou06.vmtduu..
1R~le
l'I1mary Primary
.. .." ..." ..
~ ~
_-----
Host.c-goo..07.vmedu(.com currtntly hl! no management nttworlt redRlfty liost sc-goose06.vmedu(.com currently has no malllgement nttworltrtlirldarq
The errors indicate that the ESXi hosts in the c1uster have no management network redundancy. That is, each ESXi host has a single management network port configured for the cluster. VMware HA will still work if an ESXi host is configured with one management network port, but a second management network port is necessary for redundancy. For this lab, no action is necessary. 12. Click Close.
148
Lab 23
o o o o o o o o o o o o o
)
In this task, you will verify that VMware HA works properly. Do this task as a cluster team. Student A from the higher-numbered ESXi host team should do the steps in this task.
1. Simulate a host failure by rebooting one of the hosts in the cluster: a. Right-click one of the ESXi hosts in the inventory and select Reboot. b. When a message wams you that your host is not in maintenance mode, click Yes to reboot. c. Type Testing VMware HA as the reason for rebooting and click OK. 2. Select Lab Cluster in the inventory and click the Tasks & Events tab. 3. Click Events to display the Events view. 4. From the drop-down menu, select Show Cluster Entries to monitor the events for your VMware HA cluster. The cIuster entries are sorted by time. Notice the entries made by VMware HA when the host failure was detected. 5. Select the running ESXi host in the cluster and click the Virtual Machines tab. The virtual machines that were running on the rebooted ESXi host should now be running on the remaining host in the cIuster. 6. Monitor the vCenter Server inventory until you see that the ESXi host is available. The ESXi host that was rebooted will be unavailable for a few minutes.
()
Lab 23
149
o
o
o
o
o o o o o
~...,
C
150
Lab 23
o o o o o o o o o o o o o o o
)
Lab 24
1. Use the Resource Allocation tab to determine resource use. 2. Manage VMware HA slot size. 3. Configure a VMware HA cluster with strict admission control. 4. Configure a VMware HA cluster with flexible admission control.
Lab 24
151
o o o o
0
YOUT
view should
~ .... ~~~~
I:PU
~~~'
Memory Total Capacity: Reserved C""ac~y : Avallable Capacly:
3430MB 2387.85 MD 1042.15 MD
o
o
Yi"w:
~
K enOl-l
'III10H '",,01-3
Memoryl istoragel
rN'am G) a)
~ KenOI-3
SliirsV iIUe
1000
1000 1000 1000
1%SIiii'~.J' Type
IZ
lZ lZ lZ N! A NIA NIA NI A
a)
o o
o
4. Record the following information: CPU total capacity (MHz) for the cIuster
Z[? .A G S
CPU reserved capacity (MHz) for the cIuster _ _ _0'--_ _ _ __ CPU available capacity (MHz) for the cIuster _---"1.,"'-F_1'-~_B ____ Average worst case CPU requirement (MHz) for a virtual machine _ _--L-<=-=-'-_-+__ Memory total capacity (MB) for the cIuster
.AD
(.J
SA lt
1'-e>
Memory reserved capacity (MB) for the cIuster ___ 0_ _ _ _ _ __ Memory available capacity (MB) for the cluster ---=:.-'-O_S_'\_1_ _ __ Average worst case memory requirement (MB) for a virtual machine ~d,+-"o<--.::: 'V ,-~~ _ __ 5. Based on the CPU numbers, how many more average virtual machines do you think that this cIuster can support? /1,3
c c
C
152
o o
o
6. Based on the memory numbers, how many more average virtual machines do you think that this cluster can support?
7. Ifthese two numbers are different, what must you do to your cluster resources to get to the higher number?
o o o o o o o e) o o
( )
ZI' Pl..z...
)fJ n6
b. Click OK to dismiss the window. 3. Set the CPU reservation on the virtual machine <your_name>##-3: a. Right-click <your_name>##-3 in the inventory and select Edit Settings. b. Click the Resources tab. c. In CPU Reservation, type 512MHz. d. Click OK to commit the change. 4. View slot information for this cluster: a. In the Summary tab of the cluster, click the Advanced Runtime Info link. Did changing the reservation change the slot size in comparison with the value that you recorded in step 2? How much CPU, virtual CPU space, and RAM does your slot require now?
Lab 24
153
5. Use the advanced VMware HA settings to enforce a slot size: a. Right-click Lab Cluster in the inventory and select Edit Settings. b. Select VMware HA from the list and click Advanced Options. c. In the Advanced Options (HA) window, enter the following option-value pair.
o
(J
Option
das.slotCpulnMHz
Value
300
o
(J
d. Click OK to close the Advanced Options (HA) window. e. Click OK to commit the changes. 6. View slot information for this cluster: a. In the Summary tab of the cluster, click the Advanced Runtime Info link. Compare the CUITent value with what you recorded in step 4.
o o
o
c
c
(
How much CPU, virtual CPU space, and RAM does your slot require now?
b. Click OK to dismiss the window. 7. Remove the advanced VMware HA setting: a. Right-click Lab Cluster in the inventory and select Edit Settings. b. Select VMware HA from the list and click Advanced Options. c. Select das.slotCpuInMHz and deI ete the entry. d. Click OK to close the Advanced Options (HA) window. e. Click OK to commit your changes. 8. Remove the CPU reservation on <your_name>##-3: a. Right-click <your_name>##-3 in the inventory and select Edit Settings. b. Click the Resources tab. c. In CPU Reservation, type 0 (MHz). d. Click OK to commit the change.
\.....
(~
154
o o
()
VMware vSphere to calculate slots. That is, vSphere calculated space for a virtual machine to run, based on the largest CPU and memory allocation across ail virtual machines. This task will show you how strict admission control works. In this task, you will assign enough memory reservation to force Lab Cluster to have eight slots cluster-wide. That is, Lab Cluster will have four slots per ESXi host. Do this task as a cluster team. Student B from the higher-numbered ESXi host team should do the steps in this task. 1. Select Lab Cluster in the inventory and click the Virtual Machines tab. Shut down aIl virtual machines. 2. After all virtual machines are powered off, click the Resource Allocation tab. 3. Identify the total memory capacity and divide it by the number of ESXi hosts in the cluster. The result is the usable memory per ESXi host. For example, ifyou have two ESXi hosts in your cluster and the total capacity for memory is 3,410MB, then 3,410 /2= 1,705. How much available memory is there per ESXi host?
ResourceAllocation
Memeny
o o o o o o o o o
()
)
/1 D
>'" :}- /
i
l.,
2-~tf
'd1ill
The value for Total Capacity that you see in this step might differ from what you see in the screenshot. 4. Assign memory reservations to virtual machines to configure four slots per ESXi host. To keep this exercise simple, you will reserve 1,024MB of memory resources. That is, you will reserve 256MB for each of four virtual machines: a. Right-click each <your_name>##-l virtual machine listed in the Resource Allocation tab and select Edit Resource Settings. b. Type 256 (MB) for the memory reservation. c. Click OK to commit the changes. 5. Right-click one <your_ name>##-l virtual machine and select Power> Power On.
155
6. To see the effect that powering on this virtual machine had on your cluster, click the Lab Cluster Summary tab and click Advanced Runtime Info.
In the space below, record the values for Siot size, Total slots in cluster, Used slots, and
Available slots.
o o
(J
(J
2.,(,
,>",
1'lk2...A
/f./C(?,J
~4 -;rr16
/11
7. Click OK to close the window. 8. Power on the remaining <your_name>##-l virtual machines. Click Advanced Runtime Info to see the number of available slots change. 9. Try to power on any one of the <your_name>##-3 virtual machines. Was your virtual machine allowed to power on? Why or why not?
o o
c
C
cluster team. Student A from the higher-numbered ESXi host team sbould do the steps in this task. 1. Right-click Lab Cluster in the inventory and select Edit Settings. 2. Select VMware HA from the list. 3. Set Admission Control Policy to Percentage of c1uster resources reserved as failover spare capacity and 25%. 4. Click OK to accept your changes. 5. Click Lab Cluster's Summary tab. 6. Record the following values from the VMware HA panel. Admission Control Current CPU Failover Capacity Current Memory Failover Capacity Configured Failover Capacity
(---
156
Lab 24
o o o o o o o o o o
()
7. Try to power on each <your_name>##-3 virtual machine (for example, GregOI-3). Did aIl these virtual machines start? ____-'jTU~4>'----
If any virtual machines did not power on, what can you do to allow them to power on?
8. Select Lab Cluster in the inventory and click the Summary tab. Record the following values from the VMware HA panel. Current CPU Failover Capacity Current Memory Failover Capacity Configured Failover Capacity Compare the values you recorded in step 6 to the values now displayed in the VMware HA panel. 9. Click the Resource Allocation tab. 10. Click the Memory button to enter Memory view. 11 . Remove the virtual machine memory reservation for each <your_name>##-l virtual machine: a. Click the Reservation - MB column heading. This will sort the memory reservations numerically. b. Select a virtual machine that has a memory reservation. c. Select the memory reservation value (for example, 256) and type O. Press Enter. d. Select another virtual machine. Remove the reservation as you did in step c. 12. Edit the settings of the cluster to allow the number of running virtual machines to exceed the failover capacity of the cluster: a. Right-click the cluster name and select Edit Settings. b. In the left pane, select VMware HA.
o o
(
c. In the Admission Control panel, select Disable: Power on VMs that violate availability constraints. d. Click OK to commit your changes
Lab 24
157
13. Select Lab Cluster's Summary tab and record the following values from the VMware HA panel. Current CPU Failover Capacity Current Memory Failover Capacity Configured Failover Capacity
i!)r
tf5
N' {j>I
Compare the values you recorded in step 8 to the values now displayed in the VMware HA panel. Keep the vSphere Client open for the next labo
,)
c:
158
Lab 24
o o o o o o o o
o
Lab25
o o o
)
o o
159
0 0
o o o
o
# tail -f /var/log/vmware/aam/vmware_<highernumbered_host_name>.log
Example:
# tail -f /var/log/vmware/aam/vmware_sc-plum02.1og
160
Lab 25 (Optional) Configuring VMware High Availability Network Redundancy
c
1
\..~
o o o
()
4. Prepare to time how long VMware HA takes to detect a failure. Designate one ofyour team members to time, in seconds, how long the failure detection process takes. 5. Simulate a host failure by rebooting the lower-numbered ESXi host: a. Right-click the lower-numbered ESXi host in the inventory and select Reboot. b. When a message wams you that your host is not in maintenance mode, click Yes to reboot. c. Type Testinq VMware HA as the reason for rebooting and click OK. How long did VMware HA take to detect the failure? _ _ _ _ _ __ Wait for the lower-numbered ESXi host to finish booting. 6. Continue to monitor the log file on the higher-numbered host and verify that the cluster reconnects. Leave the log monitoring active. You will use it again in task 6.
o o o o o o o o o o o
Student A from the lower-numbered ESXi host should do the steps in this task. 1. Right-click Lab Cluster in the inventory and select Edit Settings. 2. Select Cluster Features. 3. Deselect the Turn On VMware HA check box and click OK. 4. Wait until the Unconfiguring HA tasks in the Recent Tasks pane complete. 5. Right-c1ick Lab Cluster in the inventory and select Edit Settings. 6. Select Cluster Features. 7. Select the Torn On VMware HA check box. 8. Select VMware HA and click Advanced Options. 9. In the Advanced Options (HA) dialog box, type this option-value pair:
das.failuredetectiont~e
30000
10. Click OK in the Advanced Options (HA) dialog box. 11. Click OK to commit the changes. 12. Wait until the Configuring HA tasks in the Recent Tasks pane complete. 13. Test the configuration as you did in task 2. Did the time required to record the failed node change to 30 seconds? _ _ _ _ _ __
Lab 25 (Optional) Configuring VMware High Availability Network Redundancy
161
o
(]
5. Select vMotion in the Configuration colomn of the Ports pane and click Edit.
6. Select the Management traffic check box and click OK.
o
o u
(j
0 (J
8. In the Cluster Default Settings panel, change the host isolation response to Leave powered on.
9. Click OK to apply the new settings. Wait until the Configuring HA tasks in the Recent Tasks pane complete.
c c
162
Lab 25
o o o o o
()
In this task, you will test cluster behavior after network isolation is detected. Do this task as a cluster team. Student B from the lower-numbered ESXi host team should do the steps in this task. 1. Select the higher-numbered ESXi host in the inventory and click the Virtual Machines tab. 2. Migrate aU virtual machines named <student_name>##-l to the lower-numbered ESXi host in the cluster. 3. Record the ESXi host name the virtual machines were migrated to: _ _ _ _ _ __ 4. Ifyou closed the SSH session to the lower-numbered ESXi host after task 2, open your SSH client. Log in as root to the lower-numbered ESXi host with the root password that you recorded in "Preparing for the lab." 5. From the SSH session of the lower-numbered ESXi host, disable the altemate VMware HA heartbeat port, vMotion. Type this command:
# esxcfg-Vomknic -D vMotion
6. Select Lab Cluster in the inventory and click the Virtual Machines tab. 7. Monitor the running virtual machines for the next several minutes. IfVMware HA can still communicate between the nodes in the cluster, aIl virtual machines will remain powered on. 8. Access the console interface of the lower-numbered ESXi host (for example iLO or DRAC). Ask your instructor for instructions before you do this step. 9. Disable the management network interface on the lower-numbered ESXi host: a. Go to the console of the lower-numbered ESXi host and press F2. b. Enter the root password for the ESXi host, using the password that you recorded in "Preparing for the lab." c. ScroU down the list and select Disable Management Network. Press Enter. d. Press FIl to disable the management network. Leave the ESXi console open. 10. Monitor the log file messages in the SSH session of the higher-numbered ESXi host. And monitor the inventory in the vSphere Client. Wait for 2 minutes. 11. When the lower-numbered ESXi host stops responding, check the power status of the <your_name>##-l virtual machines. Are aU virtual machines powered on and running on the same ESXi host that you recorded in step 3?_ _ _ _ __ If you answered yes, the task was done correctly. If the virtual machines have been powered off and are being restarted on another cluster node, verify that you executed task 5 correctly. Ifyou fmd that the options are not set correctly, do tasks 5 and 6 again.
o
o
o o o
()
o
J
Lab 25
163
12. Reenable the management network interface on the lower-numbered ESXi host: a. Retum to the console of the lower-numbered ESXi host. b. ScroU down and select Enable Management Network. Press Enter. c. Press FIl to enable the management network. 13. From the SSH session on the lower-numbered ESXi host, reenable the secondary interface on the lower-numbered ESXi host. Type the following command:
o
0
(
# esxcfg-v.mknic -e vMotion
14. Exit the SSH session. 15. Close the ESXi host console. 16. Press Ctrl+C to stop log monitoring in the SSH sessions and exit the SSH session. 17. Reenable the VMware vMotion VMkemel port for each ESXi host in the inventory: a. Select an ESXi host. b. Click the Configuration tab and click the Networking link. c. Select the virtual switch with the vMotion VMkemel port on it and click Properties. d. Select vMotion in the Configuration column of the Ports pane and click Edit. e. Select the vMotion and Management traffie check box and click OK.
f. Click Close to exit the vSwitch Properties dialog box.
o o
(J
c
c c
164
Lab 25
()
o
()
Lab26
o o
()
o o o
)
)
'Ui1i
Not all c1assroom lab environments support VMware FauIt Tolerance. If the hardware in your c1assroom does not support FT, do the exercise with the FT simulation provided by yOUf instructor. Adobe Flash Player 8 or later is required to view the simulation.
o o
Lab 26
165
(
'-"
c::
c
{
Task 2: Activate FT
In this task, you will enable FT on a virtual machine. Students assigned to a single ESXi host should work together to complete this task. Student B should do the steps in this task. 1. If the vSphere Client is not already active, use the vSphere Client (from your vCenter Server system desktop) to log in to the team vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters. 3. Select a virtual machine in the inventory and verify that it meets the requirements for FT, as outlined in the lecture book.
'---'
166
Lab 26
o o o o o o o o o o o
I~
4. Right-click the virtual machine and select Power> Shut Down Guest. Click Yes to confirm shutdown. 5. Right-click the virtual machine and select FauU Tolerance >Turn On FauU Tolerance. 6. Read the waming window and click Yes to confirm that you want to tom on FT. 7. Monitor the Recent Tasks pane while VMware High Availability is tuming on FT. 8. After the tasks complete, view the information in the FauU Tolerance panel on the Summary tab of the virtual machine. On which host is the primary virtual machine? _ _ _ _ _ _ _ _ _ _ __ On which host is the secondary virtual machine? _ _ _ _ _ _ _ _ _ __ 9. Power on the virtual machine and observe how the information in the FauU Tolerance panel changes. 10. Click Lab Cluster in the inventory and click the Virtual Machines tab. Notice that both the primary and the secondary virtual machines are displayed in the list.
Task 3: Test FT
In this task, you will test the FT configuration. Stodents assigned to a single ESXi host should work together to complete this task. Stodent A should do the steps in this task. 1. Select Lab Cluster in the inventory and click the Virtual Machines tab. 2. Open consoles to the primary and the secondary virtual machines. Arrange the consoles side by side. Log in to the primary virtual machine as user Administrator. 3. In the primary virtual machine, open a Command Prompt window and type ipconfig. What is the IP address of the primary virtual machine? _ _ _ _ _ _ _ _ _ _ __ 4. Start a continuous ping to your ESXi host:
# ping -t <ESXi_host_name>
5. In the inventory, right-click your virtual machine and select FauU Tolerance> Test Failover to simulate a virtual machine failure. 6. Quickly view the virtual machine consoles side by side and watch what happens over the next couple of minutes. (Pay special attention to the console title bars.) What did you observe during the test? Did the ping operation see an increase in its TTL value during the failover? 7. Click the Lab Cluster's Virtual Machines tab. View the host information displayed for the primary and the secondary virtual machines.
o
)
Lab 26
167
8. In the Virtual Machines tab, double-click the primary virtual machine to open the virtual machine's Summary tab. View the FT information. 9. Access the console of the primary virtual machine. Press Ctrl+C to stop the continuous pings. Close the consoles.
(J
Task 4: Disable FT
In this task, you will disable FT for the virtual machine. Students assigned to a single ESXi host should work together to complete this task. Student B should do the steps in this task. 1. In the inventory, right-click the protected virtual machine and select Fault Tolerance. 2. Click Thrn Off Fault Tolerance. A waming message appears. Read the waming message and click No. 3. Right-click the protected virtual machine and select Fault Tolerance. Select Disable Fault Tolerance. When a waming message appears, read it and click No. What is the difference between Thrn Off Fault Tolerance and Disable Fault Tolerance?
o o
4. Tum off FT. Right-click the protected virtual machine and select Fault Tolerance> Torn Off Fault Tolerance. At the waming message, click Yeso 5. Verify that the Fault Tolerance pane on the Summary tab is no longer present. Leave the vSphere Client open for the next labo
c
(~
L
168
Lab 26 Configuring VMware Fault Tolerance
o o o o o o o o o o
()
I~
Lab27
o
) )
169
Setup language Location of vCenter Server installation software Shared repository for VMware ESXi patches
o
o
o o o o o o c c
c
(-'
Exolore medl;!
UUllly
Agent pre=lJog@de Ched
4. Click the vCenter Update Manager link. 5. When prompted by the vCenter Update Manager installation wizard, enter the following values.
\......
170
Lab 27
o o o
o
Field/setting
Setup Language
Value
Select the setup language that you recorded in "Preparing for the lab." Click Next. Click Next. Select 1 accept the terms in the license agreement and click Next. Enter the fully qualified domain name of the team vCenter Server system that you recorded in "Preparing for the lab." Enter the Administrator user name and password that you recorded in "Preparing for the lab" and click Next.
o o o o o o o o o o
)
)
Database Options
Select Install a Microsoft SQL Server 2005 Express instance (for small scale deployments) and click Next. Accept the default values. Click Next. Accept the default values and click Next. If a warning describing a free space problem appears, click OK.
Click Install.
6. After the program is installed, click Finish. Close the VMware vCenter Installer window.
a. Open the vSphere Client and log in to your team vCenter Server system as user
Administrator, with the password that you recorded in "Preparing for the lab."
b. In the menu bar, select Plug-ins > Manage Plug-ins.
c. Under Available Plug-ins in the Plug-in Manager window, click the Download and Install
link.
Lab 27 VMware vCenter Update Manager
171
d. When prompted by the VMware vCenter Update Manager Client 4.1 wizard, enter the following values. Field/setting Setup Language Value Select the setup language that you recorded in "Preparing for the lab." Click Next. Select 1 accept the terms in the Iicense agreement and click Next. Click Install.
o
o o o o
o
0 0
0
security warnings for "<host_name>" to prevent this warning from being displayed in the future. g. Click Ignore to proceed with the connection. h. Verify that the Update Manager plug-in was enabled.
i.
Click Close to close the Plug-in Manager window. click the task and click Cancel. Keep the vSphere Client open.
j. Ifyou see the Download Patch Definitions task running in the Recent Tasks pane, right-
o o
1. If the vSphere Client is not already active, use the vSphere Client (from your vCenter Server system desktop) to log in to the team vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. Go to Home> Inventory > Hosts and Clusters.
c c
172
Lab 27
o o o o o o o o o o o o o o o o
3. Right-click Lab Cluster in the inventory and select Edit Settings. The Lab Cluster Settings dialog box appears. 4. In the left pane, select Cluster Features. Select the Torn On VMware DRS check box. 5. In the left pane, select VMware DRS. Select Fully Automated. This operation ensures that DRS will migrate virtual machines to other nodes in the cluster. 6. In the left pane, select VMware HA. Verify that Disable: Power on VMs that violate availability constraints is selected. If it is not, select it now. 7. ClickOK. 8. Select Lab Cluster in the inventory and click the Resource Allocation tab. 9. Verify that no CPU and memory reservations are assigned to the virtual machines. Removing CPU and memory reservations is necessary for this training environment. In a production environment, you might not have to remove CPU or memory reservations.
1. If the vSphere Client is not already active, use the vSphere Client (from your vCenter Server system desktop) to log in to the team vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. In the vSphere Client menu bar, select Plug-ins > Manage Plug-ins. 3. Under Available Plug-ins in the Plug-in Manager window, click the Download and Installlink. 4. When prompted by the VMware vCenter Update Manager Client 4.1 wizard, enter the following values.
Field/setting
Setup Language
Value
Select the setup language that you recorded in "Preparing for the lab." Click Next. Select 1 accept the terms in the Iicense agreement and click Next. Click Install.
Lab 27
173
5. When the installation completes, click Finish. 6. When the security waming appears, select Install this certificate and do not display any security warnings for "<host_name>" to prevent this waming from being displayed in the future. 7. Click Ignore to proceed with the connection. 8. Verify that the Update Manager plug-in was enabled. 9. Click Close to close the Plug-in Manager window. 10. Ifyou see the Download Patch Definitions task running in the Recent Tasks pane, right-click the task and click Cancel.
1. If the vSphere Client is not already active, use the vSphere Client (from your vCenter Server system desktop) to log in to the team vCenter Server system as user Administrator, with the password that you recorded in "Preparing for the lab." 2. Go to Home> Solutions and Applications> Update Manager. 3. Click the Configuration tab. 4. Click the Patch Download Settings link. 5. Click Use a shared repository. 6. Enter the URL for the shared repository ofESXi patches that you recorded in "Preparing for the lab." Click Validate URL. Verify that the shared repository has a status ofConnected. 7. Click Apply. 8. Click Download Now.
c
c c
c c
174
Lab 27
o o o o o o o o o o o o o o
4. When prompted by the New Baseline wizard, enter the following values.
Field/setting
Baseline Name Baseline Description Baseline Type Patch Options Patches
Value
Type ESXi Host Update. Type Patches for ESXi 4.1. Keep the default value and click Next. Click Fixed and click Next.
In the search field, type CESX40-MMODE.
Select the first patch in the list. Click the down arrow beneath the horizontal scroll bar to add the patch to the Fixed Patches to Add pane and click Next. Ready to Complete Review your patch baseline. Verify the accuracy of Baseline Name and Baseline Type and click Finish.
Lab 27
175
8. Click Scan. 9. Monitor the Recent Tasks pane and wait for the scan to fmish. When the scan completes, it should result in noncompliance.
c
c c c
patches. Students should work as a cluster team to complete this task. Student B from the lowernumbered ESXi host should do the steps in this task. 1. Go to Home> Inventory > Hosts and Clusters. 2. Click the Update Manager tab. 3. Select both ESXi hosts and review the Patches column. Under the Patches column, no patches are staged for each hosto 4. Click Stage to copy the patches to the ESXi hosts. 5. In the Stage wizard, click Next to accept the defaults on each page. 6. Click Finish to begin the staging process. 7. Monitor the Recent Tasks pane for the Stage Patches to Entity task. Wait for the task to complete. 8. To begin the patching process, click Remediate. 9. When prompted by the Remediate wizard, enter the following values.
c
(~
c
c.
Field/setting
Remediation Selection Patches and Extensions Host Remediation Options
Value
Leave the default and click Next. Leave the default and click Next. Leave the default and click Next.
c
L
c~
l
176
Lab 27 VMware vCenter Update Manager
Field/setting
Cluster Remediation Options
Value
Click Generate Report and identify the fonctions that the remediation process will do in addition to patching the hosto Click Close. Leave the default and click Next.
)
Ready to Complete
)
)
)
10. Monitor the Recent Tasks pane and answer the following questions: a. Which ESXi host was remediated first?---------------b. Was it placed into maintenance mode by the remediation process?_ _ _ _ _ _ _ __ c. Were virtual machines migrated to the other node in cluster?_ _ _ _ _ _ _ _ _ ___ d. Was the patch installed on the ESXi host in maintenance mode?_ _ _ _ _ _ _ _ _ __ e. Did the patched ESXi host exit maintenance mode?_ _ _ _ _ __
)
)
f.
g. Were the virtual machines it hosted migrated to the other node in cluster?_ _ _ _ __ h. Was the other node patched?________________
i.
11. Ifthe hosts in Lab Cluster do not show compliance when remediation completes, click the Scan link.
Lab 27
177
o o o o c
c c c c
178 Lab 27 VMware vCenter Update Manager
()
o o o o o o o o o
)
o
J
)
I~
:J