WEBVTT

1
00:00.180 --> 00:01.380
So let's compare notes

2
00:01.380 --> 00:04.440
regarding these four questions from the validation section.

3
00:04.440 --> 00:07.059
So the first question asks, how is the functionality

4
00:07.059 --> 00:09.960
of the NSX manager that we're gonna log into

5
00:09.960 --> 00:13.230
to provide the management plane as well as the control plane

6
00:13.230 --> 00:14.790
for all of our transport nodes?

7
00:14.790 --> 00:15.840
How is that implemented?

8
00:15.840 --> 00:18.120
That also ties into the next question, which is

9
00:18.120 --> 00:20.190
where does the NSX manager run?

10
00:20.190 --> 00:23.340
So the NSX manager is implemented as a vm,

11
00:23.340 --> 00:25.950
so it can run here on this ESXI host,

12
00:25.950 --> 00:27.750
or pretty much any ESXI host

13
00:27.750 --> 00:29.280
that has the computing resources

14
00:29.280 --> 00:31.350
to provide services for that vm.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.280 --> 00:31.350
to provide services for that vm.

15
00:31.350 --> 00:32.790
And then the next question is,

16
00:32.790 --> 00:35.100
how many NSX managers should be in a

17
00:35.100 --> 00:36.510
cluster for fault tolerance?

18
00:36.510 --> 00:38.910
And the answer is ideally three.

19
00:38.910 --> 00:40.530
We'd want to have three of those

20
00:40.530 --> 00:43.560
so we can have a virtual IP address in front of all that.

21
00:43.560 --> 00:45.720
So we can connect to the virtual IP address for management.

22
00:45.720 --> 00:49.260
And then one of the NSX managers in the cluster would take

23
00:49.260 --> 00:50.280
responsibility for that.

24
00:50.280 --> 00:51.660
And in the background, each

25
00:51.660 --> 00:54.720
of the NSX managers are actually taking a responsibility

26
00:54.720 --> 00:57.180
for a portion of the transport nodes.

27
00:57.180 --> 01:01.080
So maybe this has responsibility for 10 of our host
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:57.180 --> 01:01.080
So maybe this has responsibility for 10 of our host

28
01:01.080 --> 01:02.640
or edge transport nodes.

29
01:02.640 --> 01:04.140
This has responsibility for 10,

30
01:04.140 --> 01:06.240
and let's say we have 30 nodes altogether,

31
01:06.240 --> 01:08.280
and this has responsibility for the other 10.

32
01:08.280 --> 01:10.560
But in either case, that division of work behind the scenes

33
01:10.560 --> 01:14.520
for the cluster is done automatically by the NSX manager.

34
01:14.520 --> 01:16.500
So all we need to do is connect to the VAP

35
01:16.500 --> 01:19.380
or to the IP address of any of the existing managers,

36
01:19.380 --> 01:21.030
specify what we want to happen.

37
01:21.030 --> 01:22.860
And then in the background, they divvy up the work as far

38
01:22.860 --> 01:25.089
as the management of the NSX devices.

39
01:25.089 --> 01:27.600
And then they're using corfu and the corfu database

40
01:27.600 --> 01:29.220
to synchronize all the details

41
01:29.220 --> 01:31.069
that are happening across all three
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:29.220 --> 01:31.069
that are happening across all three

42
01:31.069 --> 01:33.750
of these NSX managers inside the cluster.

43
01:33.750 --> 01:36.510
So ideally, we should have at least three NSX

44
01:36.510 --> 01:37.830
managers in our cluster.

45
01:37.830 --> 01:39.496
And then the last question is, how do you control

46
01:39.496 --> 01:44.010
how much RAM and or CPU are used by an NSX management node?

47
01:44.010 --> 01:46.860
So for the initial deployment of our NSX manager,

48
01:46.860 --> 01:48.330
when we deploy the template,

49
01:48.330 --> 01:50.947
we're gonna specify the size we want, we want extra small,

50
01:50.947 --> 01:53.370
small, medium, or large.

51
01:53.370 --> 01:55.440
And then based on that, that's gonna correspond to

52
01:55.440 --> 02:00.420
how much CPU and RAM are being consumed by that NSX manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:55.440 --> 02:00.420
how much CPU and RAM are being consumed by that NSX manager.

53
02:00.420 --> 02:02.419
And then for the second and third NSX manager,

54
02:02.419 --> 02:04.080
we simply deploy them

55
02:04.080 --> 02:06.510
after we've logged into the initial NSX manager.

56
02:06.510 --> 02:08.880
And there's an option there from within NSX manager

57
02:08.880 --> 02:10.020
to deploy the second

58
02:10.020 --> 02:12.780
and third NSX managers as part of the cluster.

59
02:12.780 --> 02:15.240
So thanks for taking a few minutes to consider some

60
02:15.240 --> 02:16.650
of the answers to these questions

61
02:16.650 --> 02:18.360
and then reviewing them here with me together.

62
02:18.360 --> 02:19.379
And then before we go,

63
02:19.379 --> 02:21.822
I've got one final poll question for you right below.

64
02:21.822 --> 02:23.730
And then once you're done with that, you're done

65
02:23.730 --> 02:25.020
with this specific skill.

66
02:25.020 --> 02:28.170
So until the next one, I hope this has been informative

67
02:28.170 --> 02:30.453
and I'd like to thank you for viewing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:28.170 --> 02:30.453
and I'd like to thank you for viewing.