Vmware Lab 14: Migrating Virtual Machines

Task 1: Migrate VM files from Local Storage to Shared Storage.

Here I went through and made sure I have completed this. This was previously done in the last lab.

Migrate host's; 1.PNG

Task 2: Create a Virtual Switch and a VMkernal Port Group for vSphere vMotion Migration

For this task we need to create a vitchural switch, much like the ones we have created previously is past labs. The only difference is clicking the vSphere vMotion network.


This slideshow requires JavaScript.

Task 3: Perform a vSphere vMotion Migration of a Virtual Machine on a Shared Datastore.

Once we have powered off all of the VMs we have, the first step will is to change some of the settings. For this, we will make sure the network adapters are set to production. Which in my case its “production2” and then the cd/DVD drive is unselected and on the “client device.” We will do this to all three VM’s.

Edit settings; 5.PNG

At this point, we need to do the same on the 2nd ESXi that we will be using. In my case, it’s my 3rd ESXi host.

Once we have done that we need to go into the cabinet VM Ammbers01-3 and type in ipconfig to make sure this is on the correct network.


Once this is done, i will continually ping the DC01

Continual ping; 8.PNGBack in the console, we will the Migrate this VM into the Third ESXi. As seen below.


This slideshow requires JavaScript.

Then there is a slight wait to migrate it over, but once it is done, it should look like below.

Migrated; 11.PNG

Now, this has been done we can go back to the VM and see if it dropped any packages in the migration.

not dropped; 13.PNG

Like I said it took a while, so we have a large number of pings sitting there, but it migrated over without dropping any packets which are good.

The next step is to migrate to another VM and transfer over both the “compute resources” and storage. As seen below.


This slideshow requires JavaScript.

Task 5: Prepare for the Next Lab

So for this, we will migrate all the VMS back, this will take some time. In this time I managed to go to go on to the next lab and leave it migrating. This worked, but I forgot to get any screenshots of this, as I understand home about nine at night.


VMware Lab 13: Modifying Virtual Machines

Task 1: Increase the size of a VMDK File

Here we will have to change some of the settings for the lab

CHange settings; 1.PNG

for this we will use the “hot-clone” we have just created, This is where we will add some extra storage to the hard drive as seen below.


This slideshow requires JavaScript.

Now we need to go into the VM and look at the storage inside of it. For the lab, i  have had to shrink the disk to be able to do this next step.

Storage; 3.PNG

Now we have some room we can extend the disk to use all of the allocated space.


This slideshow requires JavaScript.

Task 2: Adjust Memory Allocation on a Virtual Machine

In this lab, we will change the memory, but for this, we need to shut down the VM. Once it is shut down, we can then adjust the memory to 2 gigs as seen below.


This slideshow requires JavaScript.

Task 3: Rename a VM in the vCenter Server Inventory

For this, we will rename our hot-clone. As seen below.

Renaming ; 7.PNG

Task 4: Add and Remove a Raw LUN on a VM

For this, we add an “RDM” disk.

Newrdm Disk; 8.PNG

And then with this a Lun for that to point to.

New lunk 9

With this, we will then change the location to “store with the virtual machine” as well as this we will also change the “sharing” to be unspecified. As seen below.

New harddisk; 10.PNG

Once we have done this we need to start up the VM, then travel to check that the Lun is in the disk space. As seen below.

New lun in hardisk; 11.PNG

After this, we will the need to delete this Lun off.

Delete disk ; 12.PNG

Task 5: Expand a Thin-Provisioned Virtual Disk.

For this, e need to take note the Storage usage of the vm in its current “on” state.

Useage of space; 13.PNG

Once we have done this we will then need to shutdown the vm and navigate to VMFS data store and find the .vmdk file. As shoen below.

Inflate VMDK ; 13.PNG


Once in here will will then need to inflate the disk. This took a good hour or two to complete.

Inflating disk; 14.PNG

And after we will then power on the same vm and cheak the storage incress. the storage useage was orginollay at 9 gigs and here it is at 30 gigs.

Inflate mempry; 15.PNG


VMware Lab 12: Using Templates and Clones

Task1: Create a VM template

For this, we need to be in the correct place.

In the right place; 1.PNG

Once in here I need to create a Template, in this it will be put into templates as shown below.

Template; 3.PNG

For this, we will the need to rename it as well.

Renaming the template; 4.PNG

And here it is we have a template of our VM.

Task 2: Create Customization Specifications

For this, we will then need to create a “custom spec”. In this, we will be using the specifications given to us. Customised slightly to use our own machines and own specifications. As seen below.

This slideshow requires JavaScript.

Task 3: Deploy a VM from a Template

Since we have premade the template we are now ready to create a new VM from it. For this there is a simple wizard to follow, As seen below.

This slideshow requires JavaScript.

Once we have done this, we need to go back and create another VM following the same steps. As seen below.

New VMS from template; 8.PNG

Here is where you will see some differences in the system, Becuase here is where I had an issue with the ESXi.

But as seen below, both VMs are powered on and are up and running.

Lab 12.PNG

Task 4: Clone a Powered-On VM

Here is where we need a running VM to create a clone while its turned on, or “hot”. So this will be a new clone, and it will be a “hot-clone.” Here we will use the guide to go through the guide adding in the suggested inputs. As seen below.

This slideshow requires JavaScript.

As you can see below, this was made and added to our list. But for this, it took about 6 hours to complete.  It took up a good part of a day, so I suggest you allow for this.


Hotclone lab 12.PNG

And now the lab is finally complete after all of the issues I have had.



Reconfigurement :1

In the school holidays, there was an outage within the network that we were using. This caused system-wide issues. For this my preconfigured Vsim was damaged, this causes many broken disks. Which meant it was unusable. Once I was given a new VSim, I set about and done the preconfigurement.

New Config; 1.PNG

In this, I had to start the configurement back at the start and needed the dvs among other things to be created.

New different; 3.PNG

This also needed more Virtual switches as seen below here I went ahead and created some more.


Once back in the cluster the GUI interface was used to create a new Aggregate, as well as a new SMV and new Luns.

New Disks; 5.PNG

But no !! the Vsim was damaged again as seen below. This was caused by an event within the network causing the Vsim to be damaged.

Issues; 6.PNG

So we went ahead, and was given a new Vsim to started another system. But disiastarter happened again, and  our system was unable to use the previously made & previously used main ESXi “Amberssec-ESXi”. This required me to switch my main ESXi to the one I first made and then make another “Third” ESXi. as seen below.



VMware Lab 11: Managing VMFS Datastores

Task 1: Change the Name of a VMFS Datastore

Here I  will rename my VMFS datastore’s.

Rename; 1.PNG

Next step is to Create 2 new Large Luns,

This slideshow requires JavaScript.

Task 2: Create a VMFS Datastore for ESXi Host

So here we are going to create a new data store this time selecting VMFS and using one of the Large Luns we have just created. Changing the datastore from 17gigs to 20gigs per the requirements for this lab.

This slideshow requires JavaScript.

So we do this twice and create VMFS -06 and VMFS-07 as shown below.

New DataStores; 4.PNG

Task 3: Expand a VMFS Datastore to consume Unused Space on a Lun

So for this, we need to expand the datastores compacity.

This slideshow requires JavaScript.

Task 4: Remove a VMFS Datastore

Here is where I need to delete off the second data store that I have made for the lab.

This slideshow requires JavaScript.

Task 5: Extend a VMFS Datastore

Here is where we will increase the storage size of the remaining VMFS. In this we will select the second Large Lun we have created. and we will “Use all available partitions”

This slideshow requires JavaScript.

Once this is done we will then go into the deviced backing and make sure the entries appear as shown below.  Once this is done we will then look at the storage afterward.

This slideshow requires JavaScript.



VMware Lab 10: Accessing NFS Storage

TASK 1: Configure Access to NFS Datastore

For this, we need to go into storage and then select the training datastore and once in this section we will go into “actions”. This is where we will then go into storage and then new datastore.

But as I found out we need to go back into Netapp in the DC01 console and go into NFS, Creating NFS protocol.PNGOnce in here we are going to go into Export policies and new policies and then create a new rule.

NOTE: Now here is where I spent a couple of hours in the lab. You have to give the Redundant Default policy the same rule as the policy you have just created. My thinking is that it somehow still has some kind of connection to it.


This slideshow requires JavaScript.

Next step is to create an NFS Volume.


This slideshow requires JavaScript.

Next we need to attach our export policy that we have previously made.


This slideshow requires JavaScript.

So we have done that, we now need to create the new datastore we started making before.


This slideshow requires JavaScript.

This is where I had issues with the Default export policy, for about three hours. I managed to walk away for an hour to relax and work out how to fix the issue. In this, I used the “Network interface show” command to see what was going on.

Newwork interface show; 16.PNG

Below you can see my new data store.

New datastore added; 21.PNG

Below we can see the configuration for my NFS datastore.

Conectivity; 24.PNG

And below we can see its connected to the ESXi host.

Connectivity host; 26.PNG


VMware Lab 9: Accessing iSCSI Storage

Allow a whole day for this lab. This lab will take you over 8 hours to complete.

Task 1: Add a VMkernel Port Group to a Standard Switch

To do this we need to be in the Hosts and Clusters tab and then navigate to where I am below. From here we need to Click on the little “add host networking”  icon (the little world in the left-hand corner).

Switch 0; 1.PNG

We will follow through the wizard to configure the Host network.

This slideshow requires JavaScript.

Task 2: Configure the iSCSI Software Adapter and Connect it to the Storage

For this, we need to go into our ESXI host and then Storage adapters and “Add and new storage adapter”. This creates the New iSCSI adapter as shown below.

New Iscussi; 6.PNG

Once in here, we need to go into the properties tab. Now the name is the IQN name we will use later on in this lab so remember this.

This slideshow requires JavaScript.

Now we need to bind the Network port.

Selecting Ip storage; 9.PNG


Here is where we need to go into the Netapp console in the DCO1.

Netapp being a pain in the arse; 11.PNG

Then check all the lines:

Liences are there; 12.PNG

Creating an aggregate.

Creating a Aggreagte; 14.PNG

Then we will create the SVM. The first one I created was wrong so this is my second.

This slideshow requires JavaScript.

Once this was done I needed to create some LunsN Now I will create 6 2 Gig Luns.

Creation of the Luns; 18.PNG

NOTE:  For this, we need an Igroup and then an initiator group. This had me stuck for awhile because i hadn’t thought about an initiator group and had me stuck for a couple of hours.

This slideshow requires JavaScript.

So after this we should have 6 Luns there.

luns; 37.PNG

Now after this we should be able to see these when we go back to the Lab and the console we were in before.

Complete; 40.PNG