Vmware Vsphere: Troubleshooting Workshop: Lab Manual Esxi 5.5 and Vcenter Server 5.5
Vmware Vsphere: Troubleshooting Workshop: Lab Manual Esxi 5.5 and Vcenter Server 5.5
Troubleshooting Workshop
Lab Manual
ESXi 5.5 and vCenter Server 5.5
1
Lab 1
Adding the VMware vSphere
Management Assistant to Active
Directory
2
Preparing for the lab
Refer to your worksheet for information:
vSphere Management Assistant system name
Domain Name
3
Task 1: Access the desktop system
In this task, you will log in to the student desktop system.
1. Ask the instructor how to access your student desktop system. For example, the instructor
might
have you use Remote Desktop Connection to connect to this system. Depending on the
lab environment, the student desktop system and
VMware® vCenter Server™ might be the same system.
2. Log in to the student desktop system. The instructor will give you your account information.
4
Task 3: Verify that the vSphere licenses are valid
In this task, you will log in to the vCenter Server system and determine
whether the VMware vSphere® licenses are valid. If the licenses have expired,
then you will add valid, temporary licenses to your vCenter Server.
Start VMware vSphere® Client™ and use it to log in to the vCenter Server system.
You recorded the vCenter Server system name, user name, and password in “Preparing for the
lab.”
1. Select Home > administration > Licensing. The Licensing pane is
displayed.
2. On the Management tab, expand the products in the list and determine
whether the vCenter Server license and the VMware vSphere® Enterprise
Plus Edition™ license have expired.
3. If the licenses have expired, add licenses to vCenter Server. If the licenses
have not expired, proceed to task 4.
a. Click the Manage vSphere Licenses link in the upper-right corner.
b. When prompted by the Manage vSphere Licenses wizard, perform the following actions.
5
Assign Licenses Click the Show all radio button. If a security
warning appears, click Ignore.
In the ESX tab, the ESXi host appears in the
left pane. In the right pane, select the valid
license.
Click the vCenter Server tab.
In the vCenter Server tab, the vCenter Server
system appears in the left pane. In the right
pane, select the valid license.
Click Next.
c. In the Management tab, expand the products and verify that the licenses have
been successfully added.
d. Select Home > Inventory > Hosts and Clusters.
e. If the ESXi host has the disconnected status, right-click the ESXi host and select
Connect.
f. Click Yes to confirm reconnecting the host and verify that the ESXi host is reconnected.
6
Task 4: Log in to vSphere Management Assistant
In this task, you will log in to VMware vSphere® Management Assistant.
1. On your desktop system, start a PuTTY session by double-clicking the PuTTY icon.
2. In the Host Name (or IP address) field, type the vSphere Management Assistant
system name that you recorded in “Preparing for the lab.”
3. Click Open. If a PuTTY Security Alert window is displayed, click Yes.
4. At the login prompt, type the vSphere Management Assistant user name and
vSphere Management Assistant user’s password that you recorded in “Preparing for
the lab.”
When you are logged in, the vSphere Management Assistant Command Prompt
window is displayed.
7
Task 5: Add the vSphere Management Assistant instance to
an AD domain
In this task, you will join your vSphere Management Assistant instance to the
class Active Directory domain. Student A and student B must work together to perform this
task.
NOTE
All commands are case-sensitive. Type all commands in a single line unless otherwise
instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Join the vSphere Management Assistant instance to the class Active Directory
domain by running the following command:
sudo domainjoin-cli join domain-name domain-username
Replace domain-name with the Active Directory Domain name that you
recorded in “Preparing for the lab.” Replace domain-username with the
domain user name that you recorded in “Preparing for the lab.”
2. When prompted for the vSphere Management Assistant user’s password,
type the vSphere Management Assistant user’s password that you
recorded in “Preparing for the lab.”
3. When prompted for the domain administrator password, type the password that
you recorded in “Preparing for the lab.”
For help with the sudo command, type sudo -h.
4. Verify that the command successfully completes. If a warning is displayed
recommending that you reboot the system, do not reboot the system.
5. Verify that the vSphere Management Assistant instance is part of an Active Directory domain.
sudo domainjoin-cli query
6. If prompted for the vSphere Management Assistant user’s password,
type the vSphere Management Assistant user’s password that you
recorded in “Preparing for the lab.”
8
Task 6: Remove the vSphere Management Assistant
instance from
the AD domain
In this task, you will remove the vSphere Management Assistant instance from the
Active Directory vSphere Management Assistant. Student A and student B must
work together to perform this task.
1. Remove the vSphere Management Assistant instance from the Active Directory domain.
sudo domainjoin-cli leave
9
Lab 2
Using the Command Line to
Review Configuration
5. Use the esxcli and vicfg-* commands to determine virtual switch information
8. (For vClass users only) Access the ESXi host’s DCUI locally
10
Preparing for the lab
Refer to your worksheet for information
Record the following information.
*You will use the lab environment worksheet to verify important information about
your lab configuration.
11
Task 1: Configure the target server
In this task, you will log in to the VMware vSphere® Management Assistant
system and you will configure the target server. Students do the steps in this task individually.
NOTE
All commands are case-sensitive. Type all commands in a single line unless otherwise
instructed. (For readability, commands might be displayed on two lines instead of one.)
1. If you are not logged in to the vSphere Management Assistant system, perform the
following steps:
a. On your VMware® vCenter Server™ desktop, start a PuTTY session by double-
clicking the PuTTy icon.
b. In the Host Name (or IP address) text box, type the vSphere Management
Assistant system name that you recorded in “Preparing for the lab.”
c. Click Open. If a PuTTY Security Alert window is displayed, click Yes.
d. At the login prompt, type the vSphere Management Assistant user name and
user’s password that you recorded in “Preparing for the lab.”
c. Type yes.
3. Repeat step 2 but replace server with the VMware® ESXi™ host name that
you recorded in “Preparing for the lab.” Also replace user with root.
a. When prompted for the password, type the ESXi host root password that
you recorded in “Preparing for the lab.”
4. Verify that the target servers were added properly:
vifp listservers
5. Verify that your vCenter Server system and your ESXi host are in the list.
12
6. Set the target server for commands:
vifptarget -s server
server is the ESXi host name that you recorded in “Preparing for the lab.”
7. After running the command, verify that the name of the ESXi host is
displayed as part of the command prompt.
8. For help with vSphere Management Assistant commands, use the --help option.
a. esxci --help
b. vifp --help
c. vifptarget --help
13
Task 2: Experiment with the more and less commands
In this task, you will use the more and less commands. You can use these commands at the
command line to page through a command’s output.
NOTE
All commands are case-sensitive. Type all commands in a single line unless otherwise
instructed. (For readability, commands might be displayed on two lines instead of one.)
1. Display help information for the esxcli command.
esxcli --help
Notice that the command does not pause after each screen of information.
2. Display help information for the esxcli command with the more command.
esxcli --help | more
a. Use the more command to scroll
down. The more command scrolls
down only.
b. Press the space bar to scroll one screen at a time.
3. Display help information for the esxcli command with the less command.
esxcli --help | less
a. Use the less command to scroll up and down in the input.
b. Press Ctrl+F to go forward in the output.
c. Press Ctrl+B to go backward in the output.
d. Use the up and down arrow keys to navigate backward and forward one line at a time.
e. Press q to quit the less command and return to the command line.
14
Task 3: Use the esxcli command to determine the host hardware
In this task, you will use the command line interface to answer questions about the
hardware configuration of the VMware vSphere® environment. Answers are at the
end of the lab. Students do the steps in this task individually.
1. Which command lines do you use to answer the following questions?
15
Task 5: Use the esxcli and vicfg-* commands to determine virtual
switch information
In this task, you will use the command line to answer questions about the virtual switch
configuration of your vSphere environment. Answers are at the end of the lab. Students do the
steps in this task individually.
1. Which command lines do you use to answer the following questions?
a. What is the IP address of the DNS server?
In the lab environment worksheet, record the uplink name (vmnic#) associated with
each port group.
f. List the VMkernel interfaces on the host.
In the lab environment worksheet, record the VMkernel port name (vmk#) associated
with each port group.
g. List the IP address and subnet mask of the VMkernel interfaces on the host.
In the lab environment worksheet, record the IP address and subnet mask associated
with each VMkernel interface.
h. List the default gateway address for the VMkernel interfaces on the host.
In the lab environment worksheet, record the default gateway associated with each
VMkernel interface.
16
Task 6: Use the vmware-cmd command to determine
virtual machine information
In this task, you will use the command line to answer questions concerning the
virtual machines in the vSphere environment. Answers are at the end of the lab.
Students do the steps in this task individually.
1. Which command lines do you use to answer the following questions?
a. How many virtual machines are on the host?
b. Does the virtual machine that you recorded in “Preparing for the lab” have a snapshot?
d. What is the uptime for the virtual machine whose name you recorded in
“Preparing for the lab?”
17
Task 7: Access the ESXi host’s DCUI remotely
In this task, you will access your ESXi host’s DCUI from a PuTTY session. Being
able to access the DCUI remotely is a useful skill to have when troubleshooting
vSphere problems. Students do the steps in this task individually.
1. On your desktop system, start a PuTTY session by double-clicking the PuTTy icon.
2. In the Host Name (or IP address) text box, type the ESXi host name that
you recorded in “Preparing for the lab.”
3. Click Open. If a PuTTY Security Alert window is displayed, click Yes.
4. At the login prompt, type root for the user name and type the ESXi host
root password that you recorded in “Preparing for the lab.”
5. At the command prompt, type dcui.
6. Press F2 to display the login screen, and log in as user root, using the ESXi
host password that you recorded in “Preparing for the lab.”
7. View the default gateway for your ESXi host.
a. Using the down arrow key, select Configure Management Network and press Enter.
8. Using the up and down arrow keys, view the other menu selections. Do not change
anything. Familiarize yourself with the interface.
9. Press the Escape key until you are logged out of the DCUI.
10. Press Ctrl+C to exit the DCUI window.
18
Task 8: (For vCloud vClass users only) Access the ESXi host’s DCUI
locally
In this task, you will directly access the ESXi host’s DCUI. Being able to access the DCUI
directly is useful when troubleshooting vSphere problems. Students do the steps in this task
individually.
CAUTION
The steps in this task are specific to the vClass lab environment. If you are using a vClass lab
environment, perform this task. If you are not using a vClass environment, skip this task. Ask
the instructor how to access the ESXi host’s DCUI in your lab environment.
1. Open the Internet Explorer Web browser and type the vCloud Director URL that you
recorded in “Preparing for the lab.”
2. Log in to VMware® vCloud Director® by using the vCloud Director user name and
password that you recorded in “Preparing for the lab.”
3. In the vCloud Director UI, find your classroom vApp and click the Open link.
7. Press F2 to log in to the ESXi host as user root and type root’s password, which you
recorded in “Preparing for the lab.”
8. Using the up and down arrow keys, view the menu selections to become familiar with
the interface, but do not make any changes.
9. Press the Escape key until you are logged out of the DCUI.
10. Press the Ctrl+Alt key to release the insertion point from the ESXi console window.
19
Answer Key for Tasks 3 Through 6
Use the answer key to compare to the command lines that you ran in tasks 3 through 6.
1. What is the time and date on the host?
esxcli hardware clock get
2. How many CPUs are on the host?
esxcli hardware cpu list
3. How much memory does the host have?
esxcli hardware memory get
4. What is the PCI address of vmnic5?
esxcli hardware pci list
5. How many VMFS extents are available to the host?
esxcli storage vmfs extent list
6. List the SCSI host bus adapters.
esxcli storage core adapter list
7. List SCSI path statistics.
esxcli storage core path stats get
8. List datastores available to the host.
esxcli storage filesystem list
9. List information about the NFS datastores available to the host.
esxcli storage nfs list
10. What is the IP address of the DNS server?
esxcli network ip dns server list
11. List the physical NICs on the host.
esxcli network nic list
12. Is a distributed switch available to the host?
esxcli network vswitch dvs vmware list
13. List the standard virtual switch port groups.
esxcli network vswitch standard portgroup list
20
14. How many standard virtual switches are available?
esxcli network vswitch standard list
To display a screen of output at a time, type the following command:esxcli network
vswitch standard list | less
15. List the VMkernel interfaces on the host.
esxcli network ip interface list
To display a screen of output at a time, type the following command:
esxcli network ip interface list | less
16. List the IP address and subnet mask of the VMkernel interfaces on the host.
vicfg-vmknic -l
or
esxcli network ip interface ipv4 get
17. List the default gateway address for the VMkernel interfaces on the host.
vicfg-route -l
or
esxcli network ip route ipv4 list
21
18. How many virtual machines are on the host?
vmware-cmd -l
19. Does the recorded virtual machine have a snapshot?
vmware-cmd path to the .vmx file hassnapshot
For example, if the virtual machine name is RH001 and is located on the datastore named
iSCSI001-DS, then the command line is the following:
vmware-cmd /vmfs/volumes/iscsi001-DS/RH001/RH001.vmx hassnapshot
If the command returns with hassnapshot () = 0, the virtual machine has no
snapshots. If the command returns with hassnapshot () = 1, the virtual machine has
at least one snapshot.
20. How can I get state information about a virtual machine?
vmware-cmd path to the .vmx file getstate
For example, if the virtual machine name is RH001 and is located on the datastore named
iSCSI001-DS, then the command line is the following:
vmware-cmd /vmfs/volumes/iscsi001-DS/RH001/RH001.vmx getstate
21. What is the uptime for the virtual machine whose name you recorded in “Preparing for the
lab?”
22
Lab 3
Searching Log Files
Objective: Search log files for events
1. Make changes to the vSphere environment
2. Extract log files from vCenter Server
23
Task 1: Make changes to the vSphere environment
In this task, you will log in to the VMware vSphere® Web Client and make changes to the
VMware vSphere® environment. Students do the steps in this task individually.
1. Open the Web browser and navigate to the vSphere Web Client home page at
https://vCenter Server system name:9443.
2. Log in to your VMware® vCenter Server™ system. You recorded the vCenter Server
system name, user name, and password in “Preparing for the lab.”
3. Select vCenter > vCenter Servers.
4. Select the vCenter Server system that you recorded and select Manage.
6. Click Logging settings in the Edit vCenter Server Settings dialog box.
7. In the Logging options drop-down box, change the logging level to verbose.
9. Right-click the ESXi host name that you recorded in “Preparing for the lab” and select
All vCenter Actions > Add Networking.
10. When prompted by the Add Networking wizard, perform the following actions.
Select Target Device Select New standard switch and click Next.
24
Connection Settings In the Network label field, type your name_Switch.
Click Next.
Ready to Complete Verify that the settings are correct and click Finish.
12. Verify that the network you created appears in the list.
13. Right-click the VMware® ESXi™ host and select New Datastore.
14. When prompted by the New Datastore wizard, perform the following actions.
25
Ready to Complete Verify that all settings are correct and click Finish.
3. Select your vCenter Server system and click the Monitor tab.
26
6. When prompted by the Export Logs wizard, perform the following actions.
Ready to Complete Click Generate Log Bundle. Generating the log bundle will
take a few minutes to complete. When log bundle
generation completes, click Download Log Bundle.
Record the name of the log bundle (a ZIP file):
.
Save the log bundle to your desktop. Wait several
minutes for this process to complete.
When the download is complete, click Finish.
27
Task 3: Search log files for event information
In this task, you will search the log files for the time that you performed the system changes in
task
1. Students do the steps in this task individually.
1. On your desktop, double-click the ZIP file that you downloaded in task 2, step 6.
4. Double-click the directory named Logs, then double-click the directory named vpxd.
5. Double-click the log file named vpxd-##.log, where ## correlates to the current
version of the vpxd.log file.
By default, the current log file is in .log format. Older log files are compressed and have a
.gz
extension.
6. In the Notepad window, press Ctrl+F.
7. Use the Find function to answer the following questions:
a. Are there any errors noted in the file? If the answer is yes, when
was the last error noted?
b. When did the your name Switch creation process complete?
28
Task 4: Clean up for the next lab
In this task, you will delete the datastore that you created in task 1. Students do the
steps in this task individually.
1. Click the Home icon at the top of the window.
2. Select vCenter, then select Hosts.
3. Select the ESXi host and click the Related Objects tab.
4. Click Datastores.
5. Right-click your name Datastore and select All vCenter Actions > Delete Datastore.
29
Lab 4
Configuring SSL Certificates
Objective: Configure SSL certificates for vSphere
1. Generate certificate requests for vCenter components
2. Generate certificates
30
Preparing for the lab
Record the following information:
31
Task 1: Generate certificate requests for vCenter components
In this task, you will open a Windows command prompt and generate certificate requests for the
different VMware® vCenter™ components. The sso.cfg, inventoryservice.cfg,
vcenter.cfg, and webclient.cfg configuration files have been preconfigured for you. If the
files does not exist, Please refer to Instructor to run PowerCLI script to generate them.
1. Ask the instructor how to connect to the OpenSSL system. For example, the instructor
might have you use Remote Desktop Connection to connect to the OpenSSL system. You
recorded the OpenSSL system name, user name, and password in “Preparing for the lab.”
2. On the OpenSSL desktop, select Start > Command Prompt.
32
7. Generate certificate requests for the VMware vSphere® Web Client by
running the following commands:
a. openssl req -new -nodes -out Your cert dir\WebClient\rui.csr
-keyout Your cert dir\WebClient\rui-orig.key-config Your cert
dir\WebClient\webclient.cfg
b. openssl rsa -in Your cert dir\WebClient\rui-orig.key
-out Your cert dir\WebClient\rui.key
33
Task 2: Generate certificates
In this task, you will generate SSL certificates from the certificate requests. Students
do the steps in this task individually.
1. On the OpenSSL desktop, open the Internet Explorer Web browser
and type
http://windc01.vclass.local/CertSrv to go to the Microsoft
CA certificate authority Web Interface. (username : Administrator )
2. Click the Request a certificate link, then click advanced certificate request.
3. Click the Submit a certificate request by using a base-64-encoded CMC or
PKCS #10 file, or submit a renewal request by using a base-64--encoded
PKCS #7 file link.
4. Open a Windows Explorer window and navigate to the Your cert dir\sso directory.
5. Right-click the rui.csr file and open the file with Notepad.
6. Copy and paste the contents of the file to the Saved Request box of the Web
page. To select all the contents in the file in Notepad, click Edit > Select All.
CAUTION
Do not use Wordpad to modify files. Use Notepad only. Wordpad uses formatting that
might cause errors in subsequent steps.
7. From the Certificate Template drop-down menu, select the Web Server VMW template
and click the Submit button.
The Web Server VMW is a copy of the Web Server Template that has Allow Encryption of
User Data selected.
8. Select the Base 64 encoded option, then click the Download Certificate link.
9. Select Save.
34
10. In Save as type, select All Files, save the certificate as Your cert dir\sso\rui.crt,
and click the Close button.
11. Click the Home link, located in the upper-right corner.
12. Perform steps 2 through 11 for the Inventory Service, the vCenter Server Service, and
the vSphere Web Client service. Save the .crt file to the appropriate directories:
Your cert dir\InventoryService\rui.crt
Your cert dir\vCenter\rui.crt
Your cert dir\WebClient\rui.crt
13. Click the Home link, located in the upper-right corner.
14. Click Download a CA certificate, certificate chain or CRL.
15. Select the Base 64 option, then click the Download CA Certificate chain link.
16. Click Save and save the file as Your cert dir\cachain.p7b and click Close.
17. In a Windows Explorer window, double-click the cachain.p7b file you just created.
18. In the certificate manager window, expand the folder hierarchy and select the Certificates
folder.
19. Right-click the certificate listed and select All Tasks > Export.
35
Task 3: Create the PEM chain files
In this task, you will create a PEM certificate chain for vCenter Single Sign-On,
Inventory Service, vCenter Server, and the vSphere Web Client. Students do the
steps in this task individually.
1. Verify that you are logged in to the vCenter Server system.
2. From the vCenter Server desktop, create a file named chain.pem for each service.
a. Using Windows Explorer, go to the Your cert dir\SSO directory.
f. Copy and paste the contents of the Root64.cer file into chain.pem
after the certificate section.
g. Verify that no whitespace is between the certificates in the file. After
the changes are complete, the file resembles the following
screenshot.
36
h. Save the chain.pem file and exit Notepad.
i. Repeat steps a through h to create a chain.pem file for the Inventory Service, the
vCenter Server service, and the vSphere Web Client service. The rui.crt file for
each service is located in the following directories:
Your cert dir\InventoryService
Your cert dir\vCenter
Your cert dir\WebClient
j. Exit Notepad.
37
Task 4: Configure parameters in ssl-environment.bat
In this task, you will set the values of parameters in the ssl-environment.bat file. Students
do the steps in this task individually.
1. Using the Windows Explorer window, navigate to the certificate automation tool
directory, whose name you recorded in “Preparing for the lab.”
2. Open the ssl-environment.bat file with Notepad. Modify the following entries as
follows:
set sso_cert_chain=Your cert dir\SSO\chain.pem
Replace Your cert dir with the certificate directory name that you recorded in
“Preparing for the lab.”
set sso_private_key=Your cert dir\SSO\rui.key
set sso_node_type=Single
set is_cert_chain=Your cert dir\InventoryService\chain.pem
set is_private_key_new=Your cert dir\InventoryService\rui.key
set vc_cert_chain=Your cert dir\vCenter\chain.pem
set vc_private_key=Your cert dir\vCenter\rui.key
set ngc_cert_chain=Your cert dir\WebClient\chain.pem
set ngc_private_key=Your cert dir\WebClient\rui.key
38
Task 5: Plan the execution for updating certificates
In this task, you will use the Certificate Update Automation Tool to create a plan
of execution for updating the certificates for vCenter Single Sign-On, Inventory
Service, vCenter Server, and vSphere Web Client. Students do the steps in this
task individually.
1. On the vCenter Server desktop, select Start > Command Prompt.
2. At the command prompt, type the following command line:
39
Task 6: Update the vCenter Single Sign-On certificate
In this task, you will use the Certificate Update Automation Tool to update the vCenter Single
Sign- On certificate. You will perform all actions on the vCenter Server system, where the
vCenter Single Sign-On service is installed. Students do the steps in this task individually.
1. In the main menu, type 3 to update vCenter Single Sign-On.
2. Type 1 to update the vCenter Single Sign-On SSL certificate. Answer the prompts as follows:
a. Press Enter to accept the default location to the new Single Sign-On SSL chain.
b. Press Enter to accept the default location to the new Single Sign-On SSL private key.
c. Type the Single Sign-On administrator password. You recorded the SSO
administrator password in “Preparing for the lab.”
d. Type no when asked if you have a load balancer installed.
e. Verify that the task completes successfully.
40
Task 7: Update the Inventory Service certificate
In this task, you will use the Certificate Update Automation Tool to update the Inventory
Service certificate. You will perform all actions on the vCenter Server system, where the
Inventory Service is installed. Students do the steps in this task individually.
1. In the Update Inventory Service menu, type 3 to update the Inventory Service SSL certificate.
2. Answer the prompts as follows:
a. Press Enter to accept the default location to the new Inventory Service SSL chain file.
b. Press Enter to accept the default location to the new Inventory Service private key.
You recorded the SSO administrator password in “Preparing for the lab.”
e. Verify that the task completes successfully.
41
Task 8: Update the vCenter Server certificate
In this task, you will use the Certificate Update Automation Tool to update the vCenter
Server Trust to vCenter Sign-On. You will also update the vCenter Server certificate.
You will perform all actions on the vCenter Server system. Students do the steps in
this task individually.
1. In the main menu, type 5 to update vCenter Server.
3. In the main menu, type 2 to update the vCenter Server SSL certificate. Answer
the prompts as follows:
a. Press Enter to accept the default location to the new vCenter Server SSL chain.
b. Press Enter to accept the default location to the new vCenter Server private key.
42
4. Type 3 to update the vCenter Server Trust to Inventory Service.
5. Verify that the task completes successfully.
43
Task 9: Update the vSphere Web Client certificate
In this task, you will use the Certificate Update Automation Tool to update the vSphere Web
Client Trust to vCenter Single Sign-On. You will also update the vSphere Web Client certificate.
You will perform all actions on the vCenter Server system, where the vSphere Web Client is
installed.
Students do the steps in this task individually.
1. In the main menu, type 7 to update the vSphere Web Client.
a. Press Enter to accept the default location to the new Web Client SSL chain.
b. Press Enter to accept the default location to the new Web Client private key.
d. Type the Single Sign-On administrator password that you recorded in “Preparing for
the lab.”
e. Verify that the task completes successfully.
44
Task 10: Verify that the vCenter SSL certificates work properly
In this task, you will verify that the SSL certificates for the vCenter components
work properly. If the SSL certificates for the vCenter components do not work
properly, you will roll back the SSL certificates in task 11. Students do the steps in
this task individually.
1. If you are logged in to the vSphere Web Client, log out now.
2. Log back in to the vSphere Web Client. Use the vCenter Server user name
and password that you recorded in “Preparing for the lab.”
3. Verify that you can access the vCenter Server inventory and go to task 12.
5. If after verifying your work, the SSL certificates still do not work properly, go to task 11.
Task 11: (Optional) Roll back the system to use the original certificates
Perform the following steps only if the SSL certificates do not work properly. If the
SSL certificates work properly, go to task 12.
1. In the command prompt window, restart the SSL updater:
ssl-updater
2. Type 7 to update the vSphere Web Client.
3. Type 7 to roll back to the previous vSphere Web Client SSL certificate.
4. Press Enter to accept the default Single Sign-On administrator user.
5. Type the Single Sign-On administrator password that you recorded in “Preparing for the lab.”
6. Verify that the rollback of the vSphere Web Client certificate is successful.
12. Type the vCenter Server database password that you recorded in “Preparing for the lab.”
45
13. Press Enter to accept the default Single Sign-On administrator user.
14. Type the Single Sign-On administrator password that you recorded in “Preparing for the lab.”
15. Verify that the rollback of the vCenter Server certificate is successful.
18. Type 4 to roll back to the previous Inventory Service SSL certificate.
19. Press Enter to accept the default Single Sign-On administrator user.
20. Type the Single Sign-On administrator password that you recorded in “Preparing for the lab.”
21. Verify that the rollback of the Inventory Service certificate is successful.
24. Type 2 to roll back to the previous Single Sign-On SSL certificate.
25. Verify that the rollback is successful.
46
Task 12: Generate a certificate request for the ESXi(1,2) host
In this task, you will generate a certificate request for the VMware® ESXi™ host. Students
have to repeat for each ESXi host in the vcenter individually.
1. On the OpenSSL system’s desktop, select Start > Command Prompt.
2. Navigate to the OpenSSL directory:
cd C:\OpenSSL\bin
3. Generate certificate requests for the ESXi host by running the following commands:
47
Task 13: Generate a certificate for the ESXi host
In this task, you will generate a certificate for the ESXi host. Students do the
steps in this task individually.
1. On the OpenSSL system, to open a Web browser and access the
Microsoft CA certificate authority Web interface, go to
http://localhost/CertSrv.
2. Select Request a certificate and click advanced certificate request.
6. Copy the contents of the file starting with the line -----BEGIN CERTIFICATE REQUEST--
--
- and ending with the line -----END CERTIFICATE REQUEST-----.
7. Paste the contents to the Saved Request box in the Web browser.
8. From the Certificate Template drop-down menu, click the Web Server VMW link and
select
Submit.
9. Select the Base 64 encoded option and click the Download certificate link.
11. In the Save as type text box, select All Files and save the certificate
as ESXi cert dir\rui.crt.
12. Exit the Web browser.
13. Exit Notepad.
48
Task 14: Install the certificate on the ESXi host
In this task, you will install the certificate on the ESXi host. Students do the steps
in this task individually.
1. On your student desktop system, use the VMware vSphere® Client™ to log
in to the vCenter Server system.
You recorded your vCenter Server system name, user name, and password in
“Preparing for the lab.”
2. Select Home > Inventory > Hosts and Clusters. Expand the inventory until
you see the ESXi host and its virtual machines.
You recorded the ESXi host name in “Preparing for the lab.”
When the process completes, the ESXi host icon displays a yellow and black stripe.
6. Minimize the vSphere Client window.
a. On the OpenSSL system’s desktop, to start a PuTTY session, double-click the PuTTy
icon.
b. In the Host Name (or IP address) text box, type the ESXi host name and click Open.
d. At the login prompt, type root for the user name and the ESXi host root password that
you recorded in “Preparing for the lab.”
When you are logged in, you are placed at the ESXi host command prompt.
8. Back up the existing SSL certificate files.
a. At the ESXi command line, to create a backup directory for the current ssl files, type
the following command:
mkdir /backupcerts
b. To move the current certificate files to the backup directory, type the following
49
command:
mv /etc/vmware/ssl/* /backupcerts
c. To verify that the current certificate files were moved to the backup directory, type
the following command:
ls /backupcerts
d. Minimize the PuTTY session window. You will use this window in another step.
9. Copy the ESXi host’s certificate files from the OpenSSL system to the ESXi host.
b. To log in to the ESXi host, use WinSCP. Type the ESXi host name, root for the user
name, and the root password that you recorded in “Preparing for the lab.”
c. On the left pane of the WinSCP window, navigate to the ESXi host certificate
directory, whose name you recorded in “Preparing for the lab.”
d. On the right pane of the WinSCP window, navigate to the /etc/vmware/ssl directory.
e. To copy the rui.crt and rui.key files from the ESXi certificate
directory on the OpenSSL system to the SSL directory on the ESXi
host, drag the two files from ESXi cert dir to the
/etc/vmware/ssl directory on the ESXi host.
f. Close the WinSCP window.
10. Restart the management agents on the ESXi host.
If you logged out of PuTTY, perform task 14, step 7 to log back in to the
ESXi host with PuTTY.
b. At the root command prompt, type dcui to access the ESXi host’s DCUI.
c. Press F2 to display the login screen, and log in as user root, using the
ESXi host password that you recorded in “Preparing for the lab.”
d. Using the up and down arrow keys, select Troubleshooting Options and press Enter.
50
h. To log out of the DCUI, press and hold the Escape key.
If you do not see this security alert, you have properly installed the ESXi SSL certificate.
NOTE :
^Once you have done Lab 4, Please Revert all the VM in Workstation to LAB5 Snapshot
^Please refer Instructor for more information.
51
Lab 5
Virtual Network Scenario (1)
Objective: Identify, diagnose, and resolve a
virtual networking problem
1. Run the break-5-1.ps1 script
2. Verify that the system is not functioning properly
52
Task 1: Run the break-5-1.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-1 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on the desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc\
3. Type .\break-5-1.ps1. If you get a security warning, type R then press
Enter. Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
53
Task 2: Verify that the system is not functioning properly
In this task, a user has reported to you that a virtual machine cannot access resources on the
network. Immediately after discussing the issue with the user, you receive another call from
another user reporting similar issues. The network team reports that the network has no issues
and that they can ping the default gateway from the physical switch. In addition to fixing the
issue for the users, verify that the virtual environment is sound. If you can ping the default
gateway of the virtual machine, ask the instructor for help.
1. In the desktop system, double-click the Web browser.
2. Type the address of the VMware vSphere® Web Client that you recorded in “Preparing
for the lab.”
3. Using the VMware® vCenter Server™ user name and password that you
recorded in “Preparing for the lab,” log in to the vSphere Web Client.
4. Select vCenter > VMs and Templates.
5. Expand the inventory. Right-click the virtual machine name that you recorded in
“Preparing for the lab” and select Power On.
If you are powering on a virtual machine for the first time, you might get the following error:
This virtual machine might have been moved or copied. In order to
configure certain management and networking features, VMware ESX
needs to know if this virtual machine was moved or copied. If you don’t
know, answer “I copied it.” If this is the case, go to the virtual machine’s
Summary tab and select I copied it. The virtual machine then powers on.
6. Right-click the virtual machine name that you recorded and select Open Console.
7. Log in to the virtual machine with the user name and password that you
recorded in “Preparing for the lab.”
8. Open a command prompt window in the virtual machine.
54
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the network.
1. Use the available techniques and tools to troubleshoot and repair the problem.
55
Lab 6
Virtual Network Scenario (2)
Objective: Identify, diagnose, and resolve a
virtual networking problem
1. Run the break-5-2.ps1 script
2. Verify that the system is not functioning properly
56
Task 1: Run the break-5-2.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-2 script.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on the desktop system to
start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-2.ps1. If you see a security warning, type R and press
Enter.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the
instructions displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the vSphere Web Client.
4. Select vCenter > Storage.
6. If the host does not display this status, refresh the window or wait for 60 seconds.
57
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles, available at http://kb.vmware.com
• The Internet
58
Lab 7
Virtual Network Scenario (3)
Objective: Identify, diagnose, and resolve a
virtual networking problem
1. Run the break-5-3.ps1 script
2. Verify that the system is not functioning properly
59
Task 1: Run the break-5-3.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on the desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-3.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
8. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
9. Using the vCenter Server user name and password that you recorded in “Preparing for the
lab,” log in to the vSphere Web Client.
10. Select vCenter > Hosts and Clusters.
11. Verify that your ESXi host has a status of “Not Responding.”
12. If the host does not display this status, refresh the window or wait for 60 seconds.
13. If the ESXi host remains connected, ask the instructor for help.
60
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the network.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and ESXi host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
61
Lab 8
Creating a Distributed Switch
Objective: Create a distributed switch
1. Create a distributed switch
2. Verify that the distributed switch was created properly
62
Task 1: Create a distributed switch
In this task, you will run a script that creates a distribute switch. Students do the steps in this
task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
VMware vSphere® PowerCLI™ session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-4-vDS.ps1.
4. Leave the vSphere PowerCLI window open for another task.
63
Lab 9
Virtual Network Scenario (4)
Objective: Identify, diagnose, and resolve a
virtual networking problem
1. Run the break-5-4.ps1 script
2. Verify that the system is not functioning properly
64
Task 1: Run the break-5-4.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-4 script.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-4.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
65
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the network.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
66
Lab 10
Virtual Network Scenario (5)
Objective: Identify, diagnose, and resolve a
virtual networking problem
1. Run the break-5-5.ps1 script
2. Verify that the system is not functioning properly
67
Task 1: Run the break-5-5.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-5 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-5.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
68
Task 2: Verify that the system is not functioning properly
In this task, a VMware® vCenter Server™ administrator reports that the vCenter Server system
lost contact with a VMware® ESXi™ host. You will verify that the problem exists. If you see
the ESXi host connected in the vCenter Server system, ask the instructor for help.
69
Lab 11
Virtual Network Scenario (6)
Objective: Identify, diagnose, and
resolve a virtual networking problem
1. Run the break-5-6.ps1 script
2. Verify that the system is not functioning properly
70
Task 1: Run the break-5-6.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-5-6 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to
start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-5-6.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
71
Task 2: Verify that the system is not functioning properly
In this task, a virtual machine administrator reports that two virtual machines
cannot communicate in the network. You will verify that the problem exists
. If you find that the virtual machines can communicate with each other, ask the instructor for
help.
1. In the desktop system, double-click the Web browser.
2. Type the address of the VMware vSphere® Web Client that you recorded in
“Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the vSphere Web Client.
4. Click vCenter > VMs and Templates.
5. Expand the inventory and locate the second virtual machine,
whose name you recorded in “Preparing for the lab.”
Record its IP address here:
6. Right-click the first virtual machine name that you recorded in “Preparing for the lab”
and select Open Console.
7. Log in to the first virtual machine with the virtual machine user name and
password that you recorded in “Preparing for the lab.”
8. Open a command prompt window and ping the second virtual machine’s
IP address that you recorded in step 5.
You are unable to ping the virtual machine.
72
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the network.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network, storage,
and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
73
11
Lab 12
Creating a Standard Switch
Objective: Create a Standard switch
1. Create a Standard switch
2. Verify that the Standard switch was created properly
74
Task 1: Create a Standard switch
In this task, you will run a script that creates a distribute switch. Students do the steps in this
task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
5. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
VMware vSphere® PowerCLI™ session.
6. In the vSphere PowerCLI window, type cd \sc.
7. Type .\break-5-7.ps1.
8. Leave the vSphere PowerCLI window open for another task.
75
Lab 13
Storage Scenario (1)
Objective: Identify, diagnose, and resolve a
storage problem
1. Run the break-6-1.ps1 script
2. Verify that the system is not functioning properly
76
Task 1: Run the break-6-1.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-6-1 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-6-1.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
77
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the NFS datastore.
1. Use the available techniques and tools to troubleshoot and repair the problem.
78
Lab 14
Storage Scenario (2)
Objective: Identify, diagnose, and resolve a
storage problem
1. Run the break-6-2.ps1 script
2. Verify that the system is not functioning properly
79
Task 1: Run the break-6-2.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-6-2 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-6-2.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the VMware vSphere® Web Client that you recorded in “Preparing
for the lab.”
3. Using the VMware® vCenter Server™ user name and password that you
recorded in “Preparing for the lab,” log in to the vSphere Web Client.
4. Select vCenter > VMs and Templates.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On.
Power On will Fail.
6. If the system can power on, ask the instructor for help.
80
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the iSCSI LUNs.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
81
Lab 15
Storage Scenario (3)
Objective: Identify, diagnose, and resolve a
storage problem
1. Run the break-6-3.ps1 script
2. Verify that the system is not functioning properly
82
Task 1: Run the break-6-3.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-6-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-6-3.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
83
Task 2: Verify that the system is not functioning properly
In this task, a user notices that storage performance is slow.
After investigating the problem, the user determines that the affected datastore has only one
path.
If you find that the affected datastore has more than one path, ask the instructor for help.
1. In the desktop system, double-click the Web browser.
2. Type the address of the VMware vSphere® Web Client that you recorded in
“Preparing for the lab.”
3. Using the VMware® vCenter Server™ user name and password that you
recorded in
“Preparing for the lab,” log in to the vSphere Web Client.
4. Select vCenter > Datastores.
5. Select the affected datastore whose name you recorded in “Preparing for the lab.”
Only half of the total number of expected paths is displayed. For example, if
you expect to see two paths, then only one path is displayed.
10. If all expected paths are displayed, ask the instructor for help.
84
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the iSCSI LUNs.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
• This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
• See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
85
Lab 16
Storage Scenario (4)
Objective: Identify, diagnose, and resolve a
storage problem
1. Run the break-6-4.ps1 script
2. Verify that the system is not functioning properly
86
Task 1: Run the break-6-4.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-6-4 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-6-4.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Open Console.
The console opens but you cannot access the virtual machine with its console.
6. If you can access the virtual machine with its console, ask the instructor for help.
87
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the iSCSI LUNs.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
88
Lab 17
Storage Scenario (5)
Objective: Identify, diagnose, and resolve a
storage problem
1. Run the break-6-5.ps1 script
2. Verify that the system is not functioning properly
89
Task 1: Run the break-6-5.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-6-5 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to
start a vSphere PowerCLI session.
2. In the PowerCLI window, type cd \sc.
3. Type .\break-6-5.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
90
Task 2: Verify that the system is not functioning properly
In this task, a user notices that storage performance is slow.
After investigating the problem, the user determines that the affected datastore has only one
path.
If you find that the affected datastore has more than one path, ask the instructor for help.
1. In the desktop system, double-click the Web browser.
2. Type the address of the VMware vSphere® Web Client that you recorded in
“Preparing for the lab.”
3. Using the VMware® vCenter Server™ user name and password that you
recorded in
“Preparing for the lab,” log in to the vSphere Web Client.
4. Select vCenter > Datastores.
5. Select the affected datastore whose name you recorded in “Preparing for the lab.”
Only half of the total number of expected paths is displayed. For example, if
you expect to see two paths, then only one path is displayed.
10. If all expected paths are displayed, ask the instructor for help.
91
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the iSCSI LUNs.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
92
Lab 18
Creating a vSphere Cluster
Objective: Create a vSphere cluster
1. Create a vSphere HA and vSphere DRS cluster
2. Verify that the vSphere cluster was created
93
Task 1: Create a vSphere HA and vSphere DRS cluster
In this task, you will run a script that creates a cluster configured for
VMware vSphere® High Availability and
VMware vSphere® Distributed Resource Scheduler™ (DRS).
.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a VMware vSphere® PowerCLI™ session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-1-cluster.ps1.
4. Leave the vSphere PowerCLI window open for the next lab.
You recorded the team vCenter Server system name, user name, and password in
“Preparing for the lab.”
2. Select Home > Inventory > Hosts and Clusters.
3. Verify that you have a cluster named Lab Cluster, which has the following configuration:
94
Lab 19
Cluster Scenario (1)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-1.ps1 script
2. Verify that the system is not functioning properly
95
Task 1: Run the break-7-1.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-1 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-1.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
3. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power on.
You cannot power on the virtual machine.
You must work only with the virtual machines located in the rProduction resource pools.
4. If the virtual machine powers on, ask the instructor for help.
96
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, once the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
97
Lab 20
Cluster Scenario (2)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-2.ps1 script
2. Verify that the system is not functioning properly
98
Task 1: Run the break-7-2.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-2 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-2.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
3. Find the virtual machine name that you recorded in “Preparing for the lab.” Verify that
this virtual machine is powered on.
4. Right-click the virtual machine and select Migrate. Migrate the virtual machine to the
other ESXi host in the cluster.
You cannot migrate the virtual machine to the other VMware® ESXi™ host.
5. If you can migrate the virtual machine, ask the instructor for help.
99
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, after the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
100
Lab 21
Cluster Scenario (3)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-3.ps1 script
2. Verify that the system is not functioning properly
101
Task 1: Run the break-7-3.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-3 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-3.ps1.
Verify that you see the [May the Force be with you].
4. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
5. Leave the vSphere PowerCLI window open for another task.
3. Select your lab cluster in the inventory and click the Summary tab.
One or more configuration issues are displayed. Resolve only the vSphere HA issues.
5. If no vSphere HA issues are listed, ask the instructor for help.
102
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, once the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
103
Lab 22
Cluster Scenario (4)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-4.ps1 script
2. Verify that the system is not functioning properly
104
Task 1: Run the break-7-4.ps1 script
In this task, you will use the VMware vSphere® PowerCLI™ to run the break-7-4 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-4.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
105
Task 2: Verify that the system is not functioning properly
In this task, you receive complaints about the performance of some virtual machines that reside
in a VMware vSphere® cluster. You will verify that the problem exists. If you do not notice
performance problems with the virtual machines in the cluster, ask the instructor for help. Each
student in the team can do this task individually.
1. Use VMware vSphere® Client™ to log in to your team vCenter Server system.
You recorded the team vCenter Server system name, user name, and password in “Preparing
for the lab.”
2. Select Home > Inventory > Hosts and Clusters.
3. Select your lab cluster in the inventory, then click the Summary tab.
4. In the vSphere DRS pane1, click the View Resource Distribution Chart link. CPU
utilization is displayed. Determine whether the CPU resources of the hosts are utilized
evenly.
5. Click Memory.
Determine whether the memory resources of the hosts are utilized evenly.
6. Close the DRS Resource Distribution window.
7. If the hosts are not utilized evenly, click the DRS tab. In the Recommendations pane, click
the
Run DRS link.
You do not see any recommendations. Determine why host utilization is not balanced.
8. If VMware vSphere® Distributed Resource Scheduler™ successfully balances
host utilization, ask the instructor for help.
106
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, once the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
107
Lab 23
Cluster Scenario (5)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-5.ps1 script
2. Verify that the system is not functioning properly
28
Team vCenter Server system name
Team vCenter Server user name
Team vCenter Server password
Virtual machine names
108
Task 1: Run the break-7-5.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-5 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-5.ps1.
4. Verify that you see the [May the Force be with you]
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
You recorded the team vCenter Server system name, user name, and password in “Preparing
for the lab.”
2. Select Home > Inventory > Hosts and Clusters.
3. Right-click the virtual machines names that you recorded in “Preparing for the lab” and select
Power on.
You cannot power on the virtual machines.
You must work with only the virtual machines located in the rDevelopment and rProduction
resource pools.
4. If the virtual machines power on, ask the instructor for help.
109
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, after the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
110
Lab 24
Cluster Scenario (6)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-6.ps1 script
2. Verify that the system is not functioning properly
111
Task 1: Run the break-7-6.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-6 script.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-6.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
You recorded the team vCenter Server system name, user name, and password in “Preparing
for the lab.”
2. Select Home > Inventory > Hosts and Clusters.
3. Find the ESXi host that you recorded in “Preparing for the lab.”
5. Right-click the ESXi Host and exit maintenance and attempt to join back to Cluster
112
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, after the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
113
Lab 25
Cluster Scenario (7)
Objective: Identify, diagnose, and resolve a
cluster problem
1. Run the break-7-7.ps1 script
2. Verify that the system is not functioning properly
114
Task 1: Run the break-7-7.ps1 script
In this task, you will use the VMware vSphere® PowerCLI™ to run the break-7-7 script. Only
student A performs the steps in this task.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI (32-Bit) icon on your desktop system to
start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-7.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
Determine whether the memory resources of the hosts are utilized evenly.
5. If the hosts are not utilized evenly, click the Monitor tab.
115
6. Click the vSphere DRS tab.
You do not see any recommendations. Determine why host utilization is not balanced.
8. If VMware vSphere® Distributed Resource Scheduler™ successfully balances
host utilization, ask the instructor for help.
116
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the cluster.
NOTE
Students in a team can troubleshoot the problem individually. However, once the
problem is identified, students in a team must work together to fix the problem.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network, storage,
and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
117
31
Lab 26
Cluster (8)
Objective: Remove vSphere cluster
1. Run the break-7-8.ps1 script
118
Task 1: Run the break-7-8.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-7-8 script.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc
3. Type .\break-7-8.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
You recorded the team vCenter Server system name, user name, and password in “Preparing
for the lab.”
2. Select Home > Inventory > Hosts and Clusters.
3. Verify that you do not have any Cluster.
119
Lab 27
ESXi/vCenter Scenario (1)
Objective: Identify, diagnose, and resolve an
ESXi host or vCenter Server problem
1. Verify that your ESXi host is in the Training data center
2. Run the break-8-1.ps1 script
120
Task 1: Verify that your ESXi host is in the vClassDC data center
In this task, you will verify that your ESXi host is in the vClassDC
data center and not in the lab cluster.
1. Using VMware vSphere® Client™, log in to your VMware® vCenter Server™ system.
You recorded your vCenter Server system name, user name, and password in
“Preparing for the lab.”
2. Verify that your ESXi host is located directly in your vCenterDC data center and
not in the lab cluster.
3. Exit vSphere Client.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-8-1.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
121
Task 3: Verify that the system is not functioning properly
In this task, a user cannot log in to the VMware® vCenter Server™ system.
You will verify that the problem exists. If you can log in to the vCenter Server system,
ask the instructor for help.
1. In the desktop system, double-click the Web browser.
2. Type the address of the VMware vSphere® Web Client that you recorded in
“Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the vSphere Web Client.
4. Verify that you cannot access your vCenter Server system from within the vSphere Web
Client.
5. If you can access your vCenter Server system from within the vSphere
Web Client, ask the instructor for help.
34
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and ESXi host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
122
Lab 28
ESXi/vCenter Scenario (2)
Objective: Identify, diagnose, and resolve an
ESXi host or vCenter Server problem
35
1. Run the break-8-2.ps1 script
2. Verify that the system is not functioning properly
123
Task 1: Run the break-8-2.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-8-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the PowerCLI window, type cd \sc.
3. Type .\break-8-2.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Verify that you cannot use the vSphere Web Client to log in to your vCenter Server system.
5. If you can use the vSphere Web Client, ask the instructor for help.
124
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the vCenter Server system.
1. Use the available techniques and tools to troubleshoot and repair the problem.
125
Lab 29
ESXi/vCenter Scenario (3)
Objective: Identify, diagnose, and resolve an
ESXi host or vCenter Server problem
1. Run the break-8-3.ps1 script
2. Verify that the system is not functioning properly
126
Task 1: Run the break-8-3.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-8-3 script.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop
system to start a vSphere PowerCLI session.
2. In the PowerCLI window, type cd \sc.
3. Type .\break-8-3.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in
“Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Verify that you cannot use the vSphere Web Client to log in to your
vCenter Server system.
5. If you can use the vSphere Web Client, ask the instructor for help.
127
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the
lecture to troubleshoot and repair the problem with the vCenter Server system.
1. Use the available techniques and tools to troubleshoot and repair the problem.
128
Lab 30
ESXi/vCenter Scenario (4)
Objective: Identify, diagnose, and resolve an
ESXi host or vCenter Server problem
1. Run the break-8-4.ps1 script
2. Verify that the system is not functioning properly
129
Task 1: Run the break-8-4.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-8-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
7. Double-click the VMware vSphere PowerCLI icon on your desktop system to
start a vSphere PowerCLI session.
8. In the PowerCLI window, type cd \sc.
9. Type .\break-8-4.ps1.
10. Verify that you see the [May the Force be with you].
11. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
12. Leave the vSphere PowerCLI window open for another task.
7. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
8. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
9. Verify that you cannot use the vSphere Web Client to log in to your vCenter Server system.
10. If you can use the vSphere Web Client, ask the instructor for help.
130
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture
to troubleshoot and repair the problem with the vCenter Server system.
2. Use the available techniques and tools to troubleshoot and repair the problem.
131
Lab 31
ESXi/vCenter Scenario (5)
38
132
Task 1: Run the break-8-5.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-8-5 script.
.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to
start a vSphere PowerCLI session.
2. In the PowerCLI window, type cd \sc.
3. Type .\break-8-5.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
133
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the
lecture to troubleshoot and repair the problem with the vCenter Server database.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, vCenter Server, and VMware® ESXi™ host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
38
134
Lab 32
ESXi/vCenter Scenario (6)
Objective: Identify, diagnose, and resolve an
ESXi host or vCenter Server problem
35
1. Run the break-8-6.ps1 script
2. Verify that the system is not functioning properly
135
Task 1: Run the break-8-6.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-8-6 script.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-8-6.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
You recorded your ESXi host name and root password in “Preparing for the lab.”
2. Verify that you cannot log in to your ESXi host with vSphere Client.
3. If you can successfully log in to your ESXi host, ask the instructor for help.
136
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture
to troubleshoot and repair the problem with the ESXi host.
1. Use the available techniques and tools to troubleshoot and repair the problem.
Lecture manual for this course
The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
Virtual machine, VMware® vCenter Server™, and ESXi host log files
See module 3, lesson 2, in the lecture manual for information about log files.
VMware® knowledge base articles at http://kb.vmware.com
The Internet
137
Lab 33
Virtual Machine Scenario (1)
Objective: Identify, diagnose, and resolve a
virtual machine problem
1. Run the break-9-1.ps1 script
2. Verify that the system is not functioning properly
138
Task 1: Run the break-9-1.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-1 script.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-1.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter >VMs and Templates. Expand the Training data
center to view the child objects.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On..
You cannot power on the guest VM.
6. If you can power on , ask the instructor for help.
139
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
43
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
140
Lab 34
Virtual Machine Scenario (2)
Objective: Identify, diagnose, and resolve a
virtual machine problem
1. Run the break-9-2.ps1 script
2. Verify that the system is not functioning properly
141
Task 1: Run the break-9-2.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-2 script.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-2.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter >VMs and Templates. Expand the Training data center to
view the child objects.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On..
You cannot power on the VM
6. If you can power on , ask the instructor for help.
142
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
44
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and ESXi host log files
See module 3, lesson 2, in the lecture manual for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
• The vi editor on the ESXi host
If you are unfamiliar with using the vi editor, search the Internet for vi
cheat sheets or basic tutorials.
143
Lab 35
Virtual Machine Scenario (3)
Objective: Identify, diagnose, and resolve a
virtual machine problem
45
1. Run the break-9-3.ps1 script
2. Verify that the system is not functioning properly
144
Task 1: Run the break-9-3.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-3.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter > VMs and Templates. Expand the Training data center to
view the child objects.
5. View the vCenter Server inventory and locate the virtual machine whose name
you recorded in “Preparing for the lab.”
Something wrong with VM status.
145
6. If the virtual machine is listed in the inventory, ask the instructor for help.
146
Lab 36
Virtual Machine Scenario (4)
Objective: Identify, diagnose, and resolve a
virtual machine problem
1. Register the virtual machine to use for this lab
2. Run the break-9-4.ps1 script
147
Task 1: Run the break-9-4.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-3 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed.
(For readability, commands might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system
to start a vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-4.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab ,
follow the instructions displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in
“Preparing for the lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter > VMs and Templates. Expand the data center to
view the child objects.
5. View the vCenter Server inventory and locate the virtual machine whose name
you recorded in “Preparing for the lab.”
Status reports , Consolidation is required.
6. If the virtual machine is listed in the inventory has no status, ask the instructor for help.
148
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
45
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
149
Lab 37
Virtual Machine Scenario (5)
Objective: Identify, diagnose, and resolve a
virtual machine problem
1. Run the break-9-5.ps1 script
2. Verify that the system is not functioning properly
150
Task 1: Run the break-9-5.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-5 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-5.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in “Preparing for the
lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter > VMs and Templates. Expand the vClassDC data center to view the
child objects.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On.
You cannot power on the virtual machine.
6. If the virtual machine powers on, ask the instructor for help.
151
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
152
Lab 38
Virtual Machine Scenario (6)
Objective: Identify, diagnose, and resolve a
virtual machine problem
1. Run the break-9-6.ps1 script
2. Verify that the system is not functioning properly
153
Task 1: Run the break-9-6.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-6 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
1. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
2. In the vSphere PowerCLI window, type cd \sc.
3. Type .\break-9-6.ps1.
4. Verify that you see the [May the Force be with you].
5. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
6. Leave the vSphere PowerCLI window open for another task.
2. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
3. Using the vCenter Server user name and password that you recorded in “Preparing for the
lab,” log in to the VMware vSphere® Web Client.
4. Select vCenter > VMs and Templates. Expand the vClassDC data center to view the
child objects.
5. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On.
You cannot power on the virtual machine.
6. If the virtual machine powers on, ask the instructor for help.
154
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
1. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
155
Lab 39
Virtual Machine Scenario (7)
Objective: Identify, diagnose, and resolve a
virtual machine problem
5. Run the break-9-7.ps1 script
6. Verify that the system is not functioning properly
156
Task 1: Run the break-9-7.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-6 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
7. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
8. In the vSphere PowerCLI window, type cd \sc.
9. Type .\break-9-7.ps1.
10. Verify that you see the [May the Force be with you].
11. If you see any action is required Before You Start the Lab , follow the instructions
displayed in the vSphere PowerCLI window.
12. Leave the vSphere PowerCLI window open for another task.
8. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
9. Using the vCenter Server user name and password that you recorded in “Preparing for the
lab,” log in to the VMware vSphere® Web Client.
10. Select vCenter > VMs and Templates. Expand the vClassDC data center to view the
child objects.
11. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On.
You cannot power on the virtual machine.
12. If the virtual machine powers on, ask the instructor for help.
157
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
2. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
158
Lab 40
Virtual Machine Scenario (8)
Objective: Identify, diagnose, and resolve a
virtual machine problem
9. Run the break-9-8.ps1 script
10. Verify that the system is not functioning properly
159
Task 1: Run the break-9-8.ps1 script
In this task, you will use VMware vSphere® PowerCLI™ to run the break-9-6 script.
Students do the steps in this task individually.
NOTE
Type all commands in a single line unless otherwise instructed. (For readability, commands
might be displayed on two lines instead of one.)
13. Double-click the VMware vSphere PowerCLI icon on your desktop system to start a
vSphere PowerCLI session.
14. In the vSphere PowerCLI window, type cd \sc.
14. Type the address of the vSphere Web Client that you recorded in “Preparing for the lab.”
15. Using the vCenter Server user name and password that you recorded in “Preparing for the
lab,” log in to the VMware vSphere® Web Client.
16. Select vCenter > VMs and Templates. Expand the vClassDC data center to view the
child objects.
17. Right-click the virtual machine name that you recorded in “Preparing for the lab” and select
Power On.
You cannot power on the virtual machine.
18. If the virtual machine powers on, ask the instructor for help.
160
Task 3: Troubleshoot and repair the problem
In this task, you will use the techniques and tools explained in the lecture to
troubleshoot and repair the problem with the virtual machine.
3. Use the available techniques and tools to troubleshoot and repair the problem.
• Lecture manual for this course
• The lab environment worksheet
This worksheet contains important information about the network,
storage, and virtual machine configuration.
• Virtual machine, VMware® vCenter Server™, and VMware®
ESXi™ host log files See module 3, lesson 2, in the lecture manual
for information about log files.
• VMware® knowledge base articles at http://kb.vmware.com
• The Internet
161