WEBVTT 1 00:00.000 --> 00:04.000 So my first question is how did you do, how did you do with the labs? 2 00:04.000 --> 00:08.800 I've discovered that the more we practice with hands-on and configuring and ver 3 00:08.800 --> 00:10.560 ifying protocols and technologies, 4 00:10.560 --> 00:14.240 the better we get at understanding them and the better we get at troubles 5 00:14.240 --> 00:15.680 hooting when something goes south, 6 00:15.680 --> 00:18.560 when something doesn't go quite right. So hopefully you had a good experience 7 00:18.560 --> 00:19.040 in the lab, 8 00:19.040 --> 00:23.820 and in this video, we're going to do a walkthrough of the three FHRP protocols, 9 00:23.820 --> 00:25.440 starting with HSRP, 10 00:25.440 --> 00:30.000 based on these parameters here, and then we'll replace that with VRRP, and then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:30.000 --> 00:30.400 finally we'll 12 00:30.400 --> 00:34.070 finish up with a walkthrough with Gateway Load Balancing Protocol. So with that 13 00:34.070 --> 00:34.480 in mind, 14 00:34.480 --> 00:37.730 let's head over to the lab environment. All right, so here we go. The first 15 00:37.730 --> 00:38.400 thing I'm going to do 16 00:38.400 --> 00:41.900 is bring up the lab topology here. It's also included as part of the skill. If 17 00:41.900 --> 00:42.800 you want to download that 18 00:42.800 --> 00:46.170 or put it on a separate screen, but I'm a visual person I always like to see 19 00:46.170 --> 00:46.880 the topology, 20 00:46.880 --> 00:50.850 just to make sure I'm on the right interface. So we're going to be dealing with 21 00:50.850 --> 00:51.840 R1's Gig 00, 22 00:51.840 --> 00:56.400 and R2's Gig 00 as they connect to that common network segment that supporting 23 00:56.400 --> 00:56.800 the IP 24 00:56.800 --> 01:01.010 dressing space of 10.12.0. So to get to the consoles, we're going to go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:56.800 --> 01:01.010 dressing space of 10.12.0. So to get to the consoles, we're going to go ahead 25 01:01.010 --> 01:02.480 and select server 1 26 01:02.480 --> 01:05.760 nug, and then double click on it to open it up. I also took the liberty a few 27 01:05.760 --> 01:06.640 minutes ago 28 01:06.640 --> 01:10.520 of clicking on reset to reset the lab back to its defaults. So that's where we 29 01:10.520 --> 01:11.280 're starting from 30 01:11.280 --> 01:16.640 right now for this walkthrough. All right, so here is the terminal window, and 31 01:16.640 --> 01:17.280 here is the 32 01:17.280 --> 01:21.090 notepad document. Let me slide this over to the right, and I'm also going to go 33 01:21.090 --> 01:22.080 ahead and make 34 01:22.080 --> 01:27.170 this a little bit wider, just like that. All right, so for HSRP, here's our 35 01:27.170 --> 01:27.840 configuration, 36 01:27.840 --> 01:31.760 just as we did in the demos earlier. We're going to be defaulting the interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:27.840 --> 01:31.760 just as we did in the demos earlier. We're going to be defaulting the interface 37 01:31.760 --> 01:32.240 , sitting up the 38 01:32.240 --> 01:37.230 IP address, specifying standby version 2, the virtual IP address of .99, a 39 01:37.230 --> 01:38.400 priority of 99, 40 01:38.400 --> 01:43.380 and preempt all for group 1s. We'll copy that, go over to R1, paste it in, and 41 01:43.380 --> 01:44.000 then we'll do similar 42 01:44.000 --> 01:49.600 treatment for R2. So we'll grab R2's config, copy, go to R2, and paste it in. 43 01:49.600 --> 01:50.560 Now for R2, because we 44 01:50.560 --> 01:54.160 specified preempt and has a higher priority, it's going to in just a few 45 01:54.160 --> 01:55.280 moments, it's going to be 46 01:55.280 --> 02:01.910 the active router, and R1 will act as the standby. So there's the console WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 01:55.280 --> 02:01.910 the active router, and R1 will act as the standby. So there's the console 47 02:01.910 --> 02:03.200 message right there, 48 02:03.200 --> 02:08.590 seeing it's active, and let's say show standby. So currently with HSRP, this 49 02:08.590 --> 02:08.880 router, 50 02:08.880 --> 02:13.570 router 2 is going to act as the default gateway for PC12. So if we go to PC12, 51 02:13.570 --> 02:14.640 we do a trace, 52 02:14.640 --> 02:21.440 over to 4444, even as the first top is R2, and then R3, and then R4. However, 53 02:21.440 --> 02:22.640 if we went to R2, 54 02:22.640 --> 02:26.850 let's go to the right interface. So on R2, we went to gig 1 zero, and we shut 55 02:26.850 --> 02:27.280 it down, 56 02:27.280 --> 02:32.480 which we'll do right now. So we'll get a configuration mode, interface gig 1/0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 02:27.280 --> 02:32.480 which we'll do right now. So we'll get a configuration mode, interface gig 1/0, 57 02:32.480 --> 02:33.600 and we'll say shut down, 58 02:33.600 --> 02:37.610 and press enter, and then give that just a moment. Once the other router R1 59 02:37.610 --> 02:38.880 identifies, hey, there's no 60 02:38.880 --> 02:43.950 hello messages coming from R2, it'll become active. So if we go to R1, and we 61 02:43.950 --> 02:45.440 do a show standby, 62 02:45.440 --> 02:50.200 and press enter, here showing that R1 is now active, it's now supporting the 63 02:50.200 --> 02:51.200 virtual IP address, 64 02:51.200 --> 02:54.400 it's also supporting the associated virtual MAC address. And then if we went 65 02:54.400 --> 02:55.200 back to PC12, 66 02:55.200 --> 02:58.360 and we did a trace again, in fact, before we do the trace, let me just take a 67 02:58.360 --> 02:59.600 look at the cache, 68 02:59.600 --> 03:03.280 show ARP, press center, and sure enough, it still believes that the MAC address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 02:59.600 --> 03:03.280 show ARP, press center, and sure enough, it still believes that the MAC address 69 03:03.280 --> 03:04.400 for the .99 address 70 03:04.400 --> 03:08.760 still ends in F0, 0, 1, that hasn't changed, because R1 is now responsible for 71 03:08.760 --> 03:09.920 that virtual address. So 72 03:09.920 --> 03:16.620 we did a trace to 4444, the first top is now R1, who then forwards it to R3, 73 03:16.620 --> 03:17.440 who then forwards it to 74 03:17.440 --> 03:23.360 R4. And on R2, if we went back to intrace gig 1/0, when we did a no shutdown, 75 03:23.360 --> 03:24.160 as it's converging, 76 03:24.160 --> 03:27.750 if we do a show MAC address table on the switch, apparently it's showing that 77 03:27.750 --> 03:28.720 MAC address table, 78 03:28.720 --> 03:33.680 I already did it right there. There's the F0, 0, 1 associated with gig 0/2. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 03:28.720 --> 03:33.680 I already did it right there. There's the F0, 0, 1 associated with gig 0/2. So 79 03:33.680 --> 03:34.160 it's already made 80 03:34.160 --> 03:38.630 that change, and good R2, it's now the active router, it just shows standby, 81 03:38.630 --> 03:39.840 just to confirm that, 82 03:39.840 --> 03:44.410 and we went to PC12, we did that trace, the first top is once again, going to 83 03:44.410 --> 03:46.080 be as shown right here. 84 03:46.080 --> 03:52.000 All right, so that is HSRP, next let's go ahead and do VRRP. So I'm going to 85 03:52.000 --> 03:53.040 take the configuration 86 03:53.040 --> 03:58.050 for R1 copy, and it might complain about the duplicate address, because R2 is 87 03:58.050 --> 04:00.640 still active for the .99 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 03:58.050 --> 04:00.640 still active for the .99 88 04:00.640 --> 04:04.390 address, that's okay. And then I'm going to go ahead and do the configuration 89 04:04.390 --> 04:05.120 here for R2, 90 04:05.120 --> 04:12.080 for VRRP, and right click copy that and get R2 and paste it in. And because R2 91 04:12.080 --> 04:13.120 has a higher priority, 92 04:13.120 --> 04:18.400 and preempt is enabled by default, R2 should act as the master, and then the 93 04:18.400 --> 04:18.960 other device, 94 04:18.960 --> 04:23.400 or rather one in this case, will act as the backup. So here on R2, we do a show 95 04:23.400 --> 04:24.000 standby, 96 04:24.000 --> 04:29.990 we're no longer running HSRP, so let's do a show VRRP, to show the VRRP 97 04:29.990 --> 04:31.920 configuration. So this is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 97 04:29.990 --> 04:31.920 configuration. So this is 98 04:31.920 --> 04:35.240 the master device, there's the virtual IP address, there's the virtual Mac 99 04:35.240 --> 04:36.880 ending in 0, 1, 0, 1. 100 04:36.880 --> 04:42.280 And so if we went to PC12, and PC12 has a, let's do a show ARP, and it has the 101 04:42.280 --> 04:43.360 old Mac address 102 04:43.360 --> 04:47.710 for 99, that was from HSRP, so let's go ahead and do a clear ARP, give a nice 103 04:47.710 --> 04:48.800 fresh start there, 104 04:48.800 --> 04:52.700 and then without any entries in the Mac address table, here on the cache of PC 105 04:52.700 --> 04:53.280 12, 106 04:53.280 --> 04:58.920 let's go ahead and do a trace to 4444. So the first top is .2, then R3, R4. If 107 04:58.920 --> 04:59.920 we go to R2, 108 04:59.920 --> 05:04.960 and we go to interface gig 1/0, and we do a shutdown, that'll force R1 to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 04:59.920 --> 05:04.960 and we go to interface gig 1/0, and we do a shutdown, that'll force R1 to 109 05:04.960 --> 05:06.080 become the master, 110 05:06.080 --> 05:11.520 so we can verify that we go into R1, we go to a show VRRP, press enter, and now 111 05:11.520 --> 05:12.800 R1 is the master, 112 05:12.800 --> 05:16.950 supporting that same virtual Mac address. So if we go back to PC12, and we do 113 05:16.950 --> 05:17.760 another trace, 114 05:17.760 --> 05:21.720 you notice that the first top is going through R1, and then R3 and R4, and so 115 05:21.720 --> 05:22.160 we don't leave the 116 05:22.160 --> 05:25.030 network broken, if we go back to R2 and do a no shut, the parameter will go 117 05:25.030 --> 05:25.840 ahead and cause this 118 05:25.840 --> 05:30.200 one to be the master again, and as a result, if we go back to PC12, and hit the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 118 05:25.840 --> 05:30.200 one to be the master again, and as a result, if we go back to PC12, and hit the 119 05:30.200 --> 05:30.480 up here, 120 05:30.480 --> 05:34.880 key and do a trace again, now the first top is going to be .2 once again. All 121 05:34.880 --> 05:35.920 right, so that is 122 05:35.920 --> 05:40.070 VRRP, and our last option here is to go ahead and configure gateway load 123 05:40.070 --> 05:41.520 balancing protocol. 124 05:41.520 --> 05:46.160 So the syntax is GLBP, the group number, the virtual IP address, we'll set the 125 05:46.160 --> 05:46.640 priorities, 126 05:46.640 --> 05:50.960 and when they will preempt, and so let's go ahead and do R1 first, R1, right 127 05:50.960 --> 05:52.000 click and paste, 128 05:52.000 --> 05:55.730 and then we'll do R2, with the same commands we used in the demos earlier, so I 129 05:55.730 --> 05:56.560 'll copy the settings 130 05:56.560 --> 06:01.430 for R2, go over to R2, paste it in, and because preempt is enabled here, R2 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 05:56.560 --> 06:01.430 for R2, go over to R2, paste it in, and because preempt is enabled here, R2 131 06:01.430 --> 06:03.520 should become the active virtual 132 06:03.520 --> 06:08.630 gateway, and then the two active virtual forwarders will be R1 and R2. So here 133 06:08.630 --> 06:10.400 in R2, we do a show GLBP 134 06:10.400 --> 06:16.050 in percent, we are the AVG, and if we went over to R1, and we did a show GLBP, 135 06:16.050 --> 06:18.160 R1 is the standby. 136 06:18.160 --> 06:20.670 It also looks like we just stored out our forwarding as well. So let me go 137 06:20.670 --> 06:22.400 ahead and do another show GLBP 138 06:22.400 --> 06:27.200 here on R1, and I'll do also another show GLGP here on R2. So there's the 139 06:27.200 --> 06:28.640 virtual IP address, 140 06:28.640 --> 06:32.560 that the client's using is a default gateway. We have two group members, one of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 140 06:28.640 --> 06:32.560 that the client's using is a default gateway. We have two group members, one of 141 06:32.560 --> 06:34.240 those is R2 itself, 142 06:34.240 --> 06:38.650 that's the second entry, and the first one is R1. There's two forwarders, and 143 06:38.650 --> 06:39.200 if we go down a little 144 06:39.200 --> 06:42.900 bit and take a look at the details, forwarder one based on the IP address here 145 06:42.900 --> 06:44.160 is 10, 12, 0, 1, 146 06:44.160 --> 06:49.470 that's R1, supporting this virtual MAC address, and forwarder two is R2 itself. 147 06:49.470 --> 06:50.080 So if we look at the 148 06:50.080 --> 06:53.740 MAC address table on switch one, and do it, so we'll do a show MAC address 149 06:53.740 --> 06:55.520 table. Here are the two 150 06:55.520 --> 06:58.920 MAC addresses associated with gateway load balancing protocol. So the first 151 06:58.920 --> 07:00.400 forwarder is R1, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 06:58.920 --> 07:00.400 forwarder is R1, 152 07:00.400 --> 07:05.100 that's reachable out GZR1, and the second forwarder is R2 reachable out of GZR/ 153 07:05.100 --> 07:06.480 2, and should be 154 07:06.480 --> 07:10.780 shut down either of the interfaces. So let's go to PC12 here real quick, and 155 07:10.780 --> 07:11.680 let's do a show ARP, 156 07:11.680 --> 07:16.820 press enter, fantastic, let's do a trace to 4444, you know that's here that the 157 07:16.820 --> 07:18.640 first top is .1, 158 07:18.640 --> 07:21.950 and if we did a clear ARP, then we did that same trace again, with round rob 159 07:21.950 --> 07:23.040 bing, the first top should 160 07:23.040 --> 07:27.520 be R2. So it's just round robbing the active virtual gateway, just handing out 161 07:27.520 --> 07:28.240 in a round robbing 162 07:28.240 --> 07:32.180 fashion, the virtual MAC addresses associated with each of the forwarders. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 162 07:28.240 --> 07:32.180 fashion, the virtual MAC addresses associated with each of the forwarders. So 163 07:32.180 --> 07:33.040 if we were to go to 164 07:33.040 --> 07:38.680 R1 for example, and on R1 let's go ahead and go into interface gig 0/0, and let 165 07:38.680 --> 07:39.520 's shut it down, 166 07:39.520 --> 07:43.760 and then let's go back to PC12, and let's clear the ARP cache, so we'll do a 167 07:43.760 --> 07:44.800 clear ARP, let's go ahead and 168 07:44.800 --> 07:49.750 do a trace, you'll notice it's using .2 as the first top, and actually behind 169 07:49.750 --> 07:51.200 the scenes OSPF 170 07:51.200 --> 07:54.380 is still converging because they shut down an interface. So let me go ahead and 171 07:54.380 --> 07:55.680 give that just a moment. 172 07:55.680 --> 07:59.750 In fact let's do a control C to break that, and let's go ahead and try that one 173 07:59.750 --> 08:00.400 more time, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 173 07:59.750 --> 08:00.400 more time, 174 08:00.400 --> 08:05.150 and right there that was the process of OSPF converging, so OSPF is the little 175 08:05.150 --> 08:06.160 link here, so if we do it 176 08:06.160 --> 08:11.570 again, we do a trace, the first top is .2, and we do a show ARP, we're using 0/ 177 08:11.570 --> 08:13.280 0, 1 if we do a clear, 178 08:13.280 --> 08:16.900 and then we did that same trace again, you know, so we're still using 2, but 179 08:16.900 --> 08:17.440 check it out for you 180 08:17.440 --> 08:21.250 to show ARP, it's now giving us the address of 0/0, 2. So we have R2, this 181 08:21.250 --> 08:22.800 acting as the active virtual 182 08:22.800 --> 08:27.400 gateway, responding to the ARP request, and it's still round robbing with the 183 08:27.400 --> 08:28.880 virtual MAC addresses 184 08:28.880 --> 08:32.900 of each of the forwarders, and because R1 is no longer available, R2 is also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 184 08:28.880 --> 08:32.900 of each of the forwarders, and because R1 is no longer available, R2 is also 185 08:32.900 --> 08:34.400 doing the work of supporting 186 08:34.400 --> 08:39.060 both those active virtual forwarding addresses. So if we get R2 into a show GLB 187 08:39.060 --> 08:40.080 P in press center, 188 08:40.080 --> 08:44.730 it's going to be active for forwarder 1 with that first MAC address, it's also 189 08:44.730 --> 08:46.160 active for forwarder 2 190 08:46.160 --> 08:49.680 with that MAC address, and if we flip the roles, for example, we go back to R1, 191 08:49.680 --> 08:50.480 we do a no shut, 192 08:50.480 --> 08:54.770 and give that a moment for it to come up, and then if we go to R2, and R2, we 193 08:54.770 --> 08:56.080 go to config T, 194 08:56.080 --> 09:00.550 interface gig 1/0, and then we do a shut down, and then I'm also going to give WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 194 08:56.080 --> 09:00.550 interface gig 1/0, and then we do a shut down, and then I'm also going to give 195 09:00.550 --> 09:01.920 OSPF a moment to 196 09:01.920 --> 09:06.020 converge as well, and let's confirm what we just did. We just said to R1 on its 197 09:06.020 --> 09:07.360 gig 0/0, come on up, 198 09:07.360 --> 09:11.400 and we just told R2 to gig 1/0 to go ahead and shut down. So as a result, what 199 09:11.400 --> 09:12.320 should happen is 200 09:12.320 --> 09:16.560 R1 will now be the active virtual gateway, it'll also perform the role for both 201 09:16.560 --> 09:17.920 active virtual forwarders. 202 09:17.920 --> 09:22.720 So if we go back to R1 real quick, and we do a show GLBP in press center, it is 203 09:22.720 --> 09:23.520 for forwarding 204 09:23.520 --> 09:26.550 for forwarding group 1, it's active, if we go down a little bit, it's also 205 09:26.550 --> 09:28.080 active for forwarder 2, 206 09:28.080 --> 09:31.750 something to go back to PC 12, and let's go ahead and do a clear ARP, and let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 09:28.080 --> 09:31.750 something to go back to PC 12, and let's go ahead and do a clear ARP, and let's 207 09:31.750 --> 09:34.080 do a trace to 4444, 208 09:34.080 --> 09:38.070 it's using the first hop of router 1, and if we do a clear ARP, and then go 209 09:38.070 --> 09:39.760 ahead and do a trace once 210 09:39.760 --> 09:43.360 again, once again it's using .1, but check it out if we do a show ARP, and the 211 09:43.360 --> 09:44.320 ARP cache is now using 212 09:44.320 --> 09:47.670 the second MAC address for the second forwarder. And that's because R1 is doing 213 09:47.670 --> 09:48.320 all the work, 214 09:48.320 --> 09:51.840 it's the active virtual gateway, it's responding with answers for the ARP 215 09:51.840 --> 09:52.960 request, and it's round 216 09:52.960 --> 09:57.550 robbing between the two virtual MAC addresses, one from forwarder 1, and one 217 09:57.550 --> 09:58.960 from forwarder 2, 218 09:58.960 --> 10:03.020 and at this moment it's responsible for both of those because R2 is no longer WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 218 09:58.960 --> 10:03.020 and at this moment it's responsible for both of those because R2 is no longer 219 10:03.020 --> 10:03.760 responding. 220 10:03.760 --> 10:07.590 And if we brought R2 back with a no shutdown, and we gave it a few moments 221 10:07.590 --> 10:08.640 because it has a higher 222 10:08.640 --> 10:13.230 priority, it's going to become the active virtual gateway, and then as we start 223 10:13.230 --> 10:15.040 going back to PC 12, 224 10:15.040 --> 10:20.720 and we do a clear ARP for example, let's do a ping to 4444, and a show ARP, it 225 10:20.720 --> 10:21.360 was using the MAC 226 10:21.360 --> 10:25.190 address ending in 0101, let's do a clear ARP, then once again we'll do a ping 227 10:25.190 --> 10:26.080 to 4444, 228 10:26.080 --> 10:30.250 and we'll do a show ARP, and now it's using 0102. And because we're now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 228 10:26.080 --> 10:30.250 and we'll do a show ARP, and now it's using 0102. And because we're now 229 10:30.250 --> 10:31.440 dividing the load 230 10:31.440 --> 10:38.960 between R1 and R2, if we do a trace to 4444, it's using R2 as the first top, 231 10:38.960 --> 10:39.600 and then if we do a clear 232 10:39.600 --> 10:44.560 ARP to simulate doing a ARP request for that .99 again, we'll do a trace again, 233 10:44.560 --> 10:45.440 and this time our 234 10:45.440 --> 10:49.360 first top is .1, because if we do a show ARP, the layer 2 address that we were 235 10:49.360 --> 10:50.240 sent back in the ARP 236 10:50.240 --> 10:55.570 response was 0101. Also just to help reinforce this, I did a quick caption in 237 10:55.570 --> 10:57.440 the background regarding 238 10:57.440 --> 11:02.510 four messages related to ARP. Now the first one is a client, this is PC 12, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 238 10:57.440 --> 11:02.510 four messages related to ARP. Now the first one is a client, this is PC 12, 239 11:02.510 --> 11:03.840 that's doing an 240 11:03.840 --> 11:08.730 ARP request saying hey I need the layer 2 address for 10, 12, 0, 99, please let 241 11:08.730 --> 11:09.360 me know. So if 242 11:09.360 --> 11:13.440 we look at the details for that, here's the request, and the first response 243 11:13.440 --> 11:14.480 that's coming back 244 11:14.480 --> 11:19.000 from the active virtual gateway is the MAC address of 0, 0, 0, 0, 7, B4, 0, 0, 245 11:19.000 --> 11:20.560 0, 0, 0, 0, 0, 2, 246 11:20.560 --> 11:23.950 then I cleared the cache on that machine, and it did another request to reach a 247 11:23.950 --> 11:24.960 remote network, 248 11:24.960 --> 11:28.590 so I did another ARP request, and this time I responded back with the MAC 249 11:28.590 --> 11:30.800 address of 0, 1, 0, 1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 249 11:28.590 --> 11:30.800 address of 0, 1, 0, 1. 250 11:30.800 --> 11:35.690 So the initial response had 0, 1, 0, 2, and then the second response had 0, 1, 251 11:35.690 --> 11:36.640 0, 1. And that's how the 252 11:36.640 --> 11:41.480 active virtual gateway is providing load balancing by responding to the ARP 253 11:41.480 --> 11:42.960 requests with the virtual 254 11:42.960 --> 11:47.650 MAC addresses for the various forwarders associated with GLBP. So thank you for 255 11:47.650 --> 11:49.200 joining me in this set of 256 11:49.200 --> 11:53.000 videos regarding first hop, redundancy protocols, and I look forward to seeing 257 11:53.000 --> 11:54.080 you my friend in another 258 11:54.080 --> 11:58.370 set of videos in the very near future. Until then, I hope this has been 259 11:58.370 --> 12:00.560 informative, and I'd like to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 259 11:58.370 --> 12:00.560 informative, and I'd like to 260 12:00.560 --> 12:02.000 thank you for viewing.