WEBVTT

1
00:00.000 --> 00:02.600
So now that our controller is deployed,

2
00:02.600 --> 00:06.080
it's integrated with vCenter and also with NSX.

3
00:06.080 --> 00:10.040
So over here is the management plane for our load balancer.

4
00:10.040 --> 00:12.680
And over here is where we want to actually implement on

5
00:12.680 --> 00:14.440
the data plane the load balancing.

6
00:14.440 --> 00:16.120
So based on our game plan, here's what we want to do.

7
00:16.120 --> 00:20.920
We want a virtual address of 10.101.0.5.

8
00:20.920 --> 00:23.080
And then we're going to have our service engine function for

9
00:23.080 --> 00:27.920
by the load balancing between that IP address and the various servers that are

10
00:27.920 --> 00:29.080
up and available.

11
00:29.080 --> 00:33.720
And for the web servers in the back end, we use .51, .52, and .53.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.080 --> 00:33.720
And for the web servers in the back end, we use .51, .52, and .53.

12
00:33.720 --> 00:36.560
So let's head over to the interface for the controller.

13
00:36.560 --> 00:41.050
And let's create a brand new virtual service with this associated virtual IP

14
00:41.050 --> 00:41.720
address.

15
00:41.720 --> 00:43.400
So here's the interface for the load balancer.

16
00:43.400 --> 00:45.920
And before we actually create the virtual service,

17
00:45.920 --> 00:49.920
let me also give you a sneak peek at what vCenter is currently looking like.

18
00:49.920 --> 00:51.640
So here is the vSphere client.

19
00:51.640 --> 00:53.720
We're currently looking at our content library.

20
00:53.720 --> 00:55.200
We'll do a refresh here.

21
00:55.200 --> 01:00.160
Notice that there's nothing at all inside of our content library yet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:55.200 --> 01:00.160
Notice that there's nothing at all inside of our content library yet.

22
01:00.160 --> 01:04.680
Also, if we look here at running tasks, there's no activity going on.

23
01:04.680 --> 01:10.000
But once we create on the controller a virtual service and set it up at that

24
01:10.000 --> 01:10.320
moment,

25
01:10.320 --> 01:11.160
it's going to say, you know what?

26
01:11.160 --> 01:12.480
I better get to work.

27
01:12.480 --> 01:16.790
And it's going to go ahead and only copy the files it needs to deploy an SE

28
01:16.790 --> 01:18.120
over to the content library.

29
01:18.120 --> 01:21.840
But it'll also follow that up by deploying a services engine or two that they

30
01:21.840 --> 01:22.520
can use

31
01:22.520 --> 01:24.440
for the actual load balancing.

32
01:24.440 --> 01:26.480
So just as our friendly reminder of where we're at,

33
01:26.480 --> 01:30.200
we're currently inside of vSphere at .35.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:26.480 --> 01:30.200
we're currently inside of vSphere at .35.

34
01:30.200 --> 01:34.830
And what we're about to do is go over to the controller and set up our virtual

35
01:34.830 --> 01:35.720
service.

36
01:35.720 --> 01:36.960
So let's head over to the controller.

37
01:36.960 --> 01:40.280
So now this is the interface for the controller again, right here.

38
01:40.280 --> 01:44.400
And to create a new service, what we're going to do is on the applications tab

39
01:44.400 --> 01:45.480
on the top left,

40
01:45.480 --> 01:49.040
we're going to go ahead and click on virtual services here on the left.

41
01:49.040 --> 01:51.640
So currently there are no virtual services.

42
01:51.640 --> 01:55.960
So to create our first one, we're going to click right here on create virtual

43
01:55.960 --> 01:56.440
service.

44
01:56.440 --> 01:59.800
And then there's two options, basic and advanced with basic.

45
01:59.800 --> 02:03.080
It's going to ask for some basic information to go through and for advanced.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:59.800 --> 02:03.080
It's going to ask for some basic information to go through and for advanced.

46
02:03.080 --> 02:06.960
It has many of the additional nerd knobs and options that we can set up.

47
02:06.960 --> 02:08.480
So for the demo, we'll use basic.

48
02:08.480 --> 02:12.300
And if we need to go into the details and modify any of the parameters, we can

49
02:12.300 --> 02:13.440
do that as well.

50
02:13.440 --> 02:16.320
So now it's asking, OK, for this new virtual service, which is going to be

51
02:16.320 --> 02:18.080
associated with a virtual IP address.

52
02:18.080 --> 02:20.320
Do you want to do this for the default cloud?

53
02:20.320 --> 02:24.420
The one that we didn't configure or the one called our NSX cloud, which is the

54
02:24.420 --> 02:24.920
one we want.

55
02:24.920 --> 02:26.400
So we'll select the correct cloud.

56
02:26.400 --> 02:29.920
That's the one we just created and we'll click right here on next.

57
02:29.920 --> 02:33.320
Next is asking about the context for this new virtual service.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:29.920 --> 02:33.320
Next is asking about the context for this new virtual service.

58
02:33.320 --> 02:36.040
And I want to isolate this just to T1 left.

59
02:36.040 --> 02:37.600
So I'll choose T1 left.

60
02:37.600 --> 02:41.210
That's the gateway on the left hand side, the tier one gateway and we'll click

61
02:41.210 --> 02:41.800
on next.

62
02:41.800 --> 02:45.320
So let's go ahead and call this our dash web dash app.

63
02:45.320 --> 02:47.520
That'll be the name of the virtual service.

64
02:47.520 --> 02:51.480
And then we're going to associate that virtual service with an IP address of 10

65
02:51.480 --> 02:53.400
.1 0 1.0 5.

66
02:53.400 --> 02:58.960
So to do that, we use the drop down here in the section for virtual service VIP

67
02:58.960 --> 02:58.960
.

68
02:58.960 --> 03:02.440
And because we don't yet have one created, we'll simply use the opportunity
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:58.960 --> 03:02.440
And because we don't yet have one created, we'll simply use the opportunity

69
03:02.440 --> 03:03.080
right now

70
03:03.080 --> 03:07.160
to click on this option called create virtual service VIP.

71
03:07.160 --> 03:10.600
So we'll click there and that whisk this away for just a moment so we can

72
03:10.600 --> 03:13.160
create this new virtual service IP.

73
03:13.160 --> 03:16.400
And this is the name is going to give it, but we can go ahead and just go ahead

74
03:16.400 --> 03:17.160
and call it

75
03:17.160 --> 03:20.600
VIP for short or we could rename this to something else.

76
03:20.600 --> 03:25.160
So the actual virtual IP address, we're going to call it our web app VIP.

77
03:25.160 --> 03:27.960
And let me go ahead and put that in upper case as well.

78
03:27.960 --> 03:32.660
This is going to be located in our NSX cloud within the gateway on the left
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:27.960 --> 03:32.660
This is going to be located in our NSX cloud within the gateway on the left

79
03:32.660 --> 03:34.000
called tier one left.

80
03:34.000 --> 03:37.540
And as we scroll down, it's asking us here to add whatever IP address we want

81
03:37.540 --> 03:38.000
to use.

82
03:38.000 --> 03:39.120
So we'll click here on add.

83
03:39.120 --> 03:41.080
Once it's done, it'll be enabled.

84
03:41.080 --> 03:43.920
And for the demo, I'm going to do a static IP address.

85
03:43.920 --> 03:49.120
And let's use the IP address we planned on, which was 10 dot 101 dot 0 dot five

86
03:49.120 --> 03:50.120
, just like that.

87
03:50.120 --> 03:54.840
And with that in place, we'll click on save and then we'll click on save again.

88
03:54.840 --> 03:56.160
And it is thinking about it.

89
03:56.160 --> 04:01.840
So now we have this new virtual IP address and we can go back and edit it if we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:56.160 --> 04:01.840
So now we have this new virtual IP address and we can go back and edit it if we

90
04:01.840 --> 04:02.160
want to,

91
04:02.160 --> 04:06.120
but it's 10 dot 101 dot 0 dot five based on our plan.

92
04:06.120 --> 04:09.340
And that virtual IP address will be associated with this service called our web

93
04:09.340 --> 04:09.720
app.

94
04:09.720 --> 04:13.360
And then for the application type, we have a few options over here on the right

95
04:13.360 --> 04:13.360
.

96
04:13.360 --> 04:16.960
So for application type, HTTP is the default and that's why I use this well

97
04:16.960 --> 04:17.400
known port,

98
04:17.400 --> 04:19.800
TCP port 80 as the well known port.

99
04:19.800 --> 04:23.520
If we chose this HTTPS, it puts the well known port for HTTPS.

100
04:23.520 --> 04:27.040
It's also going to give us options about choosing the right certificate to use.

101
04:27.040 --> 04:30.300
If we choose L4, then we put in a port that we want to be associated with this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:27.040 --> 04:30.300
If we choose L4, then we put in a port that we want to be associated with this

102
04:30.300 --> 04:31.200
virtual service.

103
04:31.200 --> 04:34.760
And this would be for things like non HTTP related services.

104
04:34.760 --> 04:39.190
And there's one for L4 SSL slash TLS, which once again has the well known port

105
04:39.190 --> 04:40.240
443.

106
04:40.240 --> 04:42.240
And also giving us an option to choose our certificate.

107
04:42.240 --> 04:47.270
So far demo, I'm going to put three very simple servers behind the load bal

108
04:47.270 --> 04:47.840
ancer.

109
04:47.840 --> 04:51.080
And they're all going to be running HTTP on port 80.

110
04:51.080 --> 04:55.040
So if the client connects to the virtual IP address of, and if we look down

111
04:55.040 --> 04:58.040
here, it's 10 dot 101 dot 0 dot five.

112
04:58.040 --> 05:01.970
And they connect on port 80, as shown right here, then the load balancer
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:58.040 --> 05:01.970
And they connect on port 80, as shown right here, then the load balancer

113
05:01.970 --> 05:02.480
effectively,

114
05:02.480 --> 05:06.840
the services engine portion of the load balancer can proxy that request over to

115
05:06.840 --> 05:08.320
one of our servers on the back end.

116
05:08.320 --> 05:11.640
And that leads us down to this next section right here, add servers.

117
05:11.640 --> 05:14.760
So here it says add IP address range or DNS name.

118
05:14.760 --> 05:20.960
So I'm going to go ahead and put 10 dot 101 dot 0 dot 51 through 10 dot 101 dot

119
05:20.960 --> 05:24.720
0 dot and 53 and click on add server.

120
05:24.720 --> 05:27.880
And then I'm going to scroll down just a little bit and check our work.

121
05:27.880 --> 05:33.360
So we should have three servers there, 10, 101, 0, 51, 52, 53.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
05:27.880 --> 05:33.360
So we should have three servers there, 10, 101, 0, 51, 52, 53.

122
05:33.360 --> 05:34.200
That looks great.

123
05:34.200 --> 05:37.680
And those represent our back end servers and we'll click on safe.

124
05:37.680 --> 05:42.420
So now that exists, we now have one virtual service and that's what's being

125
05:42.420 --> 05:43.720
reflected right here.

126
05:43.720 --> 05:47.900
So under applications, if we go back to dashboard, it's currently showing us

127
05:47.900 --> 05:48.800
our web app.

128
05:48.800 --> 05:51.480
But on the back end, there is nothing there.

129
05:51.480 --> 05:53.000
There's no servers there yet.

130
05:53.000 --> 05:56.690
And that's why it's showing up as a red or even if there was servers sitting

131
05:56.690 --> 05:57.200
there,

132
05:57.200 --> 06:01.760
it might take a few minutes for the health checks to be successful for a period
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
05:57.200 --> 06:01.760
it might take a few minutes for the health checks to be successful for a period

133
06:01.760 --> 06:06.600
of time before this starts showing something other than red having a problem.

134
06:06.600 --> 06:12.160
So I recommend that we put some servers back here at dot 51 dot 52 and 53 so

135
06:12.160 --> 06:15.320
that the services engine that's going to be used can actually validate and

136
06:15.320 --> 06:17.440
verify that those web servers exist.

137
06:17.440 --> 06:19.200
Now, here's a little secret on the back end.

138
06:19.200 --> 06:23.530
As we speak, the controller right here should be in the process of both pop

139
06:23.530 --> 06:26.120
ulating the content library with the image.

140
06:26.120 --> 06:30.280
It's about four gigs that it needs to deploy an SE and then after that's been
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
06:26.120 --> 06:30.280
It's about four gigs that it needs to deploy an SE and then after that's been

141
06:30.280 --> 06:34.480
deployed at the content library, it should also be deploying the SE to actually

142
06:34.480 --> 06:36.120
do the load balancing itself.

143
06:36.240 --> 06:39.540
And we can take a peek over at vCenter by going to the vSphere client just to

144
06:39.540 --> 06:41.560
verify if that's started already.

145
06:41.560 --> 06:45.480
So here back at the vSphere client, it is going to work.

146
06:45.480 --> 06:48.480
So it looks like it's already deployed to the content library.

147
06:48.480 --> 06:51.600
We can verify that by going to the hamburger menu up here, going to content

148
06:51.600 --> 06:56.190
library and selecting the content library and right there in OVF and OVA

149
06:56.190 --> 06:56.800
templates.

150
06:56.800 --> 07:01.200
Currently, we have the image it's going to use to deploy the SEs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
06:56.800 --> 07:01.200
Currently, we have the image it's going to use to deploy the SEs.

151
07:01.320 --> 07:04.640
So the background, the controller, place that already in the content library,

152
07:04.640 --> 07:05.440
check this out.

153
07:05.440 --> 07:08.160
It's deploying a service engine and it is done.

154
07:08.160 --> 07:12.440
So if we minimize that and go back to our inventory here in vSphere, so I'll go

155
07:12.440 --> 07:17.110
back to the inventory and go back to VMs and templates, check this out in this

156
07:17.110 --> 07:20.520
folder called AVI SE folder, which it created.

157
07:20.520 --> 07:23.080
We now have these two VMs right here.

158
07:23.080 --> 07:26.450
And then from here, if we go to one of these and right click and then go to

159
07:26.450 --> 07:28.480
edit settings, oh, it's not done yet.

160
07:28.480 --> 07:29.240
It's going to be a minute.

161
07:29.440 --> 07:33.520
So the first interface for the SEs that is just deployed is connected right
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
07:29.440 --> 07:33.520
So the first interface for the SEs that is just deployed is connected right

162
07:33.520 --> 07:35.200
here to the management network.

163
07:35.200 --> 07:39.570
And then once it's done, because we're supporting our virtual servers over here

164
07:39.570 --> 07:42.460
and as part of the data plane, that's where you said to put it, it'll have a

165
07:42.460 --> 07:45.840
second interface over here in segment 101.

166
07:45.840 --> 07:47.680
But it is not quite done.

167
07:47.680 --> 07:51.840
So while the controller is in the process of fully deploying and getting the

168
07:51.840 --> 07:56.340
service engines all ready to go, let's go ahead and put these three VMs here

169
07:56.340 --> 07:59.400
and make sure that they have the right IP address of .51.

170
07:59.400 --> 08:02.560
.52 and .53 and that they're all running web services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

170
07:59.400 --> 08:02.560
.52 and .53 and that they're all running web services.

171
08:02.560 --> 08:04.240
So we can do that right here from the vSphere clients.

172
08:04.240 --> 08:08.220
So starting off with a folder of VMs for testing, we'll right click and click

173
08:08.220 --> 08:09.720
on deploy OVF template.

174
08:09.720 --> 08:13.500
I'll click on local file and then I'm going to select some files that I can use

175
08:13.500 --> 08:15.080
for these three web servers.

176
08:15.080 --> 08:19.490
So I grabbed four files as part of an OVF template for our first web server and

177
08:19.490 --> 08:20.840
I'll click on next.

178
08:20.840 --> 08:22.560
Let's call this web 51.

179
08:22.560 --> 08:25.400
I'll place it in a folder called VMs for testing, click on next.

180
08:25.600 --> 08:28.770
And as far as who's going to be the compute resource, let's put the first one

181
08:28.770 --> 08:29.840
here on ESXi one.

182
08:29.840 --> 08:30.760
We'll click on next.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

182
08:29.840 --> 08:30.760
We'll click on next.

183
08:30.760 --> 08:32.000
We'll click on next.

184
08:32.000 --> 08:36.260
I'll give this little data store to use, click on thin provisioning, click on

185
08:36.260 --> 08:36.640
next.

186
08:36.640 --> 08:39.600
And then I want to make sure this is on the right subnet.

187
08:39.600 --> 08:42.000
So I want this on segment 101 web servers.

188
08:42.000 --> 08:42.640
Fantastic.

189
08:42.640 --> 08:44.800
We'll click on next and then click on finish.

190
08:44.800 --> 08:48.520
And then what I'll do is I'll repeat that process to deploy the two additional

191
08:48.520 --> 08:51.600
web servers, one at .52 and one at .53.

192
08:51.840 --> 08:55.880
What's also interesting to note is that if we do not have any virtual services

193
08:55.880 --> 08:56.320
set up,

194
08:56.320 --> 09:00.280
the controller won't bother deploying any service engines and also just be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

194
08:56.320 --> 09:00.280
the controller won't bother deploying any service engines and also just be

195
09:00.280 --> 09:04.280
aware that once you do the configuration, it may take 20 to 30 minutes for

196
09:04.280 --> 09:08.140
those service engines to be deployed and properly configured before they can

197
09:08.140 --> 09:09.360
start the load balancing.

198
09:09.360 --> 09:10.080
All right.

199
09:10.080 --> 09:12.600
So those little three VMs are deployed.

200
09:12.600 --> 09:15.000
They are right here, web 51, 2 and 3.

201
09:15.000 --> 09:18.760
And for my management computer, I just want to verify that I have reachability

202
09:18.760 --> 09:19.240
to them.

203
09:19.520 --> 09:22.400
And let's also verify HTTP services are running.

204
09:22.400 --> 09:27.480
So I'm going to do a curl dash capital I and HTTP colon slash slash and the IP

205
09:27.480 --> 09:29.600
address of our first one at .51.

206
09:29.600 --> 09:30.680
That looks good.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

206
09:29.600 --> 09:30.680
That looks good.

207
09:30.680 --> 09:35.760
And .52 and that looks good and .53 and that looks good.

208
09:35.760 --> 09:36.560
Fantastic.

209
09:36.560 --> 09:39.900
So if we went to a device that wasn't out there, for example, there's no one at

210
09:39.900 --> 09:41.360
54, it's just going to hang.

211
09:41.360 --> 09:41.760
All right.

212
09:41.760 --> 09:42.520
Great, great, great.

213
09:42.520 --> 09:50.780
[BLANK_AUDIO]