WEBVTT

1
00:00.000 --> 00:05.000
In a previous skill, we implemented the NSX Advanced Load Balancer in an NSX

2
00:05.000 --> 00:05.840
cloud.

3
00:05.840 --> 00:09.550
And I realized during that set of videos that this is just like the tip of the

4
00:09.550 --> 00:10.000
iceberg.

5
00:10.000 --> 00:14.480
So what I wanted to do in this set of videos and in this skill is once again,

6
00:14.480 --> 00:17.240
take a look at working with and configuring the Advanced Load Balancer.

7
00:17.240 --> 00:21.920
But this time, instead of just using overlay segments for our service engines

8
00:21.920 --> 00:23.960
and for the virtual servers,

9
00:23.960 --> 00:27.280
this time let's go ahead and use VLAN back segments.

10
00:27.280 --> 00:30.640
So also as a precursor to this set of videos and to the skill,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.280 --> 00:30.640
So also as a precursor to this set of videos and to the skill,

11
00:30.640 --> 00:34.130
I would strongly recommend you check out the previous skill on the Advanced

12
00:34.130 --> 00:34.800
Load Balancer

13
00:34.800 --> 00:38.320
because we're going to use a lot of the concepts and techniques that we learned

14
00:38.320 --> 00:39.200
in that previous skill

15
00:39.200 --> 00:41.440
and we're going to pick up from there and move forward.

16
00:41.440 --> 00:46.160
So I've also updated the icons regarding the controller and the service engines

17
00:46.160 --> 00:46.160
.

18
00:46.160 --> 00:49.570
So this is the icon for the controller right here for the Advanced Load Bal

19
00:49.570 --> 00:49.920
ancer.

20
00:49.920 --> 00:53.040
And these are the service engines, little SES right here.

21
00:53.040 --> 00:55.920
And over time, they may choose to change those icons again.

22
00:55.920 --> 00:59.280
And so for our game plan, I've already got the controller in place here

23
00:59.280 --> 01:02.080
on the overlay segment segment 103.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.280 --> 01:02.080
on the overlay segment segment 103.

24
01:02.080 --> 01:06.280
And for this deployment of the ESX cloud, instead of having the service engines

25
01:06.280 --> 01:07.440
also on that same

26
01:07.440 --> 01:11.740
management network for management, let's go ahead and put them on an external V

27
01:11.740 --> 01:12.720
LAN right here.

28
01:12.720 --> 01:17.680
So T1 left currently has a connection to an external VLAN, my VLAN 6.

29
01:17.680 --> 01:20.880
It also has a connection to an external VLAN VLAN 5.

30
01:20.880 --> 01:25.440
And my top of RAC switch is providing DHCP services for both of those segments.

31
01:25.440 --> 01:29.600
We're going to be using VLAN 6 as a VLAN back segment to support the new

32
01:29.600 --> 01:30.640
service engines as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:29.600 --> 01:30.640
service engines as

33
01:30.640 --> 01:34.240
they get deployed. And that'll be the management network for them.

34
01:34.240 --> 01:39.840
So the controller over here at 10.103.0.15 will communicate with the service

35
01:39.840 --> 01:41.040
engines over here

36
01:41.040 --> 01:44.960
on the management network that they're on. And that's going to be 10.6.0.

37
01:44.960 --> 01:48.080
And then they'll have DHCP assigned IP addresses here.

38
01:48.080 --> 01:52.880
And a very common deployment with NSX and the Advanced Load Balancer is when we

39
01:52.880 --> 01:53.680
have existing

40
01:53.680 --> 01:58.440
servers that are already on our topology. For example, right here on VLAN 5, if

41
01:58.440 --> 01:59.120
we put three

42
01:59.120 --> 02:02.590
servers there or 10 servers there or 15 servers there and we want to make them
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:59.120 --> 02:02.590
servers there or 10 servers there or 15 servers there and we want to make them

43
02:02.590 --> 02:03.360
available through

44
02:03.360 --> 02:07.750
the load balancer, we could absolutely leave those servers in place on that V

45
02:07.750 --> 02:08.880
LAN and then just set

46
02:08.880 --> 02:13.150
up the load balancer to provide the virtual IP address wherever we need it to

47
02:13.150 --> 02:13.600
be.

48
02:13.600 --> 02:16.400
And then clients would connect to the virtual IP address associated with the

49
02:16.400 --> 02:17.360
virtual service.

50
02:17.360 --> 02:20.640
And then the service engines would proxy that connection back and forth between

51
02:20.640 --> 02:21.520
the clients

52
02:21.520 --> 02:25.580
and wherever the servers are. So as far as a game plan here, let's put a game

53
02:25.580 --> 02:26.400
plan together.

54
02:26.400 --> 02:30.880
For our game plan, I recommend that we first of all verify and clean up our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:26.400 --> 02:30.880
For our game plan, I recommend that we first of all verify and clean up our

55
02:30.880 --> 02:32.000
existing topology,

56
02:32.000 --> 02:36.330
which is also going to include taking our existing NSX cloud that we've already

57
02:36.330 --> 02:37.040
implemented

58
02:37.040 --> 02:41.120
and removing it. So we can see the entire process from scratch and every step

59
02:41.120 --> 02:41.920
along the way.

60
02:41.920 --> 02:45.120
Because there's a few additional steps that we need to take when we have VLAN

61
02:45.120 --> 02:45.680
back segments

62
02:45.680 --> 02:49.460
where our servers are. So our first step will be to verify our existing top

63
02:49.460 --> 02:50.880
ology, make sure these

64
02:50.880 --> 02:55.630
external VLANs are accessible via this T1 left and remove the existing NSX

65
02:55.630 --> 02:56.080
cloud.

66
02:56.080 --> 02:59.160
And then what we'll do is we use the cloud connector and let's call the new

67
02:59.160 --> 03:00.880
cloud NSX cloud
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:59.160 --> 03:00.880
cloud NSX cloud

68
03:00.880 --> 03:06.240
four. And let's use VLAN six as the home for the service engines that are going

69
03:06.240 --> 03:07.040
to be deployed

70
03:07.040 --> 03:10.510
by the controller. And let's use VLAN five to support these three servers. So

71
03:10.510 --> 03:11.120
these three servers

72
03:11.120 --> 03:18.730
are .51, .52, and .53 here on VLAN five. And the vCenter server that we're

73
03:18.730 --> 03:19.600
going to be integrating

74
03:19.600 --> 03:25.360
with when we build the NSX cloud that vCenter server is still at .35 and the NS

75
03:25.360 --> 03:26.080
X manager is still

76
03:26.080 --> 03:30.900
at .21 here in my studio management network right here, the 192 168 one. So
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:26.080 --> 03:30.900
at .21 here in my studio management network right here, the 192 168 one. So

77
03:30.900 --> 03:31.920
when it comes time to do

78
03:31.920 --> 03:35.020
the cleanup in the advanced load balancer, I'm going to go ahead and leave

79
03:35.020 --> 03:35.840
those credentials

80
03:35.840 --> 03:39.460
already in place because we're going to use them once again when we create the

81
03:39.460 --> 03:40.000
new cloud.

82
03:40.000 --> 03:44.220
Also in vSphere, there is already a content library created. So we can leverage

83
03:44.220 --> 03:45.040
that also once

84
03:45.040 --> 03:50.140
again. So if the servers are right here on the 1050 network here on VLAN five,

85
03:50.140 --> 03:51.120
let's go ahead and

86
03:51.120 --> 03:55.630
place a virtual IP address associated with a virtual service. Let's place one

87
03:55.630 --> 03:59.040
out here at 23.1.2.5.

88
03:59.040 --> 04:02.180
So this network segment here between the tier zero gateway in my external
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
03:59.040 --> 04:02.180
So this network segment here between the tier zero gateway in my external

89
04:02.180 --> 04:02.560
router

90
04:02.560 --> 04:08.380
is the 23.1.2 network. So let's use .5 for the virtual IP address here. And let

91
04:08.380 --> 04:09.280
's also set up a

92
04:09.280 --> 04:13.920
virtual IP address over here on the 192 168 one network. And here for the

93
04:13.920 --> 04:15.040
virtual IP address

94
04:15.040 --> 04:19.300
associated with the virtual service, let's use the IP address and the n.5 right

95
04:19.300 --> 04:20.160
here. So we can

96
04:20.160 --> 04:24.380
have two different virtual services with two different virtual IP addresses.

97
04:24.380 --> 04:25.040
And then when

98
04:25.040 --> 04:28.390
customers connect to either of those virtual services, we'll have it tied to

99
04:28.390 --> 04:29.040
this pool of

100
04:29.040 --> 04:32.140
servers on the back end over here. If we implement like this, what we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:29.040 --> 04:32.140
servers on the back end over here. If we implement like this, what we're

101
04:32.140 --> 04:33.200
actually doing is we're

102
04:33.200 --> 04:37.940
using external VLAN five, external VLAN six, external VLAN 23. And then we're

103
04:37.940 --> 04:38.800
also going to be using

104
04:38.800 --> 04:43.280
an external segment up here on the 192 168 one network. This will also give us

105
04:43.280 --> 04:43.840
an opportunity to

106
04:43.840 --> 04:47.540
see these service engines as they're being deployed and being configured to see

107
04:47.540 --> 04:48.720
how they connect. So

108
04:48.720 --> 04:52.070
their management connection as they talk back and forth between the controller

109
04:52.070 --> 04:52.800
and the service

110
04:52.800 --> 04:58.170
engine will be on VLAN six with the 1060 address. And when we set the virtual

111
04:58.170 --> 04:59.040
IP, for example,

112
04:59.040 --> 05:02.340
over here on this network segment, we're going to have a new network connection
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:59.040 --> 05:02.340
over here on this network segment, we're going to have a new network connection

113
05:02.340 --> 05:02.880
on a service

114
05:02.880 --> 05:06.780
engine that connects to that network where the VIP is going to be and also to

115
05:06.780 --> 05:08.080
the back end servers.

116
05:08.080 --> 05:11.680
So it can do the proxying. So when a client connects to this IP address, that's

117
05:11.680 --> 05:12.480
being supported by

118
05:12.480 --> 05:15.790
one of our service engines, who's then proxying it over to one of the available

119
05:15.790 --> 05:16.640
servers on the back

120
05:16.640 --> 05:20.360
end. And the very similar thing is going to happen for this VIP up here as well

121
05:20.360 --> 05:21.280
. When customers

122
05:21.280 --> 05:25.120
connect to that virtual IP address, once again, that's being proxied by one of

123
05:25.120 --> 05:26.560
our services engine.

124
05:26.560 --> 05:29.780
And then on the back end, the service engine is going to connect to one of our

125
05:29.780 --> 05:30.960
existing servers
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
05:29.780 --> 05:30.960
existing servers

126
05:30.960 --> 05:34.470
to service that client's request. So let me clean this up just a little bit.

127
05:34.470 --> 05:35.120
And let's see if there's

128
05:35.120 --> 05:38.810
anything else that we need to plan on for implementation. So I'm going to

129
05:38.810 --> 05:40.080
rewrite the virtual IP address

130
05:40.080 --> 05:44.720
as they stand out. So this will be 23 dot 1 dot 2 dot 5. And I'll use a similar

131
05:44.720 --> 05:45.520
color right here as

132
05:45.520 --> 05:49.270
I have for the services engine. And then over here, the virtual IP address is

133
05:49.270 --> 05:50.400
going to be 192

134
05:50.400 --> 05:54.400
once you see a one dot and we use five there as well. And then on the back end,

135
05:54.400 --> 05:54.960
we'll have three

136
05:54.960 --> 05:59.790
web servers at dot 51 dot 52 and dot 53. And what this is also going to give us

137
05:59.790 --> 06:01.360
the opportunity to do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
05:59.790 --> 06:01.360
the opportunity to do

138
06:01.360 --> 06:05.600
is very likely some troubleshooting. And depending on what isn't working, we

139
06:05.600 --> 06:06.880
might be troubleshooting

140
06:06.880 --> 06:10.590
NSX. We may be troubleshooting the advanced load balancer. We may be troubles

141
06:10.590 --> 06:11.440
hooting the top of

142
06:11.440 --> 06:14.950
rack switches with the HTTP services and so forth. So it's super likely that

143
06:14.950 --> 06:16.400
troubleshooting factor

144
06:16.400 --> 06:20.550
will be part of this skill as well. All right, so with this game plan in mind,

145
06:20.550 --> 06:21.680
in our next video,

146
06:21.680 --> 06:26.680
let's start the job of verifying our existing topology and cleaning up the

147
06:26.680 --> 06:28.320
previous NSX cloud

148
06:28.320 --> 06:32.450
that we had built. So I'll see you my friend in the very next video in just a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
06:28.320 --> 06:32.450
that we had built. So I'll see you my friend in the very next video in just a

149
06:32.450 --> 06:33.120
moment.