Vmware Vsphere: What'S New: Lab Manual Esxi 6.5 and Vcenter Server 6.5

VMware vSphere:
What’s New
Lab Manual
ESXi 6.5 and vCenter Server 6.5
VMware® Education Services

VMware, Inc.
www.vmware.com/education
VMware vSphere:
What’s New
ESXi 6.5 and vCenter Server 6.5
Part Number EDU-EN-VSWN65-LAB (B)
Lab Manual
Copyright © 2017 VMware, Inc. All rights reserved. This manual and its accompanying materials
are protected by U.S. and international copyright and intellectual property laws. VMware products
are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a
registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
All other marks and names mentioned herein may be trademarks of their respective companies.
The training material is provided “as is,” and all express or implied conditions, representations,
and warranties, including any implied warranty of merchantability, fitness for a particular purpose
or noninfringement, are disclaimed, even if VMware, Inc., has been advised of the possibility of
such claims. This training material is designed to support an instructor-led training course and is
intended to be used for reference purposes in conjunction with the instructor-led training course.
The training material is not a standalone training tool. Use of the training material for self-study
without class attendance is not recommended.
These materials and the computer programs to which it relates are the property of, and embody
trade secrets and confidential information proprietary to, VMware, Inc., and may not be
reproduced, copied, disclosed, transferred, adapted or modified without the express written
approval of VMware, Inc.
www.vmware.com/education
C ONTENTS
Lab 1 Working with VMware Host Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Lab 2 Working with the vCenter Server Appliance Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Lab 3 Working with vSphere Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Lab 4 Working with vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance . . . . . . . . . . . . . . . . . . . . . 19
Lab 6 vCenter Server Appliance Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Lab 7 Creating a Content Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Lab 8 Configuring Lockdown Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Lab 9 Upgrading Virtual Machines to the Current Hardware Version . . . . . . . . . . . . . . . . . . . . . . . 47
Lab 10 Working with Virtual Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Lab 11 Creating Storage Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Lab 12 Encrypting Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Lab 13 Working with Network I/O Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lab 14 Using vCenter Server High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Lab 15 Migrating Virtual Machines Across vCenter Server Instances . . . . . . . . . . . . . . . . . . . . . . . 87
Answer Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
iii
iv VMware vSphere: What’s New
Lab 1 Working with VMware Host Client
Objective: Use VMware Host Client

In this lab, you perform the following tasks:
1. Access the Student Desktop System

2. Access VMware Host Client
3. Assign Licenses to the ESXi Host
Task 1: Access the Student Desktop System

The student desktop system that is assigned to you serves as an end-user terminal. You access and
manage the lab environment from the student desktop system.
Use the following information from the class configuration handout:
• Student desktop login name
• Student desktop password
1. On your computer, start a remote connection application, such as Remote Desktop Connection
on Windows machines to connect to the lab environment.
2. Log in to your student desktop system with the student desktop login name and student desktop
password.
1
Task 2: Access VMware Host Client
You use VMware Host Client™ to directly log in to the VMware ESXi™ host. You use browser
bookmarks that have been preset in the Internet Explorer Favorites toolbar, so that you can quickly and
conveniently access VMware Host Client without entering the URL in the browser navigation bar.
• Standard lab password
1. In the desktop taskbar, click Internet Explorer to start the Web browser.
2. In the Internet Explorer Favorites toolbar, select Host Clients > SA-ESXI-01.
A Web page appears with the There is a problem with this website’s security
certificate warning.
3. Click Continue to this website (not recommended).

The VMware ESXi login page appears.
4. (Optional) Install the certificate for this Web page to prevent the certificate warning from
appearing every time you access this page.
You can repeat these steps to prevent the certificate warning from appearing whenever you
access the various Web clients in these labs.
a. In the Navigation toolbar, click the Security Report icon.
The Security Report icon is a red shield icon.
The Untrusted Certificate dialog box appears.
b. Click View certificates at the bottom of the Untrusted Certificate dialog box.
The Certificates dialog box appears.
c. Click Install Certificate.
The Certificate Import Wizard page appears.
d. Select Local Machine.
e. Click Next.
The Certificate Store page appears.
f. Click Next.
g. Click Finish.
The import was successful page appears.
h. Click OK to close the import was successful page.
i. Click OK to close the Certificate Import Wizard window.
2 Lab 1 Working with VMware Host Client
5. Log in to VMware Host Client.
a. On the VMware ESXi login page, enter root in the User name text box.
b. Enter the standard lab password in the Password text box.
c. Click Log in.
d. In the Help us improve the VMware Host Client dialog box, deselect the Join CEIP check
box and click OK.
The VMware Host Client page appears.
VMware® ESXi™ appears in the upper-left corner.
Task 3: Assign Licenses to the ESXi Host

You use VMware Host Client to update licenses for the ESXi host.
In the VMware Host Client page, you should see a message: You are currently using ESXi
in evaluation mode. This license will expire in nn days. nn is a number of days
less than 60.
• ESXi Server license key
1. In the left pane of the VMware Host Client page, click Manage.
2. In the center pane, click the Licensing tab.
If the license is not assigned, the key will appear as all zeros in the center pane.
3. If the license has not been assigned, assign a license to the ESXi host.
a. Click Assign license.
b. In the License key text box, enter the ESXi Server license key that is provided by the
instructor.
c. Click Check license.
After a few seconds, a confirmation that the license key is valid appears.
d. Click Assign license.
e. In the left pane, click Host.
The warning You are currently using ESXi in evaluation mode. This
license will expire in 60 days disappears.
4. In the center pane, dismiss other warnings that end with unless it is necessary for
administration purposes.
Lab 1 Working with VMware Host Client 3

5. Log out of VMware Host Client.
a. In the top right of the center pane, click root@sa-esxi-01.vclass.local.
b. Click Log out.
c. Close the browser tab.
4 Lab 1 Working with VMware Host Client

Lab 2 Working with the vCenter Server
Appliance Shell
Objective: Manage vCenter Server Appliance by using

the command-line shell interface
1. Access the Appliance Shell and Review Information

2. Troubleshoot the vSphere Client User Interface Service
Task 1: Access the Appliance Shell and Review Information

You use the Multi-Tabbed PuTTY (MTPuTTY) application to open a shell console with your
VMware vCenter® Server Appliance™ system.
1. Click MTPuTTY in the Windows desktop toolbar.
The MTPuTTY (Multi-Tabbed PuTTY) utility window appears.

2. In the left pane, double-click SA-VCSA-01.
A new SA-VCSA-01 tab opens in the center pane.
3. If the PuTTY Security Alert window appears, click Yes.
In this lab environment, MTPuTTY has been configured to automatically log in to the vCenter
Server Appliance as user root.
5
4. Examine the initial information displayed by the shell.
Q1. What is the version of your vCenter Server Appliance system?

1. VMware vCenter Server Appliance 6.5.0.
Q2. What is the type of your vCenter Server Appliance system?

2. VMware vCenter Server® with an external VMware Platform Services Controller™.
The type of deployment mode is selected during the installation of vCenter Server
Appliance. The other type of deployment is vCenter Server with an embedded Platform
Services Controller.
5. At the command prompt, enter software-packages --help.
Q3. Which subcommands are listed?

3. stage, unstage, validate, install, and list.
6. At the command prompt, enter software-packages list.

7. Scroll through the list of software packages.
8. Run the help api command to familiarize yourself with the appliance shell.
help api list
9. Review the API calls that are supported by this server.
Task 2: Troubleshoot the vSphere Client User Interface Service

A Web server is embedded in vCenter Service Appliance. This Web server provides the user
interface to the VMware vSphere® Client™ and VMware vSphere® Web Client. If this Web server
stops, you see a 503 error in your Web browser when you use one of these clients to manage
vCenter Server.
1. In the MTPuTTY utility window, check the status of the vsphere-ui component by executing the
following command:
service-control --status vsphere-ui
2. If the status of the vsphere-ui component is running, stop it by entering service-control --
stop vsphere-ui.
After a few seconds, a Successfully stopped service vsphere-ui confirmation

appears.
3. Open a new tab in Internet Explorer.
4. In the Internet Explorer Favorites toolbar, select vSphere Clients > SA-VCSA-01.
6 Lab 2 Working with the vCenter Server Appliance Shell

5. A Web page appears with the There is a problem with this website’s security

A 503 warning appears in the Web browser. This behavior is expected when the vsphere-ui
component is stopped.
7. Start the vsphere-ui component.
a. Return to the MTPuTTY utility window
b. In the SA-VCSA-01 session, restart the vsphere-ui component.
service-control --start vsphere-ui
After about a minute, a Successfully started service vsphere-ui confirmation
appears.
8. Return to Internet Explorer and refresh the vSphere Client login page.
a. In Internet Explorer, click Refresh (F5) to reload the vSphere Client.
If you refresh the screen too soon, you might see a message indicating that the Web page
cannot be found or the vSphere Client Web server is initializing. Wait for a few minutes
and try to refresh the screen again.
b. Click Continue to this website (not recommended).
The VMware vCenter® Single Sign-On page appears.
c. Leave the VMware vCenter Single Sign-On page open.
You use this page in the next lab.
Lab 2 Working with the vCenter Server Appliance Shell 7

8 Lab 2 Working with the vCenter Server Appliance Shell
Lab 3 Working with vSphere Client
Objective: Use vSphere Client

1. Use vSphere Client to Log In to Your vCenter Server Appliance System

2. Add an ESXi Host to the vCenter Server Inventory
Task 1: Use vSphere Client to Log In to Your vCenter Server Appliance

System
You use vSphere Client to log in to your vCenter Server Appliance system by using a browser
bookmark that has been preset in the Internet Explorer Favorites toolbar.
• vCenter Server Appliance user name
1. In Internet Explorer, open the VMware vCenter Single Sign-On page if it is not already open.
a. Open a new browser tab.
b. In the Internet Explorer Favorites toolbar, select vSphere Clients > SA-VCSA-01.
A Web page appears with the There is a problem with this website’s
security certificate warning.
c. Click Continue to this website (not recommended).

The VMware vCenter Single Sign-On page appears.
9
2. Log in to vSphere Client.
a. In the VMware vCenter Single Sign-On page, enter the vCenter Server Appliance user
name in the User name text box.
b. Enter the standard lab password in the Password text box.
c. Click Log in.
The vSphere Client page appears.
Task 2: Add an ESXi Host to the vCenter Server Inventory

You add an ESXi host to the vCenter Server inventory.
• ESXi host 01 FQDN
• ESXi user name
• vSphere license key
1. In the Navigator pane, right-click SA Compute-01 and select Add Host.
The Add Host wizard appears.
2. On the Name and location page, enter the ESXi host 01 FQDN in the Host name or IP address
text box and click Next.
3. On the Connection settings page, enter the ESXi user name, enter the standard lab password,
and click Next.
4. If you see a security alert stating that the certificate store of vCenter Server cannot verify the
certificate, click Yes to proceed.
5. On the Host summary page, review the information and click Next.
6. On the Assign license page, select the row with the VMware vSphere® license key and click
Next.
7. On the Lockdown mode page, leave Disabled clicked and click Next.
8. On the Ready to complete page, review the information and click Finish.
9. In the vSphere Client Recent Tasks pane, monitor the progress of the task until it is completed.
10. In the Navigator pane, click the arrow next to SA Compute-01 to expand the view.
The ESXi host contains one virtual machine that has been preconfigured for you, VCHA
10 Lab 3 Working with vSphere Client

11. Select the ESXi host and click the Summary tab to view the information, such as its CPU,
memory, storage, NICs, and virtual machines.
12. Scroll down to the Hardware pane to view the hardware details of the ESXi host.
13. Log out of vSphere Client.

a. In the top right of the center pane, click administrator@vsphere.local.
b. Click Log out.
c. Close the browser tab.
Lab 3 Working with vSphere Client 11

12 Lab 3 Working with vSphere Client
Lab 4 Working with vSphere Web Client
Objective: Use vSphere Web Client

1. Use vSphere Web Client to Log In to Your vCenter Server Appliance System
2. Add Another ESXi Host to the Cluster
3. Update the License Information for the vCenter Server Instance
4. Assign a License to the vCenter Server Instance
5. Customize the Workspace in vSphere Web Client
Task 1: Use vSphere Web Client to Log In to Your vCenter Server

Appliance System
You use a browser bookmark that was preset in the Internet Explorer Favorites toolbar to log in to
your vCenter Server Appliance system.
1. Log in to vSphere Web Client.
a. Open a new tab in Internet Explorer.
b. Select vSphere Web Clients > SA-VCSA-01.
13
d. Enter the vCenter Server Appliance user name in the User name text box.
e. Enter the standard lab password in the Password text box.
f. Click Log in.
The VMware vSphere Web Client page appears.
2. In the Navigator pane, expand vCenter Server Appliance and expand SA Datacenter.
The SA Compute-01 cluster that you created in the previous lab is present in the vCenter Server
inventory list.
3. If the center pane does not show the Home page, point to the Home icon and select Home.
Task 2: Add Another ESXi Host to the Cluster

You add a second ESXi host to the SA Compute-01 cluster.
• ESXi host 02 FQDN
• ESXi user name
1. In vSphere Web Client, point to the Home icon and select Hosts and Clusters.
2. In the Navigator pane, right-click SA Compute-01 and select Add Host.
The Add Host wizard appears.
3. On the Name and location page, enter the ESXi host 02 FQDN in the Host name or IP address
text box and click Next.
4. On the Connection settings page, enter the ESXi user name, enter the standard lab password,
and click Next.
5. If you see a security alert stating that the certificate store of vCenter Server cannot verify the
certificate, click Yes to proceed.
6. On the Host summary page, review the information and click Next.
7. On the Assign license page, click the row with your vSphere license key and click Next.
14 Lab 4 Working with vSphere Web Client

8. On the Lockdown mode page, leave Disabled clicked and click Next.
9. On the Ready to complete page, review the information and click Finish.
10. In the vSphere Web Client Recent Tasks pane, monitor the progress of the task until it
completes.
The ESXi host contains four virtual machines that have been preconfigured: Hardware-A,
Linux-01, Linux-02, Linux-03.
11. In the Navigator pane, click the arrow next to SA Compute-01 to expand the view.
12. In the Navigator pane, select the ESXi host that you just added and click the Summary tab to
view the information, such as its CPU, memory, storage, NICs, and virtual machines.
Task 3: Update the License Information for the vCenter Server

Instance
You use vSphere Web Client to update licenses for the vCenter Server instance.
• vCenter Server license key
1. In vSphere Web Client, point to the Home icon and select Administration.
2. In the left pane, select Licenses under Licensing.
3. In the center pane, click the Licenses tab.
4. Enter the license information for the vCenter Server instance.
a. In the center pane, click the Create New Licenses icon.
The icon appears as a green plus symbol.
b. In the License keys text box, enter the vCenter Server license key that is provided by the
instructor.
c. Click Next.
d. In the License name text box, enter vCenter License and click Next.
e. On the Ready to Complete page, click Finish.
Lab 4 Working with vSphere Web Client 15

Task 4: Assign a License to the vCenter Server Instance
You use vSphere Web Client to assign a license to the vCenter Server instance.
• vCenter Server Appliance 01 FQDN
1. In the Licenses center pane, click the Assets tab.
2. Assign a license to the vCenter Server instance.
a. From the list of vCenter Server instances, select the row with the vCenter Server Appliance
01 FQDN.
Do not click the link in that row.
b. Click the Assign License icon.
c. In the Assign License window, select vCenter License and click OK.
Task 5: Customize the Workspace in vSphere Web Client

You customize the vSphere Web Client view to increase the visual space.
1. Verify that the Work In Progress pane is minimized to the right of the center pane.
2. If the Work In Progress pane is not minimized, then minimize it.
a. Find the Work In Progress pane.
b. In the right side of the Work In Progress pane, click the Pin icon.
The Work In Progress pane is minimized to the right of the center pane.
3. Click the Work In Progress pane.
The Work In Progress pane appears until you click another part of vSphere Web Client.
4. In vSphere Web Client, point to the Home icon and select Home.
5. In the center pane, click the Global Inventory Lists icon.
6. In the top-right corner of the center pane, click the Close tab icon.
7. In the Close Getting Started Tab dialog box, click Yes.

8. In vSphere Web Client, click the Help drop-down menu and select Hide All Getting Started
Pages.
Do not log out of vSphere Web Client.
Lab 4 Working with vSphere Web Client 17

Lab 5 Migrating Windows vCenter Server
to vCenter Server Appliance
Objective: Migrate a Windows vCenter Server system to

vCenter Server Appliance
1. Verify That vCenter Server for Windows Is Running

2. Start the Migration Assistant Tool on the Windows vCenter Server System
3. Run the vCenter Server Appliance Installer and Perform Stage 1 of the Migration Process
4. Monitor Stage 1 of the Migration Process
5. Perform Stage 2 of the Migration Process
6. Verify Successful Migration
Task 1: Verify That vCenter Server for Windows Is Running

You verify that vCenter Server for Windows is running.
• Windows vCenter Server user name
1. Log in to the student desktop system.
2. Open a new tab in the Internet Explorer browser.
19
3. Log in to the Windows vCenter Server system.
a. Go to https://lab-vcs-01.vclass.local:9443/vsphere-client/.
b. If you get an website security warning message, click Continue to this website.
c. For the user name, enter the Windows vCenter Server user name.
d. For the password, enter the standard lab password.
e. Click Login.
4. Verify the version of Windows vCenter Server that is running.
a. From the Help menu in the upper-right corner, select About VMware vSphere.
The About VMware vSphere window appears.
b. View the vSphere Web Client line and verify that the running version is 5.5.0.
The vSphere Web Client line is the first line in the window.
c. Click OK to close the About VMware vSphere window.
5. Click the Home icon.
6. In the center pane, click Hosts and Clusters.
7. Verify that Training datacenter and Lab Cluster cluster are displayed in the left pane.
8. Log out of vSphere Web Client.
9. Close the browser tab for vSphere Web Client.
Task 2: Start the Migration Assistant Tool on the Windows vCenter

Server System
Migration Assistant is an application that runs on the host where vCenter Server 5.5 for Windows is
deployed. Migration Assistant communicates with the vCenter Server Appliance Installer that is
running on your student desktop, to extract the configuration data from vCenter Server 5.5 for
Windows and sends it to a new VM where the vCenter Server Appliance 6.5 is installed.
The Migration Assistant application is part of the of vSphere 6.5 release. In this lab environment,
the Migration Assistant application is in the migration-assistant folder in the Z: drive of the
host where vCenter Server 5.5 for Windows is deployed.
• Windows vCenter Server user name
20 Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance

1. Open a console to LAB-VCS-01.vclass.local.
a. Click the Remote Desktop Connection Manager icon in the Windows desktop toolbar.
The Remote Desktop Connection Manager window appears.
b. In the left pane, click LAB-VCS-01 (vclass.local).
A new LAB-VCS-01 tab opens in the center pane.
c. If the new LAB-VCS-01 shows as Disconnected from VCS-01.vclass.local, right-click
LAB-VCS-01.vclass.local and select Connect server.
d. In the Remote Desktop Connection window, click Yes to connect.
The desktop for LAB-VCS-01 appears in the center pane.
2. Open the Migration-assistant folder on the LAB-VCS-01 desktop.
3. Double-click VMware-Migration-Assistant to start the Migration Assistant application.
A console window appears.
4. If you see a security warning, click Run.
5. For the Administrator@vsphere.local password, enter the standard lab password.
Extracting the Migration Assistant scripts and running some prechecks might take a few
minutes.
Information about the existing deployment is displayed on the screen. The migration steps are
also detailed.
6. Wait until you see the message Waiting for migration to start... before proceeding
to the next task.
Migration Assistant waits on this screen while the migration is in progress.
NOTE
Do not close the console. You return to this window later.
Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance 21

Task 3: Run the vCenter Server Appliance Installer and Perform
Stage 1 of the Migration Process
You use the vCenter Server Appliance installer to perform stage 1 of the migration process.
• vCenter Server Appliance installer ISO name
1. Mount the vCenter Server Appliance installer ISO.
a. On the Student A desktop, double-click the Class Materials and Licenses folder.
b. Double-click Downloads.
c. Double-click the vCenter Server Appliance installer ISO name.
The installer ISO file is mounted as the E: drive.
2. Navigate to vcsa-ui-installer\win32.
This folder includes an application file called installer.exe.
3. Double-click installer.exe to start the migration process.
4. If you see a security warning, click Run.
The vCenter Sever Appliance 6.5 Installer window appears.
5. Select the Migrate option.
The Migrate - Stage 1: Deploy Appliance wizard appears.
6. On the Introduction page, read the information about what takes place during the migration
process.
7. Click Next.
8. On the End user license agreement page, accept the license agreement and click Next.
9. On the Connect to source server page, configure the source Windows server settings.
a. In the Source Windows server text box, enter lab-vcs-01.vclass.local.
b. In the SSO password text box, enter the standard lab password.
c. Click Next.
10. In the Verify Thumbprint window, click Yes to accept the certificate.

11. On the Appliance deployment target page, configure settings to deploy the appliance.
a. In the ESXi host or vCenter Server name text box, enter sa-esxi-03.vclass.local.
In this lab, you deploy to an ESXi host. However, you can deploy to a vCenter Server
system as well.
b. In the User name text box, enter root.
c. In the Password text box, enter the standard lab password.
d. Click Next.
e. In the Certificate Warning window, click Yes to accept the certificate.
12. On the Set up target appliance VM page, configure settings for the target appliance.
a. In the VM name text box, enter VCSA-02.vclass.local.
b. In the Root password and Confirm root password text boxes, enter the standard lab
password.
c. Click Next.
13. On the Select deployment size page, keep the default selection as Tiny and click Next.
14. On the Select datastore page, configure the datastore settings.
a. Select the SA-ESXi-03-Local datastore.
b. Select the Enable Thin Disk Mode check box.
c. Click Next.
15. On the Configure network settings page, configure the network settings.
a. From the Network list, select VM Network.
b. From the IP version list, select IPv4.
c. From the IP assignment list, select static.
d. In the Temporary IP address text box, enter 172.20.10.70.
e. In the Subnet mask or prefix length text box, enter 24.
f. In the Default gateway text box, enter 172.20.10.10.
g. In the DNS servers text box, enter 172.20.10.10.
h. Click Next.
16. On the Ready to complete stage 1 page, review your settings and click Finish.
Continue on to the next task as Stage 1 takes several minutes to complete.

Task 4: Monitor Stage 1 of the Migration Process
You monitor the progress of stage 1 of the migration process.
1. Use VMware Host Client to log in to SA-ESXi-03.
a. In the Internet Explorer Web browser, open a new tab.
b. In the Favorites toolbar, select Host Clients > SA-ESXi-03.
A Web page appears with the warning message There is a problem with this
website’s security certificate.

The VMware ESXi login page appears.
d. On the login page, enter root in the User name text box.
e. Enter the standard lab password in the Password text box.
f. Click Log in.
g. In the informational message window, deselect the Join CEIP check box and click OK.
The VMware Host Client page appears.
2. Open a console window to monitor the deployment of vCenter Server Appliance.
a. In the left pane, click Virtual Machines.
b. In the center pane, right-click VCSA-02.vclass.local and select Console > Open console
in new window.
3. Monitor the progress of the stage 1 deployment process.
a. Alternate between viewing the VCSA-02 console window and the vCenter Server
Appliance Installer progress bar window.
The console screen changes with the progress of the deployment. For example, if the
progress bar is at 81 percent, the VCSA-02 console window changes to a virtual appliance
screen.
b. In the vCenter Server Appliance Installer progress bar window, wait for stage 1 to be 100
percent complete.
c. When stage 1 is complete, click Continue.
The Stage 2: vCenter Server Appliance with an Embedded PSC wizard appears.

4. Monitor messages in Migration Assistant on the Windows vCenter Server system.
a. Switch back to Migration Assistant in the Remote Desktop Connection Manager window.
b. Verify that the Returning cached prechecks results...Successfully
returned cached prechecks results message appears in the Migration Assistant
output.
c. After you see this message, return to the vCenter Server Appliance Installer window.
Task 5: Perform Stage 2 of the Migration Process

You perform stage 2 of the migration process.
1. In the vCenter Server Appliance Installer window, read the information on the Introduction
page and click Next.
It will take a few minutes for the premigration checks to be completed.
2. On the Join AD Domain page, configure settings for the AD domain.
a. In the AD domain text box, verify that the domain is vclass.local.
b. In the AD User name text box, enter administrator.
c. In the AD Password text box, enter the standard lab password.
d. Click Next.
3. On the Select migration data page, select Configuration, events, tasks, and performance
metrics and click Next.
4. On the Configure CEIP page, deselect the Join the VMware’s Customer Experience
Improvement Program (CEIP) check box and click Next.
5. On the Ready to complete page, select the I have backed up the source vCenter Server and
all the required data from the database check box.
6. Click Finish.
The Shutdown Warning window appears with a warning that vCenter Server will shut down
after the network configuration is enabled on the destination vCenter Server Appliance system.

7. Click OK.
The rest of the migration takes about 30 minutes to complete.
When stage 2 is complete, the following screen appears.
8. Click Close to exit the vCenter Server Appliance installer.

When the vCenter Server Appliance Installer is closed, it will bring up the vSphere Web Client
for lab-vcs-01.vclass.local.
Task 6: Verify Successful Migration

You verify that the Windows vCenter Server system has been successfully migrated to vCenter
Server Appliance.
1. Use vSphere Web Client to log in to the newly migrated vCenter Server system.
a. Verify that the Internet Explorer tab that opened up in last step of the previous task is to
lab-vcs-01.vclass.local.
The newly migrated vCenter Server Appliance has the IP address and the DNS name of the
original system. The original system is powered off during the migration process.
c. Click vSphere Web Client (Flash).

d. Log in with the vCenter Server Appliance user name and the standard lab password.
If after a few minutes the log in process appears to have stalled, click the Refresh icon to the
right of the URL.
2. Point to the Home icon and select Host and Clusters.
3. In the left pane, select lab-vcs-01.vclass.local.
4. In the center pane, click the Summary tab.
5. In the Version Information panel, verify that the version is 6.5.
Recall that in Task 1 of this lab, lab-vcs-01.vclass.local was version 5.5.
6. In the left pane, expand lab-vcs-01.vclass.local and verify that you have Training Datacenter
and Lab Cluster in the inventory tree.
7. Point to the Home icon and select Administration.
8. In the left pane, select System Configuration.
9. In the left pane, select Nodes.
10. In the left pane, select lab-vcs-01.vclass.local
Review the information about the new vCenter Server Appliance system.

Lab 6 vCenter Server Appliance Backup
and Restore
Objective: Back up and restore vCenter Server Appliance

1. Prepare the Environment

2. Back Up Your vCenter Server Appliance System
3. Recover Your vCenter Server Appliance System
4. Verify the Restored vCenter Server Appliance System
5. Clean Up the Lab
Task 1: Prepare the Environment

If you logged out of systems or if systems are disconnected or timed out, you must restore the
connection to the lab environment.
2. Click the Internet Explorer icon on the toolbar.
3. In the Internet Explorer Favorites bar, select vSphere Web Clients > SA-VCSA-01.
4. Use the vCenter Server Appliance user name and the standard lab password to log in to the
vCenter Server system.
29
5. Point to the Home icon and select Hosts and Clusters.
6. In the left pane, locate the VCSA-02.vclass.local virtual machine in the SA Management
cluster.
7. In the left pane, right-click VCSA-02.vclass.local and select Console > Open console in new
window.
A new browser tab opens with the There is a problem with this website’s

The console screen for VCSA-02.vclass.local appears.
9. Make a note of the URL in the message.
Please visit the following URL to configure this appliance:
https://lab-vcs-01.vclass.Local:5480
In the next task, you will use the URL access the backup process.
10. Close the browser tab for the VCSA-02.vclass.local console.
Task 2: Back Up Your vCenter Server Appliance System

To back up and restore vCenter Server Appliance, you connect to the Appliance Management
interface for your vCenter Server Appliance. After the backup has completed virtual machine is
powered off as the restored vCenter Server will use its IP address and DNS.
1. Use the VMware vSphere Appliance Management interface to log in to your vCenter Server
Appliance system.
a. Open a new tab in Internet Explorer and enter https://lab-vcs-
01.vclass.Local:5480.
The DNS name and IP address of the migrated vCenter Server Appliance is inherited from
the Windows vCenter Server.

c. Log in with the user name root and the standard lab password.
2. In the Summary pane, click Backup at the top right of the screen.
The Backup Appliance wizard appears.
30 Lab 6 vCenter Server Appliance Backup and Restore

3. On the Enter backup details page, configure the backup details.
a. Select FTP from the Protocol drop-down menu.
b. In the Location text box, enter 172.20.10.10/VC-Backup.
c. Keep the default port.
d. In the User name text box, enter ftp-admin.
e. In the Password text box, enter the standard lab password and click Next.
4. On the Select parts to backup page, accept the defaults.
5. Wait for the size of the backups to be calculated, then click Next.
6. On the Ready to complete page, click Finish.
7. Monitor the backup progress.
Ignore the message stating that 0% backup is completed and proceed to the next step after five
minutes.
8. After the backup is complete, examine the backup files.
a. Open a new tab in Internet Explorer and enter ftp://172.20.10.10/VC-Backup.
b. In the User name text box, enter ftp-admin.
c. In the Password text box, enter the standard lab password and click Next.
d. Verify that their are 11 files in the VC-Backup directory.
e. Minimize the Internet Explorer window.
9. Power off VCSA-02.
a. From Internet Explorer, log in to sa-vcsa-01 vSphere Web Client as
administrator@vsphere.local using the standard lab password.
b. In the left pane, locate the VCSA-02 virtual machine in the SA Management cluster.
c. Right-click VCSA-02.vclass.local and select Power Off.
d. Click Yes in the Confirm power off dialog box.
Lab 6 vCenter Server Appliance Backup and Restore 31

Task 3: Recover Your vCenter Server Appliance System
You use a two-stage process to recover your vCenter Server Appliance system: you deploy a new
appliance and you restore from the backup.
1. Start the vCenter Server Appliance installer.
a. From your student desktop, click the Class Materials and Licenses shortcut and double-
click Downloads.
b. Double-click the VMware-VCSA-all-6.5.0-#######.iso file.
c. Double-click the vcsa-ui-installer folder.
d. Double-click the win32 folder.
e. Double-click the installer.exe application.
2. In the vCenter Server Appliance Installer screen, select the Restore option.
3. On the Introduction page, click Next.
4. On the End user license agreement page, accept the license agreement and click Next.
5. On the Enter backup details page, configure the backup details.
a. Select FTP from the Protocol drop-down menu.
b. In the Location text box, enter 172.20.10.10/VC-Backup.
c. Keep the default port.
d. In the User name text box, enter ftp-admin.
e. In the Password text box, enter the standard lab password.
f. Leave the Encryption password text box blank and click Next.
If the connection times out, you can click Next to try again.
6. On the Review backup information page, review the information and click Next.
7. On the Appliance deployment target page, configure settings for the target host.
a. In the ESXi host or vCenter Server name text box, enter sa-esxi-03.vclass.local.
b. Keep the default HTTPS port.
c. In the User name text box, enter root.
d. In the Password text box, enter the standard lab password and click Next.
e. Click Yes in the Certificate Warning window.

8. On the Set up target appliance VM page, configure settings for the target appliance VM.
a. In the VM name text box accept the default name VC-Backup.
b. In the Root password and Confirm Password text boxes, enter the standard lab password
and click Next.
9. On the Select deployment size page, accept the default deployment size (Tiny) and click Next.
10. On the Select datastore page, configure settings for the datastore.
a. Select SA-ESXi-03-Local02.
b. Select the Enable Thin Disk Mode check box and click Next.
11. On the Configure network settings page, configure the network settings.
a. From the Network drop-down menu, select VM Network.
b. From the IP version list, select IPv4.
c. From the IP assignment list, select static.
d. In the IP address text box, enter 172.20.10.99.
e. In the Subnet mask or prefix length text box, enter 24.
f. In the Default gateway and DNS servers text boxes, enter 172.20.10.10.
g. Click Next.
12. On the Ready to complete stage 1 page, click Finish.
13. Watch the progress bar until completion.
Stage 1 takes several minutes.
14. When stage 1 is complete and the deployment is successful, click Continue.
Stage 2 of vCenter Server Appliance begins.
15. On the Introduction page, click Next.
16. On the Backup details page, accept the defaults and click Next.
18. Click OK in the Warning box.
19. Watch the progress bar until completion.
Stage 2 can take 30 minutes to complete.
20. When stage 2 is complete and the restore is successful, click Close.
The vSphere Appliance Management interface opens in Internet Explorer.

Task 4: Verify the Restored vCenter Server Appliance System
You verify that you can access the restored vCenter Server Appliance system.
1. Use the VMware vSphere Appliance Management interface to log in to your restored vCenter
Server Appliance system.
a. In Internet Explorer, go to https://172.20.10.99:5480.

c. Log in with the user name root using the standard lab password.
d. In the upper right of the middle pane, click Shutdown.
e. Click Yes.
f. Wait one minute and then close the Internet Explorer tab.
2. Verify that the restored vCenter Server system has been powered off.
a. Open a new tab in Internet Explorer.
b. Select vSphere Web Clients > SA-VCSA-01.
c. Enter the vCenter Server Appliance user name in the User name text box.
d. Enter the standard lab password in the Password text box.
e. Click Log in.
The VMware vSphere Web Client page appears.
f. In vSphere Web Client, verify that the VC-Backup virtual machine has been powered off.
If the VC-Backup virtual is not powered off, use the vSphere Web Client to power it off.

Task 5: Clean Up the Lab
You delete the restored vCenter Server Appliance and the migrated vCenter Server Appliance to free
up resources in the lab.
2. Delete VCSA-02.
a. In the left pane, locate the VCSA-02.vclass.local virtual machine in the SA Management
cluster.
b. Right-click VCSA-02.vclass.local and select Delete from Disk.
c. Click Yes in the Confirm Delete window.
3. Delete from disk VC-Backup.
a. In the left pane, locate the VC-Backup virtual machine in the SA Management cluster.
b. Right-click VC-Backup and select Delete from Disk.
c. Click Yes in the Confirm Delete dialog box.

Lab 7 Creating a Content Library
Objective: Create a multisite content library

1. (Optional) Prepare the Environment

2. Create a Content Library
3. Upload Data to the Newly Created Content Library
4. Create a Subscriber Content Library
5. Clone a Template to the Source Library
6. Synchronize the Content Libraries
7. Deploy a Virtual Machine from the Library
Task 1: (Optional) Prepare the Environment

2. Click the Internet Explorer icon on the taskbar.
37
5. Log in to the vCenter Server system by using the vCenter Server Appliance user name and the
standard lab password.
Task 2: Create a Content Library

You configure a content library for the assigned vCenter Server instance.
• vCenter Server Appliance name
• Assigned library source datastore
2. In the left pane, click Content Libraries.
3. In the center pane, click the Create a new content library icon.
4. Configure the new Source content library.

a. In the Name text box, enter SA-Source.
b. Click the vCenter Server drop-down menu, select your assigned vCenter Server Appliance
name, and click Next.
c. On the Configure content library page, click Local content library.
d. Select the Publish externally check box.
e. Select the Enable authentication check box.
f. In the Password and Confirm password text boxes, enter the standard lab password and
click Next.
g. Click Next.
5. On the Add storage page, click Select a datastore.
6. Select your assigned library source datastore and click Next.
8. Verify that the content library appears in the list.
38 Lab 7 Creating a Content Library

Task 3: Upload Data to the Newly Created Content Library
You upload an Open Virtualization Format (OVF) file from your student desktop to the newly
created content library.
1. In the center pane, right-click the SA-Source library and select Import Item.
2. In the Import Library Item window, click Local File.
3. Click Browse.
4. In the Choose File to Upload window, click the Desktop icon on the left bar.
5. Double-click the Class Materials and Licenses folder and double-click the Downloads folder.
6. In the Downloads folder, double-click the SA-LibVM folder.
7. Select the SA-LibVM.ovf file and click Open.
8. In the Select reference files window, click Browse.
9. Double-click SA-LibVM-1.vmdk and click OK.
10. In the Import Library Item window, validate that SA-LibVM is in the Item name text box.
11. Click OK.
12. View the Recent Tasks pane to monitor the task.
13. After the task is complete, click the name of the content library in the center pane to open the
content library.
14. In the left pane, click the Templates link.
The uploaded OVF file is listed.
Task 4: Create a Subscriber Content Library

You configure a content library that is subscribed to the first library.
• Assigned library subscriber datastore
Lab 7 Creating a Content Library 39

NOTE
In this task, you are required to use the Ctrl+V pasting option. However, this may not work. As a
workaround, you can use the on-screen keyboard. You can access the on-screen keyboard from the
Start menu. Open the on-screen keyboard at the beginning of the task and keep it minimized till you
need it in step 6e. When prompted to press Ctrl+V, click Ctrl and then click V on the on-screen
keyboard.
1. At the top of the left pane, click the navigation Back arrow until you get to the Content
Libraries center pane.
2. In the center pane, click the SA-Source library.
3. In the center pane, scroll down until the Publication panel is visible on the Summary tab.
4. In the Publication panel, click Copy Link.
5. Click the navigation Back arrow to get to the Content Libraries center pane.
6. Configure a subscriber content library.
a. In the center pane, click Create a new content library.
b. In the Name text box, enter SA-Subscriber.
c. Click the vCenter Server drop-down menu, select the vCenter Server Appliance name,
and click Next.
d. On the Configure content library page, click Subscribed content library.
e. Click the Subscription URL text box and press Ctrl+V.
The subscription URL is pasted into the text box.
f. Select the Enable Authentication check box.
g. In the Password text box, enter the standard lab password.
h. Click Download library content only when needed.
i. Click Next.
7. On the Add storage page, select your assigned library subscriber datastore.
8. Click Next.
10. In the left pane, select the SA-Subscriber library.
11. In the center pane, click the Templates tab.
12. On the Templates tab, verify that the OVF file is present.
13. Point to the Home icon and select Home.

Task 5: Clone a Template to the Source Library
You use vSphere Web Client to clone a virtual machine template into the student source content
library.
• Assigned virtual machine to clone
1. In the center pane, click the VMs and Templates icon.
2. In the left pane, right-click your assigned virtual machine to clone and select Clone > Clone to
Template in Library.
3. In the Clone to Template in Content Library window, append -Library to the virtual machine
name in the Template name text box.
4. In the content library list, select the SA-Source library and click OK.
5. In the Recent Tasks pane, monitor the task to completion.
6. View the template list in both libraries.
a. Point to the Home icon and select Content Libraries.
b. In the left pane, select your SA-Source library.
c. In the center pane, click the Templates tab and verify that both templates are listed.
d. In the left pane, select your SA-Subscriber library.
e. In the center pane, click the Templates tab and verify that only the original template is
listed.
Task 6: Synchronize the Content Libraries

You use vSphere Web Client to synchronize the content libraries.
1. In the center pane at the top, click the Synchronize icon.

The synchronization takes a moment to complete.
3. Verify that both the virtual machine templates appear in the center pane.
Lab 7 Creating a Content Library 41

Task 7: Deploy a Virtual Machine from the Library
You use vSphere Web Client to deploy a new virtual machine from the template available in the
Subscriber library.
• Virtual machine template to deploy
• Shared datastore name
1. In the center pane, right-click the virtual machine template to deploy and select New VM from
This Template.
2. On the Select name and location page, enter VM01 in the Name text box.
3. Select SA Datacenter and click Next.
4. On the Select a resource page, select the first ESXi host in the SA Compute-01 cluster and click
Next.
5. On the Review details page, click Next.
6. On the Select storage page, select Thin provision from the Select virtual disk format list.
7. Select the shared datastore and click Next.
8. On the Select networks page, keep the default and click Next.
11. Verify that the virtual machine is deployed.
a. Point to the Home icon and select VMs and Templates.
b. In the left pane, expand the vCenter Server object and expand the data center.
c. Verify that the VM01 virtual machine is displayed in the inventory.

Lab 8 Configuring Lockdown Mode
Objective: Enable and test lockdown mode


2. Confirm the vSphere ESXi Shell and SSH Services are enabled
3. Test the SSH Connection
4. Enable and Test Lockdown Mode
5. Disable Lockdown Mode
6. Examine the DCUI.Access List

43
Task 2: Confirm the vSphere ESXi Shell and SSH Services are enabled
You use vSphere Web Client to confirm that VMware vSphere® ESXi™ Shell and SSH services are
enabled and will start with the host.
1. In vSphere Web Client, click the Hosts and Clusters icon in the center pane.
2. In the left pane, click the arrow to expand your vCenter Server Appliance name.
3. Click the arrow to expand your environment and select the first ESXi host in the SA Compute-
01 cluster.
4. In the center pane, click the Configure tab.
5. On the Configure tab, select System and select Security Profile.
6. In the center pane, scroll down to the Services list to find ESXi Shell and SSH, and look to see
that both show Running. in the Daemon column.
7. On the Services row, click Edit.
8. In the Edit Security Profile window, select ESXi Shell from the Services list.
9. In the Service Details panel, ensure that Start and stop with host is selected from the Startup
Policy drop-down menu.
10. In the Status field, click the Start button if the status is not Running.
11. In the Services list, select SSH.
12. In the Service Details panel, ensure that Start and stop with host is selected from the Startup
Policy drop-down menu.
13. In the Status field, click the Start button if the status is not Running.
14. Click OK.
44 Lab 8 Configuring Lockdown Mode

Task 3: Test the SSH Connection
You use MTPuTTY to connect to the ESXi host and confirm that SSH is working.
1. Minimize the Internet Explorer Web browser.
The MTPuTTY utility window appears.

3. In the left pane, double-click SA-ESXi-01.
A new SA-ESXi-01 tab opens in the center pane.
4. In the PuTTY Security Alert window, click Yes.
MTPuTTY has been configured to log you in to the ESXi hosts automatically as user root.
5. If the login is successful, enter exit.
Task 4: Enable and Test Lockdown Mode

You use vSphere Web Client to enable lockdown mode for your assigned ESXi host.
1. In the Internet Explorer Web browser, click vSphere Web Client tab.
2. In the left pane, select the first ESXi host in the SA Compute-01 cluster.
4. On the left side, scroll down until you see Security Profile.
5. Click Security Profile and scroll down until you see Lockdown Mode.
6. Click Edit next to Lockdown Mode.
7. In the Lockdown Mode wizard, click Normal.
8. In the Lockdown Mode wizard, select Exception Users.
Users are not listed.
9. Click OK.
Lab 8 Configuring Lockdown Mode 45

10. Minimize the Internet Explorer Web browser.
12. In the left pane, double-click SA-ESXi-01.
MTPuTTY automatically tries to log in as root.
13. Verify that the user root is not logged in and the Access Denied message appears.
14. Close the MTPuTTY window.
Task 5: Disable Lockdown Mode

You use vSphere Web Client to disable lockdown mode.
1. In the Internet Explorer Web browser, click vSphere Web Client tab.
2. Click Edit next to Lockdown Mode.
3. In the Lockdown Mode window, click Disabled.
4. Click OK.
Task 6: Examine the DCUI.Access List

The DCUI.Access list is a list of local users on an ESXi host. These users have the privilege
necessary to disable lockdown mode in a situation where the vCenter Server cannot be used to
manage the host. Once lockdown mode has been disabled, the host can again be managed directly.
1. In the center pane, select Advanced System Settings under System.
2. In the Advanced Systems Settings Name list, scroll down to the DCUI.Access entry.
You can also use the Filter text box and search for DCUI.
3. Examine the value of the DCUI.Access setting.
The root user is added to the DCUI.Access list by default. Thus, the root user can disable
lockdown mode, but cannot bypass lockdown mode.
46 Lab 8 Configuring Lockdown Mode

Lab 9 Upgrading Virtual Machines to the
Current Hardware Version
Objective: Upgrade a virtual machine to hardware

version 13

2. Upgrade Your Virtual Machine to Hardware Version 13


47
Task 2: Upgrade Your Virtual Machine to Hardware Version 13
You use vSphere Web Client to upgrade the virtual machine hardware to the most recent version.
• Hardware virtual machine name
1. In the vSphere Web Client, point to the Home icon and select VMs and Templates.
2. In the left pane, expand the vCenter Server Appliance name object
3. In the left pane, expand SA Datacenter.
4. In the left pane, expand Discovered virtual machine.
5. Select your hardware virtual machine name.
6. Review the Summary tab.
Q1. What is the compatibility level of the virtual machine?

1. VM version 8.
7. In the left pane, right-click your hardware virtual machine and select Compatibility > Upgrade
VM Compatibility.
8. In the Confirm VM Compatibility Upgrade window, click Yes.
9. In the Compatible with list, select ESXi 6.5 and later and click OK.
10. Review the Summary tab.
11. If the hardware version has not changed, click the vSphere Web Client Refresh icon next to the
logged in user menu.
Q2. What is the new version of the virtual machine?

2. VM version 13.
48 Lab 9 Upgrading Virtual Machines to the Current Hardware Version

Lab 10 Working with Virtual Volumes
Objective: Configure both NFS and iSCSI-backed virtual

volumes

2. Validate the Storage Endpoint
3. Use NAS to Create a Virtual Volume Datastore
4. Use iSCSI to Create a Virtual Volume Datastore

49
Task 2: Validate the Storage Endpoint

You verify that a storage provider is available and determine the storage resources that are provided.
1. If necessary, log in to vSphere Web Client.
2. In the center pane, click the Hosts and Clusters icon.
3. In the left pane, select your vCenter Server Appliance name.
5. On the left side, click Storage Providers.
6. In the center pane, click the Register a new storage provider icon.
7. In the New storage provider window, configure VASASource.
Option Action
Name Enter VASASource.
URL Enter https://172.20.10.97:8443/vasa/version.xml.
User name Enter username.
Password Enter password.
8. Click OK.
9. Click Yes to acknowledge and accept the self signed certificate warning.
50 Lab 10 Working with Virtual Volumes

10. Validate that the storage provider VASASource is listed in the Storage Provider/Storage System
column.
Q1. In the storage providers window, what is the storage provider URL for VASASource?
1. http://172.20.10.97:8443/vasa/version.xml.
Q2. What VASA API version is used?

2. Version 3.0.
Q3. Which types of storage systems are listed for this storage provider?
3. xVP SCSI Array and xVP NFS Array.
Task 3: Use NAS to Create a Virtual Volume Datastore

You mount a virtual volume datastore by using an NFS protocol endpoint.
• NFS storage container
1. Use MTPuTTY to log in to SA-ESXi-01.
a. Click MTPuTTY in the Windows desktop toolbar.
The MTPuTTY (Multi-Tabbed PuTTY) utility window appears.
b. In the left pane, double-click SA-ESXi-01.
A new SA-ESXi-01 tab opens in the center pane.
c. In the PuTTY Security Alert window, click Yes.
MTPuTTY automatically logs you in to the ESXi host as user root.
2. At the command prompt, enter cd /var/log.
3. Display the contents of the vmkernel.log file.
tail -f vmkernel.log
This command shows the contents of the vmkernel.log file, with the most recent entries at
the end of the file.
Lab 10 Working with Virtual Volumes 51

4. Use the NFS storage container to create a virtual volume datastore.
a. In the Internet Explorer Web browser, click the vSphere Web Client tab.
b. In the center pane, click Hosts and Clusters.
c. In the left pane, right-click SA-ESXi-01.vclass.local and select Storage > New Datastore.
The New Datastore wizard appears.
d. On the Type page, click VVol and click Next.
e. On the Name and container selection page, enter SA-NAS-vVol in the Datastore name
text box.
f. In the Backing Storage Container list, select the NFS storage container and click Next.
g. On the Ready to complete page, click Finish.
5. View the contents of the vmkernel.log file.
a. In the MTPuTTY session, enter cat vmkernel.log at the command prompt.
b. Review the information displayed about the recently created datastore.
Q1. Using vmkernel.log, what is the NFS mount for the NFS virtual volume?
1. 172.20.10.97:/mnt/pes/nfs_2.
c. At the command prompt, enter exit.

d. Click Close to acknowledge closing the MTPuTTY session, then close MTPuTTY.
6. In vSphere Web Client, point to the Home icon and select Storage.
7. In the left pane, click the arrow to expand your vCenter Server Appliance name and your data
center.
8. Select the SA-NAS-vVol datastore.
9. In the center pane, click the Files tab.
10. In the center pane, on the right, click the Create a new folder icon.
11. In the Create a new folder window, enter SA-NAS in the Enter a name for the new folder text
box and click Create.
The creation of the folder validates that the datastore is available.

Task 4: Use iSCSI to Create a Virtual Volume Datastore
You use vSphere Web Client to create a virtual volume datastore that is backed by an iSCSI storage
container.
• iSCSI storage container
• Storage provider IP address
1. Use the iSCSI storage container to create a virtual volume datastore.
a. In the left pane, right-click SA Datacenter and select Storage > New Datastore.
The New Datastore wizard appears.
b. On the Location page, click Next.
c. On the Type page, click VVol and click Next.
d. On the Name and container selection page, enter SA-iSCSI-vVol in the Datastore name
text box.
e. In the Backing Storage Container list, select the iSCSI storage container and click Next.
f. On the Select hosts accessibility page, select the sa-esxi-01.vclass.local check box and
click Next.
2. In the Recent Tasks pane, monitor the Create Virtual Volume datastore task to completion.
3. After the task is completed, click the vSphere Web Client Refresh icon.
4. In the left pane, verify that SA-iSCSI-vVol appears in the list.
After a short while, the datastore will be marked as Inactive. We will resolve this issue in a later
task.
Q1. Why is the iSCSI storage container backed virtual volume datastore marked as
inactive?
1. The datastore is inactive because storage provider must also be configured as an iSCSI target
of the software iSCSI adapter.
5. Create a folder on the datastore and validate that the folder is not available.
a. In the left pane, select the SA-iSCSI-vVol datastore.
b. In the center pane, click the Files tab.
c. In the center pane, click the Create a new folder icon.

d. In the Create a new folder window, enter SA-iSCSI in the Enter a name for the new
folder text box and click Create.
The folder creation fails, validating that the datastore is not available.
e. Close the failure alert.
6. Add the Storage Provider as a target to the host’s iSCSI storage adapter.
a. Point to the Home icon and select Hosts and Clusters.
b. In the left pane, select sa-esxi-01.vclass.local.
c. In the center pane, click the Configure tab and select Storage Adapters on the left side.
d. Scroll the Storage Adapters list until the iSCSI Software Adapter is visible.
e. Select the iSCSI software adapter (vmhba##).
f. In the Adapter Details panel, click the Paths tab.
Q2. How many LUNs appear?

2. Three LUNs appear: 0, 1, and 2.
g. On the Targets tab, click the Add button.

h. In the Add Send Target Server window, enter the storage provider IP address in the iSCSI
Server text box.
i. Click OK.
j. In the center pane, click the Rescan all storage adapters icon.
k. In the Rescan Storage window, click OK.

l. In the Adapter Details panel, click the Paths tab.
Q3. Is LUN 260 shown?

3. Yes. Four LUNs appear: 0, 1, 2, and 260.
7. Point to the Home icon and select Storage.

8. In the left pane, if the SA-SCSI-vVol datastore still appears as inactive, click the vSphere Web
Client Refresh icon.

9. Verify that the datastore is available.
a. In the left pane, select the SA-iSCSI-vVol datastore.
b. In the center pane, click the Create a new folder icon on the Files page.
c. In the Create a new folder window, enter SA-iSCSI in the new folder name text box and
click Create.
The creation of the folder validates that the datastore is available.

Lab 11 Creating Storage Policies
Objective: Create storage policies and use these policies

with virtual machines and virtual volume datastores

2. Create a Gold Storage Policy for a Virtual Machine
3. Apply the Gold Storage Policy to a Virtual Machine
4. Deploy a Virtual Machine with the Gold Policy

If you logged out of systems or if the systems are disconnected or timed out, you must restore the
3. In the Internet Explorer favorites bar, select vSphere Web Clients > SA-VCSA-01.
4. When you see the There is a problem with this website’s security
certificate message, click Continue to this website (not recommended).

5. Log in to the vCenter Server system using the vCenter Server Appliance user name and the
57
Task 2: Create a Gold Storage Policy for a Virtual Machine
You create a storage policy to define the gold tier of storage service.
• Virtual volume array
2. In the center pane, click the VM Storage Policies icon.
The default storage polices are displayed.
3. Configure the virtual machine storage policy for the gold tier of storage service.
a. In the center pane, click the Create new VM storage policy icon.
b. In the Create New VM Storage Policy window, verify that your vCenter Server Appliance
name is selected in the vCenter Server drop-down menu.
c. In the Name text box, enter SA-Gold and click Next.
d. On the Policy Structure page, click Next.
e. On the Common rules page, click Next.
f. On the Rule-Set 1 page, select your identified virtual volume array from the Storage Type
drop-down menu.
g. From the Add rule drop-down menu, select readOPS.
h. In the readOPS text box, enter 50 and click Next.
The Storage Compatibility page appears.
Q1. On the Storage compatibility page, which storage devices are available?
1. The NFS-backed virtual volumes datastore that was created in the previous lab.
i. Click Next.
The Ready to Complete page appears.
4. Click Finish.
58 Lab 11 Creating Storage Policies

Task 3: Apply the Gold Storage Policy to a Virtual Machine
You apply the gold storage policy to a virtual machine and remediate compliance issues.
2. In the left pane, select the VM01 virtual machine.
3. In the lower right of the center pane, view the VM Storage Policies panel.
The virtual machine does not currently have a storage policy assigned.
4. Apply the gold storage policy to the VM01 virtual machine.
a. In the left pane, right-click VM01 and select VM Policies > Edit VM Storage Policies.
The Edit VM Storage Policies window appears.
b. In the VM storage policy drop-down menu, select SA-Gold.
c. Click Apply to all.
d. Click OK.
5. In the VM Storage Policies panel, click the Check Compliance link.
The VM Storage Policies Compliance shows Not Applicable.
6. Migrate the VM01 virtual machine to the NAS-backed virtual volume datastore.
a. In the left pane, right-click VM01 and select Migrate.
The Migrate window appears.
b. Click Change storage only and click Next.
c. On the Select Storage page, select the SA-NAS-vVol datastore and click Next.
The NAS-backed virtual volumes datastore is the only compatible storage option.
d. On the Ready to complete page, click Finish.
7. View the Recent Tasks pane and monitor the Relocate Virtual Machine task to completion.
8. After the Relocate virtual machine task is completed, click the Summary tab of VM01.
9. If the virtual machine does not appear as compliant, click the Check Compliance link in the
VM Storage Policies panel.
The virtual machine now appears compliant.
Lab 11 Creating Storage Policies 59

Task 4: Deploy a Virtual Machine with the Gold Policy
You deploy a virtual machine that uses the gold storage policy and check for compliance issues.
• Virtual machine to clone
1. In the left pane, right-click the virtual machine to clone and select Clone > Clone to Virtual
Machine.
2. On the Select a name and folder page, enter VM02 in the Enter a Name for the virtual
machine text box.
3. Verify that SA Datacenter is selected as the destination and click Next.
4. On the Select a compute resource page, select the first ESXi host in the SA Compute-01 cluster
and click Next.
5. On the Select storage page, select the SA-Gold policy from the VM storage policy drop-down
menu.
The virtual volume datastores are the only compatible storage options.
6. From the compatible datastore list, select the SA-NAS-vVol datastore and click Next.
7. On the Select clone options page, click Next.
9. View the Recent Tasks pane and monitor the Clone virtual machine task to completion.
10. In the left pane, select the VM02 virtual machine.
11. In the center pane, view the VM Storage Policies panel.
The virtual machine is in compliance with its storage policy.
60 Lab 11 Creating Storage Policies

Lab 12 Encrypting Virtual Machines
Objective: Register a Key Management Server with

vCenter Server and encrypt virtual machines
1. Verify Access to the Key Management Server

2. Register the Key Management Server with vCenter Server
3. Create an Encryption Storage Policy
4. Create an Encrypted Virtual Machine
5. Check vCenter Server Events
Task 1: Verify Access to the Key Management Server

You verify that you can access the key management server.
NOTE
The key management server used in this lab is a simple Python-based key server that keeps keys
while the instance is up and running.
• vCenter Server appliance name
• Key management server name
61
1. Use MTPuTTY to log in to the vCenter Server system.
a. In the taskbar, click the MTPuTTY icon.
b. In the left pane, double-click the vCenter Server system.

You are logged in to vCenter Server Appliance as user root.
2. Ping the key management server.
a. At the command prompt, enter shell.
b. Run the ping key_management_server_name command to ping the key management
server.
c. Verify that the ping is successful.
3. Exit the MTPuTTY session and close the window.
Task 2: Register the Key Management Server with vCenter Server

You register the key management server (KMS) with vCenter Server and mark the KMS cluster as
the default cluster.
• Key management server
• Key management server IP address.
2. Log in to the vCenter Server Appliance.
4. In the left pane, select your vCenter Server appliance.
5. In the center pane, click the Configure tab and click Key Management Servers on the left side.
6. Click Add KMS.
7. In the Cluster name text box, enter SA KMS-Cluster.
62 Lab 12 Encrypting Virtual Machines

8. In the Server alias text box, enter KMS1.
9. In the Server address text box, enter the key management server IP address.
10. In the Server port text box, enter 5696.
11. Leave the rest of the text boxes blank and click OK.
12. When prompted to set the default KMS cluster, click Yes.
13. When the trust certificate window appears, click Trust.
14. Verify that the key management server appears in the list and the KMS cluster that you created
is marked as the default cluster.
Task 3: Create an Encryption Storage Policy

You create a virtual machine storage policy that includes the encryption common rule only.
1. On the Home page of vSphere Web Client, click the VM Storage Policies icon.
2. In the center pane, click the Create VM Storage Policy icon.
The Create New VM Storage Policy wizard appears.

3. On the Name and description page, enter SA Encryption Policy in the Name text box and
click Next.
4. On the Policy structure page, click Next.
5. On the Common rules page, select the Use common rules in the VM storage policy check
box.
6. Click Add component and select Encryption > Default encryption properties.
The default encryption properties rule is added to the policy.
7. Click Next.
8. On the Rule-set 1 page, deselect the Use rule-sets in the storage policy check box and click
Next.
9. On the Storage compatibility page, review the compatible storage and click Next.
All storage is compatible with the encryption filter since the filter is applied as a common rule
and is therefore a hypervisor-based storage feature and not dependent upon functionality
provided by the storage arrays.
Lab 12 Encrypting Virtual Machines 63

11. Verify that your encryption policy appears in the storage policies list.
Task 4: Create an Encrypted Virtual Machine

You create an encrypted virtual machine.
• ESXi host name
1. In vSphere Web Client, click Home and click Hosts and Clusters.
2. In the left pane, right-click the SA Compute-01 cluster and select New Virtual Machine > New
Virtual Machine.
The New Virtual Machine wizard appears.
3. On the Select a creation type page, select Create a new virtual machine and click Next.
4. On the Select a name and folder page, enter Linux-04 for the virtual machine name.
5. For the virtual machine location, select the data center and click Next.
6. On the Select a compute resource page, expand SA Compute-01 and select the first ESXi host.
7. Click Next.
8. On the Select storage page, select SA Encryption Policy from the VM storage policy drop-
down menu.
9. Click Next.
10. On the Select compatibility page, keep the default values and click Next.
11. On the Select a guest OS page, keep the defaults and click Next.
12. On the Customize hardware page, expand New Hard disk.
13. Select Thin provision from the Disk Provisioning drop-down menu.
14. Reduce the disk size to 4 GB.
15. Reduce the memory size to 1024 MB.
16. Click Next.

Task 5: Check vCenter Server Events
You check the vCenter Server cryptographic events.
1. In the left pane, select the vCenter Server object.
2. In the center pane, click the Monitor tab.
3. Click Tasks & Events and click Events on the left side.
4. Select the cryptographic operation that was performed during the virtual machine creation.
The cryptographic operation is recorded along with the user that initiated the task.
Lab 12 Encrypting Virtual Machines 65

Lab 13 Working with Network I/O Control
Objective: Create and configure a distributed switch


2. Create a Distributed Switch
3. Add the ESXi Host to the New Distributed Switch
4. Examine the Distributed Switch Configuration
5. Migrate a Virtual Machine to a Distributed Switch Port Group
6. Enable vSphere DRS on the Cluster
7. Upgrade the Distributed Switch to Version 6.5.0
8. Configure Bandwidth Allocation for a Virtual Machine

If you logged out or if systems are disconnected or timed out, you must restore the connection to the
lab environment.
67
4. When the There is a problem with this website’s security certificate
message appears, click Continue to this website (not recommended).
Task 2: Create a Distributed Switch

You create a distributed switch and configure a production port group.
2. In the center pane, click the Networking icon.
3. In the left pane, expand your vCenter Server Appliance name.
4. Create a distributed switch named dvs-Production.
a. Right-click SA Datacenter and select Distributed Switch > New Distributed Switch.
b. On the Name and location page, enter dvs-Production in the Name text box and click
Next.
c. On the Select version page, click Distributed switch: 5.5.0 and click Next.
Do not select Distributed switch: 6.5.0. You upgrade the distributed switch to 6.5 later.
d. On the Edit settings page, configure the distributed switch parameters.
Option Action
Number of uplinks Enter 4.
Network I/O Control Leave as Enabled.
Default port group Leave the check box selected.
Port group name Enter pg-Production in the text box.
e. Click Next.
f. On the Ready to complete page, review the configuration settings and click Finish.
68 Lab 13 Working with Network I/O Control

5. Configure the pg-Production port group so that it uses Uplink 3.
a. In the left pane, expand the newly created distributed switch, then right-click pg-
Production and select Edit Settings.
b. In the Edit Settings dialog box, select Teaming and failover on the left side.
c. Under Active uplinks, select Uplink 1.
d. Click the down arrow to move Uplink 1 to Unused uplinks.
e. Move Uplink 2 and Uplink 4 to Unused uplinks.
f. Verify that Uplink 3 is the only active uplink.
g. Click OK.
Task 3: Add the ESXi Host to the New Distributed Switch

Add the ESXi host and physical adapters to the distributed switch. The distributed switch serves as a
centralized interface to configure, monitor, and administer the virtual machine and vmkernel
switching for the data center.
• vmnic for the distributed switch
1. In the left pane, right-click the dvs-Production distributed switch and select Add and Manage
Hosts.
2. On the Select task page, click Add hosts and click Next.
3. On the Select hosts page, click New Hosts.
4. Select the sa-esxi-01.vclass.local and sa-esxi-02.vclass.local check boxes and click OK.
5. Click Next.
6. On the Select network adapter tasks page, deselect the Manage VMkernel adapters check box
and leave the Manage physical adapters check box selected.
7. Click Next.
8. On the Manage physical network adapters page, under sa-esxi-01.vclass.local, select the vmnic
for the distributed switch and click Assign uplink.
9. Select Uplink 3 and click OK.
10. Under sa-esxi-02.vclass.local, select the vmnic for the distributed switch and click Assign
uplink.
11. Select Uplink 3 and click OK.
12. Click Next.
Lab 13 Working with Network I/O Control 69

13. On the Analyze impact page, verify that the status appears as No impact and click Next.
14. On the Ready to complete page, review your settings and click Finish.
Task 4: Examine the Distributed Switch Configuration

You examine the configuration of the distributed switch uplinks. The distributed switch uplinks are
bound to the associated physical interfaces on the ESXi hosts. You also examine the configuration
of other distributed switch features, including maximum transmission unit (MTU) value, VLAN
capabilities, LACP aggregation groups, NetFlow, and VMware vSphere® Network I/O Control.
• Student designation
1. In the left pane, select the dvs-Production distributed switch.
2. In the middle pane, click the Configure tab.
3. Under Settings, select Topology.
4. In the distributed switch topology diagram, click the arrow next to Uplink 3 to expand the view.
5. Verify that vmnic interfaces of the two ESXi hosts are attached.
6. On the left side of the center pane, select Properties and verify the settings.
• Network I/O Control is enabled.
• Number of uplinks is 4.
• The MTU size is 1500 bytes.
• The Cisco Discovery Protocol is implemented.
7. Under Settings, select each additional item and verify the settings.
• LACP LAG is not defined.
• Private VLAN is not defined.
• NetFlow collector is not defined.
• Port mirroring is not configured.
• Health check is not enabled.
8. In the left pane, select the pg-Production port group.
9. Click the Configure tab, click Properties under Settings, and verify the following settings:
• Static port binding is implemented.
• Elastic port allocation is implemented.
• Eight ports are defined.

Task 5: Migrate a Virtual Machine to a Distributed Switch Port Group
You move the virtual machine from the current standard switch on the ESXi host to the port group
on the distributed switch.
1. In the left pane, right-click the dvs-Production distributed switch and select Migrate VMs to
Another Network.
2. Migrate the virtual machine from VM Network on the standard switch to the pg-Production
network on the distributed switch.
a. On the Select source and destination networks page, configure the source and destination
networks.
• For the Source network, leave Specific network selected, click Browse, select VM
Network, and click OK.
• For the Destination network, click Browse, select the pg-Production port group, and
click OK.
b. Click Next.
c. On the Select VMs to migrate page, select the Linux-01 check box and click Next.
d. On the Ready to complete page, review the settings and click Finish.
e. View the Recent Tasks pane to monitor the Reconfigure virtual machine task to
completion.
3. View your distributed switch configuration.
a. In the left pane, select dvs-Production.
b. In the center pane, click the Hosts tab.
c. Verify that both ESXi hosts’ state are connected.
d. Click the VMs tab and verify that the virtual machine that you migrated is listed.
e. Click the Networks tab.
f. Click Distributed Port Groups and verify that pg-Production is listed.
g. Click Uplink Port Groups and verify that an uplink port group is created for the
distributed switch.

Task 6: Enable vSphere DRS on the Cluster
You enable vSphere Distributed Resource Scheduler on the SA Compute-01 cluster.
2. Right-click the SA Compute-01 cluster and select Settings.
3. In the center pane, click the Configure tab, and click vSphere DRS under Services.
4. Click Edit.
5. In the Edit Cluster Settings dialog box, select the Turn ON vSphere DRS check box.
6. Keep the DRS Automation level at Fully Automated and click OK.
7. Right-click SA Compute-01 and select New Resource Pool.
8. In the New Resource pool dialog box, enter SA-RP in the Name text box.
9. Keep the rest of the defaults, and click OK.
10. Drag the Linux-01 virtual machine into the SA-RP resource pool.
Task 7: Upgrade the Distributed Switch to Version 6.5.0

You upgrade the distributed switch to version 6.5.0 in order to upgrade Network I/O Control to its
latest version.
1. Point to the Home icon and select Networking.
2. In the left pane, right-click dvs-Production and select Upgrade > Upgrade Distributed
Switch.
The Upgrade Distributed Switch wizard appears.
3. On the Configure upgrade page, verify that Version 6.5.0 is selected and click Next
4. On the Check compatibility page, verify host compatibility and click Next.
5. On the Ready to complete page, review the distributed switch settings and click Finish.
6. In the left pane, select dvs-Production.
8. Click Properties and verify that the upgraded version is displayed.

Task 8: Configure Bandwidth Allocation for a Virtual Machine
You use vSphere Web Client to configure the bandwidth allocation for the virtual machine that is
assigned to the dvs-Production switch.
2. In the left pane, right-click the Linux-01 virtual machine and select Edit Settings.
3. Configure bandwidth allocation for a virtual machine network adapter.
a. In the Edit Settings dialog box, expand Network Adapter 1.
b. From the Shares drop-down menu, select High.
This configuration sets the relative priority of the network traffic from this virtual machine.
c. From the Reservation drop-down menu, select Maximum 10,000.
This reservation must be available to the virtual machine network adapter when the virtual
machine is powered on.
d. From the Limit drop-down menu, select Maximum 10,000.
This limit specifies the bandwidth limit that the virtual machine network adapter can
consume.
e. From the Limit drop-down menu, select Gbit/s.
Q1. Are you able to apply the configuration?

1. No, an alert appears next to Network adapter 1, and OK is unavailable.
f. From the Limit drop-down menu, select Mbit/s and click OK.
Network I/O Control allocates the bandwidth that you reserved for the network adapter of
the virtual machine out of the reservation quota of the network resource pool.

Lab 14 Using vCenter Server High
Availability
Objective: Use vCenter Server High Availability

1. Configure the vCenter Server High Availability Network

2. Log In to the High Availability vCenter Server Appliance Instance
3. Configure vCenter Server for High Availability
4. Create the Passive Node
5. Create the Witness Node
6. Finish Configuring vCenter Server High Availability
7. Manually Initiate a vCenter Server Failover
8. Verify That Your vCenter Server Failover Took Place
9. Verify the vCenter Server Failover
Task 1: Configure the vCenter Server High Availability Network

You use vSphere Web Client to add a second network adapter to the vCenter Server Appliance
instance that you will use for this lab exercise. The second network adapter is used for the private,
vCenter Server High Availability network, which is used for communication between the vCenter
Server High Availability nodes. After you power on the vCenter Server Appliance instance, you use
the Virtual Appliance Management interface to bring the second network adapter online.
75
1. In the Internet Explorer window, click the vSphere Web Client tab.
2. On the Home page, click the Hosts and Clusters icon.
3. Add a second network adapter to the high availability vCenter Server Appliance instance.
a. In the left pane, right-click VCHA and select Edit Settings.
The Edit Settings dialog box appears.
b. Towards the bottom of the dialog box, select Network from the New device drop-down
list.
c. Click Add.
The new network adapter is added to the virtual hardware list.
d. Select VCHA-Cluster from New Network drop-down list.
VCHA-Cluster is the private network used for communication between the vCenter Server
High Availability nodes.
e. Click OK.
4. View information about the network adapters connected to VCHA.
a. In the left pane, select VCHA.
b. In the center pane, click the Summary tab.
c. Expand the VM Hardware panel.
d. Verify that Network adapter 1 is connected to the VCHA-Management network.
e. Verify that Network adapter 2 is connected to the VCHA-Cluster network.
5. Power on VCHA.
a. In the left pane, right-click VCHA and select Power > Power On.
VCHA takes a few minutes to start up completely.
6. Verify that the second network adapter on VCHA is online.
a. Open a new tab in the Internet Explorer window.
b. In the address bar, enter https://vcha.vclass.local:5480.
c. If a security exception message is displayed, click Continue to this website.
The VMware vSphere Appliance Management login page appears.
d. Log in with the user name root and the standard lab password.
e. In the Navigator pane, select Networking and click the Manage tab.
f. Under Networking Interfaces, verify that both nic0 and nic1 are up.
76 Lab 14 Using vCenter Server High Availability

7. If nic1 is down, then configure the IP settings for nic1.
a. Click Edit next to Networking Interfaces.
The Edit IP Configuration dialog box appears.
b. Expand nic1 and click Use the following IPv4 settings.
c. In the IPv4 Address text box, enter 192.168.1.60.
d. In the IPv4 Address Prefix text box, enter 24.
e. Keep the rest of the defaults and click OK.
f. Verify that the status of nic1 is Up.
8. Log out of the Virtual Appliance Management interface and close the tab.
Task 2: Log In to the High Availability vCenter Server Appliance

Instance
You use vSphere Web Client to log in to the vCenter Server Appliance instance that will be
configured for high availability. You log in by using a browser bookmark that is preset in the
Internet Explorer Favorites toolbar.
1. Open a new tab in Internet Explorer.
2. In the Favorites bar, select vSphere Web Clients > VCHA.
3. When the security exception for vSphere Web Client appears, click Continue to this website.
It takes a few minutes for the vSphere Client web server to initialize. When the web server
finishes initializing, the VMware vCenter Single Sign-On login page appears.
4. In the User name text box, enter administrator@vcha.local.
5. In the Password text box, enter the standard lab password.
6. Click Login.
The vSphere Web Client page appears.
Lab 14 Using vCenter Server High Availability 77

Task 3: Configure vCenter Server for High Availability
You configure the vCenter Server Appliance instance for high availability.
1. In the left pane, select vcha.vclass.local.
2. In the center pane, click the Configure tab and select vCenter HA on the left side.
3. In the upper-right corner of the center pane, click Configure.
The Configure vCenter HA wizard appears.
4. On the Select a configuration option page, select Advanced and click Next.
5. On the Connection IP settings page, configure the IP settings for the passive node and witness
node.
a. Under Passive Node, enter 192.168.1.61 in the vCenter HA IP address text box.
This address is the IP address on the private vCenter Server High Availability network for
the passive node.
b. In the Subnet mask (prefix for IPv6) text box, enter 255.255.255.0.
c. Under Witness Node, enter 192.168.1.62 in the vCenter HA IP address text box.
This address is the IP address on the private network for the witness node.
d. In the Subnet mask (prefix for IPv6) text box, enter 255.255.255.0.
e. Click Next.
The Clone VMs page appears. Do not click Finish yet.
You must create the passive node and witness node before you can complete the vCenter
Server High Availability configuration.
Task 4: Create the Passive Node

You create the passive node by cloning the vCenter Server High Availability active node. The active
node is the vCenter Server Appliance instance, VCHA.
1. In Internet Explorer, switch to the vSphere Web Client tab for sa-vcsa-01.vclass.local.
2. In the left pane, right-click VCHA and select Clone > Clone to Virtual Machine.
The Clone Existing Virtual Machine wizard appears.
3. On the Select a name and folder page, enter VCHA-Passive for the virtual machine name and
click Next.
4. On the Select a compute resource page, expand the SA Compute-01cluster and select sa-esxi-
02.vclass.local.

5. Click Next.
6. On the Select storage page, select the datastore and virtual disk format.
a. Select SA-ESXi-02-Local.
b. From the Select virtual disk format drop-down list, select Same format as source.
c. Click Next.
7. From the Select clone options page, select the Customize the operating system and Power on
virtual machine after creation check boxes.
8. Click Next.
9. On the Customize guest OS page, create a new customization specification for the passive node.
A preconfigured customization specification named VCHA-Passive Specification has been
created for convenience sake. As an alternative to performing step 9, you can choose VCHA-
Passive Specification instead of creating a new customization specification.
a. Click the Create a new specification icon.
The New VM Guest Customization Spec wizard appears.
b. On the New Customization Specification page, enter the name your choice in the
Customization Spec Name text box and click Next.
c. On the Computer Name page, select the Enter a name check box and enter vcha in the
text box.
The passive node computer name must match the computer name of the active node.
d. In the Domain name text box, enter vclass.local and click Next.
e. On the Time Zone page, configure the time zone settings.
Option Action
Area Select America.
Location Select Los Angeles and click Next.
f. On the Configure Network page, select NIC1 and click the Edit icon.
g. Click Use the following IP settings.

h. Configure the IP settings for NIC1.
Option Action
IP Address Enter 172.20.20.60.
This IP address is the public address of the active node.
Subnet Mask Enter 255.255.255.0.
Default Gateway Enter 172.20.20.10.
Alternate Gateway Leave blank and click OK.
i. On the Configure Network page, select NIC2 and click the Edit icon.
j. Click Use the following IP settings.
k. Configure the IP settings for NIC2.
Option Action
Default Gateway Enter 172.20.20.10.
l. On the Configure Network page, click Next.

m. On the Enter DNS and Domain Settings page, configure the DNS and domain information.
Option Action
Primary DNS Enter 172.20.20.10.
Secondary DNS and Tertiary DNS Leave blank
DNS Search Path Enter vclass.local
n. Click Add.

o. Click Next.
p. On the Ready to complete page, review the settings and click Finish.
The Clone Existing Virtual Machine wizard reappears.
q. On the Customize guest OS page, select the passive node customization specification that
you just created and click Next.
10. On the Ready to complete page, review the settings and click Finish.
11. View the Recent Tasks pane and monitor the Clone Virtual Machine task to completion.
12. In the left pane, verify that the VCHA-Passive virtual machine appears and is powered on.
Task 5: Create the Witness Node

You create the witness node by cloning the vCenter Server High Availability active node. The active
node is the vCenter Server Appliance instance, VCHA.
1. In the left pane, right-click VCHA and select Clone > Clone to Virtual Machine.
The Clone Existing Virtual Machine wizard appears.
2. On the Select a name and folder page, enter VCHA-Witness for the virtual machine name and
click Next.
3. On the Select a compute resource page, expand the SA Compute-01 cluster and select sa-esxi-
04.vclass.local.
4. Click Next.
5. On the Select storage page, select the datastore and virtual disk format.
a. Select SA-ESXi-04-Local.
b. From the Select virtual disk format drop-down list, select Same format as source.
c. Click Next.
6. From the Select clone options page, select the Customize the operating system check box and
select the Power on virtual machine after creation check box.
7. Click Next.
8. On the Customize guest OS page, create a new customization specification for the witness node.
A preconfigured customization specification named VCHA-Witness Specification is already
created for convenience sake. As an alternative to creating a new customization specification in
step 8, you can choose VCHA-Witness Specification.
a. Click the Create a new specification icon.
The New VM Guest Customization Spec wizard appears.

b. On the New Customization Specification page, enter the name of your choice in the
Customization Spec Name text box and click Next.
c. On the Computer Name page, select the Enter a name check box and enter vcha-
witness in the text box.
The witness node computer name must not match the computer name of the active node.
d. In the Domain name text box, enter vclass.local and click Next.
e. On the Time Zone page, configure the time zone settings.
Option Action
Area Select America.
Location Select Los Angeles and click Next.
f. On the Configure Network page, select NIC1 and click the Edit icon.
g. Leave Use DHCP to obtain an IP address automatically clicked and click OK.
h. On the Configure Network page, select NIC2 and click the Edit icon.
i. Click Use the following IP settings and configure the IP settings for NIC2.
Option Action
Default Gateway Leave blank.
j. On the Configure Network page, click Next.

k. On the Enter DNS and Domain Settings page, configure the DNS and domain information.
Option Action
Primary DNS Enter 172.20.20.10.
Secondary DNS and Tertiary DNS Leave blank.
DNS Search Path Enter vclass.local.

l. Click Add.
m. Click Next.
n. On the Ready to complete page, review the settings and click Finish.
The Clone Existing Virtual Machine wizard reappears.
9. On the Customize guest OS page, select the witness node customization specification that you
just created and click Next.
10. On the Ready to complete page, review the settings and click Finish.
11. View the Recent Tasks pane and monitor the Clone Virtual Machine task to completion.
This task takes a few minutes to complete. You must wait until this task is completed before
continuing to the next task.
12. In the left pane, verify that the VCHA-Witness virtual machine appears and is powered on.
13. Wait at least one minute before performing the next task.
Waiting for at least one minute gives the wizard enough time to finish preparing the witness
node.
Task 6: Finish Configuring vCenter Server High Availability

After creating the passive node and witness node, you finish configuring vCenter Server High
Availability on the high availability vCenter Server Appliance instance.
1. In Internet Explorer, switch to the vSphere Web Client tab for vcha.vclass.local.
The Configure vCenter HA wizard is open.
2. On the Clone VMs page, click Finish to complete the vCenter High Availability configuration.
3. Wait 20 minutes.
During this time you should view the Recent Tasks pane to monitor the configuration task.
4. Verify that vCenter Server High Availability is successfully configured.
a. Verify that the center pane shows that vCenter HA is enabled.
b. In the upper-right corner of the center pane, click the vCenter HA Monitoring link.
c. Verify that the health is good for the active, passive, and witness nodes.
d. In the upper-right corner of the center pane, click the vCenter HA Settings link.

Task 7: Manually Initiate a vCenter Server Failover
You use vSphere Web Client to initiate a vCenter Server failover from the active vCenter Server
instance.
1. In the upper-right corner in the center pane, click Initiate Failover.
2. In the Initiate vCenter HA Failover window, click Yes.
As the failover takes place, connectivity to the vCenter Server is lost for a short period of time.
It may take 5 minutes before you see the Connection Error dialog indicating a loss of
connectivity to the VCHA vCenter Server.
3. After connectivity to the vCenter Server instance is lost, close the vSphere Web Client tab for
vcha.vclass.local.
4. Open a new tab and select vSphere Web Clients > VCHA from the Favorites bar.
NOTE
Failover takes several minutes to complete. Click the Refresh icon in the web browser. You can
expect to see a Failover in Progress message for as long as 15 minutes before you see the
VMware vCenter Single Sign-On page for VCHA again.
Task 8: Verify That Your vCenter Server Failover Took Place

As the vCenter Server High Availability administrator, you use vSphere Web Client to examine the
settings and events to verify that the active vCenter Server instance is the peer vCenter Server
instance.
1. In the vSphere Web Client tab for vcha.vclass.local, log in to VCHA as
administrator@vcha.local using the standard lab password.
It may take up to 5 minutes after you log in for the VCHA vSphere Web Client screen to
appear.
2. In the left pane, click vcha.vclass.local at the top of the inventory tree.
3. In the center pane, click the Configure tab and click vCenter HA on the left side.
4. In the center pane, select the Active node.
5. In the Active Settings pane, view the IP address of the active node.
The IP address belongs to the VCHA-Passive virtual machine.
6. Verify that the virtual machine is the VCHA passive node.

7. In the center pane, click the Monitor tab and click Tasks & Events.
8. On the left side, select Tasks and examine the output for indications that a vCenter Server
failover was initiated.
9. Select Events and examine the output for indications that a vCenter Server failover took place.
10. In the center pane, click the Monitor tab and click vCenter HA.
11. Examine the health of the cluster.
12. Close the vSphere Web Client tab for vcha.vclass.local.
Task 9: Verify the vCenter Server Failover

As the vCenter Server administrator, you use vSphere Web Client to examine the settings and events
to verify that the active vCenter is the peer vCenter Server.
2. In the left pane, click vCenter Server at the top of the inventory tree.
3. In the center pane, click the Configure tab and click vCenter HA.
4. In the center pane, select the Active node.
5. In the Active Settings pane, select the VM Settings tab.
6. Verify that the virtual machine is the VCHA peer node.
7. In the center pane, click Monitor and click Tasks & Events.
8. Select Tasks on the left side and examine the output for indications that a vCenter Server
failover was initiated.
9. Select Events and examine the output for indications that a vCenter Server failover took place.
10. Click vCenter HA and examine the health of the cluster.

Lab 15 Migrating Virtual Machines
Across vCenter Server Instances
Objective: Use vSphere vMotion to migrate virtual

machines across vCenter Server instances

2. Add an Uplink to the Distributed Switch
3. Add a VMkernel Adapter to the vSphere vMotion Port Group
4. Use vSphere vMotion to Migrate a Virtual Machine

87
4. When the There is a problem with this website’s security certificate
warning message is displayed, click Continue to this website (not recommended).
Task 2: Add an Uplink to the Distributed Switch

You prepare the distributed switch for VMware vSphere® vMotion® traffic by adding an uplink to
the distributed switch and creating a new port group.
1. In the center pane in vSphere Web Client, click the Networking icon.
2. In the left pane, right-click the dvs-Production distributed switch and select Distributed Port
Group > New Distributed Port Group.
3. In the Name text box, enter pg-vMotion and click Next.
4. On the Configure Settings page, accept the defaults and click Next.
5. On the Ready to complete page, review the settings, and click Finish.
6. Configure the pg-vMotion port group so that it uses the Uplink 2.
a. In the left pane, click the arrow beside dvs-Production to expand the distributed switch.
b. Right-click pg-vMotion and select Edit Settings.
c. In the Edit Settings dialog box, click Teaming and failover on the left side.
d. Under Active uplinks, select Uplink 1.
e. Click the down arrow to move Uplink 1 to Unused uplinks.
f. Move Uplink 3 and Uplink 4 to Unused uplinks.
g. Verify that Uplink 2 is the only active uplink.
h. Click OK.
88 Lab 15 Migrating Virtual Machines Across vCenter Server Instances

Task 3: Add a VMkernel Adapter to the vSphere vMotion Port Group
You add a VMkernel adapter for vSphere vMotion traffic on the host to allow virtual migration
network traffic.
• ESXi host names
1. In the left pane, right-click dvs-Production and select Add and Manage Hosts.
2. On the Select task page, click Manage host networking, and click Next.
3. On the Select hosts page, click Attached hosts.
4. In the Select member hosts dialog box, select both ESXi host names and click OK.
5. Click Next.
6. On the Select network adapter tasks page, leave the Manage physical adapters and Manage
VMkernel adapters check boxes selected.
7. Click Next.
8. Add a physical network adapter for vSphere vMotion on the first and second ESXi hosts.
a. Under the first ESXi host on the Manage physical network adapters page, select vmnic1.
b. Click Assign uplink.
c. In the Select an Uplink for vmnic1 window, select Uplink 2 and click OK.
d. Under the second ESXi host, select vmnic1 and click Assign uplink.
e. In the Select an Uplink for vmnic1 window, select Uplink 2 and click OK.
f. Click Next.
9. Add a VMkernel network adapter for vSphere vMotion on the first ESXi host.
a. On the Manage VMkernel network adapters page, select the first ESXi host and click New
adapter.
b. Next to the Select an existing network text box, click Browse.
c. Select pg-vMotion and click OK.
d. Click Next.
e. On the Port properties page, select the vMotion check box, and click Next.
f. On the IPv4 settings page, keep the defaults and click Next.
Lab 15 Migrating Virtual Machines Across vCenter Server Instances 89

10. Add a VMkernel network adapter for vSphere vMotion on the second ESXi host.
a. On the Manage VMkernel network adapters page, select the second ESXi host and click
New adapter.
b. Next to the Select an existing network text box, click Browse.
c. Select pg-vMotion and click OK.
d. Click Next.
e. On the Port properties page, select the vMotion check box and click Next.
f. On the IPv4 settings page, keep the defaults and click Next.
11. On the Manage VMkernel network adapters page, click Next.
12. On the Analyze impact page, click Next.
14. View the Recent Tasks pane and monitor the tasks to completion.
15. Verify the distributed switch configuration.
a. In the left pane, select dvs-Production.
b. In the center pane, click the Configure tab and select Topology on the left side.
c. In the pg-vMotion section, click the arrow next to VMkernel Ports and make note of the IP
addresses that are assigned to the two vmk1 interfaces.
d. Click the arrow next to Uplink 2 to verify that vmnic1 exists for both ESXi hosts.
Task 4: Use vSphere vMotion to Migrate a Virtual Machine

You use vSphere Web Client to migrate a virtual machine from your vCenter Server instance to the
vCenter Server instance designated as the migration destination. Using vSphere vMotion to migrate
virtual machines between linked vCenter Server sites is a vSphere 6.x feature.
The vMotion network has been preconfigured in this lab environment with the destination host on
the destination vCenter Server.
• Destination vCenter Server Appliance name
• Destination ESXi host name
• Destination datastore.

2. If necessary, click the arrow to expand your vCenter Server Appliance name and your data
center in the left pane.
3. In the left pane, right-click the Linux-02 virtual machine and select Power > Power On.
4. Wait for the initialize powering on task to complete.
5. In the left pane, right-click the Linux-02 virtual machine and select Migrate.
The Migrate wizard appears.
6. On the Select the migration type page, click Change both compute resource and storage.
7. Click Select storage first and click Next.
8. On the Select a storage page, select the destination datastore on the destination vCenter Server
Appliance and click Next.
9. On the Select a compute resource page, select the destination ESXi host name on the Hosts tab
and click Next.
10. On the Select a folder page, select SB Datacenter and click Next.
11. On the Select network page, select pg-SB Production from the Destination Network drop-
down menu and click Next.
12. On the Select vMotion priority page, select Schedule vMotion with high priority and click
Next.
14. View the Recent Tasks pane and wait for the Relocate virtual machine task to complete.
15. In the left pane, click the arrow to expand the destination vCenter Server Appliance name and
data center to verify that the migrated virtual machine is listed.
Lab 15 Migrating Virtual Machines Across vCenter Server Instances 91

Answer Key
Lab 2: Working with the vCenter Server Appliance Shell

Task 1: Access the Appliance Shell and Review Information . . . . . . . . . . . . . . . . . . . . . . . .5
1. VMware vCenter Server Appliance 6.5.0. 3. stage, unstage, validate, install, and list.
2. VMware vCenter Server® with an external
VMware Platform Services Controller™.
Lab 9: Upgrading Virtual Machines to the Current Hardware Version

Task 2: Upgrade Your Virtual Machine to Hardware Version 13. . . . . . . . . . . . . . . . . . . . .48
1. VM version 8. 2. VM version 13.
Lab 10: Working with Virtual Volumes

Task 2: Validate the Storage Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
1. http://172.20.10.97:8443/vasa/version.xml. 3. xVP SCSI Array and xVP NFS Array.
2. Version 3.0.
Task 3: Use NAS to Create a Virtual Volume Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . .51
1. 172.20.10.97:/mnt/pes/nfs_2.
Task 4: Use iSCSI to Create a Virtual Volume Datastore . . . . . . . . . . . . . . . . . . . . . . . . . .53
1. The datastore is inactive because storage 2. Three LUNs appear: 0, 1, and 2.
provider must also be configured as an iSCSI 3. Yes. Four LUNs appear: 0, 1, 2, and 260.
target of the software iSCSI adapter.
Lab 11: Creating Storage Policies

Task 2: Create a Gold Storage Policy for a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . .58
1. The NFS-backed virtual volumes datastore
that was created in the previous lab.
93
Lab 13: Working with Network I/O Control
Task 8: Configure Bandwidth Allocation for a Virtual Machine . . . . . . . . . . . . . . . . . . . . . .73
1. No, an alert appears next to Network adapter
1, and OK is unavailable.
94 Answer Key

Vmware Vsphere: What'S New: Lab Manual Esxi 6.5 and Vcenter Server 6.5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vmware Vsphere: What'S New: Lab Manual Esxi 6.5 and Vcenter Server 6.5

Uploaded by

Copyright:

Available Formats

VMware vSphere:

VMware® Education Services

Objective: Use VMware Host Client

1. Access the Student Desktop System

Task 1: Access the Student Desktop System

3. Click Continue to this website (not recommended).

Task 3: Assign Licenses to the ESXi Host

Lab 1 Working with VMware Host Client 3

4 Lab 1 Working with VMware Host Client

Objective: Manage vCenter Server Appliance by using

1. Access the Appliance Shell and Review Information

Task 1: Access the Appliance Shell and Review Information

The MTPuTTY (Multi-Tabbed PuTTY) utility window appears.

Q1. What is the version of your vCenter Server Appliance system?

Q2. What is the type of your vCenter Server Appliance system?

Q3. Which subcommands are listed?

6. At the command prompt, enter software-packages list.

9. Review the API calls that are supported by this server.

Task 2: Troubleshoot the vSphere Client User Interface Service

After a few seconds, a Successfully stopped service vsphere-ui confirmation

6 Lab 2 Working with the vCenter Server Appliance Shell

6. Click Continue to this website (not recommended).

Lab 2 Working with the vCenter Server Appliance Shell 7

Objective: Use vSphere Client

1. Use vSphere Client to Log In to Your vCenter Server Appliance System

Task 1: Use vSphere Client to Log In to Your vCenter Server Appliance

c. Click Continue to this website (not recommended).

Task 2: Add an ESXi Host to the vCenter Server Inventory

10 Lab 3 Working with vSphere Client

13. Log out of vSphere Client.

Lab 3 Working with vSphere Client 11

Objective: Use vSphere Web Client

Task 1: Use vSphere Web Client to Log In to Your vCenter Server

Task 2: Add Another ESXi Host to the Cluster

14 Lab 4 Working with vSphere Web Client

Task 3: Update the License Information for the vCenter Server

Lab 4 Working with vSphere Web Client 15

Task 5: Customize the Workspace in vSphere Web Client

7. In the Close Getting Started Tab dialog box, click Yes.

16 Lab 4 Working with vSphere Web Client

Lab 4 Working with vSphere Web Client 17

Objective: Migrate a Windows vCenter Server system to

1. Verify That vCenter Server for Windows Is Running

Task 1: Verify That vCenter Server for Windows Is Running

Task 2: Start the Migration Assistant Tool on the Windows vCenter

20 Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance

Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance 21

22 Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance

Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance 23

c. Click Continue to this website (not recommended).

24 Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance

Task 5: Perform Stage 2 of the Migration Process

Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance 25

8. Click Close to exit the vCenter Server Appliance installer.

Task 6: Verify Successful Migration

26 Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance

Lab 5 Migrating Windows vCenter Server to vCenter Server Appliance 27

Objective: Back up and restore vCenter Server Appliance

1. Prepare the Environment

Task 1: Prepare the Environment

8. Click Continue to this website (not recommended).

Task 2: Back Up Your vCenter Server Appliance System

b. Click Continue to this website (not recommended).