Hi All,

This is my first sessions in VMware vSphere 7 Training, we will be looking at How Virtualization all started and how VMware helps us achieve this.

Agenda :

What is Virtualization?

Overview Type 1 and Type 2

What is Virtualization?

Virtualization is the process of creating a software-based, or virtual, representation of something, such as

• Virtual applications
• Servers
• Storage
• Networks

It is the single most effective way to reduce IT expenses while boosting efficiency and agility for all size businesses.

Ref: https://www.vmware.com/in/solutions/virtualization.html

Different Types of Server virtualization

• Server Virtualization
• Network Virtualization
• Storage Virtualization
• Desktop Virtualizaiton

Server Virtualization

Enables multiple operating systems to run on a single physical server as highly efficient virtual machines. 
Greater IT efficiencies
Reduced operating costs
Faster workload deployment
Increased application performance
Higher server availability
Eliminated server sprawl and complexity

Network Virtualization
Network Virtualization is achieved by reproducing a physical network, network virtualization allows applications to run on a virtual network as if they were running on a physical network — but with greater operational benefits and all the hardware independencies of virtualization. Network virtualization presents logical networking devices and services

 logical ports, switches, routers, firewalls, load balancers, VPNs and more — to connected workloads.

Note the VMware product that helps in Network virtualization is called NSX-T, The Previous version was NSX-V ( My course will not cover this topic as its a different tract of certification called VCP -NV.)

Storage Virtualization

This is achieved by virtualization the storage using storage. the Physical disk is now virtual disk in the VMware the Hard disk is a file that has the os and the user data within. usually, the storage is used by EMC, NetAPP. etc.

VMware has there Hyper Converted solution called vSAN.

Desktop Virtualizaiton

These days we have a great need of working from home so Desktop virtualization has become increasingly popular. we have different solutions for this Xen Desktop from Citrix and VMware Horizon View Desktop from VMware.

This is basically streaming the desktop to the end-user using protocols like RDP, PCOVIP, and a new protocol from VMware called Blast.

VMware has a certification path for this if you are interested in Desktop mobility.

Overview of Hypervisor Type 1 and Type 2

Type 1 Hypervisor:

This hypervisor is installed directly on the bare-metal hardware. The hypervisor is a very lightweight small software which takes care of all the IO and cpu and memory instructions, it is similar to the Kernal in our Operating systems like Windows or Linux.

Type 2 Hypervisor:

This is installed on your os like Windows or Linux, hence this is also referred to a hosted hypervisor.

The performance is better with Type 1 hypervisor as it has direct access to the CPU, memory and IOS of the physical server. In Type 2 the resources are fist used with the host Operating system then left at disposal for the type two hypervisor. an example is virtual box, VMware Player and VMware Workstation for Linux VMware Fusion

Ref:https://www.vmware.com/in/solutions/virtualization.html

I have been asked this question time and time again on how to setup a lab for vSphere to start learning VMware.

In this post today I am going to walk you through how I have created an amazing lab just using simple commodity hardware, which is easy to find and cheap to run with the electricity bills. Especially if you are planning to run it 24/7 as I do.

Hardware – Dell Optiplex 7010

I have purposely used Dell Optiplex 7010 as it is easy and cheap to buy.

Configuring / Billing of Material (BOM)

CPU Intel i7

Memory – 32GB

2TB HDD

CD/DVD

So as you can see this is a simple Dell desktop which you can buy, I have bought this from eBay for £350, The most important thing to remember is the memory, so the more the merrier. In my case, I have messaged the eBay seller and found out the maximum memory that is supported for this desktop which is 32GB and I have got 8 GB X 4 Memory Modules.

Although this looks like a good option sadly, there is no more room for an upgrade of memory as this is the maximum the motherboard supports.

I bought this kit back in Feb 2019, it fit the requirement I had for my basic home lab with vSphere 6.7

Installing ESXi

Once you get the server ready, Install ESX 6.7 you will need to register on https://www.vmware.com and download the ESX 6.7 Update 3 ISO first.

1. register with my VMware portal httpss://my.vmware.com/web/vmware/registration
2. once register login with the credentials

• Once you log-in you will find the downloads

4. click on Trial and Free products.

you will then find vSphere for Download free Trial

You can also have a go at the VMware Hands-on Lab ( HOL) they are very good too.

so once we click on the download link we will get 60 days evaluation for vSpehre 6.7 or any VMware products for that matter. as you can see my Evaluation edition time is compleated

This should let you download your software if you have registered a new MyVMware account.

You can also check out the old products that y you can click on View My Evaluation

Then you will need to burn the ISO to CD or DVD disk to install the ESX hypervisor on the server.

Please follow the blog given below to complete the ESX installation process. although this was done for ESX 6.7 Update 2 the process is the same for Update 3 too.

https://agileops.co.uk/2019/05/02/installing-vsphere-6-7-update-2/

Finally, at the end of the installation, you will find your brand new Hypervisor ready for action. you might need to check if the VT is enabled in the Bios to start nested esx host if that’s what you are planning to do like I have done in my lab.

You can find the full process of Installing the ESX on my YouTube channel where I teach VMware to beginners VMware Tutorial for Beginners | Session 3: installing vSphere 6.7

Then you can start installing the vCetner Server, you can go back to the MyVMware website and download the ISO.

Sometimes you see the error message given below:

You either are not entitled or do not have permissions to download this product.
Check with your My VMware Super User, Procurement Contact or Administrator.

If you recently purchased this product through VMware Store or through a third-party, try downloading later.

just click on Trail Download and you should be able to download the ISO

httpss://my.vmware.com/web/vmware/details?downloadGroup=ESXI670&productId=742&rPId=24857

You can follow my blog Installing VMware vCenter Server 6.7 Update 2

How does my lab look like, well that’s a good subject? please check the screenshot below:

I have the Physical dell Optiplex server which I have highlighted in red. as as you can see I am chewing almost all the memory on the server currently.

I have two VM running nested esx which are highlighted in the demo cluster running around 7 VM’s

I have the vCetner server and vROPS instance running directory on the dell server.

How can I forget I have used FreeNAS for shared storage which is provisioned using ISCSI software initiators. you will find a full process of how to provide shared storage on the YouTube chanal in two parts.

Part1:

Part2:

Hi All,

Today I will take you thought the troubleshooting for vMotion using CLI, If you have not done network troubleshooting on esx host you will find some really good esxi commands on this post. And if you are using a converged infrastructure its important to understand end to end connectivity especially if you have different vlans for each service like vMotion FT, Management traffic and VM-Traffic.

I build a brand new Data Center and after configuring the dv switch I decided to test the vMotion first and this is the error I saw on the first attempt the vm was stuck at 14 % and after a while it gave the below error message.

as shown below:

Migrate virtual machine error message

If you read the above error message you will find the IP’s of the host which I am migrating from and to.

for example lets consider the below two host this troubleshooting is done on esx-02. vmnic2 is FT vmnic3 is vMotion so I am comparing the mac address of booth the host on the ucs service profile to compare tht the vnic template has the right mac address and if they are connected to the right vlan.

esx-01

vmnic2 0000:08:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:0d 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic3 0000:09:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:0c 9000 Cisco Systems Inc Cisco VIC Ethernet NIC

 esx-02

vmnic2 0000:08:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:19 9000 Cisco Systems Inc Cisco VIC Ethernet NIC

vmnic3 0000:09:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:18 9000 Cisco Systems Inc Cisco VIC Ethernet NIC

1. check the mac address on ucs and on the esx host for the vmnic2 ( ft) vmnic3 (vmotion)
2. check the mtu it should be 9000 although this shuld not affect but I have changed them from 1500 mtu to 9000 mtu.
3.  check the nics with mac address
   esxcfg-nics -l
4.  check the vmkernal nics
   esxcfg-vmknic -l
5.  ping from the vnic using
   # vmkping -I vmk2 192.168.242.1 this is using vmk2 interface which is for vmotion
   you will notice its failing initially because the uplink on the dv switch was first given to both the ft and vmotion nics
   I then moved the dvuplink_1 to unused as I and it was my mistake which is why it was not working agian.
6.  vmkping -I vmk2 192.168.242.1 the ping test failed again
   then I moved the dvuplink_1 in active and moved dvuplink_2 to unused and the result is

The time and date of this login have been sent to the system logs.

VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # esxcfg-nics
esxcfg-nics <options> [nic]
-s|–speed <speed> Set the speed of this NIC to one of 10/100/1000/10000.
Requires a NIC parameter.
-d|–duplex <duplex> Set the duplex of this NIC to one of ‘full’ or ‘half’.
Requires a NIC parameter.
-a|–auto Set speed and duplexity automatically. Requires a NIC parameter.
-l|–list Print the list of NICs and their settings.
-r|–restore Restore the nics configured speed/duplex settings (INTERNAL ONLY)
-h|–help Display this message.

~ # esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:06:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:14 1500 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic1 0000:07:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:1a 1500 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic10 0000:10:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:10 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic11 0000:11:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:11 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic12 0000:12:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:0f 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic13 0000:13:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:10 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic14 0000:14:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:0c 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic15 0000:15:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:0f 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic2 0000:08:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:19 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic3 0000:09:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:18 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic4 0000:0a:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:13 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic5 0000:0b:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:17 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic6 0000:0c:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:12 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic7 0000:0d:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:16 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic8 0000:0e:00.00 enic Up 20000Mbps Full xx:xx:xx:a3:01:11 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
vmnic9 0000:0f:00.00 enic Up 20000Mbps Full xx:xx:xx:b3:01:15 9000 Cisco Systems Inc Cisco VIC Ethernet NIC
~ # esxcfg-vmknic -l
Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type
vmk0 Management Network IPv4 192.168.248.2 255.255.254.0 192.168.249.255 xx:xx:xx:a3:01:14 1500 65535 true STATIC
vmk1 1 IPv4 192.168.240.2 255.255.254.0 192.168.241.255 xx:xx:xx:68:7c:e3 9000 65535 true STATIC
vmk3 1 IPv4 192.168.237.2 255.255.255.0 192.168.237.255 xx:xx:xx:67:0d:34 1500 65535 true STATIC
vmk4 1 IPv4 192.168.245.2 255.255.255.0 192.168.245.255 xx:xx:xx:68:07:a0 1500 65535 true STATIC
vmk5 1 IPv4 192.168.244.2 255.255.255.0 192.168.244.255 xx:xx:xx:62:60:66 1500 65535 true STATIC
vmk6 129 IPv4 192.168.245.102 255.255.255.0 192.168.245.255 xx:xx:xx:64:9c:a8 1500 65535 true STATIC
vmk7 129 IPv4 192.168.244.102 255.255.255.0 192.168.244.255 xx:xx:xx:65:b6:41 1500 65535 true STATIC
vmk2 129 IPv4 192.168.242.2 255.255.254.0 192.168.243.255 xx:xx:xx:65:ff:87 9000 65535 true STATIC

~ # vmkping -I vmk2 192.168.242.1 –  [ping to the esx-01 failed]
PING 192.168.242.1 (192.168.242.1): 56 data bytes

— 192.168.242.1 ping statistics —
3 packets transmitted, 0 packets received, 100% packet loss
~ # vmkping -I vmk2 192.168.242.2   – [ this is the same host I am troubleshooting so its ping is ok.]
PING 192.168.242.2 (192.168.242.2): 56 data bytes
64 bytes from 192.168.242.2: icmp_seq=0 ttl=64 time=0.081 ms
64 bytes from 192.168.242.2: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 192.168.242.2: icmp_seq=2 ttl=64 time=0.055 ms

— 192.168.242.2 ping statistics —
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.027/0.054/0.081 ms
~ #
~ # vmkping -I vmk1 192.168.242.2 [  vmk1 is the vmkernal port of FaultTolarant so it will not ping as its on a different subnet and vlan]
PING 192.168.242.2 (192.168.242.2): 56 data bytes

— 192.168.242.2 ping statistics —
2 packets transmitted, 0 packets received, 100% packet loss

~ # vmkping -I vmk1 192.168.240.2
PING 192.168.240.2 (192.168.240.2): 56 data bytes
64 bytes from 192.168.240.2: icmp_seq=0 ttl=64 time=0.084 ms

— 192.168.240.2 ping statistics —
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.039/0.062/0.084 ms
~ # vmkping -I vmk1 192.168.240.1
PING 192.168.240.1 (192.168.240.1): 56 data bytes

— 192.168.240.1 ping statistics —
2 packets transmitted, 0 packets received, 100% packet loss

Now it is clear that the MAC and NIC are presented correct from UCS service profile and we have verified the MAC address and pinging from the vmkernal ports proofs that its is still not working.

I have check that they vnic template is connected to the right vlan on ucs. So next thing I have done is check the dvport group and I found that I had two uplinks on active which was wrong as one uplink is only for FT which has vlan 20and the other uplink is for vMotion which is on 21 vlan.

So, I have moved the dvuplink2 to unused as its for FT. on the dvport group which is for vMotion as shown below:

— 192.168.242.2 ping statistics —

3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.040/0.061/0.088 ms
~ # vmkping -I vmk2 192.168.242.1
PING 192.168.242.1 (192.168.242.1): 56 data bytes
64 bytes from 192.168.242.1: icmp_seq=0 ttl=64 time=0.428 ms
64 bytes from 192.168.242.1: icmp_seq=1 ttl=64 time=0.197 ms
64 bytes from 192.168.242.1: icmp_seq=2 ttl=64 time=0.219 ms

— 192.168.242.1 ping statistics —

3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.197/0.281/0.428 ms

I will  be disscussing VMware and Hyper-V Technologies and theire benifites over one and outher in detail in my next post.

 www.f5.com/solutions/resources/white-papers/

• Hypervisor contains the Virtual Machine Monitor (VMM)
• Guest OS unchanged, Host can be any kind of hardware
• Guest uses generic device drivers

Hardware Virtualization (a.k.a. Hardware Assisted)

• VMM moved to hardware
• Requires VT hardware
• Guest OS unchanged, uses generic device drivers

Paravirtualization

• Guest OS requires paravirtualized drivers
• Thin layer for hypervisor, guest has access to Host hardware
• Host any kind of hardware

in gernal we have two famous methods of Virtualizaiton : Hosted Virtualization ( installing the virtualization software VMM on a host server ie. Windows Server 2008 or Linux etc. Bare Metal Virtualization ( installing the virtualization software on physical machine directly which gives super performance eg. VMware vSphear) aka Hardware emulation Further we can classify the virtualization in three important categories Storage Virtualization: This is achieved by consolidating all the storage in a single location which makes the network admins to easily manage the storage resource. Network Virtualization This is accomplished by combining all the network bandwidth and then splitting it into channels for users. this allows the Administrator allow resources as and when they require. This allows each user to access all of the network resources, which can be files and folders on the computer, printers or hard drives etc. This streamlined approach makes the life of the network administrator much easier. Server Virtualization This is the most popular virtualization method used today to consolidate multiple virtual machines on a single high spec physical server, This will save processing power , space in DC and more importantly cost.

1.  Virtualization of old physical servers to a virtual server  also known as P2V (Physical to Virtual)
2. Setup new servers only on virtual infrastructure (unless there is a mandatory requirement of having a physical server )

Although there are a lot of products available in the market to achieve this the ones that are hugely popular is VMware and Hyper –V. both of the software does the job although there is always a big debate on which is better one. I have always been a big supporter of VMware products, with their new range of products complementing one and other. I will dig these two deeper on my next post … Thanks for reading.

Sources : VMware: https://www.vmware.com/files/pdf/VMware_paravirtualization.pdf

Dell: https://www.dell.com/downloads/global/power/ps3q05-20050191-Abels.pdf

Microsoft: https://www.microsoft.com/en-us/server-cloud/hyper-v-server/benefits.aspx]]>

1. Open VCenter  and select Convert Mechine

VCenter

 2. Specify Source: On the new screen you we will need to select source which will be the system you want to virtulize.

Specify Source

3. Specify Destination: On this screen you will need to specify the destination and destination type i.e. if you want the virtual machine to be a workstation or a vmware Infrastructure guest machine.

Specify Destination

View and Edit VMware

6.Networks: this section is to choose how you want the vm to connect to the network.

We have 3 options: •Bridge that allows you to connect directly to the physical network. •NAT (Network Address Translation) Used to share the host IP address. (recommended) •Host-only that setup a private network share with the host machine. 

 7.Services: always make sure you disable all the services which are specific to the hardware as you will not need them once the system is virtualized. an example is Apple Mobile device for iPhone.

8.  Ready to Complete: Summery of all the selections you have made just go through it to be sure that you have selection is correct. If you wish to change something you can still hit on the back button and get it changed.

Physical to Virtual Conversion by VmWare Vcenter

   After the P2V is completed, I used the VM ware Player to open the .vmdk file this understands that it’s a virtual machine and starts the system. Just by chose the option that says open an existing VM machine. And browse to the .vmdx file, you should be ready to play the vm.