IBM VM Wrae 1

Course Transcript
VMware vSphere 6 Install, Configure, Manage

- Part 1: vSphere 6 Overview
Virtualization Benefits
1. Course Introduction
2. Physical Servers
3. Virtualization Benefits
4. Hardware Resources
5. Business Continuity and High Uptimes
6. Reduced TCO and Central Management
Virtualization Components
1. ESXi Hypervisor
2. Hosts and VMs
3. Desktop Client
4. vCenter Server
5. Web Client
Standard Licensing
1. ESXi Licensing
2. Standard License Feature Set
3. vMotion
4. High Availability
5. Data Protection and Fault Tolerance
6. vShield Endpoint, Replication, and Hot Add
7. Enterprise Licensing Feature Set
Enterprise Licensing
1. Reliable Memory and Big Data
2. Distributed Resource Scheduler and Power Management
3. Storage APIs and Multipathing
4. Enterprise Plus Feature Set
5. vSphere 6.0 Additional Enterprise Plus Features
6. Essentials Kits
7. Support and Services
Practice: Selecting a vSphere Setup

1. Exercise: Choosing a License and Software
Course Introduction
Learning Objective
After completing this topic, you should be able to
◾ start the course
1. Introduction to the course

Virtualization using VMware 6 provides a host of benefits to a server environment. This
includes things like high availability, improved resource utilization scalability. And ultimately,
when you put all this together – cost benefits. This course covers the benefits of virtualizations
and the licensing level required to get those benefits. So enjoy.
Physical Servers
Learning Objective
◾ describe the problems with physical servers that lead to a requirement for
virtualization and VMware vSphere 6
1. Problems with physical servers

So what are the issues with physical servers that led us to virtualization? Well, first in our
physical environments, we had to have a 1:1 application to server ratio. Meaning if I had a
simple instant messaging application that required its own server to run on, I couldn't put
multiple applications on single servers. It was not done. It was not best practices. And this was
to keep single points of failure from bringing down multiple services at one time. If you had a
physical server down, you had one application down at that time. Now what was the problem
with that model? That model produced inefficient use of hardware resources. You take a look
right there, that second bullet point – inefficient use of hardware resources. Now that became
even more pronounced as our servers became more and more powerful.
[Issues with physical servers are one to one application to server ratio, inefficient use of
hardware resources, underutilization of resources, data center sprawl, high total cost of
ownership, and high redundancy costs.]
We saw the CPU utilization, the memory utilization. We saw that drop slowly from 40% to 30%
to 20% in some cases. And this underutilized resources – that meant that we had very low
efficiencies in our datacenter. We had very large datacenters with multiple servers and multiple
racks everywhere, but we had a finite amount of applications that we could run on each one of
those servers. It was a 1:1 ratio. Now what did this mean? This meant we had a total...a high
total cost of ownership. I had to purchase all those servers to run all those services. And if I
wanted redundancy, I used to have to do things like mirror servers. So now my ratio is 2:2 or
1:2. I am running two...one application twice on two separate servers for my redundancy. That
was an incredibly high redundancy cost.
[The presenter continues to explain the same example.]

Virtualization Benefits
Learning Objective
◾ describe the benefits of using server virtualization and VMware vSphere 6
1. Benefits of using server virtualization

Let's talk for a moment about the benefits of virtualization. Virtualization is the other side of the
physical environment coin. Where in a physical environment, we have a 1:1 ratio. In
virtualization, we have high consolidation ratios meaning I can have multiple virtual machines
providing multiple services or applications on a single physical server. This is an incredibly
efficient use of hardware resources, especially compared to our physical environments.
Remember in our physical environments we have a 1:1 ratio, in virtualization we can have 7:1,
10:1, 11:1, depending on the applications you're actually running on that server, you can have
great, great efficiencies, up to 80% in some cases. Virtualization also provides us with certain
technologies that helps us with business continuity and high uptimes. Now, back in the old
days of IT, five nines was an incredibly high bar to set for uptime. Now, what do I mean by five
nines. That was an uptime of 99.999% of the time.
[The benefits of virtualization are high consolidation ratios, efficient use of hardware resources,
business continuity and high uptimes, reduced total cost of ownership, and central point of
management.]
That is an incredible amount of uptime in a given year. That's only five minutes of downtime in
a given year. So that was the golden standard. But with virtualization that bar has lowered,
because it's much easier to attain those high uptimes. Virtualization also reduced our total cost
of ownership, because I don't have to spend the money on purchasing ten different physical
servers to put out ten different services. Now I can run all ten of those services on a single
physical box. What does this mean? This means less management. This means less total
upfront cost, less power, less cooling. Very, very important that virtualization provides us with
that cost savings. And last but definitely not least, we have a central point of management.
Sitting in front of a single terminal, I can manage multiple servers. I can also manage multiple
ESXi hosts or actual virtualized servers, which they themselves can have tens of virtual
machines on them. So incredible, incredible benefits to virtualization.
[The presenter continues to explain the same example.]

Hardware Resources
Learning Objective
◾ describe resource utilization efficiencies gained from using VMware vSphere 6
1. Describing resource utilization

Virtualization provides us the ability to take a bare metal server and install that ESXi hypervisor
on it. Now what does that hypervisor allow us to do? That hypervisor allows us to install
multiple guest operating systems on that server. This is incredible because it allows multiple
guest operating systems to share the same physical resources. The resources located here in
this box, right there, can be shared upon 2, 3, 4, upto 10, 11, 12 virtual machines – all running
different guest operating systems. Now it depends greatly upon the applications you're
running, of course. But this was an incredible leap forward in IT. We no longer relied on the 1:1
ratio – one application for one server. We can now have multiple applications running in virtual
machines all residing on the same physical server.
[Virtualization achieves high server consolidation ratios by allowing multiple guest Operating
Systems to share the same physical resources.]
This is a much more efficient use of physical resources and came to...it provided us with such
cost savings in the datacenter itself. Now with virtualization, we have multiple operating
systems. And these operating systems are all installed on one physical server. This allows us
to have a much more efficient utilization of resources. Remember, our physical environments,
1:1 ratio – one application, one full server. Virtualization allows us to have multiple applications
using the same physical server, the same hardware resources. In our traditional physical
environment, most applications used only 20% to 30% of the resources available – that's 20%
to 30% of the CPU; that's 20% to 30% of the memory; that's 20% to 30% of the hard drive.
[Sharing a single physical server with multiple Operating System allows for a more efficient use
of resources. Traditional physical server implementation goes up to 20% - 30%. Virtual
implementation goes up to 80% of utilization.]
Now that's wasted resources; that's wasted money. You paid for 100% of that CPU. Now with
virtualization, we can get up to 80% utilization. That's huge; that's 60% to 50% more resource
efficiency due to virtualization. Now what does all this mean – these efficiencies gained? This
means I don't need to purchase as much physical equipment to run the same services I had in
my physical environment. My physical environment requires much more resources than my
virtual environment will. Simply because I'm much more efficient at utilizing those resources.
[The presenter continues to explain the same text.]

Business Continuity and High Uptimes
Learning Objective
◾ describe the business continuity and high uptime benefits of using VMware vSphere
6
1. Benefits of using VMware vSphere 6

One of the main benefits of virtualization is it greatly reduces how hard it is to provide high
uptimes and business continuity. In an old-fashioned physical environment, this is a tough
thing to get, right, business continuity and maintaining high uptimes. Why is that? Because in
order to get this, right, you have to eliminate single points of failure. Now in a physical
environment, single points of failure means we're going to have multiple pieces of hardware
doing the same function. So, if we have a single application that requires high uptimes and
requires to have some business continuity built into it, that means I'm going to have multiple
physical servers – all serving as backups for that one application. So efficiencies are
exponential here. If I'm only running at 20% efficiency on original server that's running that
application and now because I need business continuity and high uptimes, I have to tap three
or four of those servers now or even just two. Guess what? I only have 20% to 30% efficiency
on those two, three, or four other servers.
[Virtualization greatly reduces the burden of maintaining high uptimes and business continuity
implementations. VMware available features include high availability, distributed resource
scheduler, fault tolerance, and site recovery manager.]
So that is really tough to get right, because not only you need to get the planning absolutely
correct in a physical environment, you must also have a lot of money. Your total cost of
ownership goes way up in a physical environment. Now virtualization, VMware in particular has
technologies to help you reduce those costs; reduce how hard it is to get this right. Some of
those technologies include high availability, distributed resource scheduler, fault tolerance –
that's a big one. Fault tolerance is a great thing for high uptime, great technology there. We
also have site recovery manager that is a huge technology dedicated to business continuity.
And all these technologies together make VMware much easier to implement our business
continuity plans and maintain our high uptimes. All these technologies provided by
virtualization and VMware in particular really help us out as administrators.

Reduced TCO and Central Management
Learning Objective
◾ describe the TCO and centralized management benefits of using VMware vSphere 6
1. TCO and centralized management benefits

You've definitely heard before that virtualization provides you cost savings. But how exactly
does it do that over our physical environment? What is the difference? Well first we have
reduced energy costs. Now how do we get reduced energy costs? We get reduced energy
cost, because we don't have as many physical servers anymore. We go from the one
application to one physical server rule to many applications to a single physical server. This
means I'm pulling less power. I have less physical servers so I'm pulling less power. Less
physical servers also mean reduced cooling costs – have greatly reduced cooling costs. I no
longer need as many people working on those physical servers because I have less physical
servers. If I go from a 100 physical servers down to 20 physical servers, I don't need a large
staff to maintain that anymore. I can lower my total staff cost or at least lower the amount of
time spent on maintaining those 100 separate physical servers.
[Virtualization allows you to consolidate several services into a single physical server. It
reduces energy costs and cooling costs. It lowers maintenance and management costs. Initial
capital outlay for hardware is reduced and lesser space and infrastructure is required.]
Because I have less servers to manage across the board, my management costs are cut. And
more importantly, employee time devoted to managing these different servers is reduced as
well. This is not even to mention the physical hardware reduction. I'm just spending less money
on physical hardware at this point. And, if you're leasing a space in an environment; if you're
leasing space from some large datacenter provider, you now get at least less space – less
infrastructure required. I don't need as many switches, because I don't have as many physical
servers. If I lessen the amount of space I use in my data center, guess what, I have less
physical space to cool as well. So very interesting financial benefits of virtualization here. Make
sure you make note of it.
One of the greatest benefits to virtualization is centralized management. I can manage my

entire virtual environment from a single terminal. I can control where my virtual machines go in
my environment. I can move virtual machines from one side of my datacenter to the other from
a single terminal. I don't have to get up; I don't need to take images; I don't need to move
images across. I can do that from my single terminal. I can also update my entire VMware
software from a single console as well using update manager. So the centralized management
feature of virtualization is a huge benefit to any administrator out there, especially if you're a
little lazy like myself. It just makes life so much easier.
[VMware offers vCenter Server, which is a centralized management server for your virtual
environment. It manages all virtual machines from a simple interface. It provides a centralized
control over migration among hosts. It offers statistics monitoring of servers and virtual
machines. It offers control of patch and update management of VMware software.]
ESXi Hypervisor
Learning Objective
◾ differentiate between type I and type II hypervisors, and describe VMware ESXi
1. VMware ESXi
Let's talk for a moment about the ESXi hypervisor. Now the ESXi hypervisor is a hardware
abstraction layer. It is the magic that makes virtualization work. Now, if we take a look at this
type 1 hypervisor down here, you'll see that the ESXi hypervisor lays right on top of the server
itself. Now this hypervisor controls access to the underlying hardware. We call this a hardware
abstraction layer. And this hardware abstraction layer allows us to control resources. And
actually give those Hardware Resources to different guest operating system. This is what
allows us to have multiple guest operating systems on a single physical piece of hardware.
Now there are two types of hypervisors – there is a type 1 and a type 2. We will discuss those
a little later. But what I really want you to understand is in virtualization, the hypervisor is where
the magic takes place. So even if it's a type 2 hypervisor, this is where we take that hardware
and we divvy it up and give it to different virtual machines.
[The ESXi Hypervisor is a software abstraction of the hypervisor. It creates an abstract layer of
the hardware. It allows the sharing of hardware resources to multiple guest operating systems.
There are two types of hypervisors: Type 1 and Type 2.]
So how does a virtual environment compare to our physical environment? What is the
difference? Well, in our classic physical computing model, we had a 1:1 ratio. We had a single
guest operating system installed on a single physical server. There was no way around that.
There was no way to cut up the resources or share the resources among multiple guest
operating systems. Now when virtualization came out, the game completely changed, we could
add multiple guest operating systems. Now if you look here, you see a nice pizza. It's kind of
making me hungry a little bit actually. But, if we think of this as Hardware Resources, if we
pretend that this piece of pizza was Hardware Resources, this would mean the entire pizza
would be given to me – none for you, all for me. Now I get the great end of that deal. I like it
quite a bit. But you might be hungry, you might want some pizza as well. Well the same went
with our physical servers. We had all these resources and whether the application needed or
not, it was getting all those resources. Virtualization allowed us to do something incredible. We
could take those hardware resources and we could cut it in half.
[Classic computing: Hardware can be presented to only one operating system. We often had a
one application to one server ratio. Virtualization: Computer resources are dividable, enabling
a single piece of hardware to serve multiple guest operating systems. Multiple applications can
now reside on the same hardware in the model displayed.]
Now I have enough, I can split up those resources. I can give half the resources to one guest
operating system and half to the other guest operating system. This allowed me to have more
than one guest operating system per server. And as you can see here, more than one person
enjoying a pizza. Okay, so we know that the hypervisor allows us to divide up that physical
hardware and give access to multiple guest operating systems. How do we do that? Well, if
we're looking at the CPU itself, let me grab a little arrow here and show you, if we're looking at
the CPU, are we going to divide up that CPU? No. We're not going to actually cut up the CPU
for use by different virtual machines. What we're going to do is we're going to take time slices
and each one of these time slices is going to be assigned to a virtual machine. Now these time
slices are incredibly small. And since it varies, we can...we don't even notice the switching
between virtual machine 1 processing and virtual machine 2 processing. We send in chunks of
data to be processed. The CPU processes it for virtual machine 1 and then moves right on to
the next time slot for virtual machine 2. And that allows us to divvy up CPU resources.
[The ESXi Hypervisor manages hardware resources allowing multiple guest operating systems
to access the hardware simultaneously. The hardware includes CPU, RAM, and storage.]
Now, if we have multiprocessors, it becomes even easier because then we have multiple
processors that are cutting up their time for multiple virtual machines and the process is even
more seamless. Now what about RAM? RAM is a little different. RAM doesn't have time slices
and processing. All we have is addressable space, right. That's what we have in RAM. And we
measure that on gigabytes and how many gigabytes we have available. Well here is what we
do for virtual machines. We allow virtual machines a portion of the addressable memory in
RAM and when we use that, that is assigned to the virtual machine. But when we're not using
that RAM, the rest of that RAM is released back into the general pool of resources for other
virtual machines that may need that RAM at the moment. It's a really, really cool way of
dividing things up. Now what about storage? Storage is pretty simple in VMware. What we
have is each virtual machine has a file and that file represents the hard disk drive of that virtual
machine.
It's just a file, but to that virtual machine, that is the disk drive. Now this file can reside on
shared storage or at local storage on the host itself. But that's how we divvy up the space and
storage for virtual machine. So we can have those different guest operating systems. We just
have a file that represents the hard disk. Now we know there are two types of hypervisor –
there is a type 1 and then type 2. What are the differences between the two hypervisors? Well
let's take a look at a type 1 hypervisor. A type 1 hypervisor resides squarely on top of the
hardware. We don't have a guest operating system in between us and the hardware. We
reside directly on the hardware. It is installed much like you would a guest operating system
the hypervisor is. It's directly installed, there is nothing else existing on that server at that time.
Now VMware's version of this type 1 or bare metal hypervisor is known as ESXi. There are
other versions from other vendors that exist. One of the more well-known ones is Microsoft's
Hyper-V.
[A type 1 hypervisor is installed directly to hardware. This is often referred to as a "bare metal"
installation. VMware's version is known as ESXi, which was formerly known as ESX.
Microsoft's version Hyper-V is not an emulation but a software presentation of a hardware.]
Now it is also a type 1 hypervisor. Now what is really important to remember is that a
hypervisor is not a hardware emulation, it is a software presentation of the existing hardware.
We're taking that hardware and the hypervisor is then presenting it to our virtual machines.
Very important to remember. Another thing you should remember about a type 1 hypervisor is
this is production level. This is what you will see at the enterprise level for large organizations.
A type 2 hypervisor is different than a type 1 hypervisor. Now what is the difference? Well, a
type 2 hypervisor exists on a previously installed operating system. If we look here at the
screen, you see that server down there at the bottom but you see the Windows icon. We have
Windows installed on that particular server. A type 2 hypervisor installs itself on top of that
existing operating system.
[A type 2 hypervisor is installed upon a guest operating system. A type 2 hypervisor should not
be used in a production implementation of services. VMware's workstation and Microsoft virtual
PC are some of the examples.]
Now is this a production level implementation? No, it is not. Because we have the underlying
overhead of that existing operating system, we do not utilize all the hardware of that particular
server. So we don't want to use this in a production environment. It's not as efficient as a type
1 hypervisor. Now what are some of the examples of a type 2 hypervisor? That would be
VMware's workstation and Microsoft's Virtual PC. Those are two examples there. But be
mindful, we don't want to use a type 2 hypervisor in production. This is great for a lab
environment or a testing environment or other small environments, where we don't have to
have very high utilization of the underlying hardware resources.

Hosts and VMs
Learning Objective
◾ describe hosts and VMs in a virtualization environment
1. Describing hosts and VMs

Let's talk a moment about the main component of virtualization. Now what is this main
component? This main component that makes up our virtual topology is a host. Now what is a
host? Well we start out with a server. Let me draw a circle around that server. I'm going to
exclude those virtual servers there for a second. So we just have a piece of hardware. That's
all we have at the moment – a clunky piece of hardware. Now as all of you, as administrators,
probably know without an operating system or some other type of software installed on this
server, it's just basically a big door stop. It doesn't do anything until we give it a program or
some type of functioning software to do something with. Now in virtualization, what we would
do is install the ESXi hypervisor. We would install that Type 1 bare-metal hypervisor on this
physical server right here. Once we install that ESXi hypervisor, we have taken the hardware
resources and we are now able to abstract it to break that up into usable pieces for more than
one guest operating system. Once we've installed that ESXi software on that physical server,
we now have a host.
[Hosts usually represent a single installation of ESXi on server hardware. Hosts are where the
hardware is shared. Host is a small portion of resources. A host can house several virtual
machines.]
Why is it called the host? It's a host because now we can install these guest operating
systems. These guest operating systems can now be installed by creating virtual machines on
this host. So this host can have multiple virtual machines, all of which reside on this physical
server and use the physical server's hardware resources. Now how many virtual machines can
any given host sustain? Well it really depends. It depends on the applications you're running
on those different virtual machines and how much hardware resource utilization they have. But
you can see anywhere from 3 to 10 to 15, depending on the applications you're running. So
that is a host. In essence, it's basically...it's like an aircraft carrier and the virtual machines are
like the aircraft. We can have multiple virtual machines sitting on that single host. And that is
the backbone of a virtual...VMware's virtualized topology – the host,
okay. So we know a host is what holds virtual machines. But what is a virtual machine? Well a
virtual machine is a predefined amount of resources that we're going to set up that's going to
hold a guest operating system. So when we boil it down to its simplest form, a virtual machine
is nothing more than a container in which we're going to put a guest operating system. Often
times, that guest operating system is providing a service of some type. In our physical
environment, this would be...this would represent a single physical server. A single physical
server used to provide the space for a single OS and a single application. No longer we can
now have a host with multiple virtual machines holding multiple guest operating systems with
multiple applications. So what is a virtual machine? When we boil it right down to it – it's a box.
And that box has defined resources; it's individual; it will not carry over into other virtual
machines; it's self-contained. And that box contains an operating system and often times an
application or server.
[A virtual machine is a defined box of resources served to a guest operating system.

Resources required are taken from the host. The virtual machine is your application, which is
traditionally referred to as a "server."]
Desktop Client
Learning Objective
◾ describe the features and versioning of the VMware vSphere 6 host client
1. Features and versioning of host client

All right, let's talk for a moment about the desktop client. Now those of you who have used
previous versions like 5.0 and 5.1 and 5.5, all remember the desktop client being a
management interface. We could use it to manage a single host or we could point it to a
vCenter Server and manage our environment from there. Now starting at 5.1, things really
started to change. In 5.1, we started to lose functionality of the desktop client. And what we
began to see was the web client start to take over more and more. Now in 6.0, the desktop
client is no more; it no longer exists. What we're going to use now is called the HOst
Client.
[The desktop client is a free to use application that you download directly to a PC. This can be
used to manage a single host or connect to vCenter Server. Functionality has been reduced
starting in version 5.1. Desktop client is operating system specific for the PC in use. It is used
for specific add-on management, which is not supported by the web client. Thus, desktop client
is no longer in development.]
Now the host client allows us the same type of functionality as a desktop client but the
interface has completely changed. The interface now looks exactly like the web client. So
those of you who were slow to adapt to the web client were hoping things would change. I'm
sorry to break the news – the web client is here to stay and the desktop client is completely
gone. It's been replaced with the host client and the host client looks exactly like the web client.
The host client is just used for that one-to-one management. Make sure you understand that.
For any type of large environment organization where we want a single point of management
for entire VMware topology, we can't use the host client for that in 6.0.

vCenter Server
Learning Objective
◾ describe the features and functionality of VMware vSphere 6 vCenter Server
1. Features and functionality

Now in large environments, we use the vCenter Server to manage our virtual topology. This is
a server created solely to manage the hosts and virtual machines that we create throughout
our virtual environment. Now this vCenter Server has to be installed on a Windows Server – an
existing Windows Server – we need that Windows license. We can use an internal or external
database depending on the size of our environment. If we're going with a small environment
and we're installing vCenter Server, we're going to be limited to about five hosts and 50 virtual
machines. And this is going to use an internal or embedded database – SQL Express – to
manage these different hosts and virtual machines. If we have an environment larger than that
and we're going to use vCenter Server...we'll talk about the vCenter Server appliance a little
later. But, if we're going to use the vCenter Server, we must use an external database for
those large environments. Now the installation of vCenter Server, as you will see through
videos coming up, it can be installed on a single server or multiple servers – up to three, four,
and five servers – depending on what your organization has available.
[vCenter Server is a service implemented to manage multiple VMware hosts from a single
point. This can be implemented virtually or physically. We can use an internal or external
database for installing vCenter Server. It can be installed on a single or multiple servers. The
server, where it is being installed, requires windows licensing. For large environments, vCenter
Server can link with other vCenter Servers. To connect to vCenter Server, desktop or the web
client is to be used. The vCenter Server requires a separate purchase, which is not included
with ESXi licensing.]
Now in order to manage this vCenter Server we need to use the web client. We'll take the web
client and we'll point it at the vCenter Server. And that will give us – as administrators – our
interface to work with these hosts and these virtual machines. In super large environments,
vCenter Server can actually link with other vCenter Servers to create a large manageable
environment even outside the scope of the maximum configuration. Now one of the drawbacks
to vCenter Server is it requires a separate purchase. This does not come with ESXi. You have
to pay extra for that licensing for vCenter Server and you have to pay extra as a support and
service agreement as well. So it's not all rainbows and unicorns but it is a pretty cool
technology.
Now the sibling to the vCenter Server is the vCenter Server appliance. Now the vCenter
Server appliance has grown leaps and bounds over the years. As way back in 5.1 and 5.5, you
saw it gaining capacity and gaining size. It has now become a really useful tool in medium-size
environments. And we'll talk a little bit about that later in videos to come. But what I really want
you to get out of this is it's a little better to install in smaller environments. Now why is this?
Well first it can be...it's a self-contained virtual unit. We just roll it out as a virtual machine. And
we don't need any Windows licensing like we did in the vCenter Server. This is installed on a
Linux backbone. So no Windows needed. Now like I said earlier, there are size limitations. And
currently, there is no way to use linked mode. I cannot connect my vCenter Server appliance to
another vCenter Server appliance within my organization to enlarge my management domain. I
can't do that at this time.
[The vCenter Server Appliance is a prepackaged version of vCenter Server. Although similar in
many ways there are some key differences to the application. The vCenter Server Appliance is
a self-contained virtual only implementation. It is built on a Linux backbone and does not
require windows licensing. It has size limitations and has no linked mode. It is easier to deploy.
It is included with vCenter Server purchase.]
But know this, in every version we moved through VMware, the vCenter Server appliance has
gained functionality. Now another advantage of the vCenter Server appliance is it's much
easier to deploy and it's much easier to manage. We'll see that in later videos. But trust me, it's
easier to manage. I can start and stop services right from my management console for the
vCenter Server appliance. Now you don't have to purchase this separately from vCenter
Server but you do have to purchase licensing for the vCenter Server. As long as you purchase
licensing for vCenter Server, you do get the vCenter Server appliance with it. So this is a really
cool implementation. Like I said, it rolls out virtually on a Linux backbone, okay. You just
download the template, deploy the template, it rolls out, and you start up the services and
you're good to go. And we'll teach you how to do that in a later video.

Web Client
Learning Objective
◾ manage VMware vSphere 6 with the web client
1. Managing with the Web client

Our final component for management of our virtual topology is the web client. Now the web
client is used to point to a vCenter Server or vCenter Server appliance. This is just the
interface we are going to use for our management. The vCenter Server or the vCenter Server
appliance is doing all the work, doing all the processing, and everything like that. We're just
creating a window into that environment using a browser. Now is this difficult to do? Not really.
Any browser will work. It's not OS dependent. What we need to do though is install a plugin for
that browser that allows it to open up console windows and other windows that VMware needs
for your management purposes as an administrator. Like I said, this is vendor neutral. You can
Mac OS X or Windows – whatever it is you're using – it is neutral. As long as you have a
browser, it's okay. Now I know, some of you guys who are moving from older version – 4.1,
4.5, 5.0 – will say that the web client is not as functional as the desktop client once was. That's
not the case anymore. The web client is a fully featured administrative tool, so don't be afraid
to use it. Well, in this case – in 6.0, you have no choice but to use it. Everything else has gone
the way of the dodo.
[The web client is used to connect to vCenter Server and manage multiple hosts at one time. It
requires a plug-in added to browser. The plug-ins must be added to each browser that is used.
The web client is vendor and browser neutral. Increasing functionality is added beginning with
version 5.0 and increasing. Web client will not manage all features. Beginning in 5.5, web
client is the only way to manage virtual machines with hardware 10.0+.]
Now there are some limitations on what the web client can do. And some of those include
rolling out of a VirtualCenter Server appliance. We need to use the host client to do that. But
the web client is pretty much full featured in 6.0. And beginning in 5.5 and higher, the web
client is the only way to manage virtual machines with a hardware level of 10.0+. There is no
other way to do it than through the web client. So, if you are in an older environment now and
you're watching this course and you're saying, "Why I use the desktop client?" It's time to start
getting used to the web client. It is all they're using in 6.0 and I don't see them bringing back
the desktop client anytime soon. So get used to that Web Interface. Now what does this Web
Interface actually look like? Well, let's jump out and take a look. First off, if you look at my
address bar, I'm just pointed at an IP address. That's the IP address of my vCenter Server.
And I'm going to go ahead and put in my password here.
It's going to log me in and let me know. And this is the basic look of the web client. On the left I
have my inventory, in the middle I have my actions what I can do. So let's check the Hosts
and Clusters view. You can see here, I have my hosts. We talked about them a little bit in
prior videos. We have virtual machines underneath. The little green arrow indicates that the
virtual machines are actually powered on and running at the moment. Down here, we see
another host. And notice the hierarchical structure of this web client. Up here, I have these two
hosts, but these two hosts reside in what? My Infrastructure datacenter. And all of those are
managed by my vCenter Server appliance, which in this case is named localhost. So take the
time, go through the web client, and learn how to use it. Those of you who have an
environment, please do so. The desktop client isn't coming back anytime soon.
[To log into the web client, the presenter enters the IP address in the User name field and
types the password. The page is divided into three sections. To the left, inventory is displayed;
to the right, recent tasks are displayed; and in the middle, the actions that can be performed
are displayed. In the middle section, Home tab selected. From the inventories section, the
presenter selects the Hosts and Clusters tab. On the left side of the screen, a directory tree
appears where all the hosts are listed. Under the Infrastructure datacenter, the hosts listed are
hansolo.home and lukeskywalker.home.]
ESXi Licensing
Learning Objective
◾ match the VMware ESXi licenses with the functionality they grant
1. ESXi licensing functionality

Hello and welcome to lesson three of our virtualization module. Now a lot of things we're going
to be talking about in these lessons have to do with licensing and the different features
associated with that licensing. Now there is a lot of stuff we're going to talk about here. And
there are a lot of different levels of licensing. So please pay attention. This is one of the things
I'm questioned about the most in my classes is what licensing grants what features. So, if you
pay attention here, you're well ahead of the game. So one of the most interesting
implementations of VMware is a free implementation. That's right. You can get a free
hypervisor from VMware that will allow you to host virtual machines. Now there are some
major limitations here as you might imagine. We can't have vCenter Server that takes out any
type of centralized management that we may want to put together. Also a lot of the features
that go with that centralized management such as vMotion, Storage vMotion, fault tolerance,
HA – those cannot be implemented in this environment because again, no vCenter Server can
be used. Now there are also resource limitations on here that are little more stringent than the
regular licensing. One of those to keep in mind is the 32 gigabytes of RAM that is the
maximum you can have on a host. It's a severe limitation if you're looking at a real fully-robust
enterprise solution.
[VMware provides the ESXi hypervisor as a free download. The first limitation is VMware has
stand alone installation. This means vCenter Server is not included. The second limitation is
the maximum size of RAM that is 32 GB.]
Now there is another way to get licensing from VMware. There is the trial license – you will
have 60 days to download and use. Any ESXi host you want, you just go to vmware.com and
you go their trial page. You pick the product you want to try and they let you try it for free for 60
days. Now you get a full-featured enterprise plus implementation at that point. And we talk
about that in other videos. But you get all the bells and whistles there. So it's very...if you're
going to build a lab environment to try and test things up, I recommend going with the trial
implementation first and then looking at the free if you're going to use it. Now free is a very
small environment. I really want to make sure you understand that. Sometimes it's not
even...doesn't even work well in a lab environment because you want to test things out. You
want to test out some of the features that may exist in your organization. And you might have
enterprise or enterprise plus licensing or even standard licensing with a vCenter Server. You
cannot test out any of the functionality with a free license. I want to make sure that everyone
out there understands. Though it's free, it may be good for, you know, something you're going
to do at very, very small level. Not even really useful at a lab or sandbox level. So keep that in
mind when you download your free copy of ESXi – the ESXi hypervisor.

Standard License Feature Set
Learning Objective
◾ describe the standard VMware vSphere 6 license and the feature set enabled
1. Matching with functionalities

Alright, at the very base level of licensing for the VMware, vSphere product is – vSphere
Standard. Now standard is the basic feature set. This is the lowest level of licensing you can
get, but it does come with quite a bit of features that can be rolled into this particular license.
Now in order to use these features, you must have a license for vCenter Server. Now like we'll
talk in other videos, and we'll see that vCenter Server is licensed individually. If you buy, you
know, vSphere ESXi Standard licensing that does not include vCenter Server, very important
to know that. One of the...some of the features we include are vMotion, Storage vMotion, HA,
data protection. There's a ton that we're going to go through. But it's good to understand that at
that very base level, we start with this feature set and we're going to add more as we go
through.
[VMware vSphere Standard is considered the basic feature set offered by VMware. This is the
lowest normal licensing set available. These features require a vCenter Server for
management. The features include vMotion, storage vMotion, high availability, data protection,
fault tolerance, vShield Endpoint, and vSphere Replication.]
Now the higher licensing such as enterprise and enterprise plus, they come with this feature
set that's in standard. So anytime you go up a level in licensing, you get everything that was
below it as well. So very, very good information to know what you have in your environment,
the type of licensing you have, and what your allowed feature was. Because it really helps you
out to understand, "Oh! Can I implement fault tolerance? Or do I not have the licensing for it?
And am I running a free license?" In that case, you would not be able to run fault tolerance. But
if you have the standard licensing or better, fault tolerance is your friend, you could definitely
put that out to any virtual machine you wanted.

vMotion
Learning Objective
◾ describe vMotion licensing in VMware vSphere 6
1. Describing vMotion licensing

One of the really cool features of standard licensing and every licensing above that is vMotion.
Now vMotion is literally the movement of a virtual machine from one host to another. If you
look the graphic there, we have that virtual machine right there and he's moving back and he's
moving forth. And we can do this is in a powered-on state or at powered-off state. Now I know I
blew some of your minds right there. In a powered-on state really we can do that? Yes, without
a loss of service even. So really, really awesome technology; really, really awesome feature
that helps you, you know, really maintain your environment. You have such control of where
virtual machines lie. And in the middle of all this, if something happens to a host, you can move
that virtual machine off of one host on to another. So from one physical server with multiple
virtual machines, you can move all those virtual machines on to another physical server with
multiple virtual machines on there with no downtime.
[vMotion is the migration of a virtual machine from one host to another. This can either be in
the powered on or powered off state. This is made possible through a shared storage solution.
Hardware can be maintained with no downtime. Virtual machines can be moved from legacy
hardware.]
What is this good for? Well this is good for hardware maintenance. If we're seeing failures in
some point places, maybe we have resource contention on particular host because the virtual
machines are getting really large. We have the ability to move those virtual machines off. And
this comes with every standard license, enterprise license, and enterprise plus license that you
purchase, you have this ability. Now there are some other requirements like I need vCenter
Server to make this work, so I need another type of license but standard licensing does
support this feature. Another really cool feature that standard licensing provides us is Storage
vMotion. Now Storage vMotion, pretty much the same as vMotion but now we're dealing with
the actual files on our shared storage devices. So, if we have resource contention on our
storage devices – our shared storage devices, we can actually move virtual machines that are
currently located on data store 1, we can move them over to data store 2 simply with a few
clicks of the button.
[Storage vMotion manages storage utilization live.]
And that's really, really cool because even if I'm just doing maintenance, if I have to take a
storage appliance down for maintenance, I can move virtual machines off to data store 2,
which is up and running. I don't have to bring that down. I don't have to bring the virtual
machines down. I can keep my high uptime by again making sure that my virtual machines are
moved to the best place possible that I have chosen as an administrator. So I'm not stuck
there. Once I create a virtual machine on data store 1, that virtual machine does not have to
reside data wise on data store 1 forever for eons and eons or until, you know, I have the time
to back it up and manually move it over. No I can do it with Storage vMotion. It's a feature
that's included in any standard enterprise or enterprise plus licensing that you get. And just like
vMotion, it does require that you have vCenter Server around to facilitate the movement of
these files across.

High Availability
Learning Objective
◾ describe uptime and high availability features enabled by VMware vSphere 6
1. Uptime and high availability features

So high availability is one of the coolest features available in our standard licensing feature set.
Now why is that? Well, back when dinosaurs were on the earth or back when we...I first started
IT, we had this golden rule. Now those of you who are out there, our golden standard used to
be the five 9s of uptime that's 99.999% of uptime. That was roughly about five minutes in a
year, yeah, five minutes in a year. That's how long we could be down to maintain that 99.999%
of uptime or five 9s. Now this was the golden standard because it was so hard to reach back
that. Think about the average maintenance on a physical server. In two...every two years or
so, you're going to want to at least take a look or upgrade certain components in there. And
that requires downtime.
[High availability monitors for host failures. When a host fails, high availability restarts virtual
machines on functional hosts without manual intervention. It reduces application downtime. It
offers automated protection of business applications.]
Now, if it was more than ten minutes in that two-year period, guess what? I've just completely
ruined my five 9s of uptime. That's why it was so difficult to maintain this five 9s of uptime. You
really had to have a lot of money and resources behind you. And merit servers and all sorts of
things going on in order to meet those five 9s. Now any type of maintenance meant to that. Not
to mention any time of unplanned downtime. You have a power supply fail, something fails,
your NIC card fails, anything like that, boom! You're down as well. Now why do I say all that?
Why all that information? Well, because high availability is something that allows me to get
away from, you know, that really difficult task of me as the admin, always having to make sure
those virtual machines are up on a running system. So what does this mean? Well, when I
have a host...let me bring out a host for you right here. If I have a host over here and this host
fails,
in the old days, I used to have to find a way to get it back up and running, right? If it was a
physical server with an application on it, I personally was responsible for getting that
application running on some other system immediately, as soon as possible. But with the host
and virtual machines what we have is we can actually have virtual machines migrate
themselves off with HA. vCenter Server will take that virtual machine that's running the
application and HA will say, I need to move this to a host that can handle the load. And it'll do
this automatically. When a host fails, that virtual machine will automatically try and restart on
another host. So this virtual machine here would actually move itself onto a new host and boot
itself back up.

Now there is lots of details that go into this process and we'll cover those in other videos. But I
want you to know that this feature has really made that golden standard, that was once really
difficult goal to achieve, much more reachable because this is an automated process. I don't
have to be in the building when this happens. I don't need to sleep with my pager under my
pillow, I mean cell phone under the pillow. I didn't mean to tell you how old I was there. But
yeah, I don't have to sleep with my cell phone under my pillow anymore, in case it goes off. So
a really automated, cool way to protect your applications and maintain your 9s of uptime – your
five 9s of uptime, maybe it's only four 9s in your case. But it allows you to really maintain your
uptime.

Data Protection and Fault Tolerance
Learning Objective
◾ describe VMware vSphere 6 data protection and fault tolerance features
1. Describing the features

Now data protection is another feature allowed to us by standard licensing. What this allows us
to do is protect the data located on our virtual machines – our application data or our guest OS
data, anything that we really need to protect. Now there are some really important things I want
you to remember here. First off, this is the basic version that comes with standard licensing. It
is installed as a virtual application but the support is with the basic version. If you want
advanced data protection, that is a separate purchase. You're going to have to purchase that
outside of your standard licensing. It's its own license; it's its own product. That's when you're
using advanced data protection that's for file-level recovery of a SQL databases and things like
that. That's very advanced recovery. Data protection itself – the standard version – is good for
backing up OSs and virtual machines in an agentless manner meaning I don't have to install
some type of backup agent on my virtual machine or application. This is done automatically
through that virtual application I was telling you about. And through vCenter Server, they work
together.
[VMware vSphere Data Protection is integrated with the vCenter Server. Back up jobs can be
centrally managed on deduplicated storage targets. This is installed as a vApp. Some of the
features of Data Protection includes management through the web client, dedupe done
automatically, fast and efficient back up process, no agents on virtual machines. Basic version
is included with licensing. Advanced Data Protection can be added at additional cost adding
even more features.]
This also – that vApp, that data protection vApp that you roll out – is managed through your
web client through vCenter Server. So again, vCenter Server really required to use this
particular feature. So make sure you know that you're going to need that as well. The basic
version, like I said, is included with standard licensing and above. If you want something a little
bit more – a little more horsepower for recovery, file-level restoration – you need to use
advanced data protection. Fault tolerance is a feature of vSphere standard licensing and
above. Now fault tolerance is basically running a virtual machine in lock step on two separate
hosts. Now why would we want to do that? Well, this copy of that virtual machine on that
secondary host is our backup. If anything happens to that primary virtual machine, that
secondary virtual machine takes over that quick.
[Fault tolerance is a redundancy technology for virtual machines. A mirrored copy of the VM is
running on a secondary host. This runs in lock step with the original VM on the primary host. It
there is any failure, the secondary VM takes over immediately. The features of fault tolerance
includes automatic failover, lossless backup, no downtime, and increase in limitations on
processors.]
So, if I ever have this host right here fail – that host fails, it goes down – this secondary virtual
machine right here, that one takes over and my end users or my customers never know the
difference. Now I know what some of you guys are saying, that's perfect. That's exactly what I
need in my environment. Let's do that right now. Well there are some limitations to fault
tolerance. First off, it's pretty resource intensive both on your network and on your host itself.
Remember, any changes made to the primary virtual machine have to take place on our
secondary virtual machine too in real time. That's a lot of traffic balancing back and forth
across your network. We also have a limitation on processors. Now in the old days – you know
5.0, 5.1, 5.5 – fault tolerance had a limitation of one processor.
And that was the biggest drawback. I saw a lot of students really jumping and say, "Oh! Fault
tolerance is really what I need." And then we talked about the one processor limitation then
and there. They were like, well that's useless to me now. Why did we even talk about that at
that point? But really exciting news – in 6.0 and above, they have increased the limitations on
processors. Right now as of the current release, it's four. We can have four processors on that
virtual machine. So that virtual machine can have four processors now and still be fault
tolerance compliant. So that is really cool and really easy to set up as well. Let me jump out to
the environment here. And you can see I'll grab this Extras right here. I'll right-click, go to All
vCenter Actions, and it's right there. That's all I have to do to Turn On Fault Tolerance. So a
really simple implementation here. There is...it's not super hard to do. I don't have to go to the
CLI or anything crazy. I can be very, very easy in rolling this out. It's an easy process.
[The web client interface is displayed. The page is divided into three sections. To the left,
localhost is displayed; to the right, recent tasks are displayed; and in the middle, the actions
that can be performed are displayed. From the localhost section, the presenter right clicks
Extras option. A flyout appears. He clicks on All vCenter Actions and another flyout appears.
He selects Fault Tolerance and clicks on Turn On Fault Tolerance.]
vShield Endpoint, Replication, and Hot Add
Learning Objective
◾ describe the vShield Endpoint, replication, and hot add features of VMware vSphere
6
1. Features of VMware vSphere 6

Standard licensing will support vShield Endpoint. Now vShield Endpoint is the security solution
for VMware. This allows us overall management of our security environment from our web
client. So our web client has access to all those virtual machines and we can do our security
management from there. Now this allows for management without installed agents on that
particular virtual machine. I don't need to install on every single application or every single
virtual machine, the vShield Endpoint product that...don't need to do that. It's centrally
managed. So this allows me to put forth a database that is always patched to what I want it to
be and I can push that out when I need it to be. So vShield Endpoint – also a standard
licensing feature and above. vSphere Replication is supported on standard licensing and
above. Now we use vSphere Replication to back up different virtual machines in our
environment to a different location. We're kind of keeping those on tap if anything happens to
our existing running virtual machines.
[vShield Endpoint processes anti-virus and anti-malware agent processing to a virtual

appliance. A hypervisor module and vApp from supported antivirus vendor. vShield is always
online for latest updates. VM is immediately protected with latest definitions when created or
powered on. It is scanned externally from host. There is no need for agent installation on VM.
A single component of an overall solution is provide by VMware. Other components are
licensed separately.]
Now they can be restored at anytime using the vSphere Web Client or some type of system-
wide restore thing like Site Recovery Manager. This provides us protection all the time. Many
of you guys need some type of solution like this because of the regulations in your
organization. So, if you're looking for this type of backup, you need at least standard licensing.
The free licensing is not going to work here. So make sure you understand what your
organization needs. There are some really cool things here. It does not require a separate
application agent to be installed. You don't have to install vSphere Replication on a virtual
machine by virtual machine basis. And you can choose the backups in time or how often you
want to keep those backups. So a lot of control here of the replication process through this
particular feature.
[vSphere Replication allows you to protect a virtual machine by backing it up to a different

location. The backup can then be restored from the vSphere Web Client or a site-wide system
solution such as vCenter Site Recovery Manager. This provides ongoing protection. Only
changes are made to the VM are backed up. vSphere Replication is managed through vCenter
Server Web Client. It works with Microsoft Volume Shadow Copy Service. No application
agents are required to be installed. The backups can be chosen in time.]
One of our main limitations in our physical environment was the hardware itself. When I rolled
out a server and I put a certain amount of CPUs in there, I was stuck with that amount of CPUs
unless I turned off that hardware and then brought it out of service, opened it up, and added a
newer CPU or another socket...another CPU in the socket if I have one available. That is no
longer the case in virtualization. Virtualization allows me to Hot Add hardware into my virtual
machine. Yeah, I just said that. We can really do that. I can take my virtual machine and add
CPU resources to it. I'm not stuck with what I originally created. Now there are some things I
had to enable that virtual machine for Hot Add when I created it. But once I've done that, I can
make changes on the fly to a running virtual machine CPU resources, RAM resources, the
hard drive space. I can even add multiple hard drives in a running environment.
[vSphere offers the ability to change virtual machines on the fly. Allowing you to change
specifications of a particular virtual machine while the machine is running. Some of the things
you can change are CPU resources, RAM, and HD space. This also lowers the amount of
downtime you need for a hardware upgrade compared to a physical server.]
So I could add two more hard drives. As long as I have the VMware Tools installed for guest
operating system, the guest operating systems will even see those hard drives when I've
added them. It's really, really a great feature. It's really a great feature for virtual machines.
They grow over time. So RAM especially...as you see RAM utilization increase slowly over
time, you can use Hot Add to add additional memory without shutting down the virtual machine
at all. The end users will never lose that connectivity to that virtual machine just because you
had to make a performance adjustment on the hardware side. So a really interesting and cool
feature that is available for standard licensing and above.

Enterprise Licensing Feature Set
Learning Objective
◾ recognize the enhancements offered by the enterprise licensing for VMware
vSphere 6
1. Recognizing the enhancements

So our next licensing level up from vSphere standard licensing is vSphere enterprise licensing.
Now enterprise licensing adds a little bit more to our feature list. We have things like Reliable
Memory and Big Data Extensions and DRS and DPM, really cool features if you have that
particular licensing standard. Now...from standard, we're going up to enterprise. Of course, the
costs are going to scale with that. Even the supports and services scale with that. And again,
like we saw with the standard license set, anytime you see these distributed or shared
services, we need vCenter Server in order to manage that. So that's an additional licensing
cost for the vCenter Server itself.
[Enterprise represents the next tier in featured available from vSphere. All the features of
standard plus is included. Some of the added features in VMware vSphere Enterprise are
reliable memory, big data extentions, distributed resource scheduler, distributed power
management, storage, and multipathing.]
Reliable Memory and Big Data
Learning Objective
◾ describe VMware vSphere 6 technologies for working with big data
1. VMware vSphere 6 technologies

The first big technology boost we get by enterprise licensing is what is known as reliable
memory. Now reliable memory is a hardware vendor feature. So you're going to buy a stick of
RAM that so...that is reliable memory enabled. And what this means is we're going to have that
feature at the hardware level and then our ESXi hypervisor will support that as well. Now we
do require that we have enterprise licensing in order to support this feature. Now why is this
feature important? Well, our hypervisor basically resides in RAM and the more reliable our
RAM is, the more reliable our hypervisor is. So usually it isn't a big problem. But when we're
talking about large enterprises where downtime is the plague basically, we want to avoid it at
all cost. This feature comes in handy. Because reliable memory has a better memory address
management for our CPU and RAM.
[ESXi supports the use of reliable memory, which is a hardware vendor feature. ESXi resides
in RAM. Errors in memory can lead to serious problems like crashing of VMware or ESXi host.
Reliable memory is a CPU feature that ranks memory address space that is more reliable.
Using this feature, ESXi will be placed in memory that is more reliable providing for greater
stability.]
And this basically gives us a more reliable, greater...more stable environment. We can
definitely have an environment that has less downtime. We see less errors in our RAM to CPU
communication. And what does this help us with? Well, our virtual machines will be up longer,
ESXi – less errors. So reliable memory is one of those technologies that you can really see
becomes important when we move from a small environment. When we're starting to move
towards those medium and large size environments, you have over a 100 hosts. You have
over 200, 300, 400 virtual machines. So you really need stability at that point and reliable
memory really provides that. Now those of you in really large environments know what big data
extensions is all about. We're basically talking about a Hadoop cluster. Now what is Hadoop
for those of you in small environments? Well, Hadoop is a way of managing large amount of
information that's not stored in a database.
[Big Data Extentions allows for the management of Hadoop clusters from vCenter Server.
Hadoop cluster is a specially designed cluster for storing and analyzing large amounts of data
not in a database. This is used in a distributed computing environment. It is an open source
software from Apache.]
We see this a lot in cluster computing or cluster computing applications that create a large
amount of data. Let's talk about the human genome. If I was mapping the human genome,
create a lot of data, this doesn't necessarily fit well into a SQL database. That's a lot of
TECGNA to go into a database; there is not a lot to sort by or find by in that case. Well, big
data extensions really helps us out. There is a different way to manage that information. This is
an open source program - the Hadoop clusters are. And as we've talked about, this requires an
enterprise license or an enterprise plus license in order to be supported in your VMware ESXi
environment. Now this open source application can be...I've seen it done by Intel, IBM. A
couple other people have their own versions of this because it is open source. You can change
it around and push it out there. But any big data extension implementation is usually supported
by VMware. Make sure you look at your vendor. Make sure that, you know, there is no conflicts
there. But big data extensions in general are supported at this enterprise license level. Really,
really cool feature if you have any type of cluster computing going on in your environment.

Distributed Resource Scheduler and Power
Management
Learning Objective
◾ describe the distributed resource scheduler and power management features of
VMware vSphere 6
1. Explaining the features

The next big feature of an enterprise license is Distributed Resource Scheduler. Now this
feature allows me to move virtual machines around between hosts in the case that there is a
resource drag or a resource run on any particular host. So, if I had a host out here – right here
on the left and I, let's say, had a run on CPU utilization, I could have DRS set up to actually
move a virtual machine over to another host. Now this process would be automated and I can
set the levels by which to do this. I can say, "Let's be really aggressive about this." Why
if...there is any performance gain to be had, let's move that virtual machine off that host and
let's move it over to host 2, so we can see a greater balance of resource utilization.
[VMware's DRS is used to maintain a balance of hardware resource load across multiple hosts
within a resource cluster. DRS has the ability to prioritize resources for virtual machines and
vApps with greater need. It can be automated to maintain a balance during peaks and lulls.
Another feature of DRS is that server can be maintained with zero downtime. When used in
conjunction with distributed power management, DRS can be used to lower energy expenses.]
Now there are some issues with that that we get into as we get more and more into this
course. But make sure that you understand DRS at the enterprise and enterprise-plus level of
licensing is a really good implementation to, really, manage the load of our resources. We can
move virtual machines over to host that have been underutilized. And in some cases using
Distributed Power Management can be used to save on energy costs. So great feature, again
only in enterprise and enterprise plus. One of the features that work with Distributed Resource
Scheduler is Distributed Power Management. Now Distributed Power Management is used in a
cluster in conjunction with Distributed Resource Scheduler to actually move virtual machines
off of a host that is being underutilized so that we can power down that host in any given time.
This really saves us on energy and cooling costs. Because let's imagine...let's take a look right
down here. Let's take a look, I have three hosts down here, okay. And one of these hosts is
definitely underutilized. Let's say the host on the far right. This host right here – greatly
underutilized.
[VMware's DPM allows a cluster to automatically turn on or off hosts as needed for resources.
Heavy resource utilization occurs when extra hosts are turned on and VM's are load balanced
to the hosts that have been added. Low resource utilization occurs when hosts are shut down
and VM's are moved to the remaining hosts within the cluster. This saves energy and cooling
costs. DOM is used in conjunction with DRS to maintain balance among existing or added
hosts. The hardware must support wake on LAN.]
What is going to happen with Distributed Power Management is we are going to have virtual
machines that – let's say, there were virtual machines on here, couple of virtual machines on
there...we're going to have virtual machines we're actually going to fairy them off. They're all
going to be moved over onto these other hosts. Now what is the purpose of that? What does
that accomplish when I move these different hosts onto host 1 and 2? Well, I have the ability
now to power this down. I can power down that entire host – that big physical box of resources
that are running right now, I can power that down. And my energy costs immediately drop. Also
I don't have to put as much energy into cooling that area because that host is now offline. Now
I know what you're thinking. What if your resource utilization starts going up? What if
everything starts turning back on? What if this virtual machine right here, or ask, what if that
virtual machine requires a ton more CPU utilization, a ton more of RAM?
Well, what happens is the opposite. DPM will now take virtual machines from these two hosts
and move them back on here. This host will be powered back on. So this host would be
powered back on and all these virtual machines instead of going this way would end up going
this way, back on to our host. So incredibly cool technology. It does require that you have
wake-on-LAN capability for your net card. But, if you are trying to save energy costs, if you're
trying to save cooling costs – really awesome function. And again, this requires our enterprise
and enterprise plus license in order to implement that. Because you have to have a cluster and
it has to use DRS, works with DRS together in a cooperative mode in order to provide the full
feature of Distributed Power Management.

Storage APIs and Multipathing
Learning Objective
◾ describe the storage APIs and multipathing feature of VMware vSphere 6
1. Storage APIs and multipathing feature

The vSphere storage API is VMware solution to application programming interfaces. This is
available at the enterprise and enterprise plus level of licensing – that's where you get the
support for this. And there are several versions of this you can use. You can use VAAI, which
is basically taking some of the processing that needs to take place on our ESXi host for our
storage communication and dumping that off to our storage processors that's giving us a little
bit more resources to play with on our ESXi host. We also have VASA, which helps with
storage awareness. We have our vCenter Server communicating with our storage device as if
they were the same piece of equipment. So really cool there. We also can use APIs as
multipath to help us with multipathing. We can use third-party multipathing algorithms and
different algorithms than what are included in our ESXi host. We can also have data protection
API, so a lot of functionality with these storage APIs – kind of an advanced implementation. A
lot of the larger organizations, kind of, implement these. You don't see it so such at the
medium and small business level. But really, really cool features that you can pull off here.
[vSphere Storage API is VMware's Application Programming Interface. APIs allow multiple
components to share information and even interact with one another. The different versions of
APIs are Array Integration, storage awareness, multi-pathing, and data protection. The Array
Integration or VAAI offloads storage processes for performance gains. In Storage awareness,
API's can be leveraged to share information with vCenter Server for a more seamless
environment. Multi-pathing uses third party multipath software features. Data protection uses
backup software without overhead and downtime in virtual machine, which is available for all
licenses.]
Enterprise Plus Feature Set
Learning Objective
◾ describe the VMware vSphere 6 enterprise plus license feature set
1. Describing enterprise plus feature set

Our last tier of licensing, the very highest we can get up is enterprise plus. This is the best they
have to offer. It has all the bells and whistles. Everything that's included in the enterprise and
the standard licensing is indeed included in enterprise plus licensing. Plus, there are some new
bells and whistles they added. We have application level HA; we have storage DRS and
profile-driven storage; we have storage and network input/output control; single root
input/output virtualization; we have flash read cache. We have distributed virtual switching on –
this is a really cool feature. This is something that really adds to the networking functionality of
virtualization. And, if you really want to see that, look at our distributed virtual switching video
in our networking – it's really, really cool stuff. We also have host profiles that is an exceptional
technology and auto deploy, which lets us have a centralized sever that can be our depot for
all our ESXi images. So let's jump into this and explain more about all of these technologies.
[VMware vSphere Enterprise Plus is the top tier of licensing offered. It includes all the features
of standard and enterprise. Additional features include App HA, Storage DRS and profile-
Driven Storage, Storage and network input-output control, Single root input-output
virtualization, Flash Read Cache, Distributed Virtual Switching, Host profiles, and Auto
Deploy.]
First up is VMware's app HA. Now we talked about high availability in our standard licensing.
Well, here at the enterprise plus level, we not only get HA – the regular version – we get a
much more detailed version. This is at the application layer. The regular HA was...you know, if
our host went down or there was some type of failure with our virtual machine, we were going
to start up on another host. Now we have much more granular control. We can actually monitor
the application itself. So, if the application is having trouble – even if the guest OS on the
virtual machine is not – the guest OS on the virtual machine is running fine. The application
itself is floundering or flapping on our network or having real issues that now can be restarted
on some other hosts. Now this again maintains our uptime – that 99.9%, that golden standard
– that's what we use here. This is what we use to help maintain that – that VMware's
Application HA. So we're looking at a much more granular level, we're looking through the
microscope, if you will.
[VMware's App HA is an application level implementation of high availability features. It

monitors applications through installed appliance. It restarts application or VMware. It is
managed with vCenter Server. It also helps protecting high uptime application requirements.]
Now at the enterprise level, we had DRS; at the enterprise plus level, we have storage DRS.
Now storage DRS works the same way as DRS did. DRS – we had virtual machines moving
around to different hosts to balance the load of resources. So we had about the same resource
utilization across a cluster of hosts. We can do the same thing now with enterprise plus but at
the storage level. We're going to have multiple data stores in a cluster that storage DRS will
manage the utilization for. We will make sure that our reads and writes are at a certain
threshold. If they are not, we're going to take virtual machines and move them to other data
stores in the cluster to maintain that balance. We are also going to make sure that our space is
about the same, if you're going to use that metric or maybe even latency between hosts and
data store appliances – our data appliances. So really cool feature. It allows for a continuous
monitoring of that performance of our storage appliances.
[vSphere's Storage DRS is a load balancing technology that helps distribute storage
input/output and space utilization to maximize efficiency within your storage solution. It
monitors continuously and no application downtime during maintenance. Profile-driven storage
lets you optimize and automate storage provisioning. It helps in managing VM placement, data
clustering and VASA.]
Now our profile-driven storage that is really, really interesting. This allows us to place virtual
machines on certain data stores and either keep them together or apart. So, if I have a
virtual...two virtual machines – let's call them virtual machine 1 and virtual machine 2 – let's
say both of these are high read/write virtual machines. Now I obviously don't want these high
read/write virtual machines to land on my same line or target because I could overwhelm it. So
I could set up rules to keep these virtual machines on separate data stores. I can create rule
that says, this virtual machine on the left, this goes to data store 1 always; this virtual machine
on the right, this goes to data store 2 always; or I could simply say that this virtual machine 1
and virtual machine 2 can never be on the same data store. We can keep them apart. So really
cool features here for enterprise plus that allow us a much more granular control of what is
happening at our storage level.
Now in enterprise plus, there is granular control of your storage. Well, here there is even more
granular control of our storage. When we talk about storage input/output control, we allow
administrator's complete control of what is going on between our hosts, our virtual machines,
and our storage appliances. Now we can use shared storage here and we can set limits on a
virtual machine level or on a host level. And it says, which host has priority over which host?
Or which virtual machine has priority to the data store over another virtual machine? So a lot of
control of who has access to the performance of a particular data store or storage appliance in
your environment. And again, this happens at the enterprise plus level. You can't do this at the
enterprise or the standard level. You need enterprise plus licensing for this fine of control of the
communication between your host and your data store.
[vSphere's Storage I/O Control allows an administrator to define I/O prioritization across hosts
and VMs. It uses shared datastore and balances storage performance or sets limits per VM.]
Flash read cache is used to keep our performance at very high levels. Now we are constantly
reading and writing from storage and that may be an issue going over our network. Sometimes
that doesn't have the speed we need. Flash read cache utilizes a solid-state disk drive that's
already stored on that host. So you have a physical server that has ESXi installed. That
physical server might have some type of card installed on it or a solid-state disk drive that we
can use for that flash read cache. This really helps with our DRS and our vMotion. It really
helps performance because we can kind of cache that information on our fast solid-state disks
when the reads and writes get too much for our network to handle. So really cool feature.
Again, we can only use this at the enterprise plus level. But this is a pure performance feature
really, really utilized in large environments.
[Flash read cache uses host flash to reduce application latency. The virtual machine is
unaware of this process. This cache is often a PCIe card, or SSD that has been installed on
the physical server. This improves vMotion and works with DRS.]
vSphere 6.0 Additional Enterprise Plus
Features
Learning Objective
◾ describe additional features enabled by enterprise plus licensing in VMware vSphere
6
1. Additional features enabled

Enterprise plus provides us with the virtual distributed switch. Now this is a lot different than
our standard switch provided to us in the enterprise and standard licensing. We have a lot
more features here. Now this is a centrally located switch, which is a vast difference from the
standard switch. The standard switch is located on the host itself. So a standard switch resides
right here, right there, on the host. A virtual distributed switch though resides on vCenter
Server. If you look up here at the slide, you'll see that that actually exists here on our vCenter
Server, that is where it's managed and any configuration changes flow out from the vCenter
Server out to those hosts through a communication channel. That is a really big difference
from the standard switch – our standard switch. We had to configure each host manually so
every single one of these hosts, I had to make sure that that all matched. I had to create every
port group manually.
[The VDS is located on your vCenter Server. Multiple hosts may connect to the vDistributed
Switch, and share the same configurations. The switch provides enhanced capabilities over
the standard switch like SNMP, templates, netflow, LACP, Centralized port configuration,
Input/Output control and traffic Shaping, BPDU filter, and PVLANs.]
If you want more information on that, look at our networking video – our VMware networking
video – where I go into this in detail. But our distributed switch – that's a different story – that's
centrally managed. I don't have to do each port configuration. I don't have to do that up three
separate times like I would, if we had a topology that matched this slide. So really cool feature.
And that's not all we have. We have SNP support...SNMP support, we have support for
templates at the networking level. We can also implement NetFlow and LACP. Now I know
some of you guys, that's not a big deal. These are virtual switches, these aren't physical
switches. These are virtual switches created on our vCenter Server that can, actually now,
share information through LACP and track our network information, what is actually flowing
across that virtual switch. So that's a big deal. Like I said, we can manage from a central
location, we have BPDU filters, we even have private VLANs.
Now that's a really advanced networking technology that we now have control over in our
virtual environment, if we want it. And all this is with the virtual distributed switch. You need
enterprise licensing to get it, but once you do, you get a lot of stuff with it. Enterprise plus has a
feature available known as host profile. Now host profile allows us to create a golden image
kind of like the golden ticket. But the golden image allows us to take a configuration of a
particular host. Let's take this host right here. And let's make that the configuration by which
other hosts are held too. That's the standard; that's the configuration I want. Now does it have
to be for all the hosts in my environment? Absolutely not. I can pick and choose. So let's say I
only want hosts three, four, and five to maintain that golden image. I can definitely do that. And
what I do is I attach these to this host. I say this host is attached, this host is attached, and this
host is attached. Now anytime, there is a configuration change or anything that happens in my
environment, every now and then, I can check these different hosts to make sure that they are
actually in compliance.
[Host profiles allows you to keep configuration consistency between multiple hosts. Allows you
to remediate any host that has a configuration outside of desired profile. It allows to create a
"golden profile" which other hosts are checked against. Configuration errors or problems can
easily be fixed through profile remediation.]
Do they match the configuration of my golden image? And, if they don't, I can remediate. I can
take this golden image, right here, and push it out to every single host and bring them back to
the original configuration that I wanted. So interesting feature to say the least for enterprise
plus. Again, we can't get this at the enterprise or standard level. But, if you have enterprise
plus licensing, worth taking a look at. If you have to roll out a lot of hosts in a very short amount
of time, you may look into AutoDeploy. Now AutoDeploy is an enterprise plus licensing feature
that allows us to utilize a centrally located depot of our images, our ESXi Hypervisor images,
whether that would be 5.5 or 6.0. This is a centrally located depot that are hosts when they
boot up, our physical boxes when they boot up, are actually going to look for an operating
system. And they're going to look to our network; they're going to look for that central depot. If
they find it, they're able to pull those images in using AutoDeploy.
[Rapid host deployment through network boot options. One Auto Deploy server that installs
ESXi into host memory. Configuration can be quickly accomplished using host profiles. This is
a fully automated process.]
So very, very cool function. If you have to roll out 10, 15 hosts at any given time, you don't
want to be carrying a disk around. So, if you need to roll out multiple hosts quickly, I highly
recommend you look into AutoDeploy. Either that or really good pair of sneakers. One of the
cool new features in 6.0 is the ability to take a PCIe device and break that up on the server
through the hypervisor and allow different virtual machines to access it. So, if I had a video
card that I have placed into that server, multiple virtual machines may access that now to
multiple virtual machines. Now this was not the case in previous versions, but now in 6.0 we're
able to do that. This can be for processing or networking. We have the ability to take a single
root input/output device and then allow multiple virtual machines access. Again, this is an
enterprise plus licensing feature. So make sure that if you have any application that requires
this, you're going to have to go to your manager and ask for a little bump up in licensing, if you
are at the standard or enterprise level.
[Allows a PCIe device to be abstracted to multiple virtual machines. This makes offloading
workloads to the PCIe hardware device possible for networking and processing.]
Essentials Kits
Learning Objective
◾ describe the features enabled in VMware vSphere 6 with the essentials kit licenses
1. Features of essentials kit licenses

Now we talked about vSphere standard, enterprise, and enterprise plus licensing. Those are
the regular licenses we have. Now out in the fringe a little bit, out here in right...left field, we
have our essentials kit. Now an essentials kit is a very, very small environment. This is in a
restrictive environment. There...to grow out of an essentials kit takes a lot of planning because
it's a very restrictive license. We only have a certain number of hosts supported. We only have
a certain number of virtual machines supported. If we have vCenter Server included in our
essentials kit, it can only manage the licenses within that essentials kit. So this is a very, very
restrictive licensing set. Now what is this good for? Well, it's good for small environments or lab
environments or environments like a branch office where you need an administrator there on-
site with access to couple of the hosts. So very limited in scope – not scalable at all. Make sure
you understand that. If you purchase this, you're planning on not really growing out of it
because you're going to need to purchase regular licenses to grow out of it. And the process of
moving out is pretty arduous.
[Size is limited for the implementation of VMware. It is designed for small office deployment or
sandbox implementation. Features can differ depending on licensing level. It does not follow
standard licensing model. This is an incredibly restrictive licensing feature set. A table is
displayed with 3 headers that is Product, Essentials, and Essentials "+". The product is feature,
whose essential is vSphere and essential "+" are vSphere, vMotion, high availability, data
protection, vShield Endpoint, and vSphere Replication.]
So, if you are going this route, at least keep in the back of your mind that this is really a small
environment and not going to be growing out of this; very, very restrictive. What other left-field
licensing options are out there? Well we have an acceleration kit. Now an acceleration kit is a
little different. An acceleration kit...let's see if I can spell this right – Acceleration Kit:
Bundle Licenses. That's right, it's a bundle of licenses. Now it's a bundle of regular
licenses as well. So, if I bought an acceleration kit of standard licenses, I would get multiple
standard of licenses for four processors, six processors. And that is very scalable because it is
just a regular license. I can at any time go out and purchase other licenses. Also, if it includes
a vCenter Server, I can use that vCenter Server to manage other hosts in my environment. So
an acceleration kit, I think, is a better idea for most growing small and medium companies
because it is much more scalable.

Support and Services
Learning Objective
◾ describe features offered by VMware vSphere 6 support and services licenses
1. Support and services licenses

The last group of licensing that we can purchase or the support we can purchase is for our
support and services agreement. Now there are two main modes for this. Now I do say two
main modes but pricing changes for the enterprise, enterprise plus, and standard licensing
here. And in each of those licensing levels, we have basic and production. So, if I had
enterprise basic support and service agreement, I could call anytime from Monday to Friday
from 6 a.m. to 6 p.m. in any local time in North America. That means, I could have...I can call
anytime I need to, based on that licensing. Now the price for the support and service
agreement scales up for each licensing level. So the standard support and service agreement
for basic is cheaper than the enterprise plus level of basic support and services. This is
because there...enterprise plus is much more complex. Now with the basic support and service
agreement, I can make four technical contacts per year. So I can basically give them a call four
times.
[Two tiers of support are basic and production. Each agreement is minimum one year in
length. There are different target response times based on severity. Access is through
telephone or web, with response by telephone or e-mail.]
Usually, they give you a little more leeway. If it's a small problem, you call them. They fix it over
the phone and usually get you on that one. But when it's a definite, you're spending, you know,
30-45 minutes on the phone with a tech – you know, technician – usually they will tag you for
that one. Now the other end of that coin is the production-level support and services. This is if
you have a really a large environment where uptime super matters. What does that give you?
That gives you 24/7 access and six contacts per year. So you get two more and this gives you
lower response times. You're not going to be dealing on e-mail mostly, you're going to be on
the phone, really, with the technician. On basic, you could end up just working it out on e-mail
in some cases. Production level, no, they're going to be right there in your face and helping
you through the problem. So make sure you are aware of the two levels of agreements here –
the basic and the production. And what you're going to get for your particular organization.

Exercise: Choosing a License and Software
Learning Objective
◾ recognize the license required for a specific product set
1. Exercise overview
Here recognize the license required for a specific product set.
In this exercise, you'll practice selecting an appropriate VMware vSphere 6 license and setup.
This involves identifying the benefits of virtualization to your company, distinguishing between
types of hypervisors, recognizing issues with free licensing of vSphere, identifying
enhancements that are offered by the Enterprise license, and recognizing the features of the
distributed resource scheduler (DRS).
2. vSphere licensing
Question
You want to set up server virtualization in your organization. How might your
company benefit?
Options:
1. High consolidation ratios

2. Efficient use of hardware resources
3. Business continuity and high uptimes
4. Reduced total cost of ownership
5. Central point of management
6. Increased storage space
7. More accessible services
Answer
Option 1: This option is correct. Virtualization allows for server consolidation ratios of
10:1, 20:1 or even higher.
Option 2: This option is correct. Virtualization more fully consumes the hardware
resources of the physical server.
Option 3: This option is correct. Virtualization increase efficiency and maintains
business continuity.
Option 4: This option is correct. Virtualization reduces total cost of ownership in a

server environment.
Option 5: This option is correct. Virtualization provides a central point to manage

hosts and VMs in the environment.
Option 6: This option is incorrect. Increased storage space is not a benefit of

virtualization.
Option 7: This option is incorrect. Virtualization does not lead to more accessible
services.
Correct answer(s):
1. High consolidation ratios

2. Efficient use of hardware resources
3. Business continuity and high uptimes
4. Reduced total cost of ownership
5. Central point of management
Question
The hypervisor is the main component that makes virtualization work. Match each
feature to the types of hypervisor.
Options:
A. Type 1
B. Type 2
Targets:
1. Installed directly to hardware

2. ESXi and HyperV are versions
3. Installed on a guest OS
4. Not used in a production environment
5. Virtual PC is a version
6. Used at enterprise level
Answer
A guest operating system is not required for Type 1 hypervisors.
VMware's version of the Type 1 hypervisor is known as ESXi, while Microsoft's

version is HyperV.
A Type 2 hypervisor exists on a previously installed operating system.
A Type 2 hypervisor is not as powerful as a Type 1 hypervisor.
Microsoft's Virtual PC is a Type 2 version.
Type 1 hypervisors are at enterprise level where there's high utilization of underlying
hardware resources.
Correct answer(s):
Target 1 = Option A
Target 2 = Option A
Target 3 = Option B
Target 4 = Option B
Target 5 = Option B
Target 6 = Option A
Question
You are setting up a lab environment at your company to fully test the software. You
are choosing a license for your ESXi hypervisor. What would deter you from choosing
the free version?
Options:
1. Functionality cannot be fully tested

2. It has none of the centralized management features
3. You can only have a max of 32 GB RAM on a host
4. The license runs out in 60 days
5. It is a large environment
Answer
Option 1: This option is correct. You cannot test out the functionality properly so it's
not useful even at a lab level.
Option 2: This option is correct. You cannot use vCenter server, so this takes out
many of the features from the environment.
Option 3: This option is correct. 32 GB of RAM is a severe limitation if you are

looking at robust enterprise solution.
Option 4: This option is incorrect. It's a free license but with limited functionality.
Option 5: This option is incorrect. The free license is a very small environment.
Correct answer(s):
1. Functionality cannot be fully tested

2. It has none of the centralized management features
3. You can only have a max of 32 GB RAM on a host
Question
You have done your testing and have now opted to go for a vSphere Enterprise
license. Identify some of the enhancements that are offered compared to the Trial or
Standard license.
Options:
1. Reliable memory
2. Big data extensions
3. Distributed Resource Scheduler
4. Distributed Power Management
5. Storage APIs for multipathing
6. High availability
7. vShield Endpoint
Answer
Option 1: This option is correct. Reliable memory is supported in the Enterprise

version of vSphere.
Option 2: This option is correct. Big data extensions means that running big data on
the platform brings increased efficiency.
Option 3: This option is correct. Distributed Resource Scheduler makes load

balancing of workloads easier.
Option 4: This option is correct. Distributed Power Management allows reduced

energy use by placing unused servers on standby.
Option 5: This option is correct. These APIs help regulate I/O path selection in a
host.
Option 6: This option is incorrect. High availability is offered by the Standard license.
Option 7: This option is incorrect. vShield Endpoint is part of the Standard license.
Correct answer(s):
1. Reliable memory
2. Big data extensions
3. Distributed Resource Scheduler
4. Distributed Power Management
5. Storage APIs for multipathing
Question
You have set up your enterprise environment and are now getting to grips with the
various applications. Identify the features of the distributed resource scheduler
(DRS).
Options:
1. Prioritize resources for virtual machines and vApps with greater needs
2. Automate to maintain a balance during peaks and lulls
3. Provides server maintenance with zero downtime
4. Facilitates lower energy expenses
5. Reliable Memory
6. Hardware maintenance with no downtime
Answer
Option 1: This option is correct. If a VM has increased load, DRS will evaluate its
priority against set rules. It will then redistribute VMs among the physical servers, if
required.
Option 2: This option is correct. DRS can be set to automatically maintain a balance
during peaks and lulls.
Option 3: This option is correct. DRS can conduct zero-downtime maintenance of

servers.
Option 4: This option is correct. DRS can lower consumption costs by up to 20%.
Option 5: This option is incorrect. While Reliable Memory is part of the Enterprise
license, it's not a feature of DRS.
Option 6: This option is incorrect. While hardware maintenance with no downtime is

a feature of vMotion, it's not part of the DRS feature list.
Correct answer(s):
1. Prioritize resources for virtual machines and vApps with greater needs
2. Automate to maintain a balance during peaks and lulls
3. Provides server maintenance with zero downtime
4. Facilitates lower energy expenses
© 2018 Skillsoft Ireland Limited

IBM VM Wrae 1

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IBM VM Wrae 1

Загружено:

Авторское право:

Доступные форматы

Course Transcript

VMware vSphere 6 Install, Configure, Manage

5. Business Continuity and High Uptimes

6. Reduced TCO and Central Management

2. Hosts and VMs

2. Standard License Feature Set

5. Data Protection and Fault Tolerance

6. vShield Endpoint, Replication, and Hot Add

7. Enterprise Licensing Feature Set

3. Storage APIs and Multipathing

4. Enterprise Plus Feature Set

5. vSphere 6.0 Additional Enterprise Plus Features

7. Support and Services

Practice: Selecting a vSphere Setup

1. Introduction to the course

1. Problems with physical servers

[The presenter continues to explain the same example.]

1. Benefits of using server virtualization

[The presenter continues to explain the same example.]

1. Describing resource utilization

[The presenter continues to explain the same text.]

1. Benefits of using VMware vSphere 6

[The presenter continues to explain the same text.]

1. TCO and centralized management benefits

[The presenter continues to explain the same text.]

One of the greatest benefits to virtualization is centralized management. I can manage my

[The presenter continues to explain the same text.]

[The presenter continues to explain the same text.]

1. Describing hosts and VMs

[The presenter continues to explain the same text.]

[A virtual machine is a defined box of resources served to a guest operating system.

1. Features and versioning of host client

[The presenter continues to explain the same text.]

1. Features and functionality

[The presenter continues to explain the same text.]

[The presenter continues to explain the same text.]

1. Managing with the Web client

[The presenter continues to explain the same text.]

1. ESXi licensing functionality

[The presenter continues to explain the same text.]

1. Matching with functionalities

[The presenter continues to explain the same text.]

1. Describing vMotion licensing

[Storage vMotion manages storage utilization live.]

[The presenter continues to explain the same text.]

1. Uptime and high availability features

[The presenter continues to explain the same text.]

[The presenter continues to explain the same text.]

[The presenter continues to explain the same text.]

1. Describing the features

[The presenter continues to explain the same text.]

1. Features of VMware vSphere 6

[vShield Endpoint processes anti-virus and anti-malware agent processing to a virtual

[vSphere Replication allows you to protect a virtual machine by backing it up to a different

[The presenter continues to explain the same text.]

1. Recognizing the enhancements

1. VMware vSphere 6 technologies

[The presenter continues to explain the same text.]

1. Explaining the features

[The presenter continues to explain the same text.]

[The presenter continues to explain the same text.]

1. Storage APIs and multipathing feature

1. Describing enterprise plus feature set