Vsphere ICM7 Lab 17
Vsphere ICM7 Lab 17
0:
INSTALL, CONFIGURE, MANAGE
Contents
Introduction ........................................................................................................................ 3
Objectives............................................................................................................................ 3
Lab Topology....................................................................................................................... 4
Lab Settings ......................................................................................................................... 5
1 Configure vSphere vMotion on sa-esxi-01 and sa-esxi-02.......................................... 6
2 Create a Production Network and Prepare a Virtual Machine for vSphere vMotion
Migration........................................................................................................................... 16
3 Migrate Virtual Machine Files from Local Storage to Shared Storage ..................... 26
4 Migrate Virtual Machines Using vSphere vMotion .................................................. 30
5 Migrate Both the Compute Resource and Storage of a Virtual Machine................. 34
Introduction
In this lab, you will configure vSphere vMotion networking and migrate virtual machines
using vSphere vMotion.
Objectives
Lab Topology
Lab Settings
The information in the table below will be needed in order to complete the lab. The
task sections below provide details on the use of this information.
In this task, you create a virtual switch and a VMkernel port group on sa-esxi-01 and sa-
esxi-02 that can be used to move virtual machines from one host to another while
maintaining continuous service availability.
1. Launch the sa-student virtual machine to access the graphical login screen.
To launch the console window for a virtual machine, you may access by
either clicking on the machine’s graphic image from the topology page
or by clicking on the machine’s respective tab from the navigation bar.
3. Launch the Mozilla Firefox web browser by either clicking on the icon shortcut
found on the bottom toolbar or by navigating to Start Menu > Internet > Firefox
Web Browser.
4. Notice the homepage is automatically configured to load the URL address of the
VMware vCenter Server Appliance (sa-vcsa virtual machine). Click on the LAUNCH
VSPHERE CLIENT (HTML5) button to launch the vSphere Client.
5. In the Username text field, type [email protected] and in the Password text
field, type vmware123. Click on LOGIN.
6. In the navigator pane, ensure that you are viewing the Hosts and Clusters tab.
Expand the Datacenter object in the navigator pane, select sa-esxi-01.vclass.local. In
the right pane, click Configure.
9. In the Add Networking window, on the Select connection type step, select VMkernel
Network Adapter. Click Next.
10. On the Select target device step, click New standard switch. Click Next.
11. On the Create a Standard Switch step, click the green + sign to add a physical
adapter to the switch.
12. Select vmnic2 for the vSphere vMotion network and click OK.
13. Back on the Add Networking window, review the information shown. Ensure that
vmnic2 appears underneath Active adapters and click Next.
14. On the Port properties step, enter vMotion in the Network label text box. Select the
vMotion checkbox and click Next.
15. On the IPv4 settings step, select to Use static IPv4 settings and use the information
below to make configurations:
a. IPv4 address: 172.20.12.51
b. Subnet mask: 255.255.255.0
c. Click Next.
16. On the Ready to complete step, review the information and click Finish.
17. In the Virtual switches pane, verify that the new virtual switch for vSphere vMotion
migration is listed.
18. Repeat Task 1 for your second ESXi host (sa-esxi-02.vclass.local). Assign
172.20.12.52 for the IP Address on the IPv4 Settings step.
19. Leave vSphere Client open to continue with the next task.
In this task, you will re-create the Production network on sa-esxi-01.vclass.local and sa-
esxi-02.vclass.local and prepare virtual machines for hot migration between host.
1. While in the vSphere Client, select sa-esxi-01.vclass.local and click Add Networking.
2. In the Add Networking window, on the Select connection type step, select the radio
button for Virtual Machine Port Group for a Standard Switch and click Next.
3. On the Select target device step, select the radio button for the New standard
switch and click Next.
4. On the Create a Standard Switch step, click the Add adapters icon (the green plus
icon).
5. In the Add Physical Adapters to the Switch window, select vmnic1 for the virtual
switch of the Production network and click OK.
6. Review the information for the new active adapter and click Next.
7. On the Connection settings step, enter Production in the Network label text box and
click Next.
8. On the Ready to complete step, verify that the information is accurate and click
Finish.
9. In the Virtual switches pane, click on Standard Switch: vSwitch2 to expand the view.
Notice the Production group appears, and it has the Physical Adapter of vmnic1.
10. Repeat steps 1 -9 in this task for your second ESXi host (sa-esxi-02.vclass.local).
Once you have repeated the steps for sa-esxi-02, you may continue to the next step.
11. In the navigator pane, select the VMs and Templates tab.
12. Expand the Datacenter object. Right-click Linux-01 and select Edit Settings.
13. In the Edit Settings window, click the dropdown menu for the Network adapter 1
and select Browse.
14. In the Select Network window, select the Production network and click OK.
15. Expand the view for Network adapter 1 by clicking the arrow and verify that the
Connect At Power On checkbox is selected. Click OK to save the configurations.
16. In the navigation pane, right-click Linux-01 and select Power > Power On.
18. Log in to the virtual machine as sysadmin with the password of vmware123.
19. Open the terminal by clicking on the Terminal Emulator icon in the panel.
20. At the prompt, enter the command below and verify the IP address is set to
172.20.11.21.
Linux-01:~$ ifconfig
21. Ping the default gateway IP address of 172.20.11.10 (sa-aio) by entering the
command below at the command prompt. Leave the continuous ping running to
complete the next task.
22. Notice the successful pings where Linux-01 can now communicate with sa-AIO.
Repeat steps 11 - 21 for the Linux-02 virtual machine and verify the IP address is
172.20.11.22. Leave the continuous ping running to complete the next task.
23. As an extra step, confirm that both Linux-01 and Linux-02 virtual machines can
communicate with each other on the Production network by using the ping
command.
24. Minimize the Linux-01 and Linux-02 VMware Remote Console windows and continue
to the next task.
In this task, you will migrate the files of a virtual machine from one datastore to another
while the virtual machine is running.
1. Change focus back to the vSphere Client. In the navigator pane, select the VMs and
Templates tab.
2. Select the Linux-01 virtual machine from the navigator pane, followed by clicking on
the Summary tab.
3. In the main workspace, scroll (if necessary) to the Related Objects pane and notice
the name of the storage on which the Linux-01 virtual machine resides.
5. In the Migrate window, on the Select the migration type step, select the radio
button for Change storage only and click Next.
6. On the Select storage step, select iSCSI-LUN0 as the destination datastore and
choose Thin Provision as the disk format. Click Next.
7. On the Ready to complete step, review the information and click Finish.
8. Monitor the Recent Tasks pane and wait for the virtual machine migration process to
complete before proceeding to the next task.
In this task, you will perform hot migrations of virtual machines residing on a shared
datastore that is accessible to both the source and the target ESXi hosts.
1. Verify that the VMs and Templates tab is selected. Right-click Linux-01 and select
Migrate.
2. In the Migrate window, on the Select the migration type step, click Change compute
resource only and click Next.
3. On the Select a compute resource step, choose sa-esxi-02.vclass.local and click Next.
4. On the Select networks step, ensure that Production is selected from the Destination
Network dropdown menu and click Next.
5. On the Select vMotion priority step, leave Schedule vMotion with high priority
(recommended) selected and click Next.
6. On the Ready to complete step, review the information and click Finish.
7. Reopen the Linux-01 VMware Remote Console and monitor that no pings are
dropped during migration. If the login window appears, type vmware123 for the
password and click Unlock.
Align the virtual machine console window so that you can see the
terminal window with pings as well as the Recent Tasks pane
progression. This will give you the best view when monitoring the
ping requests.
8. Change focus back to the vSphere Client. In the navigation pane, select Hosts and
Clusters. Expand the Datacenter, sa-esxi-01.vclass.local, and sa-esxi-02.vclass.local
objects. Verify that Linux-01 has been successfully migrated to sa-esxi-
02.vclass.local.
In this task, you will perform a compute resource and storage migration. You can
migrate virtual machines not only to a different host but also to a different datastore
across storage accessibility boundaries.
1. Verify that you are on the Hosts and Clusters tab. Select sa-esxi-02.vclass.local
object in the navigator pane. Right-click Linux-01 and select Migrate.
2. In the Migrate window, on the Select the migration type step, choose Change both
compute resource and storage. Click Next.
3. On the Select a compute resource step, expand Datacenter and select sa-esxi-
01.vclass.local. Click Next.
4. On the Select storage step, select NFS-1 and ensure Thin Provision is selected from
the virtual disk format dropdown menu. Click Next.
5. On the Select networks step, ensure that Production is selected from the Destination
Network dropdown menu and click Next.
6. On the Select vMotion priority step, verify that Schedule vMotion with high priority
(recommended) is selected. Click Next.
7. On the Ready to complete step, review the information and click Finish.
8. In the Recent Tasks pane, monitor the progress of the virtual machine migration.
This process can take about 3-4 minutes to complete. Once the migration task is
completed, view the inventory pane to verify that the Linux-01 virtual machine is
listed under sa-esxi-01.vclass.local.
9. In the Linux-01 pane, scroll down to the Related Objects pane and verify Linux-01
has successfully migrated to the NFS-1 datastore.