WEBVTT 1 00:00.000 --> 00:07.360 So once we jump in and verify that our router has been properly deployed and 2 00:07.360 --> 00:08.760 verified, we're 3 00:08.760 --> 00:12.840 then going to want to set up a few other things on our new router. 4 00:12.840 --> 00:17.860 Specifically, we need to assign it an outside public address so that we can SSH 5 00:17.860 --> 00:19.040 into it. 6 00:19.040 --> 00:22.060 And then we want to make sure that the rest of the interfaces are configured 7 00:22.060 --> 00:22.720 properly, 8 00:22.720 --> 00:25.960 specifically, of course, just gigabit to it the moment. 9 00:25.960 --> 00:29.710 And then we want to put some baseline configuration on it that I normally put 10 00:29.710 --> 00:30.520 on most routers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:29.710 --> 00:30.520 on most routers 11 00:30.520 --> 00:34.280 that I build, and then we'll verify connectivity. 12 00:34.280 --> 00:39.120 So let's go ahead and jump in and get started on those tasks. 13 00:39.120 --> 00:44.580 So starting off here looking at our instances, we can see that our C8000V is 14 00:44.580 --> 00:45.480 now not just 15 00:45.480 --> 00:49.680 running, but that the status check has been passed. 16 00:49.680 --> 00:54.040 So the next thing we're going to want to do is go to our elastic IPs. 17 00:54.040 --> 00:56.880 Again, I already have these configured. 18 00:56.880 --> 01:01.680 If you don't, you just want to go up here to the allocate elastic IP addresses WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:56.880 --> 01:01.680 If you don't, you just want to go up here to the allocate elastic IP addresses 19 01:01.680 --> 01:02.400 and create 20 01:02.400 --> 01:04.520 one for yourself. 21 01:04.520 --> 01:07.560 Right now we're just going to be using the R1 gig one. 22 01:07.560 --> 01:10.120 So let's go ahead and select that. 23 01:10.120 --> 01:15.310 After we select it, we'll go to actions and we'll say to associate the elastic 24 01:15.310 --> 01:16.280 IP address. 25 01:16.280 --> 01:20.480 What we want to associate it to is going to be a network interface. 26 01:20.480 --> 01:24.760 So we'll select network interface, then for the network interface, we're going 27 01:24.760 --> 01:25.360 to choose 28 01:25.360 --> 01:30.480 R1 gig one, and then it's going to also want to know which private IP address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 01:25.360 --> 01:30.480 R1 gig one, and then it's going to also want to know which private IP address. 29 01:30.480 --> 01:35.520 So we'll choose it to address the 10 dot 20 dot 1 dot 254. 30 01:35.520 --> 01:39.710 Now just in case this has been associated to another machine in the past, I 31 01:39.710 --> 01:40.160 usually 32 01:40.160 --> 01:44.720 just hit this, allow this elastic IP address to be reassociated. 33 01:44.720 --> 01:48.100 We scroll down and we simply hit associate. 34 01:48.100 --> 01:50.560 This has been associated successfully. 35 01:50.560 --> 01:56.690 So now if we go back to our instances, then we highlight our C8000 V. Notice 36 01:56.690 --> 01:57.140 that it now 37 01:57.140 --> 02:01.060 has a public IPV for address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 37 01:57.140 --> 02:01.060 has a public IPV for address. 38 02:01.060 --> 02:06.300 So now that this has been associated, we should be able to SSH into our AWS 39 02:06.300 --> 02:08.100 router one here. 40 02:08.100 --> 02:12.640 So let's open up secure CRT and SSH into this router. 41 02:12.640 --> 02:19.320 So now we're connected into AWS R1. Keep in mind, in your SSH session, you will 42 02:19.320 --> 02:19.700 have to 43 02:19.700 --> 02:23.980 use that key file to do your authentication. 44 02:23.980 --> 02:28.340 And the default username is EC2 dash user. 45 02:28.340 --> 02:30.900 So that'll get you into the router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 02:28.340 --> 02:30.900 So that'll get you into the router. 46 02:30.900 --> 02:36.700 Notice that AWS has set the host name based on its IP address, which is fine. 47 02:36.700 --> 02:40.500 We know that is 10 dot 20 dot 1 dot 254. 48 02:40.500 --> 02:42.300 Let's do some other quick verifications. 49 02:42.300 --> 02:45.240 Let's just do a show IP interface brief. 50 02:45.240 --> 02:47.080 And a few things we want to note. 51 02:47.080 --> 02:51.520 First, we have this interface virtual port group zero. 52 02:51.520 --> 02:53.720 Let's go ahead and get that out of the way. 53 02:53.720 --> 02:59.480 There's also, if you do a show VRF, there's also this VRF called GS. 54 02:59.480 --> 03:04.360 These are some components that are pre-configured for enabling the guest shell. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:59.480 --> 03:04.360 These are some components that are pre-configured for enabling the guest shell. 55 03:04.360 --> 03:07.330 We're not going to get into that right now, but that's why we have some extra 56 03:07.330 --> 03:08.440 things here 57 03:08.440 --> 03:12.710 that you would not have on a normal blank route or so to speak, if you would 58 03:12.710 --> 03:13.640 just configured 59 03:13.640 --> 03:14.640 it. 60 03:14.640 --> 03:18.630 Also note that our gigabit one interface has been properly configured with its 61 03:18.630 --> 03:19.820 IP address 62 03:19.820 --> 03:23.640 from DHCP and it is up up. 63 03:23.640 --> 03:27.960 However, our gigabit two interface is not yet configured. 64 03:27.960 --> 03:31.480 So let's go ahead and go into configuration mode here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 03:27.960 --> 03:31.480 So let's go ahead and go into configuration mode here. 65 03:31.480 --> 03:34.200 And we'll do some basic configuration. 66 03:34.200 --> 03:39.000 Let's start with the host name, again, we'll just make this AWS R1. 67 03:39.000 --> 03:42.200 Let's configure our gigabit two interface. 68 03:42.200 --> 03:44.680 We'll put in the IP address. 69 03:44.680 --> 03:47.000 Now we do have two choices here. 70 03:47.000 --> 03:51.490 When it comes to the IP address, we could at this point hard code in the 71 03:51.490 --> 03:52.480 address that 72 03:52.480 --> 03:58.000 we know we told AWS to use for this interface. 73 03:58.000 --> 04:02.630 For that matter, we could hard code the gigabit one interface if we wanted to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:58.000 --> 04:02.630 For that matter, we could hard code the gigabit one interface if we wanted to 74 04:02.630 --> 04:03.200 as well. 75 04:03.200 --> 04:10.090 Or we can just let AWS give this interface its address through DHCP, just like 76 04:10.090 --> 04:10.720 we did 77 04:10.720 --> 04:13.000 for interface gigabit one. 78 04:13.000 --> 04:17.280 So let's go ahead and take that method just so we can see how it works. 79 04:17.280 --> 04:22.720 So we'll just say IP address DHCP and we'll do a no shut. 80 04:22.720 --> 04:26.960 Let's go ahead and exit configuration for now and just do a little bit of 81 04:26.960 --> 04:29.040 verification. 82 04:29.040 --> 04:34.440 First, let's ping 10 dot 20 dot one dot one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 04:29.040 --> 04:34.440 First, let's ping 10 dot 20 dot one dot one. 83 04:34.440 --> 04:35.760 This is the default gateway. 84 04:35.760 --> 04:38.440 This is AWS's address. 85 04:38.440 --> 04:42.080 We can also tell this if we do a show IP route. 86 04:42.080 --> 04:49.050 Notice that we have a static default route pre-configured pointing to the AWS 87 04:49.050 --> 04:50.120 router. 88 04:50.120 --> 04:53.640 That also means that we should be able to ping out to the internet. 89 04:53.640 --> 04:57.600 So let's just ping the infamous eight dot eight dot eight dot eight. 90 04:57.600 --> 05:00.200 We can see that that is working as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 04:57.600 --> 05:00.200 We can see that that is working as well. 91 05:00.200 --> 05:03.280 And DNS is properly configured as well. 92 05:03.280 --> 05:08.330 If we were to ping something like www dot Cisco dot com, we can see that that 93 05:08.330 --> 05:09.320 successfully 94 05:09.320 --> 05:12.880 looks up the IP address and we can ping it. 95 05:12.880 --> 05:18.310 So overall, we have some basic connectivity here already working from router 96 05:18.310 --> 05:19.040 one since 97 05:19.040 --> 05:23.560 we have that internet gateway configured in our VPC. 98 05:23.560 --> 05:27.830 The next thing we want to do now that we have our interfaces configured is we 99 05:27.830 --> 05:28.440 do have to 100 05:28.440 --> 05:33.960 go modify the routing table for the network 10 subnet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 05:28.440 --> 05:33.960 go modify the routing table for the network 10 subnet. 101 05:33.960 --> 05:37.280 So let's go back over to our VPC. 102 05:37.280 --> 05:42.970 So when the VPC will go to route tables, we'll select our network 10 route 103 05:42.970 --> 05:43.320 table. 104 05:43.320 --> 05:45.040 We'll go to routes. 105 05:45.040 --> 05:46.840 We'll edit routes. 106 05:46.840 --> 05:48.480 Then we'll add a route. 107 05:48.480 --> 05:51.680 And of course, the one we want to add is the default. 108 05:51.680 --> 05:55.120 But this time we're not going to point it to the internet gateway. 109 05:55.120 --> 05:59.120 This time we're going to point it to a network interface. 110 05:59.120 --> 06:05.560 Specifically, we want to point it to router one's gigabit to interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 05:59.120 --> 06:05.560 Specifically, we want to point it to router one's gigabit to interface. 111 06:05.560 --> 06:09.720 That's the inside interface on our router. 112 06:09.720 --> 06:12.160 Let's go ahead and save the changes. 113 06:12.160 --> 06:17.920 And by the way, what that does is essentially modifies the DHCP scope for that 114 06:17.920 --> 06:18.720 subnet to 115 06:18.720 --> 06:24.760 give our clients the correct default gateway when they get their IP address. 116 06:24.760 --> 06:28.980 So now that that's done and out of the way before we forget, let's go back over 117 06:28.980 --> 06:29.200 and do 118 06:29.200 --> 06:33.320 some baseline configuration on router one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 118 06:29.200 --> 06:33.320 some baseline configuration on router one. 119 06:33.320 --> 06:36.470 So before we just put the configuration on there, let's just take a look at it 120 06:36.470 --> 06:37.120 real quickly 121 06:37.120 --> 06:39.520 here in notepad++. 122 06:39.520 --> 06:43.720 This is certainly not an extensive baseline configuration. 123 06:43.720 --> 06:48.250 It's just doing things like turning on millisecond timers for our time stamps, 124 06:48.250 --> 06:49.400 for our debugging 125 06:49.400 --> 06:51.360 and our logging. 126 06:51.360 --> 06:53.640 It's also configuring my time zone. 127 06:53.640 --> 06:57.600 Of course, you would want to adjust these based on your time zone. 128 06:57.600 --> 07:01.800 I'm turning off the login message that comes on by default every time somebody WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 06:57.600 --> 07:01.800 I'm turning off the login message that comes on by default every time somebody 129 07:01.800 --> 07:02.680 successfully 130 07:02.680 --> 07:04.480 logs in. 131 07:04.480 --> 07:10.320 Notice also under the VTY lines, we're setting the exact time out to zero zero, 132 07:10.320 --> 07:11.040 which is 133 07:11.040 --> 07:12.400 never. 134 07:12.400 --> 07:15.470 We're doing this, of course, because it's a lab that way we don't keep getting 135 07:15.470 --> 07:15.880 kicked 136 07:15.880 --> 07:16.880 out. 137 07:16.880 --> 07:21.270 We're turning on logging synchronous, which simply causes commands to be re-ty 138 07:21.270 --> 07:21.640 ped if 139 07:21.640 --> 07:25.980 you're in the middle of typing one when a console message comes up and we're 140 07:25.980 --> 07:26.600 changing 141 07:26.600 --> 07:31.300 the history size so that we have more of a scrollback buffer when we're going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 141 07:26.600 --> 07:31.300 the history size so that we have more of a scrollback buffer when we're going 142 07:31.300 --> 07:31.800 back through 143 07:31.800 --> 07:33.600 previous commands. 144 07:33.600 --> 07:38.360 We're also configuring an NTP server here so it can pull down the time. 145 07:38.360 --> 07:41.760 These, of course, can all be adjusted to meet your needs, but this is just a 146 07:41.760 --> 07:42.440 really, really 147 07:42.440 --> 07:45.480 basic baseline configuration. 148 07:45.480 --> 07:50.440 Let's go ahead and put all of this on the router one. 149 07:50.440 --> 07:54.120 So we simply put all those things into router one. 150 07:54.120 --> 07:57.920 So that takes care of some basic configuration for router one. 151 07:57.920 --> 08:03.340 Next up, let's see if our subnet 10 can actually get out to the internet like WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 07:57.920 --> 08:03.340 Next up, let's see if our subnet 10 can actually get out to the internet like 152 08:03.340 --> 08:04.480 the router itself 153 08:04.480 --> 08:05.480 can.