WEBVTT

1
00:00.000 --> 00:01.800
So here's the customer scenario.

2
00:01.800 --> 00:05.540
They recently implemented the load balancing with a VIP,

3
00:05.540 --> 00:12.080
a virtual IP address of 10.101.0.5, just like we did in the lab.

4
00:12.080 --> 00:15.720
And what they also have is three backend servers, one at .51,

5
00:15.720 --> 00:18.840
one at .52, and one at .53.

6
00:18.840 --> 00:22.280
So after setting up the virtual service with the virtual IP address,

7
00:22.280 --> 00:26.100
a customer, when they tried to connect to that IP address using this

8
00:26.100 --> 00:31.580
HTTP colon slash slash 10.101.0.5, the client,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:26.100 --> 00:31.580
HTTP colon slash slash 10.101.0.5, the client,

9
00:31.580 --> 00:35.940
instead of getting the web page for one of those servers, they get this.

10
00:35.940 --> 00:37.300
And so here's your mission.

11
00:37.300 --> 00:38.780
Should you choose to accept it?

12
00:38.780 --> 00:43.300
I'd like you to take a peek at the screenshots following this presentation

13
00:43.300 --> 00:44.420
of the customer scenario.

14
00:44.420 --> 00:48.180
And then based on those screenshots, I'd like you to identify what you think

15
00:48.180 --> 00:53.220
the problem might be with their implementation of the load balancer.

16
00:53.420 --> 00:56.820
And when you think you've identified what the problem is, join me for the

17
00:56.820 --> 00:59.500
follow up video and we'll take a look at it together.

18
00:59.500 --> 01:02.460
So I'll see you in just a few minutes when you are ready.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.500 --> 01:02.460
So I'll see you in just a few minutes when you are ready.

19
01:02.460 --> 01:12.460
[BLANK_AUDIO]