WEBVTT 1 00:00.000 --> 00:03.200 So for this scenario, the first thing we might want to do, if we have the 2 00:03.200 --> 00:06.500 option to do it, is to verify the customer's experience. 3 00:06.500 --> 00:13.460 So here we're going to HTTP colon slash slash 10 10105 click on reload and sure 4 00:13.460 --> 00:17.400 enough, we are not able to go ahead and access those servers. 5 00:17.400 --> 00:19.400 Now also we might want to check on the back end. 6 00:19.400 --> 00:20.800 Those servers are up. 7 00:20.800 --> 00:26.020 So because they're on the same subnet, let's go ahead and just go to 51 and 8 00:26.020 --> 00:27.800 that works and 52. 9 00:27.800 --> 00:32.790 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 9 00:27.800 --> 00:32.790 That's up and 53 and that's up just to verify that those servers on the back 10 00:32.790 --> 00:34.200 end really are up. 11 00:34.200 --> 00:37.480 So now that we know those servers are up, let's go take a look from the 12 00:37.480 --> 00:41.800 controllers perspective and see what's going on with that virtual service. 13 00:41.800 --> 00:46.100 So here at the controller, we did a quick peek at our service engines and looks 14 00:46.100 --> 00:47.800 like they're all good to go. 15 00:47.800 --> 00:50.400 So the service engines don't look like a problem. 16 00:50.400 --> 00:55.090 And so if we go up to applications and we take a look at our virtual services, 17 00:55.090 --> 00:57.400 here is our virtual service called web app. 18 00:57.400 --> 01:01.200 And it's health is 84 with a service port. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:57.400 --> 01:01.200 And it's health is 84 with a service port. 19 01:01.200 --> 01:02.400 Oh, that's the problem right there. 20 01:02.400 --> 01:05.800 They're not using the default port for HTTP. 21 01:05.800 --> 01:09.000 So I bet if we try going to 80 80, that might work. 22 01:09.000 --> 01:10.400 In fact, let's just test that real quick. 23 01:10.400 --> 01:14.460 If that's the port associated with the virtual service, let's see if that'll 24 01:14.460 --> 01:19.540 get us to those back end servers and sure enough, I just went to HTTP colon 25 01:19.540 --> 01:23.200 slash slash 10 dot one zero one dot zero dot five colon 80 80. 26 01:23.200 --> 01:26.000 And if I do a control shift refresh there. 27 01:26.000 --> 01:28.000 Yeah, it's cycling through all of them. 28 01:28.000 --> 01:32.610 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 28 01:28.000 --> 01:32.610 So they just have the non default port for HTTP associated with their virtual 29 01:32.610 --> 01:33.400 service. 30 01:33.400 --> 01:34.400 So let's fix it. 31 01:34.400 --> 01:37.000 Let's go ahead and click on the little pencil for edit. 32 01:37.000 --> 01:40.000 So here are the settings for the virtual service called our web app. 33 01:40.000 --> 01:43.400 And if we scroll down here is the service port. 34 01:43.400 --> 01:46.800 So what we could do here is just change it back to 80. 35 01:46.800 --> 01:49.200 So that's the well known port for HTTP. 36 01:49.200 --> 01:52.000 And if that was the only problem, we are good to go. 37 01:52.000 --> 01:53.400 So let's go ahead and save that change. 38 01:53.400 --> 01:54.400 So we'll click on save. 39 01:54.400 --> 01:58.200 Now that here's the virtual service, the service port is 80. 40 01:58.200 --> 02:01.800 This health score, by the way, is getting better and better over time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 01:58.200 --> 02:01.800 This health score, by the way, is getting better and better over time. 41 02:01.800 --> 02:04.200 And that's because everything on the back end is working. 42 02:04.200 --> 02:06.200 So let's bring back our browser. 43 02:06.200 --> 02:10.520 And this time we're not going to go to port 80 80 was use the default port of 44 02:10.520 --> 02:13.200 80 by just not putting any port at all pressing enter. 45 02:13.200 --> 02:15.200 And there's a website now is that cached? 46 02:15.200 --> 02:15.600 I don't know. 47 02:15.600 --> 02:19.200 Let's do a control shift R and R and R and look at that. 48 02:19.200 --> 02:19.800 That's great. 49 02:19.800 --> 02:23.760 We're just round robbing through those web servers on the back end because we 50 02:23.760 --> 02:26.600 set the policy for the pool to be round Robin. 51 02:26.600 --> 02:30.760 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 51 02:26.600 --> 02:30.760 And because we stopped logging enabled, if we went back to the dashboard and 52 02:30.760 --> 02:34.200 selected our virtual service right here, we'll click on our web app. 53 02:34.200 --> 02:38.230 And then we click here on logs and I'll say I want to see all the logs, both 54 02:38.230 --> 02:40.000 significant and non significant. 55 02:40.000 --> 02:42.000 Then we can go down and grab one of those. 56 02:42.000 --> 02:45.080 In fact, let me go ahead and collapse the right hand column there and we'll 57 02:45.080 --> 02:47.000 click on view for this one right here. 58 02:47.000 --> 02:49.720 And that's once again showing us all the details regarding that client 59 02:49.720 --> 02:50.400 connection. 60 02:50.400 --> 02:54.870 So the client was coming from dot 151 to the virtual IP address, the load bal 61 02:54.870 --> 02:59.400 ancer courtesy of the service engine proxy that over to the server in this one 62 02:59.400 --> 03:01.000 that we're looking at is at dot 52. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 02:59.400 --> 03:01.000 that we're looking at is at dot 52. 63 03:01.000 --> 03:03.800 And this is the service engine that did the work. 64 03:03.800 --> 03:07.570 So thanks for joining me in this set of videos for getting the advanced load 65 03:07.570 --> 03:11.900 balancer from VMware and also you my friend in another set of videos very, very 66 03:11.900 --> 03:12.400 soon. 67 03:12.400 --> 03:16.950 Until then, I hope this has been informative and I'd like to thank you for 68 03:16.950 --> 03:17.400 viewing. 69 03:17.400 --> 03:26.760 [BLANK_AUDIO]