WEBVTT

1
00:00.000 --> 00:06.960
So this step may take a little bit of explanation here for you to get your head

2
00:06.960 --> 00:07.520
around what

3
00:07.520 --> 00:09.680
we're trying to accomplish.

4
00:09.680 --> 00:16.440
In order to configure devices in Cisco SD-WAN, we apply templates to them.

5
00:16.440 --> 00:21.200
The problem of course is we can't apply a template to a router until that

6
00:21.200 --> 00:23.120
router exists.

7
00:23.120 --> 00:26.080
So what we're going to use here is a shadow router.

8
00:26.080 --> 00:30.760
And just so we're clear, that is 100% my term for it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:26.080 --> 00:30.760
And just so we're clear, that is 100% my term for it.

9
00:30.760 --> 00:33.420
That is not any sort of official name for this.

10
00:33.420 --> 00:38.050
But essentially what we're going to do is we're going to apply a template just

11
00:38.050 --> 00:38.320
to a

12
00:38.320 --> 00:42.280
UUID off of our list of available devices.

13
00:42.280 --> 00:46.650
Specifically we're going to do it to two routers because that's what we need to

14
00:46.650 --> 00:47.040
deploy.

15
00:47.040 --> 00:51.540
We're going to use that as a placeholder so we can put the initial

16
00:51.540 --> 00:53.280
configuration on those

17
00:53.280 --> 00:54.880
devices.

18
00:54.880 --> 00:59.290
That way when Cloud Gateway rolls those routers out, they already have their

19
00:59.290 --> 01:00.920
initial configuration
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.290 --> 01:00.920
initial configuration

20
01:00.920 --> 01:06.800
with things like their host name, their system IP, their site ID and so on.

21
01:06.800 --> 01:09.400
So that's what we need to do in this step.

22
01:09.400 --> 01:11.840
So let's go ahead and jump in and take a look at it.

23
01:11.840 --> 01:17.490
I think it'll become very clear what we're doing as we go through the

24
01:17.490 --> 01:19.200
configuration.

25
01:19.200 --> 01:24.040
So for this configuration, we're not going to be going through Cloud on RAM.

26
01:24.040 --> 01:27.240
What we're going to be doing is going to configuration.

27
01:27.240 --> 01:29.080
So we'll go to our main menu here.

28
01:29.080 --> 01:31.440
We'll go to configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.080 --> 01:31.440
We'll go to configuration.

29
01:31.440 --> 01:33.440
We'll go to templates.

30
01:33.440 --> 01:37.040
Then under templates, we'll go to device templates.

31
01:37.040 --> 01:42.040
Now as you can see, we currently have two device templates here.

32
01:42.040 --> 01:46.170
One is for the on-prem router one that's already been deployed and is

33
01:46.170 --> 01:47.720
synchronized with that

34
01:47.720 --> 01:48.720
router.

35
01:48.720 --> 01:53.840
The other one here is a template for Google Cloud Platform.

36
01:53.840 --> 01:57.400
Now there's nothing particularly special about this template.

37
01:57.400 --> 02:02.680
Again, we just need to apply it to devices as a placeholder for configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:57.400 --> 02:02.680
Again, we just need to apply it to devices as a placeholder for configuration.

38
02:02.680 --> 02:08.250
However, if we do come down here and we edit the settings for this, we can see

39
02:08.250 --> 02:09.080
that most

40
02:09.080 --> 02:14.920
of the settings in here are in fact defaults with sort of one exception.

41
02:14.920 --> 02:22.130
If we come down here to our VPN configuration, we'll see that for VPN zero and

42
02:22.130 --> 02:23.840
VPN 512,

43
02:23.840 --> 02:29.640
we have default GCP templates assigned to them.

44
02:29.640 --> 02:33.330
Their default, so they are still included with SD-WAN, but they are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:29.640 --> 02:33.330
Their default, so they are still included with SD-WAN, but they are

45
02:33.330 --> 02:34.280
specifically for

46
02:34.280 --> 02:36.200
GCP.

47
02:36.200 --> 02:41.840
Also on our VPN zero for the underlay, we're configuring an ethernet interface,

48
02:41.840 --> 02:42.560
also using

49
02:42.560 --> 02:47.040
that default GCP ethernet interface template.

50
02:47.040 --> 02:51.120
So other than that, this is just a very generic template.

51
02:51.120 --> 02:54.920
We'll go ahead and hit cancel here since we didn't change anything.

52
02:54.920 --> 02:59.750
What we're really here for of course is to attach this to the two routers that

53
02:59.750 --> 03:00.360
are going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:59.750 --> 03:00.360
are going

54
03:00.360 --> 03:04.600
to be deployed as part of the Cloud Gateway.

55
03:04.600 --> 03:07.340
So we want to come back over here to our menu.

56
03:07.340 --> 03:10.840
This time we're going to say attach devices.

57
03:10.840 --> 03:16.280
We're simply going to choose two devices off our list of available devices.

58
03:16.280 --> 03:18.440
So we'll choose these two UUIDs.

59
03:18.440 --> 03:21.200
We'll add them to our list.

60
03:21.200 --> 03:22.960
We'll say attach.

61
03:22.960 --> 03:26.200
And this page represents what we're really here for.

62
03:26.200 --> 03:30.160
We need to do some initial configuration for these devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
03:26.200 --> 03:30.160
We need to do some initial configuration for these devices.

63
03:30.160 --> 03:33.800
So the first thing we want to do here is specify the color.

64
03:33.800 --> 03:38.640
So we can do it here in this table by clicking on the drop down, scrolling down

65
03:38.640 --> 03:39.560
and choosing

66
03:39.560 --> 03:41.360
public internet.

67
03:41.360 --> 03:45.120
And then for things like the host name, we can simply click over here.

68
03:45.120 --> 03:50.600
We'll say this is GCP R1 for the system IP.

69
03:50.600 --> 03:58.250
We'll say that this is 10.255.20.1 and for the site ID, we'll make this site 20

70
03:58.250 --> 03:58.440
.

71
03:58.440 --> 04:01.360
That's one way we can put the information in.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:58.440 --> 04:01.360
That's one way we can put the information in.

72
04:01.360 --> 04:05.690
Another way you can do it is actually clicking on the menu over here and

73
04:05.690 --> 04:07.120
choosing edit device

74
04:07.120 --> 04:08.560
template.

75
04:08.560 --> 04:12.190
If we do it this way, we're still putting in the same information, but we can

76
04:12.190 --> 04:12.800
sort of do

77
04:12.800 --> 04:15.560
it in this one field.

78
04:15.560 --> 04:17.960
So we can again click on the drop down.

79
04:17.960 --> 04:22.840
We can choose our public internet for the host name.

80
04:22.840 --> 04:33.280
This would be GCP R2 for the system IP 10.255.20.2 and it's still site ID 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:22.840 --> 04:33.280
This would be GCP R2 for the system IP 10.255.20.2 and it's still site ID 20.

81
04:33.280 --> 04:38.500
We hit update and now our status is green on both of these because they're

82
04:38.500 --> 04:39.280
ready to be

83
04:39.280 --> 04:40.480
applied.

84
04:40.480 --> 04:43.240
All the necessary information has been provided.

85
04:43.240 --> 04:45.320
So let's go ahead and hit next.

86
04:45.320 --> 04:49.600
Now at this point, we could of course click on the devices over here on the

87
04:49.600 --> 04:50.400
left, look

88
04:50.400 --> 04:54.160
at the configuration that's going to be applied to them and so on.

89
04:54.160 --> 04:58.710
We've been through this many times before in this course and we already sort of

90
04:58.710 --> 04:59.200
saw that

91
04:59.200 --> 05:01.560
the templates aren't really anything special.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:59.200 --> 05:01.560
the templates aren't really anything special.

92
05:01.560 --> 05:04.280
So these aren't going to be complicated configurations.

93
05:04.280 --> 05:06.120
We don't really need to look at them.

94
05:06.120 --> 05:11.960
Let's just hit configure devices, confirm it, hit okay.

95
05:11.960 --> 05:16.760
And after a few minutes, it'll come back here and say that it's done.

96
05:16.760 --> 05:21.960
But notice under the status where it says done, it also says scheduled.

97
05:21.960 --> 05:25.860
If we were to click on one of these to open up the detailed information, what

98
05:25.860 --> 05:26.440
we actually

99
05:26.440 --> 05:31.690
find out in the output here is that the device is offline, which of course it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
05:26.440 --> 05:31.690
find out in the output here is that the device is offline, which of course it

100
05:31.690 --> 05:32.480
is, it hasn't

101
05:32.480 --> 05:34.520
even been deployed yet.

102
05:34.520 --> 05:40.300
But the important thing is that this template, GCP template is scheduled to be

103
05:40.300 --> 05:41.480
attached when

104
05:41.480 --> 05:43.400
the device comes online.

105
05:43.400 --> 05:46.040
In other words, when it's deployed.

106
05:46.040 --> 05:51.810
So this is exactly what we needed to do attaching this configuration to these

107
05:51.810 --> 05:52.720
shadow routers

108
05:52.720 --> 05:57.040
that don't actually exist yet, but the configuration will be applied when they

109
05:57.040 --> 05:59.320
come online.

110
05:59.320 --> 06:04.320
So now that we have this configuration done, we have our templates applied to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:59.320 --> 06:04.320
So now that we have this configuration done, we have our templates applied to

111
06:04.320 --> 06:05.240
these UUIDs

112
06:05.240 --> 06:09.040
acting as I like to call them shadow routers.

113
06:09.040 --> 06:13.160
We're now ready to actually deploy the cloud gateway.

114
06:13.160 --> 06:15.760
And that's exactly what we're going to do in the next video.

115
06:15.760 --> 06:23.760
[BLANK_AUDIO]