WEBVTT 1 00:00.000 --> 00:08.480 So next up, we're going to deploy the Catalyst 8000V into our AWS environment. 2 00:08.480 --> 00:12.710 Now, this isn't really going to be all that different from how we just deployed 3 00:12.710 --> 00:13.280 our Linux 4 00:13.280 --> 00:14.280 workstation. 5 00:14.280 --> 00:19.200 It's just going to be another instance in AWS, where it's going to get a little 6 00:19.200 --> 00:19.520 bit 7 00:19.520 --> 00:23.370 different is of course, it's going to have two network cards, one connected to 8 00:23.370 --> 00:24.920 each subnet, 9 00:24.920 --> 00:28.870 one for the outside interface connected to the internet, which will also be 10 00:28.870 --> 00:29.560 getting an 11 00:29.560 --> 00:31.960 elastic IP assigned to it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:29.560 --> 00:31.960 elastic IP assigned to it. 12 00:31.960 --> 00:36.860 And of course, the other interface for the inside that's connecting to the same 13 00:36.860 --> 00:37.400 subnet 14 00:37.400 --> 00:41.400 that our workstation or jump box is currently on. 15 00:41.400 --> 00:46.260 Now another substantial difference here with doing, we'll say a traditional SD- 16 00:46.260 --> 00:47.280 WAN router 17 00:47.280 --> 00:51.000 is this is not going to come up in controller mode. 18 00:51.000 --> 00:56.800 This is going to come up in standalone mode as a traditional Catalyst 8000V. 19 00:56.800 --> 01:00.880 So we will have to convert this to controller mode. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:56.800 --> 01:00.880 So we will have to convert this to controller mode. 20 01:00.880 --> 01:07.240 Once we do that, tickle script or TCL script will no longer be available. 21 01:07.240 --> 01:11.910 And we're going to be using that to put our certificate onto the router, just 22 01:11.910 --> 01:12.400 because 23 01:12.400 --> 01:14.800 it's a quick, easy way to do it. 24 01:14.800 --> 01:19.040 So therefore, the order here is going to be very important. 25 01:19.040 --> 01:23.900 We need to put the certificate on, then converter to controller mode, and then 26 01:23.900 --> 01:25.960 do our configuration. 27 01:25.960 --> 01:30.680 We also can't do our configuration first, because when you change to controller WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 01:25.960 --> 01:30.680 We also can't do our configuration first, because when you change to controller 28 01:30.680 --> 01:31.200 mode, 29 01:31.200 --> 01:33.840 you lose all of your current configuration. 30 01:33.840 --> 01:37.930 So the order is going to be a little bit important, but our goal in this video 31 01:37.930 --> 01:38.920 is to deploy the 32 01:38.920 --> 01:45.390 8000V, switch it over to controller mode, then put our configuration on it and 33 01:45.390 --> 01:45.800 get it 34 01:45.800 --> 01:49.240 connected into our SD-WAN environment. 35 01:49.240 --> 01:50.840 So that's a lot to do. 36 01:50.840 --> 01:55.080 Let's just jump in and get started. 37 01:55.080 --> 02:01.560 So starting off here on console home, let's begin by going over here to EC2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 37 01:55.080 --> 02:01.560 So starting off here on console home, let's begin by going over here to EC2. 38 02:01.560 --> 02:04.040 We'll choose to launch an instance. 39 02:04.040 --> 02:08.840 For the instance name, we'll simply call this AWS R1. 40 02:08.840 --> 02:15.360 And then for the image here in the search bar, we'll put C8000V. 41 02:15.360 --> 02:17.240 We'll do a search. 42 02:17.240 --> 02:22.370 And then here under the AWS marketplace, the one that we want is going to come 43 02:22.370 --> 02:22.800 up as 44 02:22.800 --> 02:24.600 the bottom choice. 45 02:24.600 --> 02:29.440 The catalyst 8000V for SD-WAN and routing. 46 02:29.440 --> 02:32.280 This is the bring your own license version. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:29.440 --> 02:32.280 This is the bring your own license version. 47 02:32.280 --> 02:35.750 Now of course, if you don't have your own license, you can of course choose one 48 02:35.750 --> 02:36.080 of the 49 02:36.080 --> 02:39.200 pay as you go models a little bit further up. 50 02:39.200 --> 02:42.240 But in this case, we're going to do the bring your own license. 51 02:42.240 --> 02:44.080 So we'll just hit select. 52 02:44.080 --> 02:48.430 Now one thing I've noticed here about AWS, I already have a subscription for 53 02:48.430 --> 02:49.040 this. 54 02:49.040 --> 02:53.680 I've launched numerous catalyst 8000Vs in this account. 55 02:53.680 --> 02:57.040 But it seems to ask this every single time. 56 02:57.040 --> 02:58.040 That's okay. 57 02:58.040 --> 03:00.240 I'm just going to go ahead and hit subscribe now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:58.040 --> 03:00.240 I'm just going to go ahead and hit subscribe now. 58 03:00.240 --> 03:02.840 It hasn't seemed to harm anything. 59 03:02.840 --> 03:06.640 But then this will come up ready to deploy the 8000V. 60 03:06.640 --> 03:08.440 Now of course, we have to change a few things. 61 03:08.440 --> 03:10.400 So let's scroll down. 62 03:10.400 --> 03:14.840 It wants the default to an instance type of C5 and large. 63 03:14.840 --> 03:17.960 You can actually go a little bit smaller if you want here. 64 03:17.960 --> 03:21.980 I'm going to leave this as the default, but you can choose what instance type 65 03:21.980 --> 03:22.720 you want. 66 03:22.720 --> 03:26.400 Of course, you can go larger if you have a larger environment. 67 03:26.400 --> 03:30.720 The bigger the instance type, the more throughput it can handle. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 03:26.400 --> 03:30.720 The bigger the instance type, the more throughput it can handle. 68 03:30.720 --> 03:33.320 So you need to choose your size accordingly. 69 03:33.320 --> 03:37.760 This being a lab, the C5 and large is going to be perfectly fine. 70 03:37.760 --> 03:42.150 For our key pair, I'm going to choose my existing key pair just to make it easy 71 03:42.150 --> 03:43.680 to log in. 72 03:43.680 --> 03:47.510 And then under the network settings, we're going to have to make some changes 73 03:47.510 --> 03:47.760 here. 74 03:47.760 --> 03:50.800 So the first thing we're going to want to do is hit edit. 75 03:50.800 --> 03:52.840 We're going to choose the correct VPC. 76 03:52.840 --> 03:55.200 So it's set to SD WAN. 77 03:55.200 --> 03:58.720 Our first interface is going to be on subnet one. 78 03:58.720 --> 04:02.440 That's going to be the outside interface, which is going to be our gigabit one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 03:58.720 --> 04:02.440 That's going to be the outside interface, which is going to be our gigabit one 79 04:02.440 --> 04:03.320 interface. 80 04:03.320 --> 04:05.440 So we'll leave that part alone. 81 04:05.440 --> 04:11.360 The auto assign public IP once again, I already have elastic IPs to assign. 82 04:11.360 --> 04:13.320 So I'm not going to do that. 83 04:13.320 --> 04:17.480 We're going to go ahead and use the same security group we used for the other 84 04:17.480 --> 04:18.360 interface. 85 04:18.360 --> 04:23.690 So we'll just choose security group one, then we'll hit advanced network 86 04:23.690 --> 04:24.960 configuration. 87 04:24.960 --> 04:27.320 And there's a few things here we want to do. 88 04:27.320 --> 04:29.640 First, we're going to set its IP address. 89 04:29.640 --> 04:36.120 So the outside interface is going to be 10 dot 20 dot 1 dot 254. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 04:29.640 --> 04:36.120 So the outside interface is going to be 10 dot 20 dot 1 dot 254. 90 04:36.120 --> 04:38.000 The rest of this is fine. 91 04:38.000 --> 04:40.960 And then we want to add a network interface. 92 04:40.960 --> 04:44.160 This network interface is going to be on the other subnet. 93 04:44.160 --> 04:47.800 So we need to make sure that we select subnet 10 here. 94 04:47.800 --> 04:54.280 And then set its primary address, which is going to be the 10 dot 20 dot 10 dot 95 04:54.280 --> 04:55.440 254. 96 04:55.440 --> 04:57.480 Everything else here should be fine. 97 04:57.480 --> 05:01.160 If we scroll down through the rest, the storage is going to be fine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 97 04:57.480 --> 05:01.160 If we scroll down through the rest, the storage is going to be fine. 98 05:01.160 --> 05:04.160 And we don't need to set any advanced details. 99 05:04.160 --> 05:07.080 So now let's go ahead and say to launch. 100 05:07.080 --> 05:08.480 It's launched successfully. 101 05:08.480 --> 05:10.680 Let's go back to instances. 102 05:10.680 --> 05:15.320 And we'll give this just a moment for the status checks to complete. 103 05:15.320 --> 05:19.440 So now that both of these status checks have been passed, the next thing we 104 05:19.440 --> 05:20.080 want to do 105 05:20.080 --> 05:24.000 is for convenience, we want to rename the interfaces. 106 05:24.000 --> 05:27.160 And we also need to map that elastic IP. 107 05:27.160 --> 05:31.670 But the problem is, since it has two interfaces, we need to know how to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 107 05:27.160 --> 05:31.670 But the problem is, since it has two interfaces, we need to know how to 108 05:31.670 --> 05:32.920 identify them. 109 05:32.920 --> 05:38.720 So let's go to the instance ID here, go down here to networking. 110 05:38.720 --> 05:43.000 And if we look down here, we can see the different interfaces. 111 05:43.000 --> 05:49.000 What we want to do is note which interface ID is tied to which private IPV for 112 05:49.000 --> 05:50.000 address. 113 05:50.000 --> 05:51.680 So we know which subnet it's on. 114 05:51.680 --> 05:56.440 And we want to be careful here because at this screen resolution, our interface 115 05:56.440 --> 05:56.920 ID is 116 05:56.920 --> 05:58.240 sort of wrapping around there. 117 05:58.240 --> 06:01.040 So we want to expand that column just a little bit. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 05:58.240 --> 06:01.040 So we want to expand that column just a little bit. 118 06:01.040 --> 06:07.060 And now we can see that the interface ID ending with seven F five nine is on 119 06:07.060 --> 06:09.120 subnet one. 120 06:09.120 --> 06:13.120 And the A nine eight F is on subnet 10. 121 06:13.120 --> 06:17.640 So now that we know that we can go over here to our network interfaces. 122 06:17.640 --> 06:23.040 And again, we'll take the one that ends in seven F five nine. 123 06:23.040 --> 06:25.920 We'll name this AWS R one. 124 06:25.920 --> 06:30.040 And again, since that's the one connected subnet one, that would be the gigabit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 124 06:25.920 --> 06:30.040 And again, since that's the one connected subnet one, that would be the gigabit 125 06:30.040 --> 06:31.720 one interface. 126 06:31.720 --> 06:33.920 So we'll name it accordingly. 127 06:33.920 --> 06:36.640 And again, just so we can see our names a little better, we can expand this 128 06:36.640 --> 06:37.000 column a 129 06:37.000 --> 06:38.480 little bit. 130 06:38.480 --> 06:42.480 And then this one would be gigabit two. 131 06:42.480 --> 06:45.280 That's the one connected to subnet 10. 132 06:45.280 --> 06:47.880 Again, this step is not entirely necessary. 133 06:47.880 --> 06:51.640 It's just to make things easier to reference as we go. 134 06:51.640 --> 06:54.080 Now the elastic IP, we do need to assign. 135 06:54.080 --> 06:56.680 So let's get down here to our elastic IPs. 136 06:56.680 --> 07:02.280 I do have an IP address reserved here for our one VPN zero, which is going to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 136 06:56.680 --> 07:02.280 I do have an IP address reserved here for our one VPN zero, which is going to 137 07:02.280 --> 07:02.920 be that 138 07:02.920 --> 07:04.680 outside interface. 139 07:04.680 --> 07:11.280 So under actions, we'll associate our elastic IP with the network interface. 140 07:11.280 --> 07:13.480 And again, this is where those names are a little bit nicer. 141 07:13.480 --> 07:16.800 We know it's going to go to the gigabit one interface. 142 07:16.800 --> 07:19.440 We could of course still do it by the number. 143 07:19.440 --> 07:21.760 The names just make it a little nicer. 144 07:21.760 --> 07:25.760 And then of course, it should list the private address, which it does. 145 07:25.760 --> 07:30.040 And we'll say it will allow it to be reassociated in case we need to. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 07:25.760 --> 07:30.040 And we'll say it will allow it to be reassociated in case we need to. 146 07:30.040 --> 07:34.370 Now that that address has been properly associated, we should now be able to 147 07:34.370 --> 07:36.160 use that public address 148 07:36.160 --> 07:40.480 to SSH into our newly deployed router. 149 07:40.480 --> 07:42.480 So here we see that we're connected. 150 07:42.480 --> 07:45.080 Let's go ahead and begin our configuration. 151 07:45.080 --> 07:49.630 The first thing we need to do, as I mentioned during the introduction, is we 152 07:49.630 --> 07:50.360 need to use 153 07:50.360 --> 07:55.920 TCL shell or tickle shell to put our certificate into this router. 154 07:55.920 --> 07:59.760 Now of course, the certificate has to be the same one that you use throughout 155 07:59.760 --> 08:00.400 your entire WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 155 07:59.760 --> 08:00.400 your entire 156 08:00.400 --> 08:03.200 deployment of SD WAN. 157 08:03.200 --> 08:05.400 So you should have this handy. 158 08:05.400 --> 08:08.240 I'm just going to go ahead and paste mine in. 159 08:08.240 --> 08:11.760 So now we have our certificate in our router. 160 08:11.760 --> 08:15.940 If you need the script to know how to do that, it is included in the code 161 08:15.940 --> 08:17.040 window below this 162 08:17.040 --> 08:18.520 video. 163 08:18.520 --> 08:22.440 The next thing we want to do is put this into controller mode. 164 08:22.440 --> 08:26.880 All you have to do is say a controller mode enable. 165 08:26.880 --> 08:30.480 It's going to tell us that it's going to wipe out the entire configuration. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 165 08:26.880 --> 08:30.480 It's going to tell us that it's going to wipe out the entire configuration. 166 08:30.480 --> 08:32.560 We already know that that's fine. 167 08:32.560 --> 08:34.600 So we're going to go ahead and hit enter. 168 08:34.600 --> 08:39.560 It's also going to tell us that the bootstrap config file is missing. 169 08:39.560 --> 08:43.920 That's the file that would automatically connect this into SD WAN and so on. 170 08:43.920 --> 08:44.920 That's okay. 171 08:44.920 --> 08:47.080 We're going to put our own baseline config on here. 172 08:47.080 --> 08:51.720 So when it says you want to abort, we're going to say no, we want to proceed. 173 08:51.720 --> 08:56.160 At this point, it's going to kick us out because it's going to reboot. 174 08:56.160 --> 08:59.560 So we'll give router one just a few moments to reboot and we'll jump ahead 175 08:59.560 --> 09:00.280 until router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 175 08:59.560 --> 09:00.280 until router 176 09:00.280 --> 09:04.200 one is back up and running in controller mode. 177 09:04.200 --> 09:05.960 So it's been just a few minutes. 178 09:05.960 --> 09:08.520 AWS R1 rebooted. 179 09:08.520 --> 09:12.580 And if we try to type configure terminal, it's going to tell us we can't do 180 09:12.580 --> 09:13.440 that because 181 09:13.440 --> 09:16.720 we are in fact in controller mode, which is good. 182 09:16.720 --> 09:18.360 That's exactly what we want. 183 09:18.360 --> 09:23.600 So instead, we need to go into config transaction. 184 09:23.600 --> 09:28.280 Now notice there's a slight delay when you go into config transaction. 185 09:28.280 --> 09:32.710 The reason I'm pointing that out is if you like to copy and paste configuration WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 185 09:28.280 --> 09:32.710 The reason I'm pointing that out is if you like to copy and paste configuration 186 09:32.710 --> 09:33.080 as I 187 09:33.080 --> 09:37.000 do, well, that can actually cause a little bit of an issue. 188 09:37.000 --> 09:41.890 So you might want to make sure that you don't paste the config transaction 189 09:41.890 --> 09:42.920 along with the 190 09:42.920 --> 09:45.480 configuration you actually want to put in. 191 09:45.480 --> 09:47.760 It doesn't always work very well. 192 09:47.760 --> 09:52.520 So going to config transaction first and then paste in your configuration. 193 09:52.520 --> 09:56.300 The things we're going to do, we're going to go ahead and configure the host 194 09:56.300 --> 09:56.720 name as 195 09:56.720 --> 10:02.400 well as the system IP, the site ID, the organization name, the V bond external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 195 09:56.720 --> 10:02.400 well as the system IP, the site ID, the organization name, the V bond external 196 10:02.400 --> 10:04.280 server address, 197 10:04.280 --> 10:06.440 and then we're going to commit those changes. 198 10:06.440 --> 10:10.210 Now as you can see, we get a whole lot of errors from smart licensing and stuff 199 10:10.210 --> 10:10.520 here 200 10:10.520 --> 10:15.200 on the screen right away, making it very difficult to see what we just did. 201 10:15.200 --> 10:20.440 Therefore, I have included the script below this video for your reference. 202 10:20.440 --> 10:24.400 The next thing we have to do is install the root certificate chain, which is a 203 10:24.400 --> 10:25.160 certificate 204 10:25.160 --> 10:27.400 we put on here earlier. 205 10:27.400 --> 10:29.800 So we can just paste in the command to do that. 206 10:29.800 --> 10:35.360 It's request platform software, SD WAN, root cert chain install. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 10:29.800 --> 10:35.360 It's request platform software, SD WAN, root cert chain install. 207 10:35.360 --> 10:41.260 And then we call to the name of the file that we created previous to our reboot 208 10:41.260 --> 10:41.360 . 209 10:41.360 --> 10:45.320 This again takes a couple seconds, but we can see that it has now successfully 210 10:45.320 --> 10:45.960 installed 211 10:45.960 --> 10:48.080 the certificate chain. 212 10:48.080 --> 10:53.280 So now we can put in the configuration for SD WAN, including the gigabit one 213 10:53.280 --> 10:54.600 interface, 214 10:54.600 --> 10:59.420 configuring it as a tunnel, allowing all of our services, turning on the encaps 215 10:59.420 --> 11:00.200 ulation, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 215 10:59.420 --> 11:00.200 ulation, 216 11:00.200 --> 11:03.160 and then creating our tunnel one interface. 217 11:03.160 --> 11:05.640 So then we can exit out of configuration. 218 11:05.640 --> 11:10.670 So then our last step is going to be to actually register this with SD WAN 219 11:10.670 --> 11:11.600 manager. 220 11:11.600 --> 11:17.740 So what you need to do is collect an available chassis number and token from SD 221 11:17.740 --> 11:18.280 WAN. 222 11:18.280 --> 11:22.710 I already have one collected from my environment, so I'm simply going to paste 223 11:22.710 --> 11:23.640 in the command. 224 11:23.640 --> 11:26.920 Once again, it's a long command and hard to see. 225 11:26.920 --> 11:31.760 So all of this is referenced in the code block below this video. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 225 11:26.920 --> 11:31.760 So all of this is referenced in the code block below this video. 226 11:31.760 --> 11:37.920 Once all of this is correct, this should take care of configuring AWS R1. 227 11:37.920 --> 11:44.480 To verify it, let's go ahead and jump over to our SD WAN manager. 228 11:44.480 --> 11:50.610 So as we see here on the SD WAN monitor overview page, we now have three WAN 229 11:50.610 --> 11:51.400 edges. 230 11:51.400 --> 11:55.840 That would be two on-prem plus the new one we just deployed. 231 11:55.840 --> 12:01.340 If we click on the three here to look at more detail, we see that AWS R1 is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 231 11:55.840 --> 12:01.340 If we click on the three here to look at more detail, we see that AWS R1 is 232 12:01.340 --> 12:03.400 currently reachable. 233 12:03.400 --> 12:06.920 Now its health is still listed there as a red X. 234 12:06.920 --> 12:09.060 That's of course because it just came online. 235 12:09.060 --> 12:14.000 We don't have any CPU load or memory utilization information from that router 236 12:14.000 --> 12:14.760 just yet. 237 12:14.760 --> 12:16.080 It just came up. 238 12:16.080 --> 12:21.600 However, it is properly connected in here to SD WAN. 239 12:21.600 --> 12:27.440 So in this video, we deployed AWS R1 into our environment. 240 12:27.440 --> 12:30.840 We got it configured into controller mode. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 240 12:27.440 --> 12:30.840 We got it configured into controller mode. 241 12:30.840 --> 12:36.330 Then we put on our baseline configuration and connected it into SD WAN where it 242 12:36.330 --> 12:37.240 is now 243 12:37.240 --> 12:40.600 in the process of being brought online. 244 12:40.600 --> 12:44.720 And then in our next video, we're going to roll out our templates. 245 12:44.720 --> 12:54.720 [BLANK_AUDIO]