1 00:00:00,390 --> 00:00:04,230 In this lab, you need to configure a grid tunnel. 2 00:00:13,870 --> 00:00:21,880 We now need to configure a geo tunnel between customer rather one and two so that the PCs can ping each 3 00:00:21,880 --> 00:00:22,420 other. 4 00:00:23,200 --> 00:00:25,930 So on customer roster one. 5 00:00:27,520 --> 00:00:30,070 We going to create a tunnel interface? 6 00:00:30,910 --> 00:00:39,460 We'll use zero as the tunnel number IP address that we'll use is ten one, two, three, one slash 24 7 00:00:39,460 --> 00:00:40,030 mosque. 8 00:00:40,030 --> 00:00:47,470 In the real world, you probably want to use a slash 30 mask to conserve IP addresses, but we don't 9 00:00:47,470 --> 00:00:49,690 need to worry about that for the lab. 10 00:00:50,620 --> 00:00:54,040 We then need to specify a tunnel source. 11 00:00:54,520 --> 00:01:00,070 In this case, the tunnel source will be gigabit 001. 12 00:01:00,430 --> 00:01:04,569 Now you don't have to use the local interface as the source. 13 00:01:04,569 --> 00:01:12,580 You could specify the local routers IP address if you want to, but I've used the interfaces in this 14 00:01:12,580 --> 00:01:13,420 example. 15 00:01:13,900 --> 00:01:19,600 The tunnel destination will be the rudder on the other side, which is router two. 16 00:01:19,990 --> 00:01:30,700 Now in this lab, the routers are using DHCP addresses on the internet facing interfaces in the real 17 00:01:30,700 --> 00:01:31,210 world. 18 00:01:31,210 --> 00:01:38,530 You're going to want to use static IP addresses because if these addresses change, your tunnels will 19 00:01:38,530 --> 00:01:39,340 break. 20 00:01:40,030 --> 00:01:42,490 But that's okay for this lab. 21 00:01:43,320 --> 00:01:51,630 The tunnel interface has come up because the local router has IP reachability to the destination. 22 00:01:52,200 --> 00:02:00,180 That doesn't mean that the tunnel is going to work because we need to still configure the other side. 23 00:02:01,040 --> 00:02:05,330 So the tunnel is up now en route. 24 00:02:05,330 --> 00:02:08,150 A two interface tunnel is zero. 25 00:02:10,520 --> 00:02:21,170 IP address to use this ten 132 slash 24 mosque tunnel source is going to be the local interface gigabit 26 00:02:21,290 --> 00:02:28,280 001 tunnel destination is going to be customer router one. 27 00:02:29,140 --> 00:02:34,540 With IP address eight eight, ten two tunnel has come up on the side. 28 00:02:34,540 --> 00:02:37,840 So can we ping ten 131? 29 00:02:38,260 --> 00:02:43,690 In other words, can we ping from the local tunnel interface to the remote tunnel interface? 30 00:02:43,900 --> 00:02:47,200 It took it a while, but that's working now. 31 00:02:47,920 --> 00:02:50,260 So ping ten, one, two, three, two. 32 00:02:50,830 --> 00:02:56,200 We can ping from this tunnel interface to this tunnel interface and back again. 33 00:02:56,530 --> 00:03:05,860 But notice that the KOL routers don't know about that network, so show IP route. 34 00:03:06,340 --> 00:03:09,640 This router only knows about network eight. 35 00:03:09,880 --> 00:03:12,220 It doesn't know about network ten. 36 00:03:12,400 --> 00:03:17,200 The traffic is being encapsulated on the internet. 37 00:03:17,470 --> 00:03:21,160 So what we've done thus far is configure a geo tunnel. 38 00:03:21,550 --> 00:03:28,120 The two routers can ping each other, but we now need to advertise these networks via copy. 39 00:03:28,330 --> 00:03:30,880 Otherwise the routers will not know. 40 00:03:32,610 --> 00:03:37,200 About the internal networks behind the other router. 41 00:03:37,830 --> 00:03:42,840 As an example, router two knows about. 42 00:03:44,570 --> 00:03:49,340 Network ten one to this network ten 130. 43 00:03:49,520 --> 00:03:51,260 The tunnel. 44 00:03:51,290 --> 00:03:52,310 Subnet. 45 00:03:52,520 --> 00:03:56,270 But it doesn't know about network ten 110. 46 00:03:56,960 --> 00:03:57,500 Customer. 47 00:03:57,500 --> 00:03:58,430 Writer one. 48 00:04:02,040 --> 00:04:05,490 Also knows about ten 130. 49 00:04:06,600 --> 00:04:13,050 It knows about ten 110, but it doesn't know about network ten 120. 50 00:04:13,410 --> 00:04:19,019 So we need to configure ERP and autonomous system 100. 51 00:04:19,890 --> 00:04:21,420 So I'll do that. 52 00:04:22,110 --> 00:04:27,390 And enable Ian GOP on Network ten and disable automatic summarization. 53 00:04:27,840 --> 00:04:32,430 We were told to use IGP as the routing protocol. 54 00:04:33,270 --> 00:04:42,800 And rather to do something similar, wrote a GOP 100 Network ten Note Order Summary. 55 00:04:42,810 --> 00:04:46,500 And as you can see there, a neighbor relationship was established. 56 00:04:47,450 --> 00:04:49,640 We've got a new adjacency. 57 00:04:50,630 --> 00:05:00,650 So on router to show IP your neighbor we've got a neighbor relationship to customer router one through 58 00:05:00,680 --> 00:05:03,500 the tunnel show IP route. 59 00:05:04,070 --> 00:05:08,300 This router has now learnt about network ten 110. 60 00:05:08,420 --> 00:05:12,630 So it should be able to ping ten 111, which it can. 61 00:05:12,650 --> 00:05:17,720 So right a two can ping this IP address through the tunnel. 62 00:05:17,840 --> 00:05:20,470 Notice the difference when I do a trace. 63 00:05:20,480 --> 00:05:22,790 So trace to ten 111. 64 00:05:24,980 --> 00:05:29,060 We don't see the internet routers. 65 00:05:29,270 --> 00:05:36,800 It looks like these two routers are directly connected to each other, which they logically are through 66 00:05:36,830 --> 00:05:38,210 the tunnel. 67 00:05:39,180 --> 00:05:40,350 En route a one. 68 00:05:43,010 --> 00:05:48,350 Show IP job neighbor neighbor relationship to write to show IP route. 69 00:05:48,680 --> 00:05:53,270 It can now see this network through the tunnel. 70 00:05:53,570 --> 00:05:58,490 So it should be able to ping ten 1 to 1, which it can. 71 00:05:59,150 --> 00:06:03,770 So we have IP connectivity between the two routers. 72 00:06:03,920 --> 00:06:06,170 Can the PC ping each other? 73 00:06:06,850 --> 00:06:08,620 So this is PC one. 74 00:06:09,600 --> 00:06:12,210 And here's PC to. 75 00:06:16,190 --> 00:06:18,890 Ten PC one ping ten. 76 00:06:18,890 --> 00:06:20,630 One, two, two. 77 00:06:21,900 --> 00:06:23,550 Let's see if that works. 78 00:06:25,870 --> 00:06:26,890 It took it a while. 79 00:06:26,980 --> 00:06:29,530 But notice now the pings succeed. 80 00:06:31,280 --> 00:06:44,210 And we should be able to trace to that PC and notice we only see three hops, this router, this router 81 00:06:44,300 --> 00:06:46,280 and the remote PC. 82 00:06:46,550 --> 00:06:48,980 Because the internet routers are hidden. 83 00:06:51,960 --> 00:06:55,770 Traffic is being forwarded through the logical tunnel. 84 00:06:56,040 --> 00:07:00,660 So can this PC ping PC one? 85 00:07:01,500 --> 00:07:02,730 Yes, it can. 86 00:07:04,560 --> 00:07:10,020 So the PC on the right can ping the PC on the left. 87 00:07:10,500 --> 00:07:18,990 So we've successfully configured this network so that the PC can ping each other and the routers can 88 00:07:18,990 --> 00:07:22,050 ping each other through the tunnel.