1 00:00:00,920 --> 00:00:09,890 On switch one at the moment show IP route shows us that we've learned one IP route so DX being IP in 2 00:00:09,890 --> 00:00:14,990 the routing table, but we haven't got a gateway of last resort set. 3 00:00:16,200 --> 00:00:21,360 On switch to show IP route gateway of last resort is not set. 4 00:00:21,570 --> 00:00:27,720 We're learning about one route through ISP, the loopback of router three, but no other routes are 5 00:00:27,750 --> 00:00:28,530 being learnt. 6 00:00:29,040 --> 00:00:31,560 This is the configuration on router three. 7 00:00:31,680 --> 00:00:33,830 So router erp 100. 8 00:00:33,840 --> 00:00:41,970 We advertising the loopback and enabling ERP on the first ethernet interface and we've disabled automatic 9 00:00:41,970 --> 00:00:47,070 summarization, but nothing else is being configured at the moment. 10 00:00:48,880 --> 00:00:51,290 No gateway of last resort is configured. 11 00:00:51,550 --> 00:00:53,950 Show IP interface. 12 00:00:54,780 --> 00:00:55,650 Brief. 13 00:00:57,980 --> 00:01:03,830 We're having a problem with the IP address on this interface which was allocated previously through 14 00:01:04,129 --> 00:01:05,150 DHCP. 15 00:01:05,570 --> 00:01:11,030 So I'll shut the interface down and then no, shut it. 16 00:01:13,070 --> 00:01:14,720 But while we're waiting for that. 17 00:01:18,380 --> 00:01:27,170 I'll configure a static default route on this router to what I know is the default gateway on the cloud. 18 00:01:27,590 --> 00:01:33,380 So I'm going to configure a default route on this router to point to my internet facing router here 19 00:01:33,380 --> 00:01:34,100 at home. 20 00:01:36,140 --> 00:01:41,930 When this interface comes up, we should have a default route show in the routing table. 21 00:01:42,640 --> 00:01:43,090 Now. 22 00:01:43,120 --> 00:01:46,930 Instead of waiting for that, I'll configure the address manually. 23 00:01:46,930 --> 00:01:50,560 So 192168124 is an example. 24 00:01:52,060 --> 00:01:53,860 Make sure the interface is no shut. 25 00:01:54,430 --> 00:01:56,410 Show IP rot. 26 00:01:57,820 --> 00:01:58,630 So. 27 00:01:59,110 --> 00:02:05,350 Writer three now has a gateway of last resort being 1921681254. 28 00:02:05,350 --> 00:02:07,990 And the static route is appearing in the routing table. 29 00:02:08,820 --> 00:02:11,730 Ping that router. 30 00:02:13,660 --> 00:02:17,200 And I'm having a problem with the cloud, but I'll resolve that later. 31 00:02:17,650 --> 00:02:24,000 For now, I just want to advertise the default route through air GOP. 32 00:02:24,010 --> 00:02:27,400 So rather air GOP 100. 33 00:02:27,790 --> 00:02:34,930 And I'm going to type, redistribute, redistribute allows me to take a route from one routing protocol 34 00:02:34,930 --> 00:02:36,690 and advertise it in another. 35 00:02:36,700 --> 00:02:41,800 So I'm going to redistribute, in this case, a static route, the static default route. 36 00:02:42,340 --> 00:02:48,290 And I need to create what's called a seed metric or beginning metric to bring it into ERP. 37 00:02:48,670 --> 00:02:53,380 So I'm going to specify a bandwidth value of 10,000. 38 00:02:54,260 --> 00:03:03,800 A delay value of 100, a reliability of 255 where 255 is 100% reliable, a load of one which means no 39 00:03:03,800 --> 00:03:07,010 load and a MTU of 500. 40 00:03:07,370 --> 00:03:12,680 You just need to specify some kind of value so that you can bring that route into ERP. 41 00:03:13,590 --> 00:03:15,360 So on switch to. 42 00:03:16,080 --> 00:03:20,130 Previously we didn't have a gateway of last resort, but now we do. 43 00:03:20,340 --> 00:03:24,390 So the default route is being advertised into ERP. 44 00:03:24,600 --> 00:03:30,180 So in other words, on router three, we have a static default route pointing to my internet facing 45 00:03:30,180 --> 00:03:37,230 router in the cloud that's being redistributed into ERP and being advertised to switch to and to switch 46 00:03:37,230 --> 00:03:37,860 one. 47 00:03:38,190 --> 00:03:39,390 So on switch one. 48 00:03:39,390 --> 00:03:46,500 Previously, once again, no gateway of last resort and no default route shown in the routing table. 49 00:03:46,530 --> 00:03:55,290 But notice now we do have a gateway of last resort and we have a static route advertised through IRP 50 00:03:55,780 --> 00:04:00,190 X means external ERP route. 51 00:04:00,210 --> 00:04:03,240 In other words, it was advertised from another writing protocol. 52 00:04:04,340 --> 00:04:11,000 Notice this route has a administrative distance or believability factor of 90 because we advertise that 53 00:04:11,000 --> 00:04:15,410 into ERP using the network command on router three. 54 00:04:16,459 --> 00:04:20,630 But the aesthetic default route has an administrative distance of 170. 55 00:04:20,720 --> 00:04:28,340 In other words, it's much less believable than the route that came directly into ERP through the network 56 00:04:28,340 --> 00:04:29,210 command. 57 00:04:30,140 --> 00:04:36,800 Once again, we can see that on switch to measure of distance for the static route there was advertised 58 00:04:36,800 --> 00:04:43,760 into ERP is 170 administrative distance of the route that was brought directly into ERP has administrative 59 00:04:43,760 --> 00:04:44,870 distance of 90. 60 00:04:45,530 --> 00:04:52,580 Show IP protocols shows me what the default administrative distances are in IRP. 61 00:04:52,820 --> 00:04:57,170 So at the moment we've enabled ERP on these two switches. 62 00:04:57,410 --> 00:05:02,510 We've created a static default route on router three and advertised that into ERP. 63 00:05:02,840 --> 00:05:05,150 In the next video, I'm going to troubleshoot the cloud. 64 00:05:05,150 --> 00:05:09,140 If you're not interested in seeing that, then skip ahead. 65 00:05:09,140 --> 00:05:14,270 But I'd like to get my cloud working so that we can configure Nat in a later video. 66 00:05:14,690 --> 00:05:18,590 In this video, I'm going to troubleshoot an issue with the cloud in three. 67 00:05:19,040 --> 00:05:24,140 This is not a CCAR specific topic, so if you're not interested, then skip ahead. 68 00:05:24,930 --> 00:05:31,710 But at the moment, Rada three has an IP address configured on Fost Ethernet zero one, the interface 69 00:05:31,710 --> 00:05:35,040 of 1921681 124. 70 00:05:35,730 --> 00:05:44,370 My local PC that Ginny three is running on has an IP address of 1921681199 in that subnet. 71 00:05:44,730 --> 00:05:48,510 So ping one on 21681 124. 72 00:05:49,350 --> 00:05:57,780 That's not working, but I can ping my default gateway on the Windows PC, so I'll configure this cloud. 73 00:05:58,440 --> 00:06:04,680 At the moment it's being connected to the local area connection, which is the correct interface to 74 00:06:04,680 --> 00:06:06,210 use on my PC. 75 00:06:08,370 --> 00:06:10,440 So what I'll simply do is delete the cloud. 76 00:06:11,610 --> 00:06:13,500 And then create another cloud. 77 00:06:14,340 --> 00:06:16,350 So drag a cloud across. 78 00:06:17,190 --> 00:06:21,210 Or configure the cloud should be using the local area connection. 79 00:06:21,810 --> 00:06:22,170 Click. 80 00:06:22,170 --> 00:06:22,830 Okay. 81 00:06:25,250 --> 00:06:29,390 I'll connect Foster Ethernet zero one to the cloud and. 82 00:06:30,880 --> 00:06:35,440 Hopefully now my PC can ping rather three, which it's able to do. 83 00:06:36,710 --> 00:06:46,340 And hopefully rather three can now ping one on 21681254, which is the local internet facing router 84 00:06:46,340 --> 00:06:48,080 in the cloud, which it can. 85 00:06:48,380 --> 00:06:52,010 So I've successfully resolved the issue in Genesis three. 86 00:06:52,400 --> 00:06:55,460 This router can now ping the internet facing router.