Lab 19 Part 2 - High Availability Functionality of vSphere Lab (part 2)
Video Activity
High Availability Functionality of vSphere Lab (part 2) This lesson continues working with the high availability functionality of vSphere. In this lab-based class, participants learn step by step instructions in how to examine source allocations, which is very useful when removing hosts from a cluster or rebooting a virtual machine. Participants al...
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Difficulty
Intermediate
Video Description
High Availability Functionality of vSphere Lab (part 2) This lesson continues working with the high availability functionality of vSphere. In this lab-based class, participants learn step by step instructions in how to examine source allocations, which is very useful when removing hosts from a cluster or rebooting a virtual machine. Participants also learn how to change the CPU reservations for the Win7 clone.
Video Transcription
00:04
Okay, so now I want to look at my resource allocation tab,
00:12
and I can see that if I've got this cluster selected,
00:16
it shows me my total capacity of memory, my total capacity for our CPU and memory,
00:23
how much I've gotten reserved for CPU and memory
00:27
and then the total
00:28
amount available.
00:30
So some good good staff to keep an eye on
00:33
when you're
00:35
removing hosts from a cluster or rebooting one.
00:39
So my total capacity for the cluster, then for processor
00:43
his 11 3 61
00:45
or 11.3 gigahertz, 2.8 gigahertz for the capacity
00:51
reserved and then 8.5 for the available capacity.
00:57
If we can look in our virtual machines tab,
01:00
we can see at a relative basis how much memory and
01:04
processor is being consumed by each of the virtual machine.
01:08
***, too, is a virtual host,
01:11
so it it consumes a fair amount of memory on the real host as well as a lot of its CPU.
01:19
But V Center,
01:21
the center server appliance in this case,
01:23
is the most active VM fires memory requirements.
01:29
So we've got some nice stats to look at here
01:33
and what we can do is, um,
01:36
look at the summary of each of'em individually. If we want to get more detail
01:41
on what it's resource usage actually is.
01:57
So for a, um, host
02:00
with a virtual host added as a cluster, we get pretty decent performance.
02:05
We can look at the performance tab for the cluster itself
02:08
and see how the aggregate resource is. Our are doing
02:13
the next task that we have to,
02:15
uh, have a look at them
02:19
would be how to look at the H A slot size.
02:23
Okay, so let's look at our cluster
02:27
more right click and go to at its settings.
02:35
We already have the name picked and we've
02:38
turned on a J. So let's go to the age a section
02:43
We've got our checkbox for host monitoring, which uses that heart heartbeat data store, the NFS datastore.
02:51
We can see now that the reboot of the host has completed, it's finally finished.
03:00
So our mission control
03:04
we have the two either enable or disable this.
03:07
So this tries to set aside he
03:10
a reservation of custard capacity
03:14
to do fail overs of the virtual machines. So when one host goes down,
03:19
the other host,
03:21
um,
03:22
should be able to have the capacity to
03:24
absorbed wth e v ems, that air moving over to it
03:30
so we'll make sure this is selected.
03:34
The number of host failures that the cluster can tolerate is exactly one. We've only got a two note cluster.
03:38
If we had a three note cluster than we could change this to to
03:42
so we can't tolerate to know it's potentially failing.
03:45
In this case, with a simple cluster of just two, we can only tolerate a failure of one of those hosts,
03:52
so we want to make sure that was changed. We'll go ahead and click, okay,
03:57
we'll go back to our summary tab,
04:00
and the link we want to click now is the advanced runtime info for the cluster,
04:04
so this can show us
04:06
various parameters, such as our slot size.
04:11
We can see that
04:13
this lot sizes 32 megahertz,
04:15
73 megabytes of memory, one virtual CPO. That's that's what it's defined as right now. And the size of a slot effectively determines how many virtual machines you can run on the cluster,
04:29
although unless you've got it very finely tuned, one slot does not necessarily equal one of'em,
04:35
so it's here. We've got 138 slots total.
04:39
Five are being used, 12 are available.
04:42
And then we have 100 21 as fail Owers.
04:48
Well, go ahead and close that.
04:51
Now we're gonna change the CPU reservation for
04:57
the wind seven clone.
04:59
Now, I want to be able to, uh,
05:03
move this this virtual machine back to the host E. It was original living. I can see it's still here
05:11
and that host
05:12
100 doesn't have any running. PM's
05:21
all right. So I want to just change the host,
05:27
move it back to 0.200
05:29
validation succeed session and any problems moving it back,
05:32
I'll make it a high priority
05:34
and we click finish,
05:36
so this should run fairly quickly.
05:41
I'll go back to 0.200
05:43
and we should see that that virtual machine pop up here in just a moment.
05:46
Of'em still running.
05:50
Okay, so I'm getting a message saying that this
05:54
host is not support
05:56
running long mode guests.
06:00
Once in a while, you see a message like this. This one
06:02
is just particular to my configuration.
06:05
So what I'm going to do is power the VM down
06:12
and that way I can
06:15
move, move the virtual machine once it's powered off. And I shouldn't have any problems
06:21
and your production environment,
06:23
you would need to, uh,
06:26
Makesem make some adjustments. Make sure you've got actual virtual host. Sometimes there are
06:30
problems and you try to simulate a lab with virtual host. So keep that in mind,
06:36
but we'll come back in just a moment when all this has been moved over.
06:40
It's gonna take a couple minutes.
06:44
Okay, so when seven clone to is now
06:46
been powered off,
06:48
I'll go ahead and close that counsel
06:53
enough. I migrated
06:55
to the other host.
06:57
Should go very quickly and easily.
07:08
All right, that was pretty fast.
07:10
Now select that host double check. VM is there.
07:14
I can go ahead and power that one back on.
07:21
And now what I want to do is
07:26
a justice lot size
07:28
so I could make it larger. I could make it smaller,
07:30
and that effects the way that the cluster will perform depending on how many V EMS
07:34
are up and running at any given time.
07:36
All right, so let's adjust the CPI reservation
07:42
for the wind. Seven clone
07:44
will right click go to at its settings.
07:49
Then we'll go to the resource is tab.
07:54
And so you can see we have no Reese Reese reservation set for see pure memory. Both are set to zero megahertz, zero megabytes.
08:01
So we're gonna make a reservation for
08:05
memory 512.
08:07
Sorry for CPU to 512 megahertz.
08:11
Well, go ahead and accept that change.
08:18
Now I can see that the VM gets reconfigured,
08:20
but also we get some changes to the cluster itself.
08:26
I go back to the cluster in the inventory and select
08:31
runtime info link.
08:35
I could see that My, my my information has changed.
08:41
Now I've got 512 megahertz as a slot size because I've made that a reservation for the CPU.
08:48
We've talked about what with the reservations. D'oh!
08:52
My mind and memory was 80
08:56
was 81 megabytes per slot,
09:01
But whereas before I had 115 slots. Now I am only 22
09:07
so I've made the slots Maur.
09:09
I've given each lot more Resource is
09:11
so therefore they have less slots available.
09:16
I've only got 16 for fail over and only one available
09:20
with these particular parameters.
09:22
So this just goes to show that you can adjust the slots
09:28
to make them larger or
09:30
are smaller,
09:31
and then actually enforce
09:33
a particular slot size
09:35
more specifically.
09:39
So if I go to my cluster
09:41
and right click
09:43
now, I want to go to edit settings for the cluster.
09:50
I'll go back to V. Sphere A. J,
09:54
and this time,
09:56
in order to put in a advanced option,
09:58
I need to click the Advanced Options button
10:05
and you double click in that little window there. Then you can type in
10:09
something more specific.
10:11
If the option we're going to use as daz dot slot
10:15
CPU
10:18
and
10:20
Megahertz,
10:22
we're gonna pick 300 megahertz.
10:28
Now we're not gonna go into a whole lot of detail about
10:31
all the different available advanced options. That's a topic for another, another video.
10:37
But just
10:39
trust me for now, to know that this particular option
10:43
tells you what
10:45
the
10:46
megahertz of the CPU allocation will be per slot.
10:50
So we'll go ahead and click. Okay,
10:54
click OK again.
10:58
Now let's inspect the advance runtime info to link one more time.
11:05
Now I can see the slot size went from 5 12 done a 300
11:09
memory state roughly the same,
11:11
but Now I have 37 slots in my cluster.
11:15
Whereas before I had 22
11:18
I still got five or six years, depending how many Of'em were running.
11:22
And now, now that I've lowered
11:26
the CPU requirement for your slot, I can actually say I've got four in reserve
11:31
27 available for fail over.
11:37
So by adjusting this up and down, we can see how
11:41
to reallocate the total aggregate resource is available in the given cluster.
11:50
Okay, so our last task
11:54
would be too
11:56
undo some of these settings.
11:58
So first thing we're going to do is get rid of that requirement we just added
12:03
about at its settings for the Cluster
12:05
Select Free Spirit chain.
12:09
Go back to advanced options
12:13
and I can just select this and delete it.
12:18
Select this and delete it.
12:24
I also want to undo my CPU reservation for the Window seven clone.
12:31
So I go back to edit settings here,
12:35
to my resource is tab
12:39
and then for CPU.
12:41
I'm just gonna replace 5 12 with the default which is zero.
12:46
And for kicks, we can go back to the cluster
12:50
and look at the advanced runtime info link one last time
12:54
see how that changed.
12:58
So now I gotta back up. 218 slots for cluster
13:01
noticed the slop size by default is basically 1/10 of what we had sat itude previously.
13:07
It went from 300 megahertz 2 32 megahertz. Which means I've got ninth lots of with this configuration available
13:16
in 104 for fail over.
Up Next
Lab 19 Part 3 - High Availability Functionality of vSphere Lab (part 3)
Lesson 4 - Introduction to Fault Tolerance
Lab 20 - Configuring Fault Tolerance on a Virtual Machine VM (Lab)
Lesson 5 Part 1 - Introduction to Replication
Lesson 5 Part 2 - Single Site Replication
Similar Content
