WEBVTT 1 00:00.000 --> 00:07.320 So this step may take a little bit of explanation to get your head around why 2 00:07.320 --> 00:09.000 we have to do this. 3 00:09.000 --> 00:15.000 Keep in mind that in SD when the way we configure routers is with templates. 4 00:15.000 --> 00:20.120 The problem is you have to apply a template to a router and we don't have the 5 00:20.120 --> 00:21.000 routers yet. 6 00:21.000 --> 00:25.000 Cloud on ramp is going to be deploying those routers. 7 00:25.000 --> 00:31.910 So what we're actually going to do is we're going to take two UUIDs out of our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:25.000 --> 00:31.910 So what we're actually going to do is we're going to take two UUIDs out of our 8 00:31.910 --> 00:37.390 list of available devices and we're actually going to apply our template with 9 00:37.390 --> 00:41.000 our initial configuration to those UUIDs. 10 00:41.000 --> 00:46.450 This way we can pre configure or pre stage those routers so that when cloud on 11 00:46.450 --> 00:51.000 ramp deploys them, it has its initial configuration. 12 00:51.000 --> 00:54.600 Again, I think this will make a little more sense as we go through and look at 13 00:54.600 --> 00:55.000 it. 14 00:55.000 --> 01:02.000 Let's go ahead and jump in to VManage or SDWAN Manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:55.000 --> 01:02.000 Let's go ahead and jump in to VManage or SDWAN Manager. 15 01:02.000 --> 01:07.000 So for this step, we take a slight step away from cloud on ramp. 16 01:07.000 --> 01:11.770 So for this, when I decided to start just here on the monitor overview page 17 01:11.770 --> 01:16.500 where we're really headed though is of course to our main menu, then we're 18 01:16.500 --> 01:20.000 going to go into configuration and then we're going to go into templates. 19 01:20.000 --> 01:24.000 Under templates, we're going to choose our device templates. 20 01:24.000 --> 01:28.000 Now here I have two device templates already pre configured. 21 01:28.000 --> 01:32.270 The first one is simply the template for on-prem one that has already been WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 21 01:28.000 --> 01:32.270 The first one is simply the template for on-prem one that has already been 22 01:32.270 --> 01:33.000 applied. 23 01:33.000 --> 01:36.000 The other one is this Azure template. 24 01:36.000 --> 01:42.030 And if we click on the settings for this and we go into edit, I just want to 25 01:42.030 --> 01:46.000 show you that there's not really much configured in this template. 26 01:46.000 --> 01:49.830 What we're really just trying to do again is give a place for the initial 27 01:49.830 --> 01:51.000 configuration. 28 01:51.000 --> 01:55.000 If you look over most of these, they are set to defaults. 29 01:55.000 --> 02:00.660 The only sort of exception here is if we take a look here at our VPN zero and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:55.000 --> 02:00.660 The only sort of exception here is if we take a look here at our VPN zero and 30 02:00.660 --> 02:04.000 VPN 512 interfaces. 31 02:04.000 --> 02:07.000 We are still using default templates. 32 02:07.000 --> 02:10.000 So these are things that are still built into SDWAN. 33 02:10.000 --> 02:16.340 You just have to choose to use these default Azure templates for VPN zero 34 02:16.340 --> 02:23.000 interface one and two for VPN zero and for Cisco VPN 512. 35 02:23.000 --> 02:28.000 We simply choose this default template for VPN 512. 36 02:28.000 --> 02:32.830 So there's nothing really fancy in this template, but it is a baseline for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 02:28.000 --> 02:32.830 So there's nothing really fancy in this template, but it is a baseline for 37 02:32.830 --> 02:36.000 rolling out the routers into Azure. 38 02:36.000 --> 02:40.470 The main thing we're here to do, we'll cancel out of this since we didn't 39 02:40.470 --> 02:44.000 change anything is attach devices to this template. 40 02:44.000 --> 02:47.000 So we're going to go over here to our menu again. 41 02:47.000 --> 02:53.600 We're going to choose attach devices and we're simply going to choose two UUIDs 42 02:53.600 --> 02:57.000 off of our list of available devices. 43 02:57.000 --> 03:01.000 Add them to our list and hit attach. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:57.000 --> 03:01.000 Add them to our list and hit attach. 44 03:01.000 --> 03:04.640 Now as we're going to do this, this is the part where we need to put in that 45 03:04.640 --> 03:06.000 initial configuration. 46 03:06.000 --> 03:09.000 So for example, we need to put in the host name. 47 03:09.000 --> 03:11.000 Now there's sort of two ways to do this. 48 03:11.000 --> 03:16.000 We can either click right here on this table, put in the name. 49 03:16.000 --> 03:21.680 We'll just call this like Azure R1, then we can click over here, put in the 50 03:21.680 --> 03:24.000 system IP. 51 03:24.000 --> 03:28.000 And the site ID will set this to 20. 52 03:28.000 --> 03:32.860 The other way to put this information in, we'll do it for the second router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 03:28.000 --> 03:32.860 The other way to put this information in, we'll do it for the second router 53 03:32.860 --> 03:36.230 here is you can click on this little menu over here and hit edit device 54 03:36.230 --> 03:37.000 template. 55 03:37.000 --> 03:42.000 And this simply brings up a dialogue where we can put in that same information. 56 03:42.000 --> 03:45.000 So this one will of course be Azure R2. 57 03:45.000 --> 03:53.000 We'll make this system IP 10.255.20.2 and the site ID is also going to be 20. 58 03:53.000 --> 03:55.000 We hit update. 59 03:55.000 --> 03:59.000 And we just see that that's simply another way to fill in that information. 60 03:59.000 --> 04:01.000 Now let's go ahead and hit next. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 03:59.000 --> 04:01.000 Now let's go ahead and hit next. 61 04:01.000 --> 04:06.160 Now just like we could when we're normally applying a template to a router, we 62 04:06.160 --> 04:09.000 could of course click on the devices over here on the left. 63 04:09.000 --> 04:12.000 Look at their configuration and so on. 64 04:12.000 --> 04:13.000 We've done that previously. 65 04:13.000 --> 04:17.000 And again, there's not really anything fancy being configured here. 66 04:17.000 --> 04:19.000 So let's just say configure devices. 67 04:19.000 --> 04:22.000 We'll confirm and hit OK. 68 04:22.000 --> 04:24.000 So now this is completed. 69 04:24.000 --> 04:28.000 Notice however, where it says done, it says scheduled. 70 04:28.000 --> 04:32.870 And if we expand one of these messages, we can see of course what it's really WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:28.000 --> 04:32.870 And if we expand one of these messages, we can see of course what it's really 71 04:32.870 --> 04:36.870 saying is that this device is offline, which of course it is it has not even 72 04:36.870 --> 04:38.000 been deployed yet. 73 04:38.000 --> 04:43.700 And it tells us on the last line here that the configuration template will be 74 04:43.700 --> 04:47.000 attached when the device comes online. 75 04:47.000 --> 04:51.740 So again, what we've essentially done here is configured the initial 76 04:51.740 --> 04:56.000 configuration for these routers when they do get deployed. 77 04:56.000 --> 05:01.220 So with this step, this wraps up everything we need to do as far as our prep WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 04:56.000 --> 05:01.220 So with this step, this wraps up everything we need to do as far as our prep 78 05:01.220 --> 05:05.000 work for actually deploying the cloud gateway. 79 05:05.000 --> 05:09.400 And that means we are up to that point where we're going to deploy the cloud 80 05:09.400 --> 05:12.000 gateway in the next video.