WEBVTT 1 00:00.000 --> 00:03.360 In this video, we're going to cover yet another first hop residency protocol 2 00:03.360 --> 00:04.320 with its configuration 3 00:04.320 --> 00:09.080 and verification. In this time, we're going to use GLBP. That's the gateway, 4 00:09.080 --> 00:10.720 load balancing protocol. 5 00:10.720 --> 00:14.910 And the two major roles, this is based on priority, is we're going to have the 6 00:14.910 --> 00:16.160 AVG. And the AVG has 7 00:16.160 --> 00:19.940 a few responsibilities, including it's going to respond to our requests for 8 00:19.940 --> 00:21.120 clients that are asking, 9 00:21.120 --> 00:23.720 "Hey, what is the layer to address for our default gateway?" And regarding 10 00:23.720 --> 00:24.640 their response, it gives. 11 00:24.640 --> 00:28.710 If we have three routers, for example, in our GLBP group, it could go ahead and 12 00:28.710 --> 00:29.840 hand out, for example, 13 00:29.840 --> 00:37.280 1010 and then 1011 and 1012. If those were the virtualized MAC addresses that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.840 --> 00:37.280 1010 and then 1011 and 1012. If those were the virtualized MAC addresses that 14 00:37.280 --> 00:37.600 each of the 15 00:37.600 --> 00:40.580 routers were using, and where do they get those virtual MAC addresses? The 16 00:40.580 --> 00:42.240 device acting as the AVG 17 00:42.240 --> 00:47.430 also assigned the AVFs, as the active virtual forwarders, their respective 18 00:47.430 --> 00:49.280 virtual MAC addresses. 19 00:49.280 --> 00:52.660 So the AVG is the brains behind the operation that's assigning out these 20 00:52.660 --> 00:54.160 virtual MAC addresses to the, 21 00:54.160 --> 00:57.310 in this case, three routers that would be participating on that segment. Let me 22 00:57.310 --> 00:58.320 go ahead and draw another 23 00:58.320 --> 01:02.290 router here. We'll put router 9, connect it in. And then whichever device is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:58.320 --> 01:02.290 router here. We'll put router 9, connect it in. And then whichever device is 24 01:02.290 --> 01:03.200 acting as the AVG 25 01:03.200 --> 01:06.920 is going to be getting the ARP requests for the virtualized IP address, and 26 01:06.920 --> 01:07.760 responding back to the 27 01:07.760 --> 01:11.340 client with one, in this case, one of the three MAC addresses to provide load 28 01:11.340 --> 01:12.960 balancing. So a third 29 01:12.960 --> 01:16.540 of the clients could be using one physical gateway, another, a third could be 30 01:16.540 --> 01:17.280 using a different 31 01:17.280 --> 01:20.820 physical gateway, and yet a third group of computers could be using a third 32 01:20.820 --> 01:22.160 virtual gateway. And it's 33 01:22.160 --> 01:26.590 all due to which MAC address they got back from the AVG regarding their query. 34 01:26.590 --> 01:27.600 How do I reach 35 01:27.600 --> 01:31.840 .99? What's the layer to address for .99? Also, gateway load balancing protocol WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:27.600 --> 01:31.840 .99? What's the layer to address for .99? Also, gateway load balancing protocol 36 01:31.840 --> 01:32.400 has some fault 37 01:32.400 --> 01:37.750 tolerance mechanisms for the AVG itself. So if the AVG goes away, for example, 38 01:37.750 --> 01:38.480 let's say it's R1, 39 01:38.480 --> 01:42.060 that's the AVG, and it goes away, and the other members in the group realize, 40 01:42.060 --> 01:43.200 hey, the AVG is gone, 41 01:43.200 --> 01:46.460 they'll have a new election, and they'll point a new one. Or in the event, we 42 01:46.460 --> 01:47.600 have one of our routers. 43 01:47.600 --> 01:52.480 It has the virtual MAC address, 1011, and it goes away, that MAC address, 44 01:52.480 --> 01:53.120 because it's already in the 45 01:53.120 --> 01:56.750 cache of our PCs. If that's already being used, another member in the group 46 01:56.750 --> 01:57.520 will be given the 47 01:57.520 --> 02:01.370 responsibility of forwarding based on that MAC address. So the goal is that no WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 01:57.520 --> 02:01.370 responsibility of forwarding based on that MAC address. So the goal is that no 48 02:01.370 --> 02:03.040 matter what happens to 49 02:03.040 --> 02:06.950 just a single router or a portion of our routers, if we have at least one 50 02:06.950 --> 02:08.560 router standing with gateway 51 02:08.560 --> 02:12.050 load balancing protocol, it can still provide that fault tolerance as the 52 02:12.050 --> 02:13.120 default gateway function. 53 02:13.760 --> 02:17.920 So as far as our game plan for gateway load balancing protocol, let's do the 54 02:17.920 --> 02:20.080 following. Let's configure 55 02:20.080 --> 02:25.630 R2 as the AVG. In the way we can do that, it's just simply configure it first. 56 02:25.630 --> 02:26.720 And if we want to also 57 02:26.720 --> 02:29.570 give it a higher priority, that would also confirm it keeps it once the other 58 02:29.570 --> 02:31.120 routers are in place. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 02:29.570 --> 02:31.120 routers are in place. So 59 02:31.120 --> 02:36.300 on R2, we'll make it the AVG by giving a priority of 105. Let's also set it pre 60 02:36.300 --> 02:37.440 -empt. And then on 61 02:37.440 --> 02:41.840 R1, we'll give it a priority of 99, and we'll also enable pre-empt there. Now, 62 02:41.840 --> 02:42.800 even though R2 is 63 02:42.800 --> 02:45.840 going to be the active virtual gateway and R1 is not, these two routers are 64 02:45.840 --> 02:47.280 also going to be acting 65 02:47.280 --> 02:51.420 as an AVF, an active virtual forwarder. And it's part of that this might have a 66 02:51.420 --> 02:52.480 virtual MAC address of 67 02:52.480 --> 02:57.220 1010 and down here a virtual MAC address of 1011. And as the active virtual 68 02:57.220 --> 02:58.480 gateway sees our request 69 02:58.480 --> 03:01.810 coming in, trying to resolve that .99 address and find out what the layer 2 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 02:58.480 --> 03:01.810 coming in, trying to resolve that .99 address and find out what the layer 2 70 03:01.810 --> 03:02.800 address is for it, 71 03:02.800 --> 03:06.720 the active virtual gateway can respond back with, first of all, like 1010, 72 03:06.720 --> 03:07.680 which would mean 73 03:07.680 --> 03:12.160 R2 itself is going to be forwarding that traffic, or I can respond with 1011, 74 03:12.160 --> 03:12.560 which would mean 75 03:12.560 --> 03:15.540 that R1 is going to be forwarding the traffic. And it can go ahead and round 76 03:15.540 --> 03:16.480 robin between the two. 77 03:16.480 --> 03:19.730 And that's how we can accomplish load balancing with gateway load balancing 78 03:19.730 --> 03:21.680 protocol and have the 79 03:21.680 --> 03:25.250 redundancy as well. So if either of the routers fails, the other one will pick 80 03:25.250 --> 03:26.080 up the slack and keep 81 03:26.080 --> 03:29.510 on going. So with that in mind, let's go back to the lab environment and let's 82 03:29.510 --> 03:30.080 configure WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 03:29.510 --> 03:30.080 configure 83 03:30.080 --> 03:34.960 R2 and R1 for gateway load balancing protocol. So here in the lab environment, 84 03:34.960 --> 03:36.400 in my notepad document, 85 03:36.400 --> 03:39.250 just to make it a little bit more convenient for the implementation error, I 86 03:39.250 --> 03:40.400 have a section for 87 03:40.400 --> 03:45.760 GLBP. And so on R1, we're going to default interface gig 00, and I then go in 88 03:45.760 --> 03:46.640 and put its IP 89 03:46.640 --> 03:51.950 address back on, which is 101201. And then we're going to set up GLPB group 90 03:51.950 --> 03:53.280 number one. So we're going to 91 03:53.280 --> 03:57.820 specify the virtual IP address, the priority, and also specify preempt. And 92 03:57.820 --> 03:59.120 then in R2, very similar 93 03:59.120 --> 04:02.750 treatment except we're going to go ahead and give it a priority of 105. The IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 03:59.120 --> 04:02.750 treatment except we're going to go ahead and give it a priority of 105. The IP 94 04:02.750 --> 04:03.440 address on the 95 04:03.440 --> 04:08.080 actual interface itself for R2 is going to be 101202. And the priority we're 96 04:08.080 --> 04:09.120 going to specify for 97 04:09.120 --> 04:12.750 gateway load balancing protocol is going to be 105. So with that in mind, let 98 04:12.750 --> 04:13.840 me go ahead and copy 99 04:13.840 --> 04:18.670 the config here for R1. We'll right-click copy, go to the right router, there's 100 04:18.670 --> 04:19.760 R1, and we'll paste it 101 04:19.760 --> 04:23.210 in. And we'll do the same thing for R2. So we'll go ahead and copy the config 102 04:23.210 --> 04:24.640 here for R2, copy, 103 04:24.640 --> 04:28.160 and then before we paste it in, I noticed here that we had a state change going 104 04:28.160 --> 04:29.360 from speak to active. 105 04:29.360 --> 04:35.760 So R1 is the AVG. So here on R1, if we did a show, GLBP, I'm pressed enter, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 105 04:29.360 --> 04:35.760 So R1 is the AVG. So here on R1, if we did a show, GLBP, I'm pressed enter, 106 04:35.760 --> 04:36.320 here's showing the 107 04:36.320 --> 04:40.660 state as active, here's the virtual IP address, preempt is enabled, active is 108 04:40.660 --> 04:41.760 local, we don't have a 109 04:41.760 --> 04:45.780 standby set up yet, we have one forwarder, one active virtual forwarder, and 110 04:45.780 --> 04:47.120 that's R1 itself. 111 04:47.120 --> 04:51.330 And state is active, and here's the MAC address that it's using for its active 112 04:51.330 --> 04:52.080 virtual forwarding 113 04:52.080 --> 04:57.590 function, it's 0, 0, 0, 7, B400, ending in 0, 1, 0, 1. The actual MAC address 114 04:57.590 --> 04:58.800 is not identical to what 115 04:58.800 --> 05:02.660 it was with the RRP, however the last four characters happened to be. So this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 04:58.800 --> 05:02.660 it was with the RRP, however the last four characters happened to be. So this 116 05:02.660 --> 05:04.000 is 0, 1, 0, 1. 117 05:04.000 --> 05:08.800 So once we configure R2, so I'll go ahead and copy that back into my buffer, 118 05:08.800 --> 05:09.680 and we'll go to R2, 119 05:09.680 --> 05:12.870 and we'll paste that in, and we'll give that a moment to settle. Here for 120 05:12.870 --> 05:13.840 Gateway Load Balancing 121 05:13.840 --> 05:19.880 Protocol, it went from state speak to active. So here, if we did a show GLBP, I 122 05:19.880 --> 05:20.640 'm pressed enter, 123 05:20.640 --> 05:23.840 and then we have another state change here, let me go ahead and do that show GL 124 05:23.840 --> 05:24.560 BP again. 125 05:24.560 --> 05:28.710 So here's showing the state as active, here's the virtual IP address, the 126 05:28.710 --> 05:30.000 active router is local, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 05:30.000 --> 05:35.000 the standby is over at 10, 12, 0, 1, our priority is 105, the waiting, and that 128 05:35.000 --> 05:36.400 's going to impact the 129 05:36.400 --> 05:40.460 load balancing ratio. The waiting is at 100 by default, the load balancing 130 05:40.460 --> 05:41.520 mechanism is round 131 05:41.520 --> 05:46.450 Robin, and the group members are 10, 12, 0, 1, with that corresponding layer to 132 05:46.450 --> 05:47.280 address on that 133 05:47.280 --> 05:52.130 real interface, that's R1, and ourselves at 10, 12, 0, 2, with that MAC address 134 05:52.130 --> 05:53.200 associated with that 135 05:53.200 --> 05:57.600 interface. So in R2, it's its gig 1/0 interface. And here's showing us there's 136 05:57.600 --> 05:58.640 two forwarders. So we 137 05:58.640 --> 06:02.500 have forwarder 1, disappointing this MAC address, and the owner has the MAC WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 137 05:58.640 --> 06:02.500 have forwarder 1, disappointing this MAC address, and the owner has the MAC 138 06:02.500 --> 06:03.840 address of the one ending in 139 06:03.840 --> 06:07.480 0, 0, 8, so that equates to R1, and forwarder 2 is using this virtual MAC 140 06:07.480 --> 06:11.120 address, 0, 0, 7, B400, 0, 0, 0, 1, 0, 2, 141 06:11.120 --> 06:16.630 and this is the actual real MAC address on R2 on its gig 1/0 interface. So just 142 06:16.630 --> 06:17.440 to test this out, 143 06:17.440 --> 06:22.470 if we had multiple clients here on this network segment, the 10, 12, 0 network, 144 06:22.470 --> 06:23.280 that were making our 145 06:23.280 --> 06:28.830 request for .99, the active virtual gateway would be handing out first the MAC 146 06:28.830 --> 06:30.880 address of 0, 1, 0, 1, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 06:28.830 --> 06:30.880 address of 0, 1, 0, 1, 147 06:30.880 --> 06:33.750 and then for the next request would be 0, 1, 0, 2, and then it would round 148 06:33.750 --> 06:35.440 Robin back to 0, 1, 0, 1. 149 06:35.440 --> 06:39.500 Now to confirm that, what we could do is go to PC12, and here on PC12, let's go 150 06:39.500 --> 06:40.560 ahead and do a show 151 06:40.560 --> 06:43.550 ARP, look at the ARP cache, the ARP cache is empty, that's convenient, if it 152 06:43.550 --> 06:44.960 wasn't, we could do a clear 153 06:44.960 --> 06:49.480 ARP, and that would remove everything. So here let's go ahead and do a ping to 154 06:49.480 --> 06:50.880 4.4.4.4, which will 155 06:50.880 --> 06:56.070 cause PC12 to make an ARP request and let's do a show ARP and press center. So 156 06:56.070 --> 06:57.040 there's the MAC address 157 06:57.040 --> 07:01.660 that was given 0, 1, 0, 1. So if we clear the ARP cache, the clear ARP, and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 06:57.040 --> 07:01.660 that was given 0, 1, 0, 1. So if we clear the ARP cache, the clear ARP, and 158 07:01.660 --> 07:02.640 then we did a ping again, 159 07:02.640 --> 07:06.010 it's going to make an ARP request again for its default gateway address, but 160 07:06.010 --> 07:06.480 this time, 161 07:06.480 --> 07:10.380 with the round Robin from the active virtual gateway, it should be handing out 162 07:10.380 --> 07:11.920 0, 1, 0, 2. We can 163 07:11.920 --> 07:16.770 verify that with a show ARP, press center, and sure enough, 0, 1, 0, 2. Also if 164 07:16.770 --> 07:17.760 we looked at the 165 07:17.760 --> 07:21.590 switch MAC address table, which we should do right now, let's go to switch 1, 166 07:21.590 --> 07:22.320 and here at the switch, 167 07:22.320 --> 07:26.050 let's do a show MAC address table, press center. Even as here, we have this MAC 168 07:26.050 --> 07:27.120 address associated with 169 07:27.120 --> 07:32.460 gig 0/1, and this MAC address, ending in 0, 1, 0, 2, associated with gig 0/2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 169 07:27.120 --> 07:32.460 gig 0/1, and this MAC address, ending in 0, 1, 0, 2, associated with gig 0/2. 170 07:32.460 --> 07:33.840 So currently the PC, 171 07:33.840 --> 07:38.120 let's go back to PC12, it's currently using 0, 1, 0, 2. So if we go back to 172 07:38.120 --> 07:39.680 switch, 0, 1, 0, 2, 173 07:39.680 --> 07:43.670 is associated with gig 0, 2, which goes out to router 2. So if we were to tell 174 07:43.670 --> 07:44.560 router 2 on its 175 07:44.560 --> 07:47.660 interface, let's do that real quick. So if we're going over to R2 on gig 1, 0, 176 07:47.660 --> 07:48.880 and we shut it down, 177 07:48.880 --> 07:52.880 R1 would recognize I'm no longer seeing messages over this common Ethernet 178 07:52.880 --> 07:53.920 segment, and it would 179 07:53.920 --> 07:58.130 take over responsibility for that MAC address. Because R2 not only is going to 180 07:58.130 --> 07:59.360 lose its role as the 181 07:59.360 --> 08:02.820 active virtual gateway, because that interface is shut down, but it'll also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 07:59.360 --> 08:02.820 active virtual gateway, because that interface is shut down, but it'll also 182 08:02.820 --> 08:03.600 lose its role as an 183 08:03.600 --> 08:08.230 active virtual forwarder, because it's no longer reachable. So let's go to R2's 184 08:08.230 --> 08:10.560 gig 1, 0. So go to R2, 185 08:10.560 --> 08:14.320 go to configuration mode for interface gig 1/0, and let me confirm we got the 186 08:14.320 --> 08:14.880 right interface, 187 08:14.880 --> 08:18.500 yeah gig 1, 0, and let's go into a shutdown. So while that's shutting down, let 188 08:18.500 --> 08:19.040 's also go back to 189 08:19.040 --> 08:24.800 PC12. This is a verify that we still have that in our ARP cache. Oh, it's going 190 08:24.800 --> 08:26.400 to be expiring 3 seconds. 191 08:26.400 --> 08:33.010 Well, let's go ahead and do a ping to 4444, and let's do a show ARP, and it was WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 191 08:26.400 --> 08:33.010 Well, let's go ahead and do a ping to 4444, and let's do a show ARP, and it was 192 08:33.010 --> 08:34.800 given 0, 1, 0, 1. 193 08:34.800 --> 08:38.250 So now that R2 is out of the picture, let's go ahead and clear ARP, and let's 194 08:38.250 --> 08:39.040 ping again, 195 08:39.040 --> 08:43.390 and let's do a show ARP, and I hit clear ARP by default. So let's go ahead and 196 08:43.390 --> 08:44.160 let's try that 197 08:44.160 --> 08:49.030 again, let's do a ping to 4.4.4. Let's do a show ARP, and so now currently has 198 08:49.030 --> 08:51.360 the MAC address of 0, 1, 0, 2. 199 08:51.360 --> 08:55.570 Let's go ahead and clear the ARP cache, and then ping again, which will once 200 08:55.570 --> 08:56.400 again cause us to do an 201 08:56.400 --> 08:59.270 ARP request in the background, then we'll do a show ARP, and now we have the 202 08:59.270 --> 09:00.800 MAC address of 0, 1, 0, 1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 202 08:59.270 --> 09:00.800 MAC address of 0, 1, 0, 1. 203 09:00.800 --> 09:05.070 So at the moment, R1 is supporting not only the role of the active virtual 204 09:05.070 --> 09:05.600 gateway, 205 09:05.600 --> 09:09.930 responding to ARP requests, but it's also responding for both virtual forward 206 09:09.930 --> 09:11.440 ers that had been present, 207 09:11.440 --> 09:17.230 and now that R2 is gone, R1 is carrying all the weight. So if we go to switch 1 208 09:17.230 --> 09:18.480 , and we do a show MAC 209 09:18.480 --> 09:22.610 address table here, notice that these two MAC addresses are both associated 210 09:22.610 --> 09:23.840 with gig 0/1, 211 09:23.840 --> 09:27.660 that's the port going down to R1, who's currently taking responsibility for 212 09:27.660 --> 09:28.960 both of those MAC addresses. 213 09:28.960 --> 09:34.330 And here on R1, if we do a show, GLBP in present, or it is the active virtual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 213 09:28.960 --> 09:34.330 And here on R1, if we do a show, GLBP in present, or it is the active virtual 214 09:34.330 --> 09:34.880 gateway, 215 09:34.880 --> 09:39.040 there are two forwarders, and even though R2 is no longer reachable or 216 09:39.040 --> 09:39.600 available, 217 09:39.600 --> 09:42.960 we are doing the forwarding for both. And that's why I right here shows as 218 09:42.960 --> 09:44.080 forwarder 1, 219 09:44.080 --> 09:49.050 that this router R1 is active, and for forwarder 2, it's also active. So if we 220 09:49.050 --> 09:50.400 were to go to R2, 221 09:50.400 --> 09:54.240 let's go ahead and do a no-shot on the center face, and because preempt is 222 09:54.240 --> 09:54.960 enabled, 223 09:54.960 --> 09:59.290 and it has a higher priority, suffer a few moments, we'll do a show GLBP, it 224 09:59.290 --> 10:01.200 shows there's two forwarders, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 224 09:59.290 --> 10:01.200 shows there's two forwarders, 225 10:01.200 --> 10:04.870 and for forwarder 1, the state is listen, that's on this local router, and if 226 10:04.870 --> 10:06.160 we go down to forwarder 2, 227 10:06.160 --> 10:10.250 the state is active. Effectively what that means is that router 2, the one we 228 10:10.250 --> 10:11.520 're currently looking at, 229 10:11.520 --> 10:16.140 is forwarding for this virtual MAC address right here, and router 1 is forward 230 10:16.140 --> 10:17.280 ing for this virtual 231 10:17.280 --> 10:21.100 MAC address right here. And if we went to R1, and in R1, if we did a show GLBP 232 10:21.100 --> 10:22.240 in present center, 233 10:22.240 --> 10:26.090 here showing that for forwarder 1, it's active, meaning it's forwarding based 234 10:26.090 --> 10:27.120 on that MAC address, 235 10:27.120 --> 10:32.860 0101, and forwarder 2, R1 is acting as a state of listen. That means R2 is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 235 10:27.120 --> 10:32.860 0101, and forwarder 2, R1 is acting as a state of listen. That means R2 is 236 10:32.860 --> 10:34.160 actually doing the forwarding 237 10:34.160 --> 10:37.980 for that second forwarder group with the MAC of 0102. And we can verify that 238 10:37.980 --> 10:39.040 also on the switch by 239 10:39.040 --> 10:42.500 going to the switch, and how the switch doing a show MAC address table, and 240 10:42.500 --> 10:44.720 indeed 0101 goes out 241 10:44.720 --> 10:49.690 to the port where R1 is, and 0102 goes out to the port where R2 is. And in the 242 10:49.690 --> 10:50.560 event that we had a 243 10:50.560 --> 10:56.180 failure on R1, so let's go to R1, did a config T, interface gig, 0/0, we'll do 244 10:56.180 --> 10:56.880 a shutdown, 245 10:57.280 --> 11:00.790 so now that it's down, if we go over to R2, or a moment ago, it was doing a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 245 10:57.280 --> 11:00.790 so now that it's down, if we go over to R2, or a moment ago, it was doing a 246 11:00.790 --> 11:02.400 listen state for forwarder 247 11:02.400 --> 11:06.130 1 and being active from forwarder 2, now it should be active for both forward 248 11:06.130 --> 11:07.360 ers, because R1 is no 249 11:07.360 --> 11:11.260 longer part of the picture. So we'll do a show GLBP in present center, you go 250 11:11.260 --> 11:12.640 down, and sure enough, 251 11:12.640 --> 11:17.220 we are active for the first MAC address here of 0101, and we're also active for 252 11:17.220 --> 11:18.480 the second MAC address 253 11:18.480 --> 11:23.160 of 0102. So we're here to go back to PC12, and it's going to show ARP, and it's 254 11:23.160 --> 11:24.160 going to do a ping 255 11:24.160 --> 11:29.040 to 4444, now it's R2 doing all the work. So we do a show ARP, and it's going to 256 11:29.040 --> 11:30.000 do a clear ARP, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 257 11:30.000 --> 11:32.780 and we'll do a ping again, and then once that's done, we'll look at the ARP 258 11:32.780 --> 11:33.600 cache, and we should have 259 11:33.600 --> 11:38.090 0102, and all of this work is now being done by R2. And so we should see those 260 11:38.090 --> 11:38.720 MAC addresses 261 11:38.720 --> 11:44.520 ending in 0101 and 0102, from the switch perspective, both going out to gig 02 262 11:44.520 --> 11:46.160 where R2 is. So if we get 263 11:46.160 --> 11:49.680 the upper key, do a show MAC address table, sure enough there's those two MAC 264 11:49.680 --> 11:50.800 addresses right there, 265 11:50.800 --> 11:55.360 being supported now fully by R2. And if we brought our one back by doing a no 266 11:55.360 --> 11:56.000 shutdown, 267 11:56.000 --> 11:59.280 and giving it just a few moments, so let's go ahead and generate some traffic 268 11:59.280 --> 12:00.400 here, let's go ahead, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 268 11:59.280 --> 12:00.400 here, let's go ahead, 269 12:00.400 --> 12:05.990 and from PC12, we'll do a, let's do a clear ARP, and they'll do a ping to 4444, 270 12:05.990 --> 12:07.200 and a show ARP, 271 12:07.200 --> 12:10.700 and a clear ARP, and another ping that should have round robbed into the second 272 12:10.700 --> 12:12.800 MAC address of 0102, 273 12:12.800 --> 12:16.180 we'll do a show ARP, it's sure did, and then if you dig a look at the switch, 274 12:16.180 --> 12:17.360 here's switch number 1, 275 12:17.360 --> 12:21.360 and we hit the upper arrow key in press center, now it has the 0101 going over 276 12:21.360 --> 12:22.240 to the port that's 277 12:22.240 --> 12:26.040 connecting R1 to the network, and if we look at 0102, the switch believes that 278 12:26.040 --> 12:27.520 's reachable out of gig 02, 279 12:27.520 --> 12:30.500 which goes over to R2. So in this video, we've taken a look at the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 279 12:27.520 --> 12:30.500 which goes over to R2. So in this video, we've taken a look at the 280 12:30.500 --> 12:32.000 configuration and verification 281 12:32.000 --> 12:35.530 of gateway load balancing protocol, and in the next video, I'd like to give you 282 12:35.530 --> 12:36.400 an opportunity to 283 12:36.400 --> 12:39.990 get some hands-on practice with all three of these first hop redundancy 284 12:39.990 --> 12:40.800 protocols.