WEBVTT 1 00:00.000 --> 00:08.410 Our first step in troubleshooting cloud connectivity, whether it be for IPsec 2 00:08.410 --> 00:13.100 VPN like we're looking at here or even if we're just trying to get directly to 3 00:13.100 --> 00:17.000 the cloud, we need to have internet access first. 4 00:17.000 --> 00:21.000 And of course, that's going to happen through our local ISP. 5 00:21.000 --> 00:24.000 So what are some of the things we need to worry about here? 6 00:24.000 --> 00:34.120 We have to worry first about how we're going to get our IP address. Of course, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 6 00:24.000 --> 00:34.120 We have to worry first about how we're going to get our IP address. Of course, 7 00:34.120 --> 00:34.930 we could either have a static assignment. That's usually going to be for 8 00:34.930 --> 00:36.320 businesses, but a lot of small businesses and home users like home offices and 9 00:36.320 --> 00:38.000 such will use DHCP. 10 00:38.000 --> 00:41.990 Now, what doesn't really matter which one we're using for this particular 11 00:41.990 --> 00:43.000 environment. 12 00:43.000 --> 00:47.420 However, we have to make sure our devices are configured properly, depending on 13 00:47.420 --> 00:49.000 which option we're using. 14 00:49.000 --> 00:52.000 Of course, we also have to have some form of routing. 15 00:52.000 --> 00:57.500 Now, the two most common, of course, to use for internet access would be static 16 00:57.500 --> 01:02.460 routing, which again is going to be popular in small businesses and home WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:57.500 --> 01:02.460 routing, which again is going to be popular in small businesses and home 17 01:02.460 --> 01:04.000 offices and such. 18 01:04.000 --> 01:09.000 And then we also have the option of running BGP with our service provider. 19 01:09.000 --> 01:13.450 Now that's generally going to be for medium to large size enterprises, but it 20 01:13.450 --> 01:18.120 could be available really anytime that you have multiple connections out to the 21 01:18.120 --> 01:19.000 Internet. 22 01:19.000 --> 01:23.320 Most service providers will not run BGP with you unless you have multiple 23 01:23.320 --> 01:25.000 Internet connections. 24 01:25.000 --> 01:28.000 But of course, there's always exceptions. 25 01:28.000 --> 01:32.240 So what we're going to do in this video is take a look at those options and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:28.000 --> 01:32.240 So what we're going to do in this video is take a look at those options and 26 01:32.240 --> 01:36.520 take a look at some really cool tools to verify that our Internet access is 27 01:36.520 --> 01:38.000 actually functional. 28 01:38.000 --> 01:39.000 So let's go ahead and jump in. 29 01:39.000 --> 01:43.960 We're going to take a look first at our on-prem router one, which is using a 30 01:43.960 --> 01:47.000 static address and it's using a static route. 31 01:47.000 --> 01:51.000 And we'll also take a look at an environment that's using BGP. 32 01:51.000 --> 01:58.000 So let's go ahead and take a look at the command line starting on on-prem R1. 33 01:58.000 --> 02:03.890 So probably the most common or well-known tool to verify that we have Internet WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:58.000 --> 02:03.890 So probably the most common or well-known tool to verify that we have Internet 34 02:03.890 --> 02:06.000 access would be paying. 35 02:06.000 --> 02:06.000 Right? 36 02:06.000 --> 02:11.410 We're just going to bounce an ICMP echo request off of another device and look 37 02:11.410 --> 02:13.000 for an answer back. 38 02:13.000 --> 02:17.350 A fairly common one to do is simply eight dot eight dot eight dot eight, which 39 02:17.350 --> 02:19.000 is one of Google's DNS servers. 40 02:19.000 --> 02:23.280 So we can just go ahead and ping that and verify that we have Internet reach 41 02:23.280 --> 02:28.550 ability, which as we can see here we do because we got successful ping responses 42 02:28.550 --> 02:29.000 back. 43 02:29.000 --> 02:33.770 If you want to look at the actual path you're taking to get there, another very WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:29.000 --> 02:33.770 If you want to look at the actual path you're taking to get there, another very 44 02:33.770 --> 02:36.000 popular tool of course is Trace Route. 45 02:36.000 --> 02:41.000 And Trace Route, we could again just go to eight dot eight dot eight dot eight. 46 02:41.000 --> 02:45.920 If you just hit enter, what's going to happen is your device is going to try to 47 02:45.920 --> 02:50.860 do DNS resolution on each hop and show you each hop you're going through to get 48 02:50.860 --> 02:53.000 to a specific destination. 49 02:53.000 --> 02:58.990 Now one thing a lot of people don't know about Trace on iOS is you can actually 50 02:58.990 --> 03:03.000 put numeric after it and then it'll just show you the addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 02:58.990 --> 03:03.000 put numeric after it and then it'll just show you the addresses. 51 03:03.000 --> 03:06.000 This is going to make it happen a bit faster. 52 03:06.000 --> 03:10.700 And if we're not worried about the DNS names, this can just make it a little 53 03:10.700 --> 03:13.000 easier to interpret the output. 54 03:13.000 --> 03:17.440 So you can see here of course hop by hop, how this packet is traversing the 55 03:17.440 --> 03:21.000 network and ultimately getting to its destination. 56 03:21.000 --> 03:27.510 If you see instances like hop six and hop seven here, where it's hitting three 57 03:27.510 --> 03:32.000 different locations, this means that it's doing multipath thing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 03:27.510 --> 03:32.000 different locations, this means that it's doing multipath thing. 58 03:32.000 --> 03:37.000 So it took different paths for each of the three trace requests. 59 03:37.000 --> 03:41.000 That's what happens when we do this, it sends three trace requests. 60 03:41.000 --> 03:45.790 That's why each answer, such as one, two, three and four here, have three 61 03:45.790 --> 03:48.000 separate times after them. 62 03:48.000 --> 03:52.000 Those are the three different echo requests that were sent. 63 03:52.000 --> 03:56.750 Notice on the multipath thing options, there's only one time on each because 64 03:56.750 --> 04:00.000 the time is representing each individual path. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 04:00.000 --> 04:04.000 Now, of course, in this case, everything's working as it should be. 66 04:04.000 --> 04:07.470 But there are some things we want to take a look at, particularly if things are 67 04:07.470 --> 04:09.000 not working as they should. 68 04:09.000 --> 04:14.000 A very popular command, of course, is show IP interface brief. 69 04:14.000 --> 04:18.290 Show IP interface brief here will show us how our interfaces are configured and 70 04:18.290 --> 04:21.000 how they're getting their address. 71 04:21.000 --> 04:25.530 Now, an interesting thing here, since this is running in an emulated 72 04:25.530 --> 04:31.000 environment and the configuration is actually coming from the startup config. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 04:25.530 --> 04:31.000 environment and the configuration is actually coming from the startup config. 73 04:31.000 --> 04:38.150 Notice that the method is listed as TFTP for how this got its address, say, for 74 04:38.150 --> 04:40.000 example, on the gigabit one interface. 75 04:40.000 --> 04:45.610 However, if we were to say show run interface gigabit one, notice that it is in 76 04:45.610 --> 04:49.000 fact configured as a static address. 77 04:49.000 --> 04:54.630 So if I were to write the configuration and reload this router, the method 78 04:54.630 --> 04:58.000 would change to manual rather than TFTP. 79 04:58.000 --> 05:02.000 As you can see, for example, tunnel one and tunnel two are. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 04:58.000 --> 05:02.000 As you can see, for example, tunnel one and tunnel two are. 80 05:02.000 --> 05:06.180 Notice those are set to manual because those were configured after this device 81 05:06.180 --> 05:12.000 was brought up with its baseline configuration from the emulation software. 82 05:12.000 --> 05:17.000 In this case, this is running on CML, Cisco modeling lab. 83 05:17.000 --> 05:21.270 Of course, if you're supposed to be getting a DHCP address from your service 84 05:21.270 --> 05:24.730 provider, what you would do is instead of putting in the IP address, like is 85 05:24.730 --> 05:30.000 listed here, you would simply say IP address DHCP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 86 05:30.000 --> 05:31.000 That's all you have to do. 87 05:31.000 --> 05:36.210 Then when that interface comes up, it will attempt to do a DHCP request and get 88 05:36.210 --> 05:38.000 its address from DHCP. 89 05:38.000 --> 05:43.230 Now, of course, the other aspect for internet access is also to have routing, 90 05:43.230 --> 05:46.000 not just an IP address on an interface. 91 05:46.000 --> 05:51.250 So if I were to do a show IP route here, notice that we have some connected 92 05:51.250 --> 05:56.610 local and static routes dealing with things like our AWS access out tunnel one 93 05:56.610 --> 06:03.160 and tunnel two, but also notice that we have a static default route pointing to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 05:56.610 --> 06:03.160 and tunnel two, but also notice that we have a static default route pointing to 94 06:03.160 --> 06:04.000 our service provider. 95 06:04.000 --> 06:09.000 In this case, the 204 dot 186 dot 19 dot one. 96 06:09.000 --> 06:15.060 So this, of course, is simply an example of doing static routing for internet 97 06:15.060 --> 06:16.000 access. 98 06:16.000 --> 06:21.000 Now, it's also possible that your device could be using VRFs. 99 06:21.000 --> 06:25.860 And if it's using VRFs, you may not see those routes here in this routing table 100 06:25.860 --> 06:26.000 . 101 06:26.000 --> 06:30.360 So you might have to do a show VRF. Now we can see this particular router isn't WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 06:26.000 --> 06:30.360 So you might have to do a show VRF. Now we can see this particular router isn't 102 06:30.360 --> 06:34.000 really using VRFs except that we have one for management. 103 06:34.000 --> 06:39.000 But notice the routing table for management is not listed here. 104 06:39.000 --> 06:44.000 What I would have to do instead is say show IP route for VRF management. 105 06:44.000 --> 06:49.280 And now we can see that there's a separate default route specifically for the 106 06:49.280 --> 06:54.000 management VRF pointing to my router for my management network. 107 06:54.000 --> 06:59.680 This is simply on the 192 dot 168 dot one network that I'm using for management 108 06:59.680 --> 07:00.000 . WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 109 07:00.000 --> 07:04.420 Now, if I were to say show IP route again, of course, it's going to show me the 110 07:04.420 --> 07:06.000 global routing table. 111 07:06.000 --> 07:08.000 And I don't see those routes again. 112 07:08.000 --> 07:14.000 If you are dealing with VRFs a lot, or you're in VRFs a lot, a little trick 113 07:14.000 --> 07:19.460 that most platforms support that support VRFs that some people may not be aware 114 07:19.460 --> 07:20.000 of. 115 07:20.000 --> 07:23.000 There's actually a command called routing context. 116 07:23.000 --> 07:27.180 And if you do the question mark after this, not only one choice, you have to 117 07:27.180 --> 07:30.000 say VRF and then you put in the name of the VRF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 118 07:30.000 --> 07:36.500 So in my case, I would say management hit enter and notice how my command 119 07:36.500 --> 07:42.000 prompt changes indicating that I am now in the management VRF. 120 07:42.000 --> 07:47.520 So now if I type something like show IP route, notice that it's showing me the 121 07:47.520 --> 07:50.000 routing table for that VRF now. 122 07:50.000 --> 07:56.000 Now, some things like show IP interface brief are not VRF sensitive. 123 07:56.000 --> 07:59.000 So this is just showing me the regular output. 124 07:59.000 --> 08:04.640 But anything like your routing table and such that are related to a VRF, you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 124 07:59.000 --> 08:04.640 But anything like your routing table and such that are related to a VRF, you 125 08:04.640 --> 08:10.020 can actually change your routing context to that VRF so you don't have to type 126 08:10.020 --> 08:11.000 VRF whatever. 127 08:11.000 --> 08:14.000 In every single command you type. 128 08:14.000 --> 08:18.000 It can just be a little more convenient if you work with VRFs a lot. 129 08:18.000 --> 08:23.000 And of course, exit will simply take you out of that routing context. 130 08:23.000 --> 08:27.530 So now that we've taken a look at some functional internet access, and we've 131 08:27.530 --> 08:32.650 seen how it looks with a static IP address, we talked about how to configure it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 131 08:27.530 --> 08:32.650 seen how it looks with a static IP address, we talked about how to configure it 132 08:32.650 --> 08:34.000 as a DHCP address. 133 08:34.000 --> 08:36.680 And we've seen our static routes, which by the way, we haven't seen what they 134 08:36.680 --> 08:38.000 look like in the configuration. 135 08:38.000 --> 08:40.000 So let's look at that real quick. 136 08:40.000 --> 08:43.000 Let's do a show run include route. 137 08:43.000 --> 08:46.000 So we see here what these routes look like. 138 08:46.000 --> 08:50.550 The first one, of course, the IP route for zero dot zero dot zero dot zero zero 139 08:50.550 --> 08:56.000 dot zero dot zero dot zero and then going to the 204 dot 186 dot 19 dot one. 140 08:56.000 --> 09:00.000 That is our default route for our internet access. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 141 09:00.000 --> 09:05.110 We then have the two static routes that we're currently using for our tunnels 142 09:05.110 --> 09:06.000 going out to AWS. 143 09:06.000 --> 09:10.000 We'll be looking at those in some upcoming videos. 144 09:10.000 --> 09:15.100 And then of course we have that route that's specifically in the management for 145 09:15.100 --> 09:17.000 our management network. 146 09:17.000 --> 09:22.000 So this is what the static routes look like in your configuration. 147 09:22.000 --> 09:27.000 So now that we've seen all this, let's jump over to our BGP environment. 148 09:27.000 --> 09:32.010 The diagram for this and the configurations for this are located just above WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 148 09:27.000 --> 09:32.010 The diagram for this and the configurations for this are located just above 149 09:32.010 --> 09:37.950 this video. So you can fire this up in CML or whatever virtualized platform you 150 09:37.950 --> 09:39.000 're using. 151 09:39.000 --> 09:41.000 So let's jump over to that environment now. 152 09:41.000 --> 09:42.000 now.