So now that our controller is deployed,
it's integrated with vCenter and also with NSX.
So over here is the management plane for our load balancer.
And over here is where we want to actually implement on
the data plane the load balancing.
So based on our game plan, here's what we want to do.
We want a virtual address of 10.101.0.5.
And then we're going to have our service engine function for
by the load balancing between that IP address and the various servers that are
up and available.
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
And for the web servers in the back end, we use .51, .52, and .53.
So let's head over to the interface for the controller.
And let's create a brand new virtual service with this associated virtual IP
address.
So here's the interface for the load balancer.
And before we actually create the virtual service,
let me also give you a sneak peek at what vCenter is currently looking like.
So here is the vSphere client.
We're currently looking at our content library.
We'll do a refresh here.
Notice that there's nothing at all inside of our content library yet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Notice that there's nothing at all inside of our content library yet.
Also, if we look here at running tasks, there's no activity going on.
But once we create on the controller a virtual service and set it up at that
moment,
it's going to say, you know what?
I better get to work.
And it's going to go ahead and only copy the files it needs to deploy an SE
over to the content library.
But it'll also follow that up by deploying a services engine or two that they
can use
for the actual load balancing.
So just as our friendly reminder of where we're at,
we're currently inside of vSphere at .35. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we're currently inside of vSphere at .35.
And what we're about to do is go over to the controller and set up our virtual
service.
So let's head over to the controller.
So now this is the interface for the controller again, right here.
And to create a new service, what we're going to do is on the applications tab
on the top left,
we're going to go ahead and click on virtual services here on the left.
So currently there are no virtual services.
So to create our first one, we're going to click right here on create virtual
service.
And then there's two options, basic and advanced with basic.
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
It's going to ask for some basic information to go through and for advanced.
It has many of the additional nerd knobs and options that we can set up.
So for the demo, we'll use basic.
And if we need to go into the details and modify any of the parameters, we can
do that as well.
So now it's asking, OK, for this new virtual service, which is going to be
associated with a virtual IP address.
Do you want to do this for the default cloud?
The one that we didn't configure or the one called our NSX cloud, which is the
one we want.
So we'll select the correct cloud.
That's the one we just created and we'll click right here on next.
Next is asking about the context for this new virtual service. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Next is asking about the context for this new virtual service.
And I want to isolate this just to T1 left.
So I'll choose T1 left.
That's the gateway on the left hand side, the tier one gateway and we'll click
on next.
So let's go ahead and call this our dash web dash app.
That'll be the name of the virtual service.
And then we're going to associate that virtual service with an IP address of 10
.1 0 1.0 5.
So to do that, we use the drop down here in the section for virtual service VIP
.
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
And because we don't yet have one created, we'll simply use the opportunity
right now
to click on this option called create virtual service VIP.
So we'll click there and that whisk this away for just a moment so we can
create this new virtual service IP.
And this is the name is going to give it, but we can go ahead and just go ahead
and call it
VIP for short or we could rename this to something else.
So the actual virtual IP address, we're going to call it our web app VIP.
And let me go ahead and put that in upper case as well.
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
This is going to be located in our NSX cloud within the gateway on the left
called tier one left.
And as we scroll down, it's asking us here to add whatever IP address we want
to use.
So we'll click here on add.
Once it's done, it'll be enabled.
And for the demo, I'm going to do a static IP address.
And let's use the IP address we planned on, which was 10 dot 101 dot 0 dot five
, just like that.
And with that in place, we'll click on save and then we'll click on save again.
And it is thinking about it.
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
So now we have this new virtual IP address and we can go back and edit it if we
want to,
but it's 10 dot 101 dot 0 dot five based on our plan.
And that virtual IP address will be associated with this service called our web
app.
And then for the application type, we have a few options over here on the right
.
So for application type, HTTP is the default and that's why I use this well
known port,
TCP port 80 as the well known port.
If we chose this HTTPS, it puts the well known port for HTTPS.
It's also going to give us options about choosing the right certificate to use.
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
If we choose L4, then we put in a port that we want to be associated with this
virtual service.
And this would be for things like non HTTP related services.
And there's one for L4 SSL slash TLS, which once again has the well known port
443.
And also giving us an option to choose our certificate.
So far demo, I'm going to put three very simple servers behind the load bal
ancer.
And they're all going to be running HTTP on port 80.
So if the client connects to the virtual IP address of, and if we look down
here, it's 10 dot 101 dot 0 dot five.
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
And they connect on port 80, as shown right here, then the load balancer
effectively,
the services engine portion of the load balancer can proxy that request over to
one of our servers on the back end.
And that leads us down to this next section right here, add servers.
So here it says add IP address range or DNS name.
So I'm going to go ahead and put 10 dot 101 dot 0 dot 51 through 10 dot 101 dot
0 dot and 53 and click on add server.
And then I'm going to scroll down just a little bit and check our work.
So we should have three servers there, 10, 101, 0, 51, 52, 53. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we should have three servers there, 10, 101, 0, 51, 52, 53.
That looks great.
And those represent our back end servers and we'll click on safe.
So now that exists, we now have one virtual service and that's what's being
reflected right here.
So under applications, if we go back to dashboard, it's currently showing us
our web app.
But on the back end, there is nothing there.
There's no servers there yet.
And that's why it's showing up as a red or even if there was servers sitting
there,
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
it might take a few minutes for the health checks to be successful for a period
of time before this starts showing something other than red having a problem.
So I recommend that we put some servers back here at dot 51 dot 52 and 53 so
that the services engine that's going to be used can actually validate and
verify that those web servers exist.
Now, here's a little secret on the back end.
As we speak, the controller right here should be in the process of both pop
ulating the content library with the image.
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
It's about four gigs that it needs to deploy an SE and then after that's been
deployed at the content library, it should also be deploying the SE to actually
do the load balancing itself.
And we can take a peek over at vCenter by going to the vSphere client just to
verify if that's started already.
So here back at the vSphere client, it is going to work.
So it looks like it's already deployed to the content library.
We can verify that by going to the hamburger menu up here, going to content
library and selecting the content library and right there in OVF and OVA
templates.
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
Currently, we have the image it's going to use to deploy the SEs.
So the background, the controller, place that already in the content library,
check this out.
It's deploying a service engine and it is done.
So if we minimize that and go back to our inventory here in vSphere, so I'll go
back to the inventory and go back to VMs and templates, check this out in this
folder called AVI SE folder, which it created.
We now have these two VMs right here.
And then from here, if we go to one of these and right click and then go to
edit settings, oh, it's not done yet.
It's going to be a minute.
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
So the first interface for the SEs that is just deployed is connected right
here to the management network.
And then once it's done, because we're supporting our virtual servers over here
and as part of the data plane, that's where you said to put it, it'll have a
second interface over here in segment 101.
But it is not quite done.
So while the controller is in the process of fully deploying and getting the
service engines all ready to go, let's go ahead and put these three VMs here
and make sure that they have the right IP address of .51.
.52 and .53 and that they're all running web services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
.52 and .53 and that they're all running web services.
So we can do that right here from the vSphere clients.
So starting off with a folder of VMs for testing, we'll right click and click
on deploy OVF template.
I'll click on local file and then I'm going to select some files that I can use
for these three web servers.
So I grabbed four files as part of an OVF template for our first web server and
I'll click on next.
Let's call this web 51.
I'll place it in a folder called VMs for testing, click on next.
And as far as who's going to be the compute resource, let's put the first one
here on ESXi one.
We'll click on next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll click on next.
I'll give this little data store to use, click on thin provisioning, click on
next.
And then I want to make sure this is on the right subnet.
So I want this on segment 101 web servers.
Fantastic.
We'll click on next and then click on finish.
And then what I'll do is I'll repeat that process to deploy the two additional
web servers, one at .52 and one at .53.
What's also interesting to note is that if we do not have any virtual services
set up,
the controller won't bother deploying any service engines and also just be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the controller won't bother deploying any service engines and also just be
aware that once you do the configuration, it may take 20 to 30 minutes for
those service engines to be deployed and properly configured before they can
start the load balancing.
All right.
So those little three VMs are deployed.
They are right here, web 51, 2 and 3.
And for my management computer, I just want to verify that I have reachability
to them.
And let's also verify HTTP services are running.
So I'm going to do a curl dash capital I and HTTP colon slash slash and the IP
address of our first one at .51.
That looks good. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That looks good.
And .52 and that looks good and .53 and that looks good.
Fantastic.
So if we went to a device that wasn't out there, for example, there's no one at
54, it's just going to hang.
All right.
Great, great, great.
[BLANK_AUDIO]