Lab 19 Part 1 - High Availability Functionality of vSphere Lab
Video Activity
High Availability Functionality of vSphere Lab In this lesson, participants work with the high availability functionality of vSphere. In this lab-based lesson, participants will receive step by step instructions in how to create a cluster out of two hosts and then test the high availability functionality. The lesson will also examine resource usage...
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 In this lesson, participants work with the high availability functionality of vSphere. In this lab-based lesson, participants will receive step by step instructions in how to create a cluster out of two hosts and then test the high availability functionality. The lesson will also examine resource usage statistics and try to help participants gain an understanding of what happens when VMs and hosts are added and subtracted from a cluster.
Video Transcription
00:04
hello and welcome to have number 19
00:07
in this lab. We will be working with the high availability functionality of the sphere.
00:14
So we'll be creating a cluster out of two hosts
00:18
and we'll test some of the H A functionality.
00:21
And then we'll look at resource usage statistics
00:25
and
00:26
try to understand a little bit about what happens when you add and subtract V EMS and hosts from a cluster.
00:34
We'll also get to explore the restricted mission control
00:38
and manipulate the slot size. All right, so let's get signed into our environment.
00:48
Still in the V. M. We're
00:50
domain.
00:58
So the first thing that we're gonna have to do is create the cluster itself.
01:04
So very simple to do
01:07
you go to host and clusters where we are right now, or you can do control shift H.
01:12
I feel like those shortcuts.
01:17
Then we select our
01:19
our data center,
01:21
right click
01:22
and select New cluster.
01:29
We're just gonna call this my cluster
01:34
and we have to enable
01:36
high availability. So we'll check this box for H A.
01:41
This means that if a if
01:42
you've got V EMS,
01:46
register to a different hosts in her cluster. If one of those posts go down
01:51
than those V EMS automatically get moved to the other members of the cluster. We're only gonna make a to note cluster.
01:57
So it's pretty obvious where the PM's will be going.
02:02
We're not going to use DRS until a little bit later. We'll do a lab for that.
02:09
Okay, We're gonna leave host monitoring. In effect,
02:14
that means we're using a heartbeat
02:15
across something like an n f s d a store.
02:19
We'll leave the admission control
02:24
check,
02:27
and then we're going to change the policy. However, for mission control
02:31
to be a percentage of the custom resource is
02:35
reserved as fail spare capacity
02:38
feel over spare capacity. Okay,
02:44
the ree strike priority
02:46
and isolation response. We're gonna leave those
02:49
at the default settings
02:53
via monitoring also at the default.
03:00
Then we have
03:02
enhanced the emotion compatibility or e V C settings.
03:07
We're just gonna leave us disabled for now.
03:10
We'll talk more about that later.
03:15
And then for the swap file location will keep it at the same director is the virtual machine, which is
03:20
typically what you'll do.
03:23
And then we'll get our summary screen
03:25
and click finish.
03:29
Okay, so now we have a
03:31
cluster created
03:32
conceding the inventory here, my cluster
03:38
and what I can do is just take a host and drag it to my cluster
03:44
and let it go.
03:46
Now I've got a cluster of one host.
03:49
Okay, so we're gonna go select your cluster
03:53
and we'll go to the summary tab
03:58
and check the cluster status linked.
04:00
You got some other
04:01
parameters here related to H A.
04:06
But right now we're just interested in the cluster status.
04:11
So
04:13
the master host is top 100. It's the only host, so it has to be the master.
04:17
There's no host connected to the master.
04:20
I can see we have four V ems that are being protected by being members of this cluster.
04:26
So Croc's CSX to which is this virtual host,
04:30
the center and win seven
04:32
and then our harpy data store.
04:35
We don't have one configured yet
04:36
because we only have one host.
04:44
Okay,
04:46
now what we can do
04:48
his coach, too.
04:50
Tasks in events.
04:56
We're going to show all cluster entries
05:00
so we can see that we moved a host into the cluster,
05:04
the user account that did this work.
05:11
We also have some events
05:13
showing each individual machine moving into the cluster.
05:16
Then we have an error here saying that we have insufficient resource is to satisfy. Fail over.
05:21
That's because the cluster only has one note.
05:25
Make sets.
05:28
All right,
05:30
let's drag the second host into the cluster.
05:35
Let's try it again. They bought it and grab it right
05:39
Here we go.
05:41
Okay, so now I have a cluster with two hosts.
05:48
You see how easy it is to just drag
05:51
tracked the other host in.
05:54
Now I want to go back to Mommy
05:58
tests and events
06:02
and I'll look in on my cluster entries.
06:05
So I've got a, um
06:08
another message about H A fail over resource is
06:16
probably some
06:18
messages about network redundancy.
06:24
So harpy data Stores.
06:26
Let's look at that.
06:35
So it was connected to master. Now we show one, whereas before it was zero,
06:41
I still have four PM's,
06:43
and now our harpy data store is
06:46
the NFS volume.
06:47
We can see both hosts are connected to NFS
06:50
and so they will use a small file within that data store to establish heartbeat between these hosts.
07:00
If the harpy goes down, obviously
07:02
the cluster,
07:03
we'll take some kind of action, depending on what kinds of alerts and alarms we have set up
07:11
and the other Klink that we need to look at his configuration issues.
07:15
And this is a little bit more what I was talking about earlier. We can see that
07:19
we have no management network redundancy,
07:23
so this is just qualifies as a warning.
07:26
It doesn't mean that the cluster can't work.
07:28
It's just trying to tell us that
07:30
if the manager network goes down, there's no redundant path.
07:33
So you may lose contact with your host. So that's that's kind of what we're getting at here.
07:41
The Harpy data stores
07:43
is also on Lee set toe one.
07:46
We're supposed to have at least two again for redundancy reasons.
07:54
And that basically wraps up what we need to look at as far as
07:58
the initial configuration of the clusters will go ahead and close that window
08:03
and move on to our next task.
08:07
Okay, so we can see that
08:11
we've got V EMS running on each of the hosts in the cluster.
08:15
I go to host 100
08:16
and the virtual machines tab
08:18
I've got view center that win 7 p.m.
08:22
Yes, that's true, which is actually this virtual host
08:26
and then my 2012 serve, which is crux.
08:30
If I look at the V. EMS on got 200
08:33
I can see that. I've got the Windows seven clone
08:37
number two running here.
08:39
Okay, So what we want to do now is test
08:43
the high availability functionality. So
08:46
if I reboot
08:50
got 200
08:52
then this win seven clone to should automatically move to the 70.100 host.
09:01
So first of all, let's
09:03
open up the council
09:05
for the host.
09:09
That way we can keep an eye on it's rebooting activity when we need to.
09:15
And I will simply right click the host
09:18
and select reboot.
09:20
I get a
09:22
message asked me if I won't really want to do this, I'll go ahead and say yes.
09:28
And my reason for rebooting is
09:31
trusting
09:33
P J.
09:37
Okay,
09:41
so we'll watch this screen for just a moment here.
09:54
So it says that it's that initiated the reboot
09:56
down in our tasks area. But nothing's really happening. It takes a few seconds
10:03
for us to actually start working. So if I select my cluster now
10:07
and
10:11
go to my tasks and events, Tab
10:15
can see, I've got a bunch of entries here. What I'm interested in mostly is the cluster entries,
10:22
and now we can see that I'm getting some messages.
10:28
So, uh,
10:31
back here, we've got sufficient resources are available to satisfy an itch a little fail over.
10:35
So that's what just happened.
10:39
And then we've got some other entries
10:41
talking about the
10:43
changing of the status of the different alarms.
10:48
So there's my sail over action,
10:50
and now my alarm has gone from grey to yellow,
10:58
so this takes a little while to run. If I go back to host 100
11:03
I can see that my
11:05
my VM already
11:07
appears to be running on the other host.
11:09
Go back to 200.
11:11
That V M is not running there.
11:13
Let's look at our console. We can see that we're in the process of rebooting.
11:20
So within probably less than a minute, the VM was brought up and running on the other host.
11:24
She works pretty quickly
11:28
now, depending on how much
11:31
activity is going on with the V M and how busy the hosts are.
11:35
This activity, this process rather could take
11:39
considerably longer amount of time.
11:43
But right now it's it's pretty pretty quick,
11:46
so we're back to our cluster in the inventory.
11:50
And now we're going to select the summary link
11:52
summary tab.
11:56
And here we can see various things like our total number of hosts in the cluster told number of processors, Summer days stores, virtual machines.
12:05
We still got a little bit of change going on, but click cluster status.
12:09
I got 100 is the master.
12:13
I've got zero host connected because that hostess still rebooting
12:18
we can still see that
12:18
going on here. It's almost done.
12:28
I still have my five protective e ems.
Up Next
Similar Content
