WEBVTT

1
00:00.240 --> 00:01.920
Hello and welcome.

2
00:01.920 --> 00:04.080
My name is Keith Barker.

3
00:04.080 --> 00:05.407
And if somebody came up to us and said,

4
00:05.407 --> 00:07.620
"Hey, regarding your ESXI host

5
00:07.620 --> 00:09.150
and all their compute resources,

6
00:09.150 --> 00:10.470
how do you manage all of them?"

7
00:10.470 --> 00:11.303
We would simply say,

8
00:11.303 --> 00:14.820
"We use a centralized control system called vCenter

9
00:14.820 --> 00:17.850
to work with and manage all those ESXI hosts."

10
00:17.850 --> 00:19.470
And that's a very common paradigm

11
00:19.470 --> 00:20.700
in controller based networking.

12
00:20.700 --> 00:22.500
You and I, we connect to

13
00:22.500 --> 00:24.600
or interact with the management device.

14
00:24.600 --> 00:27.450
In the case of vSphere, it is the vCenter.

15
00:27.450 --> 00:29.100
And then, the vCenter interacts

16
00:29.100 --> 00:31.830
and communicates with all of the ESXI hosts.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:29.100 --> 00:31.830
and communicates with all of the ESXI hosts.

17
00:31.830 --> 00:33.000
Now, why do I mention that?

18
00:33.000 --> 00:34.440
Well, I mentioned that because that is

19
00:34.440 --> 00:36.900
the same exact paradigm that we're gonna use

20
00:36.900 --> 00:38.670
when we're working with NSX.

21
00:38.670 --> 00:39.503
If somebody asks us,

22
00:39.503 --> 00:41.400
"Hey, what are you using to manage

23
00:41.400 --> 00:43.950
and control all of your NSX devices?"

24
00:43.950 --> 00:44.783
We would say,

25
00:44.783 --> 00:46.800
"We use a centralized management system

26
00:46.800 --> 00:49.050
called the NSX Manager."

27
00:49.050 --> 00:51.930
So just like the vCenter is responsible for the management

28
00:51.930 --> 00:53.130
of our ESXI host,

29
00:53.130 --> 00:55.140
the NSX manager is responsible

30
00:55.140 --> 00:57.390
for the management, and implementation, and configuration,

31
00:57.390 --> 01:00.780
and also the control plane of our NSX nodes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
00:57.390 --> 01:00.780
and also the control plane of our NSX nodes.

32
01:00.780 --> 01:01.680
Now, the one rub is

33
01:01.680 --> 01:04.770
that it's not possible to use NSX Manager

34
01:04.770 --> 01:06.660
unless it's running somewhere. (chuckles)

35
01:06.660 --> 01:08.670
Now that somewhere in our environment

36
01:08.670 --> 01:13.140
is gonna be running as a VM on one of our ESXI hosts.

37
01:13.140 --> 01:14.220
So in this skill, you and I

38
01:14.220 --> 01:15.990
get to walk through the planning,

39
01:15.990 --> 01:18.120
implementation, and verification

40
01:18.120 --> 01:20.760
of an NSX manager and for fault tolerance.

41
01:20.760 --> 01:22.320
We don't want to just have one of them,

42
01:22.320 --> 01:24.030
we wanna have a few of them

43
01:24.030 --> 01:26.400
inside of an NSX management cluster.

44
01:26.400 --> 01:28.620
So I'll see you, my friend, in the very next video

45
01:28.620 --> 01:31.440
as we put a game plan together for our implementation
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:28.620 --> 01:31.440
as we put a game plan together for our implementation

46
01:31.440 --> 01:33.273
of our NSX managers.