WEBVTT

1
00:00.000 --> 00:03.300
All right, my friend, it is game plan time.

2
00:03.300 --> 00:07.300
So let's use an NSX Topology look something like this.

3
00:07.300 --> 00:12.600
So one of the first steps we want to take is to confirm our NSX Topology.

4
00:12.600 --> 00:15.600
And then once we confirm that we have this topology in place,

5
00:15.600 --> 00:20.000
our next step would be to go ahead and deploy the advanced load balancer.

6
00:20.000 --> 00:23.700
Now, VMware bought this advanced load balancer from a company.

7
00:23.700 --> 00:27.500
And so if you see AVI, that's simply the previous company's name.

8
00:27.500 --> 00:29.900
So that still shows up a few times.

9
00:29.900 --> 00:31.700
So we'll deploy the advanced load balancer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.900 --> 00:31.700
So we'll deploy the advanced load balancer.

10
00:31.700 --> 00:32.800
It is an OVA.

11
00:32.800 --> 00:34.300
So we'll deploy that in vSphere.

12
00:34.300 --> 00:36.800
We'll find a nice home for it for a compute resource.

13
00:36.800 --> 00:38.900
And the actual file is an OVA file.

14
00:38.900 --> 00:41.900
So now that I've mentioned that, we can go ahead and just as our tasks,

15
00:41.900 --> 00:44.300
say deploy the advanced load balancer.

16
00:44.300 --> 00:46.600
And for management for that advanced load balancer,

17
00:46.600 --> 00:50.300
let's put it right here on the 10-10-30 network,

18
00:50.300 --> 00:52.800
which is segment 103-ALB management.

19
00:52.800 --> 00:55.100
That's the name of it, inside of NSX.

20
00:55.100 --> 00:58.300
So that'll be the management network for the advanced load balancer.

21
00:58.300 --> 01:01.300
So its IP address will be .15.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:58.300 --> 01:01.300
So its IP address will be .15.

22
01:01.300 --> 01:04.900
Now also in the topology, I have this 192.1 state one network.

23
01:04.900 --> 01:09.500
And that's my management network for all of the vCenter and NSX stuff.

24
01:09.500 --> 01:11.800
So I have the NSX controller right there.

25
01:11.800 --> 01:13.900
I've got the vCenter right there.

26
01:13.900 --> 01:16.400
So the vCenter is at .35.

27
01:16.400 --> 01:18.700
And my NSX manager is at .21.

28
01:18.700 --> 01:21.200
In fact, let me just clean that up and write that a little bit better.

29
01:21.200 --> 01:25.600
And so to facilitate communications between the advanced load balancer here

30
01:25.600 --> 01:29.000
we're going to look down on segment 103 and these two devices,

31
01:29.000 --> 01:32.800
instead of trying to train both of these devices on how to route back
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:29.000 --> 01:32.800
instead of trying to train both of these devices on how to route back

32
01:32.800 --> 01:36.000
through this tier one gateway, I'm going to go ahead and simply set up a little

33
01:36.000 --> 01:39.800
reflexive NAT right here that says, "Hey, dear Mr. load balancer,

34
01:39.800 --> 01:42.600
if you're ever going out to the 192.1 state one network,

35
01:42.600 --> 01:45.900
I'm going to net you out to .15 on that network."

36
01:45.900 --> 01:50.200
And that way as the vCenter and the NSX manager communicate and talk to the

37
01:50.200 --> 01:51.000
load balancer,

38
01:51.000 --> 01:53.000
those will think he's coming from 15.

39
01:53.000 --> 01:56.760
So the load balancer here will be at .15 on the 10.1,

40
01:56.760 --> 01:58.600
0, 3.0, 0 network.

41
01:58.600 --> 02:02.640
And again, it'll be netted to 192.1 state one .15 for the benefit of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:58.600 --> 02:02.640
And again, it'll be netted to 192.1 state one .15 for the benefit of

42
02:02.640 --> 02:03.000
communicating

43
02:03.000 --> 02:05.600
with the vCenter and the NSX manager up here.

44
02:05.600 --> 02:09.600
Now part of the job of the controller is to deploy the service engines

45
02:09.600 --> 02:12.900
wherever they're needed based on the topology we end up creating.

46
02:12.900 --> 02:17.700
And so to do that, there needs to be a content library up here on the vCenter

47
02:17.700 --> 02:22.200
where the controller can actually place the image is going to use

48
02:22.200 --> 02:23.300
to deploy the SEs.

49
02:23.300 --> 02:26.600
And that way if it needs to deploy an SE over here or somewhere else,

50
02:26.600 --> 02:29.700
it can leverage the content library in the vCenter.

51
02:29.700 --> 02:34.300
So one of our steps here is to create the vCenter content library.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:29.700 --> 02:34.300
So one of our steps here is to create the vCenter content library.

52
02:34.300 --> 02:37.100
And we don't actually have to put anything in that library.

53
02:37.100 --> 02:39.100
The controller, once it's all set up,

54
02:39.100 --> 02:43.800
will automatically place the images needed in the content library.

55
02:43.800 --> 02:48.400
Then once the advanced load balancer is deployed and we can reach it at .15,

56
02:48.400 --> 02:50.800
we need to take care of the licensing issue.

57
02:50.800 --> 02:54.500
And with the current version, I'm using, I think there's like a 30 day window

58
02:54.500 --> 02:57.300
for an actual trial once you deploy the controller.

59
02:57.300 --> 03:00.900
So we'll make sure that that license is active and available for us.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:57.300 --> 03:00.900
So we'll make sure that that license is active and available for us.

60
03:00.900 --> 03:03.800
We can actually work with the controller down here.

61
03:03.800 --> 03:06.600
Also, because this controller is going to need to log into the vCenter

62
03:06.600 --> 03:08.800
and also to the NSX to interact with them,

63
03:08.800 --> 03:12.600
we also need to create the credentials here on the controller

64
03:12.600 --> 03:16.800
that it can use when we tell it to go ahead and start logging into the vCenter

65
03:16.800 --> 03:18.400
and to the NSX respectively.

66
03:18.400 --> 03:21.100
So here at the advanced load balancer controller,

67
03:21.100 --> 03:24.400
we're going to go ahead and create what are referred to as credentials

68
03:24.400 --> 03:27.900
that we can then use to log into the vCenter and the NSX manager.

69
03:27.900 --> 03:31.200
That also means that we need to know what those logging credentials are.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:27.900 --> 03:31.200
That also means that we need to know what those logging credentials are.

70
03:31.200 --> 03:34.300
So it can log on to the vCenter and to NSX.

71
03:34.300 --> 03:35.800
And in a production environment,

72
03:35.800 --> 03:37.800
instead of logging on with King Kong writes,

73
03:37.800 --> 03:41.200
for example, like admin at the vCenter and NSX,

74
03:41.200 --> 03:44.700
it'd be better to go ahead and carve out unique user accounts

75
03:44.700 --> 03:47.000
with the correct roles associated with them.

76
03:47.000 --> 03:50.600
And that way, when the advanced load balancer is interacting with vCenter

77
03:50.600 --> 03:55.500
and NSX, the credentials it's using aren't the full admin writes,

78
03:55.500 --> 03:57.500
but instead using just the rights that are needed.

79
03:57.500 --> 03:58.600
So for the lab environment, though,

80
03:58.600 --> 04:00.800
I'm going to go ahead and simply tell it to go ahead and log in with the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:58.600 --> 04:00.800
I'm going to go ahead and simply tell it to go ahead and log in with the

81
04:00.800 --> 04:01.300
credentials

82
04:01.300 --> 04:03.800
for admin on both those platforms.

83
04:03.800 --> 04:05.700
With the warning that in a production environment,

84
04:05.700 --> 04:08.000
you might want to scale that back and log in within the count.

85
04:08.000 --> 04:09.500
That just has the rights that are needed.

86
04:09.500 --> 04:12.800
And as far as what roles would be needed and so forth for the accounts

87
04:12.800 --> 04:16.900
on the vCenter and on NSX, those are spelled out meticulously.

88
04:16.900 --> 04:20.200
In the documentation for the advanced load balancer.

89
04:20.200 --> 04:22.300
So in a production environment, you get that documentation,

90
04:22.300 --> 04:25.500
walk through step by step and set up the user accounts that are needed

91
04:25.500 --> 04:27.100
just for the access that's needed.

92
04:27.100 --> 04:30.400
So then our next step would be to go ahead on the advanced load balancer
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:27.100 --> 04:30.400
So then our next step would be to go ahead on the advanced load balancer

93
04:30.400 --> 04:33.800
and create the connection to our NSX environment.

94
04:33.800 --> 04:37.200
This is going to leverage the username and password so it can log in

95
04:37.200 --> 04:40.900
and start interacting with the vCenter and the NSX manager.

96
04:40.900 --> 04:45.200
So we'll create a cloud connector on the controller to our NSX environment

97
04:45.200 --> 04:48.000
and as part of building and setting up that cloud connector to the NSX

98
04:48.000 --> 04:48.500
environment,

99
04:48.500 --> 04:52.400
it's going to ask us a lot of questions, including who is your vCenter?

100
04:52.400 --> 04:53.400
How do we reach it?

101
04:53.400 --> 04:55.800
Who is the NSX manager? How do we reach it?

102
04:55.800 --> 04:58.400
It's at that point, by the way, we would use the credentials we'd set up

103
04:58.400 --> 05:02.400
to go ahead and log on from the controller to those two platforms.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:58.400 --> 05:02.400
to go ahead and log on from the controller to those two platforms.

104
05:02.400 --> 05:04.200
It's going to ask us what's the management network.

105
05:04.200 --> 05:07.200
So we'll specify for the management network that we want to use the

106
05:07.200 --> 05:09.400
THEG 103 for the management network.

107
05:09.400 --> 05:11.100
There's currently DHCP services here.

108
05:11.100 --> 05:14.800
So these little service engines, they can get an IP address automatically.

109
05:14.800 --> 05:17.000
So that management would be part of the control plane.

110
05:17.000 --> 05:20.700
And it's also going to ask us about the data plane, meaning where do we want to

111
05:20.700 --> 05:23.000
implement the function of load balancing.

112
05:23.000 --> 05:26.600
So as far as options here in our topology, we could use some servers here

113
05:26.600 --> 05:31.900
out on VLAN 5 or we could use some servers here on segment 101.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:26.600 --> 05:31.900
out on VLAN 5 or we could use some servers here on segment 101.

114
05:31.900 --> 05:33.900
In either case, I'm going to have to put the servers there.

115
05:33.900 --> 05:37.300
So it'd be easier, I think, to go ahead and use another overlay segment

116
05:37.300 --> 05:41.300
that way I can just pop VMs in here, set them up for HTTP services

117
05:41.300 --> 05:41.900
and the way we go.

118
05:41.900 --> 05:45.100
So let's go ahead as far as our game plan goes and specify that this will be

119
05:45.100 --> 05:47.600
the data plane off of tier one left.

120
05:47.600 --> 05:51.500
And specifically off tier one left here, let's go ahead and specify segment

121
05:51.500 --> 05:53.800
101 for the data plane.

122
05:53.800 --> 05:57.600
So once that's all set up and once it's all fully deployed, our service

123
05:57.600 --> 06:00.300
engine that's being used would have one connection here for the management
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:57.600 --> 06:00.300
engine that's being used would have one connection here for the management

124
06:00.300 --> 06:00.900
network.

125
06:00.900 --> 06:03.900
And then the other interface here would be for the data plane.

126
06:03.900 --> 06:07.240
So once the cloud connector is all set up, we all need to at the advanced load

127
06:07.240 --> 06:07.900
balancer.

128
06:07.900 --> 06:11.100
We need to specify the virtual service that we're going to use.

129
06:11.100 --> 06:14.800
So let's create a virtual service for our web servers and for the virtual IP

130
06:14.800 --> 06:15.300
address

131
06:15.300 --> 06:16.900
associated with this web service.

132
06:16.900 --> 06:20.500
Let's use 10.101.0.5.

133
06:20.500 --> 06:24.500
So that IP address won't be used by any of our little VMs here.

134
06:24.500 --> 06:28.400
There'll just be a virtual IP address associated with this service that the

135
06:28.400 --> 06:29.100
service engine

136
06:29.100 --> 06:33.200
as part of the data plane will be listening and waiting for requests to come in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:29.100 --> 06:33.200
as part of the data plane will be listening and waiting for requests to come in

137
06:33.200 --> 06:34.100
at that address.

138
06:34.100 --> 06:38.700
And then as part of our configuration, let's also configure a pool of servers.

139
06:38.700 --> 06:41.100
And for our pool, let's use that same subnet.

140
06:41.100 --> 06:43.700
Now these servers don't have to be on the same exact subnet.

141
06:43.700 --> 06:46.700
They could actually be on a different subnet somewhere else.

142
06:46.700 --> 06:50.010
But for the lab environment, let's go ahead and some of these the same segment

143
06:50.010 --> 06:51.500
for our pool of servers.

144
06:51.500 --> 06:53.100
So let's use for the servers.

145
06:53.100 --> 06:56.100
Let's use .51 and 52.

146
06:56.100 --> 06:59.700
And if we want, we can go ahead and bring in a 53 as well.

147
06:59.700 --> 07:03.100
Those would be the real IP addresses of our three servers, but the customers
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

147
06:59.700 --> 07:03.100
Those would be the real IP addresses of our three servers, but the customers

148
07:03.100 --> 07:06.100
would come into the 10.1.0.1.0.5 address

149
07:06.100 --> 07:09.970
and then the load balancer, specifically the service engine as part of our

150
07:09.970 --> 07:11.100
advanced load balancer

151
07:11.100 --> 07:14.300
would then proxy the request to one of the servers that is up and available.

152
07:14.300 --> 07:17.910
Now, if we were talking about connectivity from the public internet, we could

153
07:17.910 --> 07:18.220
also do

154
07:18.220 --> 07:23.560
destination NAT right here that says, OK, traffic coming into, for example, 23.

155
07:23.560 --> 07:25.700
1.2.90

156
07:25.700 --> 07:29.430
or whatever addresses available to us from a service provider, we could go

157
07:29.430 --> 07:30.900
ahead and do destination NAT
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:29.430 --> 07:30.900
ahead and do destination NAT

158
07:30.900 --> 07:33.700
down to 10.1.0.5.

159
07:33.700 --> 07:37.110
And then when that destination NAT happens, that would go down to the virtual

160
07:37.110 --> 07:37.620
IP address

161
07:37.620 --> 07:41.540
associated with our virtual service, at which point the service engine acting

162
07:41.540 --> 07:42.780
as the load balancer

163
07:42.780 --> 07:46.270
function on the data plane, we then proxy that request to one of the available

164
07:46.270 --> 07:46.900
servers.

165
07:46.900 --> 07:50.580
However, because I realized we want to keep this lab to somewhere in the 45

166
07:50.580 --> 07:50.900
minutes to

167
07:50.900 --> 07:54.490
hour and 15 minute range, instead of also dealing with that, let me go ahead

168
07:54.490 --> 07:55.500
for testing.

169
07:55.500 --> 07:59.110
We can just test it from my management computer over here or from some other

170
07:59.110 --> 07:59.940
system by just

171
07:59.940 --> 08:03.460
going to the IP address 10.1.0.5.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
07:59.940 --> 08:03.460
going to the IP address 10.1.0.5.

172
08:03.460 --> 08:06.660
And then the load balancer will spin us off to one of the back end servers.

173
08:06.660 --> 08:16.660
[BLANK_AUDIO]