So for this scenario, the first thing we might want to do, if we have the
option to do it, is to verify the customer's experience.
So here we're going to HTTP colon slash slash 10 10105 click on reload and sure
enough, we are not able to go ahead and access those servers.
Now also we might want to check on the back end.
Those servers are up.
So because they're on the same subnet, let's go ahead and just go to 51 and
that works and 52.
That's up and 53 and that's up just to verify that those servers on the back WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's up and 53 and that's up just to verify that those servers on the back
end really are up.
So now that we know those servers are up, let's go take a look from the
controllers perspective and see what's going on with that virtual service.
So here at the controller, we did a quick peek at our service engines and looks
like they're all good to go.
So the service engines don't look like a problem.
And so if we go up to applications and we take a look at our virtual services,
here is our virtual service called web app.
And it's health is 84 with a service port. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And it's health is 84 with a service port.
Oh, that's the problem right there.
They're not using the default port for HTTP.
So I bet if we try going to 80 80, that might work.
In fact, let's just test that real quick.
If that's the port associated with the virtual service, let's see if that'll
get us to those back end servers and sure enough, I just went to HTTP colon
slash slash 10 dot one zero one dot zero dot five colon 80 80.
And if I do a control shift refresh there.
Yeah, it's cycling through all of them.
So they just have the non default port for HTTP associated with their virtual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So they just have the non default port for HTTP associated with their virtual
service.
So let's fix it.
Let's go ahead and click on the little pencil for edit.
So here are the settings for the virtual service called our web app.
And if we scroll down here is the service port.
So what we could do here is just change it back to 80.
So that's the well known port for HTTP.
And if that was the only problem, we are good to go.
So let's go ahead and save that change.
So we'll click on save.
Now that here's the virtual service, the service port is 80.
This health score, by the way, is getting better and better over time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This health score, by the way, is getting better and better over time.
And that's because everything on the back end is working.
So let's bring back our browser.
And this time we're not going to go to port 80 80 was use the default port of
80 by just not putting any port at all pressing enter.
And there's a website now is that cached?
I don't know.
Let's do a control shift R and R and R and look at that.
That's great.
We're just round robbing through those web servers on the back end because we
set the policy for the pool to be round Robin.
And because we stopped logging enabled, if we went back to the dashboard and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And because we stopped logging enabled, if we went back to the dashboard and
selected our virtual service right here, we'll click on our web app.
And then we click here on logs and I'll say I want to see all the logs, both
significant and non significant.
Then we can go down and grab one of those.
In fact, let me go ahead and collapse the right hand column there and we'll
click on view for this one right here.
And that's once again showing us all the details regarding that client
connection.
So the client was coming from dot 151 to the virtual IP address, the load bal
ancer courtesy of the service engine proxy that over to the server in this one
that we're looking at is at dot 52. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that we're looking at is at dot 52.
And this is the service engine that did the work.
So thanks for joining me in this set of videos for getting the advanced load
balancer from VMware and also you my friend in another set of videos very, very
soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.
[BLANK_AUDIO]