WEBVTT

1
00:00.180 --> 00:02.700
For the deployment, configuration,

2
00:02.700 --> 00:05.280
and management of our NSX environments, we are going

3
00:05.280 --> 00:08.490
to use an entity called the NSX Manager

4
00:08.490 --> 00:10.890
and think of the NSX Manager, very similar to the function

5
00:10.890 --> 00:12.780
of a vCenter Server Appliance.

6
00:12.780 --> 00:15.660
So we're using vCenter to manage our ESXI hosts.

7
00:15.660 --> 00:18.510
We're gonna use the NSX Manager to manage all

8
00:18.510 --> 00:20.010
of our NSX components.

9
00:20.010 --> 00:24.120
What we're gonna first do is deploy the NSX Manager as a VM.

10
00:24.120 --> 00:27.690
So we'll choose one of our ESXI hosts to deploy that on

11
00:27.690 --> 00:30.300
and then once we deploy it, it's gonna encourage us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.690 --> 00:30.300
and then once we deploy it, it's gonna encourage us

12
00:30.300 --> 00:32.250
to go ahead and create a cluster.

13
00:32.250 --> 00:35.580
And a cluster is three VMs,

14
00:35.580 --> 00:38.640
specifically three NSX Manager VMs that we can use

15
00:38.640 --> 00:40.740
to help manage our entire NSX environment.

16
00:40.740 --> 00:43.290
So let's say we have three VMs that we've deployed.

17
00:43.290 --> 00:46.185
Now the first one we're gonna deploy as an OVF.

18
00:46.185 --> 00:47.310
So you deploy it, install it,

19
00:47.310 --> 00:48.750
you let it get up and initialized

20
00:48.750 --> 00:50.490
and then once it's running, it encourages you

21
00:50.490 --> 00:52.590
to add additional managers.

22
00:52.590 --> 00:55.620
So right from the interface of the NSX one, for example,

23
00:55.620 --> 00:58.320
you can go ahead and deploy NSX two and NSX three.

24
00:58.320 --> 01:00.030
It'd also be wise to have each of those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:58.320 --> 01:00.030
It'd also be wise to have each of those

25
01:00.030 --> 01:01.920
on a separate ESXI host.

26
01:01.920 --> 01:05.280
So this could be on host X, and this could be on host Y,

27
01:05.280 --> 01:06.780
and this could be on host Z.

28
01:06.780 --> 01:09.450
So we may wanna set up some affinity rules to make sure

29
01:09.450 --> 01:14.450
that if we're using DRS that our NSX VMs are being deployed

30
01:14.550 --> 01:16.650
and not on the same exact host.

31
01:16.650 --> 01:19.260
That way we can share the love and the resources that each

32
01:19.260 --> 01:21.690
of those NSX appliances is gonna get.

33
01:21.690 --> 01:24.240
So let's imagine this is our management network right here,

34
01:24.240 --> 01:29.240
and I'm gonna use 192, 168.1.0 with a 24 bit mask.

35
01:29.400 --> 01:31.020
So maybe this guy's at .11,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:29.400 --> 01:31.020
So maybe this guy's at .11,

36
01:31.020 --> 01:32.880
and we put the second one in at .12,

37
01:32.880 --> 01:34.920
and we put the third one in at .13.

38
01:34.920 --> 01:37.140
And what we can also do is set up a virtual address,

39
01:37.140 --> 01:40.500
a virtual IP, to manage them as a cluster.

40
01:40.500 --> 01:42.630
So let's go ahead and pick, for example, .10

41
01:42.630 --> 01:45.420
as the virtual IP so you and I, we connect to the IP address

42
01:45.420 --> 01:48.825
of .10 with https, and this is gonna associate that with one

43
01:48.825 --> 01:51.480
of our NSX managers, and that's where we can go ahead

44
01:51.480 --> 01:52.410
and start working.

45
01:52.410 --> 01:55.920
Now, behind the scenes, let's say we have 50 objects

46
01:55.920 --> 01:59.340
inside of NSX, including hosts and other VMs

47
01:59.340 --> 02:01.170
that we'll be talking about here in just a moment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:59.340 --> 02:01.170
that we'll be talking about here in just a moment.

48
02:01.170 --> 02:03.090
Even though when we connect to the virtual IP address,

49
02:03.090 --> 02:05.760
we're only connected to one of the NSX appliances

50
02:05.760 --> 02:08.280
or one of the NSX managers, behind the scenes,

51
02:08.280 --> 02:09.450
it's gonna divvy up some of the loads.

52
02:09.450 --> 02:11.670
So perhaps this NSX Manager is gonna be managing

53
02:11.670 --> 02:15.120
15 of our objects, and this device is gonna be managing

54
02:15.120 --> 02:17.910
15 of our objects, and this one may be 20,

55
02:17.910 --> 02:19.440
so hopefully that adds up to 50.

56
02:19.440 --> 02:22.830
So that division on the backend is done automatically.

57
02:22.830 --> 02:25.350
Also, in addition to using a virtual IP address,

58
02:25.350 --> 02:27.870
we could also set up a load balancing service

59
02:27.870 --> 02:30.450
on the front end and if we did implement a load balancer,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:27.870 --> 02:30.450
on the front end and if we did implement a load balancer,

60
02:30.450 --> 02:32.130
we would connect them to the load balancer virtual

61
02:32.130 --> 02:35.250
IP address, and then it could spin us off to the least busy

62
02:35.250 --> 02:38.220
or based on the load balancer rules, the NSX Manager

63
02:38.220 --> 02:40.470
that it believed was the least busy,

64
02:40.470 --> 02:41.730
but even without a load balancer,

65
02:41.730 --> 02:43.350
we can set up a virtual IP address,

66
02:43.350 --> 02:45.000
have multiple NSX managers,

67
02:45.000 --> 02:47.309
and behind the scenes, they'll divvy up the responsibility

68
02:47.309 --> 02:51.120
of interacting with and working with our NSX devices.

69
02:51.120 --> 02:54.120
And these NSX managers working together are referred to

70
02:54.120 --> 02:56.040
as an NSX Cluster.

71
02:56.040 --> 02:58.350
So to give you a visual idea of what that looks like,

72
02:58.350 --> 03:01.050
this is the interface for the NSX manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
02:58.350 --> 03:01.050
this is the interface for the NSX manager.

73
03:01.050 --> 03:03.390
So I've gone here to the appliances section,

74
03:03.390 --> 03:06.480
and I currently have one NSX manager in place.

75
03:06.480 --> 03:08.460
So it's begging me, please add more.

76
03:08.460 --> 03:11.130
So I simply click here and I could go through the process

77
03:11.130 --> 03:13.260
of yet adding a second, and then repeat that

78
03:13.260 --> 03:16.140
to add a third NSX manager that would become

79
03:16.140 --> 03:17.610
part of this cluster.

80
03:17.610 --> 03:20.220
So on this first NSX Manager, there's its management address

81
03:20.220 --> 03:23.820
right there of 192 168, 1.11 and then here's the version

82
03:23.820 --> 03:25.380
of NSX that I'm currently running.

83
03:25.380 --> 03:28.110
So the NSX Manager is the brains of the operation.

84
03:28.110 --> 03:30.510
So let's imagine this is our NSX Manager right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:28.110 --> 03:30.510
So let's imagine this is our NSX Manager right here.

85
03:30.510 --> 03:32.280
As part of the deployment, once we deploy it,

86
03:32.280 --> 03:34.140
we'll also tell it where our vCenter is.

87
03:34.140 --> 03:36.360
Let's mention we also have here on our management network,

88
03:36.360 --> 03:38.310
the vCenter Server Appliance

89
03:38.310 --> 03:40.080
and the reason the NSX manager needs to know

90
03:40.080 --> 03:42.660
about the vCenter Server is because the vCenter Server

91
03:42.660 --> 03:44.730
is in charge of the distributed switch,

92
03:44.730 --> 03:47.310
which in the current flavor of NSX,

93
03:47.310 --> 03:49.230
we're gonna be leveraging the virtual distributed switch

94
03:49.230 --> 03:54.090
and adding our logical segments from NSX to our VDS.

95
03:54.090 --> 03:55.800
So as part of that integration, in addition

96
03:55.800 --> 03:58.770
to identifying the virtual distributed switch in vSphere

97
03:58.770 --> 04:01.530
that we're gonna use and enhance, we're also gonna leverage
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
03:58.770 --> 04:01.530
that we're gonna use and enhance, we're also gonna leverage

98
04:01.530 --> 04:05.910
that relationship with the vCenter to identify the ESXI host

99
04:05.910 --> 04:08.730
that we are going to include as part of NSX.

100
04:08.730 --> 04:11.550
So that way right here from the NSX manager, we can specify,

101
04:11.550 --> 04:13.530
oh, for this host or that host, we want

102
04:13.530 --> 04:17.040
to add the NSX software to those hosts

103
04:17.040 --> 04:19.500
so they can participate as part of NSX.

104
04:19.500 --> 04:22.290
And the NSX Manager is gonna become the centralized control

105
04:22.290 --> 04:24.600
plane for the NSX environment.

106
04:24.600 --> 04:29.130
So any of the details regarding segments or routers,

107
04:29.130 --> 04:31.470
virtual routers in the NSX environment,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:29.130 --> 04:31.470
virtual routers in the NSX environment,

108
04:31.470 --> 04:34.800
or which segments should be included on which hosts,

109
04:34.800 --> 04:36.690
that's all controlled by the NSX Manager,

110
04:36.690 --> 04:38.910
and it's gonna be the Centralized Control Plane.

111
04:38.910 --> 04:40.560
And then on each of the ESXI hosts

112
04:40.560 --> 04:42.180
and other objects that we'll soon talk about here

113
04:42.180 --> 04:45.570
in a moment, they'll receive a copy of what they're supposed

114
04:45.570 --> 04:48.240
to do and that's called the Local Control Plane.

115
04:48.240 --> 04:50.190
So the Centralized Control Plane is managed

116
04:50.190 --> 04:51.800
by the NSX Manager cluster.

117
04:51.800 --> 04:54.900
And for individual hosts that are participating in NSX,

118
04:54.900 --> 04:57.210
they'll have a Local Control Plane.

119
04:57.210 --> 04:59.700
Effectively what they need to know to do their jobs

120
04:59.700 --> 05:01.530
as part of NSX.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
04:59.700 --> 05:01.530
as part of NSX.

121
05:01.530 --> 05:03.090
Let's imagine that you and I are sitting here

122
05:03.090 --> 05:06.120
at this management PC, we've logged onto the NSX Manager

123
05:06.120 --> 05:08.520
and we've identified these two hosts, we'll call it host A

124
05:08.520 --> 05:12.060
and B, that we want them to participate as part of NSX.

125
05:12.060 --> 05:15.441
So from the NSX Manager, we install and add the software

126
05:15.441 --> 05:16.590
to those hosts.

127
05:16.590 --> 05:19.170
And the moment that we add that NSX software

128
05:19.170 --> 05:21.270
and they're up and running and happy, happy,

129
05:21.270 --> 05:24.210
those are now referred to as transport nodes.

130
05:24.210 --> 05:26.760
And think of a transport node as an ESXI host

131
05:26.760 --> 05:30.390
with the additional software regarding NSX that allows it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
05:26.760 --> 05:30.390
with the additional software regarding NSX that allows it

132
05:30.390 --> 05:32.250
to do the tunneling that we took a look at

133
05:32.250 --> 05:35.310
a couple videos ago where traffic coming in, for example,

134
05:35.310 --> 05:38.880
from one VM on a segment is encapsulated and tunneled

135
05:38.880 --> 05:41.340
and shipped off to a remote destination

136
05:41.340 --> 05:43.530
where the receiving site is de-encapsulated.

137
05:43.530 --> 05:46.500
Effectively, that's the function of a transport node

138
05:46.500 --> 05:48.003
in the world of NSX.