WEBVTT

1
00:00.000 --> 00:04.000
To help reinforce the concepts that we've taken a look at in this skill,

2
00:04.000 --> 00:07.000
I've got a customer scenario for you and here it is.

3
00:07.000 --> 00:11.500
The customer, they tried to implement load balancing with the following.

4
00:11.500 --> 00:13.300
They have a virtual IP address,

5
00:13.300 --> 00:18.780
they hopefully have a virtual IP address for HTTP services at this virtual IP

6
00:18.780 --> 00:19.400
address.

7
00:19.400 --> 00:23.480
That's over here, very similar to what we configured in the lab up to this

8
00:23.480 --> 00:24.000
point.

9
00:24.000 --> 00:27.400
Behind the scenes, they have a pool of servers over here at VLAN 5,

10
00:27.400 --> 00:30.700
at .51, .52 and .53.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.400 --> 00:30.700
at .51, .52 and .53.

11
00:30.700 --> 00:34.100
So there's these three backend servers right here on VLAN 5.

12
00:34.100 --> 00:38.700
However, after they configured it, unfortunately, when clients attempt to

13
00:38.700 --> 00:40.500
connect to that virtual IP address

14
00:40.500 --> 00:44.100
over here at 192.168.1.5,

15
00:44.100 --> 00:49.000
the clients do not receive any of the content from those backend servers.

16
00:49.000 --> 00:50.300
So here's what I invite you to do.

17
00:50.300 --> 00:54.180
Take a look at the following screenshots regarding the current configuration at

18
00:54.180 --> 00:55.400
the controller

19
00:55.400 --> 00:58.400
and identify what you believe the problem is.

20
00:58.400 --> 01:00.900
And then once you've had a chance to take a look at those screenshots
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.400 --> 01:00.900
And then once you've had a chance to take a look at those screenshots

21
01:00.900 --> 01:03.900
and determine what you feel the problem is or might be,

22
01:03.900 --> 01:07.900
join me in the follow-up video and we'll walk through the scenario together.