You are on page 1of 3

VMware Infrastructure 3: Install and Configure

Module 11 – Lab for Lesson 1


Troubleshooting Lab Instructions for Student B

Module 11 Objective: Troubleshoot VM problems.


In this lab you will perform the following tasks:
• Cause a problem for your lab partner
• Verify that your lab partner identified the cause of the problem

Part 1: Prepare for this lab


1. Work with your lab partner to identify a virtual machine that you will break, and another
virtual machine that your lab partner will break. Identify them here:

Virtual machine you will break


(and which your partner will
troubleshoot):
Virtual machine your partner will
break (and which you will
troubleshoot):

2. Work with your partner to ensure that these virtual machines are powered down before
continuing.
3. Turn the page and follow the instructions to break your virtual machine. You will also create a
new virtual machine with a different problem for your partner to diagnose.

VI3IC MOD11 LESS1 LAB1 Page 1 of 3 Rev. C


VMware Infrastructure 3: Install and Configure
Module 11 – Lab for Lesson 1
Troubleshooting Lab Instructions for Student B

Part 2: Break a virtual machine for your partner to diagnose


1. Use the VI Client to access the virtual machine to break.
2. To break the virtual machine, reconfigure its network adapter so that it is configured with the
internal-only virtual switch rather than the Production virtual switch. Also configure the
network adapter so that it remains disconnected at power-on:
a. Right-click on the virtual machine.
b. Select Edit Settings from the menu.
c. In the Hardware panel of the resulting Virtual Machine Properties screen, click on
Network Adapter 1.
d. In the right-side panel, clear the Connect at Power-On check box.
e. Change the Network Connection pull-down to the internal-only virtual switch created in
a previous lab.
f. Click OK to save your work.

Part 3: Break another virtual machine for your partner to diagnose


In this part, you will create a new problem: a corrupt virtual disk. In practice, virtual disks become
corrupted through improper handling by administrators: being copied incorrectly or to a destination
without enough space, being copied using tools that do not handle large files correctly, or even being
transferred by FTP in ASCII mode.
For this lab, you will simulate a virtual machine that was not copied correctly. ESX Server 3 virtual
disks are composed of two files: a file with a name ending in .vmdk that serves as a header for the
disk, and a file with a name ending in –flat.vmdk that contains the disk contents. You will make a
new virtual machine and then delete its –flat.vmdk file.
1. Create a new virtual machine:
a. Right-click on your ESX Server
b. Select New Virtual Machine… from the menu.
c. The New Virtual Machine Wizard appears. Use the following values when prompted by
the wizard:

New Virtual Machine Prompts Values


Virtual Machine Configuration Custom
Virtual Machine Name Name the virtual machine, “Won’t Power
On”, followed by your name
Virtual Machine Inventory Location Select your datacenter
Datastore for the Virtual Machine Select the SAN-based VMFS intended for
virtual-disk storage
Select a Guest Operating System
Æ Guest Operating System Select Windows
Æ Version Select Windows Server 2003 Enterprise
Number of virtual processors 1
Memory Keep the default
Create Network Connections

Rev. C MOD11 LESS1 LAB1 Page 2 of 3 VI3IC


VMware Infrastructure 3: Install and Configure
Module 11 – Lab for Lesson 1
Troubleshooting Lab Instructions for Student B

Æ Number of NICs to connect 1


Æ Network Production
Æ Connect at Power On Leave selected
Storage Adapter Types Keep the default
Select a Disk Select Create a new virtual disk
Disk Create a new virtual disk
Disk Size Keep the default
Location Select the SAN-based VMFS intended for
virtual-disk storage
Virtual Device Node Keep the default
Disk Mode Keep the default

2. In the Ready to Complete screen, review all settings, and click Finish to create the virtual
machine.
3. After the creation of the new virtual machine is complete, do not yet power on the virtual
machine. “Corrupt” the virtual disk by deleting the –flat.vmdk file:
a. Select your ESX Server in the inventory.
b. Choose the Configuration tab.
c. Click the Storage (SCSI, SAN, and NFS) link.
d. In the Storage list, find the SAN-based VMFS intended for virtual-disk storage.
e. Right-click on its name and select Browse Datastore… from the menu.
f. Find the subdirectory named after your newly created virtual machine and double-click on
its name to enter it. Caution: do not interfere with your fellow students’ virtual machines!
g. In this subdirectory, you will find the files that make up your virtual machine. Find the
file named after your just-created virtual machine and ending in –flat.vmdk.
h. Right-click on this file and select Delete from Disk.
i. When you are prompted to confirm, make sure that you are indeed examining your own
just-created virtual disk. Click Yes to confirm deletion.

Part 4: Inform your partner of the “broken” virtual machines


1. Advise your partner that the virtual machine you broke in Part 2 will not boot.
2. Also direct your partner to the virtual machine you created in Part 3.
3. Ask your partner to explain why the virtual machine will not power on.
4. Work on the problems that your partner assigns you.
5. Discuss the problems with your partner.

VI3IC MOD11 LESS1 LAB1 Page 3 of 3 Rev. C

You might also like