In a previous skill, we implemented the NSX Advanced Load Balancer in an NSX
cloud.
And I realized during that set of videos that this is just like the tip of the
iceberg.
So what I wanted to do in this set of videos and in this skill is once again,
take a look at working with and configuring the Advanced Load Balancer.
But this time, instead of just using overlay segments for our service engines
and for the virtual servers,
this time let's go ahead and use VLAN back segments.
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
So also as a precursor to this set of videos and to the skill,
I would strongly recommend you check out the previous skill on the Advanced
Load Balancer
because we're going to use a lot of the concepts and techniques that we learned
in that previous skill
and we're going to pick up from there and move forward.
So I've also updated the icons regarding the controller and the service engines
.
So this is the icon for the controller right here for the Advanced Load Bal
ancer.
And these are the service engines, little SES right here.
And over time, they may choose to change those icons again.
And so for our game plan, I've already got the controller in place here
on the overlay segment segment 103. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on the overlay segment segment 103.
And for this deployment of the ESX cloud, instead of having the service engines
also on that same
management network for management, let's go ahead and put them on an external V
LAN right here.
So T1 left currently has a connection to an external VLAN, my VLAN 6.
It also has a connection to an external VLAN VLAN 5.
And my top of RAC switch is providing DHCP services for both of those segments.
We're going to be using VLAN 6 as a VLAN back segment to support the new
service engines as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
service engines as
they get deployed. And that'll be the management network for them.
So the controller over here at 10.103.0.15 will communicate with the service
engines over here
on the management network that they're on. And that's going to be 10.6.0.
And then they'll have DHCP assigned IP addresses here.
And a very common deployment with NSX and the Advanced Load Balancer is when we
have existing
servers that are already on our topology. For example, right here on VLAN 5, if
we put three
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
servers there or 10 servers there or 15 servers there and we want to make them
available through
the load balancer, we could absolutely leave those servers in place on that V
LAN and then just set
up the load balancer to provide the virtual IP address wherever we need it to
be.
And then clients would connect to the virtual IP address associated with the
virtual service.
And then the service engines would proxy that connection back and forth between
the clients
and wherever the servers are. So as far as a game plan here, let's put a game
plan together.
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
For our game plan, I recommend that we first of all verify and clean up our
existing topology,
which is also going to include taking our existing NSX cloud that we've already
implemented
and removing it. So we can see the entire process from scratch and every step
along the way.
Because there's a few additional steps that we need to take when we have VLAN
back segments
where our servers are. So our first step will be to verify our existing top
ology, make sure these
external VLANs are accessible via this T1 left and remove the existing NSX
cloud.
And then what we'll do is we use the cloud connector and let's call the new
cloud NSX cloud WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
cloud NSX cloud
four. And let's use VLAN six as the home for the service engines that are going
to be deployed
by the controller. And let's use VLAN five to support these three servers. So
these three servers
are .51, .52, and .53 here on VLAN five. And the vCenter server that we're
going to be integrating
with when we build the NSX cloud that vCenter server is still at .35 and the NS
X manager is still
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
at .21 here in my studio management network right here, the 192 168 one. So
when it comes time to do
the cleanup in the advanced load balancer, I'm going to go ahead and leave
those credentials
already in place because we're going to use them once again when we create the
new cloud.
Also in vSphere, there is already a content library created. So we can leverage
that also once
again. So if the servers are right here on the 1050 network here on VLAN five,
let's go ahead and
place a virtual IP address associated with a virtual service. Let's place one
out here at 23.1.2.5.
So this network segment here between the tier zero gateway in my external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this network segment here between the tier zero gateway in my external
router
is the 23.1.2 network. So let's use .5 for the virtual IP address here. And let
's also set up a
virtual IP address over here on the 192 168 one network. And here for the
virtual IP address
associated with the virtual service, let's use the IP address and the n.5 right
here. So we can
have two different virtual services with two different virtual IP addresses.
And then when
customers connect to either of those virtual services, we'll have it tied to
this pool of
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
servers on the back end over here. If we implement like this, what we're
actually doing is we're
using external VLAN five, external VLAN six, external VLAN 23. And then we're
also going to be using
an external segment up here on the 192 168 one network. This will also give us
an opportunity to
see these service engines as they're being deployed and being configured to see
how they connect. So
their management connection as they talk back and forth between the controller
and the service
engine will be on VLAN six with the 1060 address. And when we set the virtual
IP, for example,
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
over here on this network segment, we're going to have a new network connection
on a service
engine that connects to that network where the VIP is going to be and also to
the back end servers.
So it can do the proxying. So when a client connects to this IP address, that's
being supported by
one of our service engines, who's then proxying it over to one of the available
servers on the back
end. And the very similar thing is going to happen for this VIP up here as well
. When customers
connect to that virtual IP address, once again, that's being proxied by one of
our services engine.
And then on the back end, the service engine is going to connect to one of our
existing servers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
existing servers
to service that client's request. So let me clean this up just a little bit.
And let's see if there's
anything else that we need to plan on for implementation. So I'm going to
rewrite the virtual IP address
as they stand out. So this will be 23 dot 1 dot 2 dot 5. And I'll use a similar
color right here as
I have for the services engine. And then over here, the virtual IP address is
going to be 192
once you see a one dot and we use five there as well. And then on the back end,
we'll have three
web servers at dot 51 dot 52 and dot 53. And what this is also going to give us
the opportunity to do WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the opportunity to do
is very likely some troubleshooting. And depending on what isn't working, we
might be troubleshooting
NSX. We may be troubleshooting the advanced load balancer. We may be troubles
hooting the top of
rack switches with the HTTP services and so forth. So it's super likely that
troubleshooting factor
will be part of this skill as well. All right, so with this game plan in mind,
in our next video,
let's start the job of verifying our existing topology and cleaning up the
previous NSX cloud
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
that we had built. So I'll see you my friend in the very next video in just a
moment.