WEBVTT 1 00:00.000 --> 00:03.770 As I was putting together this hands-on lab, I thought to myself, there are a 2 00:03.770 --> 00:04.480 lot of routers. 3 00:04.480 --> 00:07.860 I think 10 routers to configure here. So, for the lab, here's what I'd like you 4 00:07.860 --> 00:08.000 to do. 5 00:08.000 --> 00:12.160 We're going to take a subset of this network topology and configure effectively 6 00:12.160 --> 00:13.600 an entire autonomous system. 7 00:13.600 --> 00:15.750 So here's what I'd like you to do. I'm going to like you to take this 8 00:15.750 --> 00:19.200 autonomous system, which involves R21 and R22, 9 00:19.200 --> 00:22.660 and I'd like you to go into configuration mode and issue this one command on 10 00:22.660 --> 00:23.600 those two routers, 11 00:23.600 --> 00:28.740 and that's going to remove all of their respective BGP configuration completely 12 00:28.740 --> 00:29.040 . 13 00:29.040 --> 00:33.720 So, with it gone, then, I'd like you to go into the steps of actually config WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.040 --> 00:33.720 So, with it gone, then, I'd like you to go into the steps of actually config 14 00:33.720 --> 00:35.040 uring internal BGP 15 00:35.040 --> 00:40.400 neighborships between R21 and R22. Inside of AS20, I'll also feel free to use 16 00:40.400 --> 00:40.880 loopbacks. 17 00:40.880 --> 00:45.200 If you don't want any loopbacks, you can point to the actual addresses on those 18 00:45.200 --> 00:46.480 respective interfaces, 19 00:46.480 --> 00:51.540 but the loopback addresses, which are 21, etc., and 22, etc., are both reach 20 00:51.540 --> 00:52.400 able via OSPF. 21 00:52.400 --> 00:56.300 So, if you want to point and neighbor up with those loopback interfaces, feel 22 00:56.300 --> 00:57.280 free to do so. 23 00:57.280 --> 01:00.960 Also, when you're seeing the neighborship, because R21 is going to be receiving WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:57.280 --> 01:00.960 Also, when you're seeing the neighborship, because R21 is going to be receiving 24 01:00.960 --> 01:01.680 routes from 25 01:01.680 --> 01:06.000 external BGP peers, and we want to sit the next top to be R21's address, 26 01:06.000 --> 01:09.680 you'd also want to go ahead and use that next hop-self option when you're 27 01:09.680 --> 01:10.960 configuring R21 28 01:10.960 --> 01:14.880 to peer over with R22. Then, once you have that neighborship set up, the second 29 01:14.880 --> 01:14.960 thing I'd 30 01:14.960 --> 01:19.650 love you to do is set up external BGP. And for the level to just be external BG 31 01:19.650 --> 01:20.960 P between R21 and 32 01:20.960 --> 01:27.230 R11 and external BGP between R21 and R42. And the rest of the network, 33 01:27.230 --> 01:28.800 including a ton of system 10 and 34 01:28.800 --> 01:32.600 30 and 40, they're already configured ready to go. And then once you have the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:28.800 --> 01:32.600 30 and 40, they're already configured ready to go. And then once you have the 35 01:32.600 --> 01:33.840 external BGP session set 36 01:33.840 --> 01:39.460 up, I'd then like you to go ahead over to R22 and advertise R22's loopback zero 37 01:39.460 --> 01:40.480 interface, 38 01:40.480 --> 01:45.520 which is 22.22.22.22. And once that's advertised, and after you give the 39 01:45.520 --> 01:46.080 network a second 40 01:46.080 --> 01:51.120 or two to converge, all of these routers should have those four routes inside 41 01:51.120 --> 01:53.040 of their BGP table. 42 01:53.040 --> 01:57.350 And the best of those routes that are usable would also be placed into the 43 01:57.350 --> 01:58.640 routing table. So, 44 01:58.640 --> 02:02.580 as a test, you should be able to ping from, once it's all set up, you should be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 01:58.640 --> 02:02.580 as a test, you should be able to ping from, once it's all set up, you should be 45 02:02.580 --> 02:03.200 able to ping from 46 02:03.200 --> 02:10.200 loopbacks on R12, R32, R43, and R22 to any of the other respective loopbacks. 47 02:10.200 --> 02:10.880 So, and they'll put 48 02:10.880 --> 02:14.040 the arrows there as a reminder. So, from any of the loopbacks to any of the 49 02:14.040 --> 02:15.440 other loopbacks, we should be 50 02:15.440 --> 02:20.090 able to have full connectivity. And that would include a trace or a ping once B 51 02:20.090 --> 02:21.120 GP is all in place. 52 02:21.120 --> 02:25.040 Again, your mission should you choose to accept it is just the configuration of 53 02:25.040 --> 02:28.000 R21 and R22 using 54 02:28.000 --> 02:32.450 these steps. Also, as an aid to this lab, I also have a configuration file, a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:28.000 --> 02:32.450 these steps. Also, as an aid to this lab, I also have a configuration file, a 55 02:32.450 --> 02:33.360 little note pad document 56 02:33.360 --> 02:37.000 early, sitting on server1-nug that you can refer to. If you want to just 57 02:37.000 --> 02:38.000 confirm many of the 58 02:38.000 --> 02:41.300 steps or look at those details, they're in that note pad document. So, have 59 02:41.300 --> 02:42.160 some fun with the lab. 60 02:42.160 --> 02:45.570 But when you're done and you have that full connectivity from loopback to loop 61 02:45.570 --> 02:46.240 back, they're being 62 02:46.240 --> 02:49.990 advertised via BGP. If you want to join me for the walkthrough, we'll do that 63 02:49.990 --> 02:51.280 next in the next video. 64 02:51.280 --> 02:53.680 So, I'll see you there after you've had an opportunity to get some hands-on 65 02:53.680 --> 02:54.640 practice with the lab 66 02:54.640 --> 02:56.400 and want to do the walkthrough together.