WEBVTT 1 00:00.000 --> 00:08.680 So our first step is going to be to jump in and create a device template. 2 00:08.680 --> 00:13.650 Now part of that device template, we're also going to put in two feature 3 00:13.650 --> 00:14.840 templates. 4 00:14.840 --> 00:17.890 Something to keep in mind as we go through here, and I will sort of show you 5 00:17.890 --> 00:18.280 where to 6 00:18.280 --> 00:23.840 do this, you can actually create the feature templates separately on their own 7 00:23.840 --> 00:24.240 and then 8 00:24.240 --> 00:30.040 apply them or what we can do, which I generally prefer to do is while we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:24.240 --> 00:30.040 apply them or what we can do, which I generally prefer to do is while we're 9 00:30.040 --> 00:31.280 going through 10 00:31.280 --> 00:36.480 our device template, we can actually add and create the feature templates on 11 00:36.480 --> 00:37.240 the fly. 12 00:37.240 --> 00:40.040 Now we can't edit them that way. 13 00:40.040 --> 00:43.420 So if we need to change them later, well, then we still have to go over to 14 00:43.420 --> 00:45.240 feature templates. 15 00:45.240 --> 00:49.120 We'll see as we jump in and start looking at the interface. 16 00:49.120 --> 00:53.710 But our main goal here is going to be to start the configuration of our device 17 00:53.710 --> 00:54.600 template. 18 00:54.600 --> 00:59.110 And then there's two specific feature templates that we'll be adding in this 19 00:59.110 --> 00:59.760 video. 20 00:59.760 --> 01:06.160 So let's go ahead and jump into SD-WAN and get started. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:59.760 --> 01:06.160 So let's go ahead and jump into SD-WAN and get started. 21 01:06.160 --> 01:12.360 So starting off here on the SD-WAN dashboard, let's go over to our main menu. 22 01:12.360 --> 01:16.800 We'll go to configuration and then we want to go to templates. 23 01:16.800 --> 01:20.820 Now under templates, there are four different sections here, configuration 24 01:20.820 --> 01:21.760 groups, feature 25 01:21.760 --> 01:26.080 profiles, device templates, and feature templates. 26 01:26.080 --> 01:30.670 For this skill, we're going to be focusing on device templates and feature WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:26.080 --> 01:30.670 For this skill, we're going to be focusing on device templates and feature 27 01:30.670 --> 01:31.640 templates. 28 01:31.640 --> 01:36.750 Now as I mentioned during the introduction, we can create feature templates 29 01:36.750 --> 01:37.720 while we're 30 01:37.720 --> 01:40.360 creating our device templates. 31 01:40.360 --> 01:45.280 However, if we need to edit one later, we are still going to have to come over 32 01:45.280 --> 01:45.680 here 33 01:45.680 --> 01:48.680 to the feature templates and edit them. 34 01:48.680 --> 01:51.760 Now as we can see, there are currently none installed. 35 01:51.760 --> 01:54.920 So we're going to be starting with our device templates. 36 01:54.920 --> 01:57.850 So going over to the device templates section, what we're going to do is we're 37 01:57.850 --> 01:58.280 going to go 38 01:58.280 --> 02:03.780 over here to create template and we're going to be creating a template from WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:58.280 --> 02:03.780 over here to create template and we're going to be creating a template from 39 02:03.780 --> 02:05.400 feature templates. 40 02:05.400 --> 02:09.880 The device template is a combination of feature templates. 41 02:09.880 --> 02:13.240 So let's go ahead and say from feature template. 42 02:13.240 --> 02:17.520 First thing we need to do is choose the device model, where of course, going to 43 02:17.520 --> 02:17.960 choose the 44 02:17.960 --> 02:22.240 catalyst 8000 V for the device role. 45 02:22.240 --> 02:26.560 This is going to be SD WAN edge for the template name. 46 02:26.560 --> 02:33.560 I'm simply going to call it HQ underscore WAN edge. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:26.560 --> 02:33.560 I'm simply going to call it HQ underscore WAN edge. 47 02:33.560 --> 02:37.830 Now the description field, as you can see by that little red asterisk is 48 02:37.830 --> 02:39.120 actually required 49 02:39.120 --> 02:40.120 here. 50 02:40.120 --> 02:44.310 So you have to put in a description, quite honestly, my descriptions are 51 02:44.310 --> 02:45.320 usually pretty 52 02:45.320 --> 02:49.560 similar to the name because I try to make the name descriptive. 53 02:49.560 --> 02:57.880 So in this case, I'm just going to call it HQ WAN edge routers. 54 02:57.880 --> 03:01.200 Then we start creating our feature templates. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:57.880 --> 03:01.200 Then we start creating our feature templates. 55 03:01.200 --> 03:05.820 Now we're actually going to be creating quite a few feature templates here in 56 03:05.820 --> 03:06.560 our device 57 03:06.560 --> 03:07.720 template. 58 03:07.720 --> 03:13.200 But to start with, let's start here under Cisco triple A. So let's scroll down 59 03:13.200 --> 03:14.840 a little bit. 60 03:14.840 --> 03:16.720 We'll click on the drop down. 61 03:16.720 --> 03:20.880 And this is where I was saying you can actually create a template. 62 03:20.880 --> 03:24.000 So we'll just go right here and say create template. 63 03:24.000 --> 03:27.120 This will bring up the create template dialog. 64 03:27.120 --> 03:32.900 For this template name, we'll simply call this local user because we're just WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 03:27.120 --> 03:32.900 For this template name, we'll simply call this local user because we're just 65 03:32.900 --> 03:33.400 going to 66 03:33.400 --> 03:37.280 use this to configure local authentication on these devices. 67 03:37.280 --> 03:42.650 Of course, if we had triple A like a radius or a tachdach server in our 68 03:42.650 --> 03:44.080 environment, we 69 03:44.080 --> 03:46.400 could configure that here. 70 03:46.400 --> 03:51.880 But we're just going to be doing a local user for the description once again, 71 03:51.880 --> 03:52.880 local admin 72 03:52.880 --> 03:54.920 user. 73 03:54.920 --> 04:01.600 Now notice here under our local users, there's already a user called admin. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:54.920 --> 04:01.600 Now notice here under our local users, there's already a user called admin. 74 04:01.600 --> 04:05.400 The problem is it's not the password that we want it to be. 75 04:05.400 --> 04:10.270 So what we want to do is come over here and under action, we're going to click 76 04:10.270 --> 04:10.440 edit. 77 04:10.440 --> 04:14.760 And for the password, we're going to put in the password that we want. 78 04:14.760 --> 04:16.960 Of course, we have to confirm it. 79 04:16.960 --> 04:19.120 And then we hit save changes. 80 04:19.120 --> 04:23.360 The next thing we have to do is scroll down a little bit more under 81 04:23.360 --> 04:24.720 authorization. 82 04:24.720 --> 04:26.920 We want to change this setting. 83 04:26.920 --> 04:30.200 Now if you're not familiar with how this works, you can see that each of these WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 04:26.920 --> 04:30.200 Now if you're not familiar with how this works, you can see that each of these 84 04:30.200 --> 04:31.280 have three 85 04:31.280 --> 04:32.440 settings. 86 04:32.440 --> 04:38.030 If we change this to global, that means that we're going to make this setting 87 04:38.030 --> 04:38.760 on every 88 04:38.760 --> 04:42.960 single device that we apply this template to. 89 04:42.960 --> 04:46.560 We can also set it to device specific. 90 04:46.560 --> 04:51.400 That means that when we go to apply this template, it will ask us for this 91 04:51.400 --> 04:52.320 information 92 04:52.320 --> 04:54.400 for each device. 93 04:54.400 --> 05:00.130 Some things, just as an example, OSPF router ID would have to be different for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 04:54.400 --> 05:00.130 Some things, just as an example, OSPF router ID would have to be different for 94 05:00.130 --> 05:01.400 each device. 95 05:01.400 --> 05:05.480 I could not set that globally or else they would all be the same. 96 05:05.480 --> 05:08.760 Also things like an IP address on a given interface. 97 05:08.760 --> 05:12.400 So we're going to be using this device specific a lot. 98 05:12.400 --> 05:16.120 You can also, of course, just leave it at the default setting, which is what 99 05:16.120 --> 05:16.600 most of 100 05:16.600 --> 05:18.960 these are set to to begin with. 101 05:18.960 --> 05:25.000 In this case, we want to globally change this setting to be on that way. 102 05:25.000 --> 05:29.970 We're going to do console authorization on all of our devices using this 103 05:29.970 --> 05:30.840 username and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 05:29.970 --> 05:30.840 username and 104 05:30.840 --> 05:32.320 password. 105 05:32.320 --> 05:36.750 And the last thing we need to set if we scroll all the way to the bottom under 106 05:36.750 --> 05:38.040 the authentication 107 05:38.040 --> 05:43.840 and authorization order, if we click on this, we need to choose local. 108 05:43.840 --> 05:46.880 We're telling it to use the local database. 109 05:46.880 --> 05:52.700 Of course, if we hit added radius or tach-ax groups up above, they would show 110 05:52.700 --> 05:53.640 up here. 111 05:53.640 --> 05:57.960 Since we've only configured local, that's the only thing that shows up. 112 05:57.960 --> 06:04.450 So next we hit save and we see that now under Cisco AAA, it now has our feature WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 112 05:57.960 --> 06:04.450 So next we hit save and we see that now under Cisco AAA, it now has our feature 113 06:04.450 --> 06:05.520 template, 114 06:05.520 --> 06:08.760 local user, that we just created. 115 06:08.760 --> 06:14.490 The other thing we want to create, if we scroll down here almost to the bottom, 116 06:14.490 --> 06:14.680 there's a 117 06:14.680 --> 06:19.080 section here called CLI add-on template. 118 06:19.080 --> 06:23.760 We can use this template to add things to our configuration that aren't 119 06:23.760 --> 06:24.680 necessarily 120 06:24.680 --> 06:29.820 supported here by device templates and, of course, the feature templates that 121 06:29.820 --> 06:30.520 they call WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 06:29.820 --> 06:30.520 they call 122 06:30.520 --> 06:31.760 to. 123 06:31.760 --> 06:35.000 So there's actually sort of two things we want to set here. 124 06:35.000 --> 06:37.000 So let's click on the dropdown. 125 06:37.000 --> 06:39.280 Let's click on create template. 126 06:39.280 --> 06:43.430 Now one thing to note, it's a little hard to read there, but notice it says 127 06:43.430 --> 06:44.640 that the CLI 128 06:44.640 --> 06:52.020 add-on template is supported with iOS XE 17.2.1 version onward. 129 06:52.020 --> 06:57.860 So we can't use these particular templates with older devices, but our devices 130 06:57.860 --> 06:58.460 are new 131 06:58.460 --> 06:59.500 enough. 132 06:59.500 --> 07:02.160 So let's give this a template name. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 06:59.500 --> 07:02.160 So let's give this a template name. 133 07:02.160 --> 07:07.910 We'll simply call this CLI underscore commands and we'll pretty much make it 134 07:07.910 --> 07:10.340 the same description. 135 07:10.340 --> 07:15.160 And then here under the CLI configuration is where we put whatever commands we 136 07:15.160 --> 07:15.500 want to 137 07:15.500 --> 07:18.300 push through to the devices. 138 07:18.300 --> 07:26.780 Now the first thing we want to set is a command that's platform console serial. 139 07:26.780 --> 07:30.080 Now you might be asking, why do we want this command? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 139 07:26.780 --> 07:30.080 Now you might be asking, why do we want this command? 140 07:30.080 --> 07:34.650 Well, some versions of code and not necessarily all of them, but I put this in 141 07:34.650 --> 07:35.420 here just in 142 07:35.420 --> 07:38.600 case on the virtual devices. 143 07:38.600 --> 07:43.530 So in other words, a device running in a virtual environment, some of the code 144 07:43.530 --> 07:44.680 will default 145 07:44.680 --> 07:50.900 when you push your templates down, they'll default to a virtual console, 146 07:50.900 --> 07:51.920 meaning it wants 147 07:51.920 --> 07:57.080 to use the VGA interface on these devices. 148 07:57.080 --> 07:59.880 Now that's not necessarily a problem. 149 07:59.880 --> 08:06.960 If you want to access them through VGA, in other words, for example, in VMware WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 149 07:59.880 --> 08:06.960 If you want to access them through VGA, in other words, for example, in VMware 150 08:06.960 --> 08:07.520 ESXi, 151 08:07.520 --> 08:10.320 you would open the console to the device. 152 08:10.320 --> 08:13.400 That would be like a VGA output. 153 08:13.400 --> 08:15.440 We want to stay with serial. 154 08:15.440 --> 08:20.600 That way we can use the terminal software in CML2. 155 08:20.600 --> 08:26.640 So this is being put in here just to ensure that our console remains a serial 156 08:26.640 --> 08:27.440 port and 157 08:27.440 --> 08:31.280 does not try to switch over to being virtual. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 08:27.440 --> 08:31.280 does not try to switch over to being virtual. 158 08:31.280 --> 08:36.800 The other command we're going to put in here is simply no logging console. 159 08:36.800 --> 08:40.200 And the reason we're doing this one I've already explained, but it's simply 160 08:40.200 --> 08:41.000 because this is 161 08:41.000 --> 08:45.120 a lab environment and we don't need to be seeing all the console messages. 162 08:45.120 --> 08:49.740 If we want to see something, we can of course always just do a show log on the 163 08:49.740 --> 08:50.680 devices. 164 08:50.680 --> 08:57.120 So now that we have our CLI template created, let's go ahead and hit save. 165 08:57.120 --> 09:01.600 Now if we wanted to just to make sure that we have this and nothing happens, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 165 08:57.120 --> 09:01.600 Now if we wanted to just to make sure that we have this and nothing happens, 166 09:01.600 --> 09:02.160 like we 167 09:02.160 --> 09:07.190 accidentally hit cancel or close the window, we'll go ahead and hit create at 168 09:07.190 --> 09:08.240 this point. 169 09:08.240 --> 09:11.540 This is of course not a complete device template. 170 09:11.540 --> 09:15.920 If we were to push this out to the devices right now, we would have a massive 171 09:15.920 --> 09:16.520 problem 172 09:16.520 --> 09:21.510 because we haven't even configured VPN zero, which means theoretically we would 173 09:21.510 --> 09:22.040 cut the 174 09:22.040 --> 09:26.160 device off from talking to VManage itself. 175 09:26.160 --> 09:29.720 Now the good news there is the device will prevent that. 176 09:29.720 --> 09:32.360 What'll happen is it'll try to push out the config. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 176 09:29.720 --> 09:32.360 What'll happen is it'll try to push out the config. 177 09:32.360 --> 09:36.560 It'll realize it can no longer talk to VManage and then it would revert. 178 09:36.560 --> 09:40.660 So if we even tried to push this right now, it would fail. 179 09:40.660 --> 09:44.240 But two things I want to show you before we move on. 180 09:44.240 --> 09:49.280 First, we can of course go to this extended menu over here and this is what we 181 09:49.280 --> 09:50.040 'll be doing 182 09:50.040 --> 09:51.040 moving forward. 183 09:51.040 --> 09:55.450 We'll be coming in here and editing this so we can hit edit and come right back 184 09:55.450 --> 09:55.800 into 185 09:55.800 --> 09:58.160 the same page we were just in. 186 09:58.160 --> 10:03.280 Of course, if we make any changes, we would then hit update. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 186 09:58.160 --> 10:03.280 Of course, if we make any changes, we would then hit update. 187 10:03.280 --> 10:07.890 But the other thing to note is for example, if we were to come down here and 188 10:07.890 --> 10:08.480 look at our 189 10:08.480 --> 10:15.080 CLI template, if we click on this drop down and we save you template, this will 190 10:15.080 --> 10:15.760 show us 191 10:15.760 --> 10:17.120 the template. 192 10:17.120 --> 10:19.240 There are the two commands we put in. 193 10:19.240 --> 10:22.600 We see the device type, the template name, the description. 194 10:22.600 --> 10:26.320 Notice that nothing here can be edited. 195 10:26.320 --> 10:30.640 Although it lets me type in this window, there's no save. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 195 10:26.320 --> 10:30.640 Although it lets me type in this window, there's no save. 196 10:30.640 --> 10:34.920 The only choice at the bottom is cancel. 197 10:34.920 --> 10:37.240 So of course, if I cancel, it's going to do just that. 198 10:37.240 --> 10:38.920 It's going to cancel. 199 10:38.920 --> 10:43.090 And if I were to scroll down again, yes, it puts you at the top of the page 200 10:43.090 --> 10:43.840 every time. 201 10:43.840 --> 10:48.180 But if I were to click on see it like a man's again, go to view template, 202 10:48.180 --> 10:48.720 notice what I 203 10:48.720 --> 10:51.260 just typed is gone. 204 10:51.260 --> 10:56.310 This is what I meant when I said we can create our feature templates from the 205 10:56.310 --> 10:57.840 device templates, 206 10:57.840 --> 11:00.280 but we cannot edit them here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 10:57.840 --> 11:00.280 but we cannot edit them here. 207 11:00.280 --> 11:04.160 If we wanted to edit this, we would cancel here. 208 11:04.160 --> 11:06.960 We would go up here to feature templates. 209 11:06.960 --> 11:12.000 Here are the two feature templates we've already created, our local user and 210 11:12.000 --> 11:12.480 our CLI 211 11:12.480 --> 11:13.920 commands. 212 11:13.920 --> 11:18.880 Now I go to the extended menu and I can edit these from here. 213 11:18.880 --> 11:25.920 Now if I were to change something and hit update, it will actually change it. 214 11:25.920 --> 11:31.020 So now we'll just come in here and save you, notice that now the test is in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 214 11:25.920 --> 11:31.020 So now we'll just come in here and save you, notice that now the test is in 215 11:31.020 --> 11:31.440 there. 216 11:31.440 --> 11:35.160 Once again, I can't change anything because I said view. 217 11:35.160 --> 11:36.440 So let me go ahead and cancel. 218 11:36.440 --> 11:38.680 And of course, we don't want to leave test in there. 219 11:38.680 --> 11:39.680 That would be bad. 220 11:39.680 --> 11:41.360 It's not a valid command. 221 11:41.360 --> 11:47.840 So let's go back into edit, take our test back out and then update it again. 222 11:47.840 --> 11:53.000 So that's what we need to do to edit a feature template after we've already 223 11:53.000 --> 11:54.080 created it. 224 11:54.080 --> 11:57.520 So that concludes everything we need to do in this video. 225 11:57.520 --> 12:00.440 We have our device template created here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 225 11:57.520 --> 12:00.440 We have our device template created here. 226 12:00.440 --> 12:06.040 We've created these two feature templates just to handle some baseline 227 12:06.040 --> 12:06.480 configuration. 228 12:06.480 --> 12:11.620 So now that this is complete, our next step of course would be to edit this and 229 12:11.620 --> 12:12.480 then configure 230 12:12.480 --> 12:14.600 our VPN zero. 231 12:14.600 --> 12:16.960 And that's exactly what we're going to do next.