Lab 19 Part 3 - High Availability Functionality of vSphere Lab (part 3)
Video Activity
High Availability Functionality of vSphere Lab (part 3) 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 work with strict admission control. Strict admission control allows the cluster to only support four slots which allows for tighter...
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 »
Video Description
High Availability Functionality of vSphere Lab (part 3) 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 work with strict admission control. Strict admission control allows the cluster to only support four slots which allows for tighter control in how the cluster treats host failures.
Video Transcription
00:04
Our next task is to work with strict admission control.
00:09
So we're gonna try to
00:11
make sure that the cluster could only support four slots.
00:16
That way we'd have a much tighter control over
00:20
how the
00:21
failures of the host are treated by the cluster.
00:26
So in the in the earlier part of Lad, we were telling
00:29
the high availability configuration to calculate the slot size.
00:34
So then it figured out how much face
00:37
a virtual she needs to run based on the available CPU and memory requirements for all the virtual machines.
00:47
So we have our cluster selected will look a virtual machines, and we're going to shut a couple of machines down.
00:55
We don't need Win seven and
00:59
when seven clone running right now, so we'll shut goes down.
01:11
That's happening. We can see that
01:12
if we go to the resource allocation tab for the cluster,
01:19
we can see that are
01:19
total capacity for CPU memory
01:23
and the capacity we've gotten reserve have changed a little bit.
01:26
Based on those machines being powered down,
01:33
they're not quite finished shutting down,
01:34
but the numbers should be relatively close. So since we only have
01:38
two
01:41
virtual machines in this cluster,
01:42
we can see the available capacity just went up a little bit because when someone's down,
01:49
when seven clones should be almost finished shutting down
01:52
and that might go up a little bit more.
01:59
Okay, looks like it's kind of stabilized here.
02:02
In any case,
02:04
if we had three hosts, we we could divide
02:07
these numbers up by three. But since we've only got two, we'll divide it in half.
02:12
That basically means that I've got,
02:15
um,
02:16
nearly six gigahertz of CPU per host,
02:20
a little over five
02:22
gigabytes of RAM for host,
02:27
so it's pretty evenly split.
02:32
All right, now what we want to do
02:35
is make a memory reservation for each of the two V EMS,
02:39
and we'll pick something nice and easy, like 256 megabytes,
02:46
some going to right click the Windows seven V M.
02:49
Go to edit settings.
02:52
My resource is tab.
02:54
This time we're working with RAM,
02:57
so we'll select memory
02:59
and
03:00
put in to 56
03:05
and then I'll do the same
03:07
for the second
03:09
GM
03:16
Resource is chap again
03:19
memory
03:22
2 56
03:28
All right, so let's go back to your cluster
03:32
and we can look at the summary cab
03:37
advanced runtime influence were doing earlier.
03:39
Let's see how this
03:42
how this looks
03:43
So 138
03:46
total slots
03:46
32 megahertz Each
03:50
tells me how many I've got three use and 14 available
03:54
with 121
03:59
fail over.
04:08
I was power one of these back on.
04:16
It's telling me that insufficient resource is to satisfy the configuration level.
04:23
Oh, you know what? I was supposed to turn this one back. I believe. That's why,
04:31
All right, so get on the host a few moments. Thio, settle down and stabilize after making these changes.
04:39
Now let's see if I can
04:42
power on one of these v abs.
04:48
That's still giving me an error.
04:51
So that means I must have an allocation. It's a little too large
04:55
for this particular set up.
04:58
Let's go to our resource is Tab
05:02
and will change this too
05:09
175 megabytes of RAM.
05:20
Similar. I just change. Sorry
05:23
that to win seven
05:26
settings,
05:31
see if this does the trick.
05:38
Okay, that completed.
05:44
And now the VM is powering up. Let's open up a console.
05:50
So 2 56 megabytes is a little bit too high for my particular set up.
05:55
Based on the other PM's that I have running in my available amount of memory.
06:00
You may run into this problem yourself
06:02
if you can't
06:04
fit enough ram into your host
06:10
so usually a little bit of of ah, fine shooting those memory values.
06:15
Six. The problem.
06:18
So let's look at what our clusters doing. I'll go back to cluster. Summary tab
06:24
advanced one time info.
06:29
So my slot size is 32 megahertz for CPU to 20 meg for RAM,
06:34
and now I've got 45 total slots, whereas before had 138
06:40
only one available.
06:42
So that means that at this particular setting,
06:45
it's it's probable that
06:47
turning on the second VM may fail. Let's see what happens.
06:59
Help that sale.
07:00
Okay, so I've got to adjust the settings even further
07:10
for the purposes of keeping everything moving here. We're gonna go ahead and remove
07:14
the reservation altogether.
07:15
That should fix the problem.
07:27
There we go.
07:30
So it just goes to show that that there is some careful tweaking that needs to happen. Sometimes when you are
07:36
trying to
07:40
get multiple V EMS to run on your host with different types of resource usage profiles
07:49
and now that that VM is a booting. We'll go back and look at our cluster one more time.
07:56
Advance runtime in. So let's see what our slots situation is now.
08:00
So
08:01
it still thinks there are 46 available five and use.
08:05
Basically, I've got no reserve capacity at this point. Zero available slots.
08:11
So if you were in this situation, you'd have to
08:15
either continue to try to re balance
08:18
the reservations that you've made for your virtual machines
08:20
or the better option the long term
08:24
a solution would be to just get
08:26
more RAM for your host.
08:33
Okay,
08:35
so now we're gonna need to do a little bit of cleanup.
08:39
First thing we're going to do is go to the resource allocation
08:43
tab for the cluster.
08:48
We could look at our memory of you
08:52
and we can see we've still got a reservation set.
08:54
Four wins, seven.
08:58
So we're going to undo that reservation.
09:05
So you get to this information a couple different ways I can. Long as I can see the icon, I can right click and at its settings
09:11
in this dialogue, let's me look att, CPU and ram on the same screen.
09:16
So go ahead and reduce that.
09:20
Now you noticed that the reserve capacity for CPU
09:22
and memory adjust itself somewhat after I
09:28
lead it that reservation.
09:33
And the next thing we're going to do is look at the settings with a Cluster
09:41
Select V's very Che.
09:46
And now we're going to disable admission control
09:50
to reverse that change
09:52
and make the cluster Maur bounced from the V star point of view.
09:56
So let it try to keep track of
09:58
how big a things everything this lot should be. And how many of'em can run.
10:03
This gets us set up for the next lab.
10:09
So in the next lab will be working with,
10:11
uh,
10:13
V Sphere fault tolerance.
10:16
All right, see you in lab number 20.
Up Next
Similar Content
