WEBVTT

1
00:00.000 --> 00:06.800
So let's take just a moment to look at the templates that we're going to be

2
00:06.800 --> 00:07.880
using when

3
00:07.880 --> 00:14.120
we deploy our routers into AWS, Azure, and Google Cloud.

4
00:14.120 --> 00:17.640
Now there's nothing really spectacular in these templates.

5
00:17.640 --> 00:20.200
However, they are not created by default.

6
00:20.200 --> 00:26.400
So we do need to create them, but we will be using built in feature templates

7
00:26.400 --> 00:26.840
as we can

8
00:26.840 --> 00:29.800
figure the various interfaces and protocols.

9
00:29.800 --> 00:32.200
So let's just take a quick look at these templates.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.800 --> 00:32.200
So let's just take a quick look at these templates.

10
00:32.200 --> 00:36.310
Again, they're not overly complicated, but we do have to create them and we

11
00:36.310 --> 00:36.840
need to be

12
00:36.840 --> 00:38.640
aware of what's in them.

13
00:38.640 --> 00:42.680
So let's jump in and take a look.

14
00:42.680 --> 00:48.260
So we'll start off here in SD-WAN manager under configuration and under device

15
00:48.260 --> 00:49.360
templates.

16
00:49.360 --> 00:54.400
Now as you can see, I actually have four device templates created here.

17
00:54.400 --> 00:59.440
One of them, the WAN edge site 100 is for the on-prem routers.

18
00:59.440 --> 01:02.460
So we're not going to be looking at that one specifically right now, but then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.440 --> 01:02.460
So we're not going to be looking at that one specifically right now, but then

19
01:02.460 --> 01:03.000
you can see

20
01:03.000 --> 01:08.680
we have the other three for AWS, Azure, and Google Cloud.

21
01:08.680 --> 01:12.780
Now we can also see that each of these have two devices attached because this

22
01:12.780 --> 01:13.600
environment

23
01:13.600 --> 01:15.440
is already deployed.

24
01:15.440 --> 01:19.220
We're going to be looking at it in more detail in the next video, but I wanted

25
01:19.220 --> 01:19.800
to start with

26
01:19.800 --> 01:23.480
this foundational step of seeing what's in the template.

27
01:23.480 --> 01:26.600
So let's just start with AWS.

28
01:26.600 --> 01:31.250
We'll simply come over here, click on the context menu and we'll just go into
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:26.600 --> 01:31.250
We'll simply come over here, click on the context menu and we'll just go into

29
01:31.250 --> 01:31.880
edit.

30
01:31.880 --> 01:35.810
So of course, the device model, the device role, the template name, the

31
01:35.810 --> 01:36.740
description, these

32
01:36.740 --> 01:40.760
have already been filled in under the basic information.

33
01:40.760 --> 01:45.220
Everything is just the defaults that you get when you create a new template.

34
01:45.220 --> 01:52.320
As we scroll down though, the first thing we want to see is under Cisco OMP.

35
01:52.320 --> 01:58.560
Notice that it is a default template, but specifically it's the default AWS

36
01:58.560 --> 01:59.760
template.

37
01:59.760 --> 02:02.400
So that's one thing that needs to be changed.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:59.760 --> 02:02.400
So that's one thing that needs to be changed.

38
02:02.400 --> 02:05.640
And then we have the management interfaces.

39
02:05.640 --> 02:10.810
So if we scroll down a little more here, first looking at the Cisco VPN zero

40
02:10.810 --> 02:11.880
interface, we

41
02:11.880 --> 02:14.760
see that again, this is a default template.

42
02:14.760 --> 02:18.040
However, if we click on the drop down here and look at the name in a little

43
02:18.040 --> 02:18.680
more detail

44
02:18.680 --> 02:23.790
that we're currently using, we can see that this is the default AWS template

45
02:23.790 --> 02:24.840
specifically

46
02:24.840 --> 02:27.320
for VPN zero.

47
02:27.320 --> 02:31.470
We'll see the same thing if we look at the interface itself, that this is the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:27.320 --> 02:31.470
We'll see the same thing if we look at the interface itself, that this is the

48
02:31.470 --> 02:32.080
template

49
02:32.080 --> 02:37.020
designed specifically for VPN zero and it's going to be referencing interface

50
02:37.020 --> 02:37.600
gigabit

51
02:37.600 --> 02:43.280
ethernet to that's how it's going to be showing up in AWS.

52
02:43.280 --> 02:49.490
For VPN 512, it's very similar if we click on this drop down and look at it, we

53
02:49.490 --> 02:49.960
see that

54
02:49.960 --> 02:53.840
this name is specifically for VPN 512.

55
02:53.840 --> 02:57.480
And of course, we have the same thing with the interface.

56
02:57.480 --> 03:02.280
If we look at the detail template here, this is the default AWS template
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:57.480 --> 03:02.280
If we look at the detail template here, this is the default AWS template

57
03:02.280 --> 03:03.520
specifically for

58
03:03.520 --> 03:05.280
VPN 512.

59
03:05.280 --> 03:09.680
We can see that this one is going to be using gigabit ethernet one.

60
03:09.680 --> 03:13.040
So that's all that's really set in this template.

61
03:13.040 --> 03:18.710
So you need to set the OMP template and then the templates for your VPN zero

62
03:18.710 --> 03:20.080
and your VPN

63
03:20.080 --> 03:21.880
512 interfaces.

64
03:21.880 --> 03:25.760
Again, these device templates aren't made by default.

65
03:25.760 --> 03:30.480
However, these feature templates that we're using are part of the default
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:25.760 --> 03:30.480
However, these feature templates that we're using are part of the default

66
03:30.480 --> 03:31.680
installation.

67
03:31.680 --> 03:33.040
So let's go back.

68
03:33.040 --> 03:35.360
We'll simply hit cancel here.

69
03:35.360 --> 03:38.440
We'll look at the same thing for Azure.

70
03:38.440 --> 03:43.280
Once again, this is almost identical, we named it in a similar fashion.

71
03:43.280 --> 03:49.120
But once again, notice that the Cisco OMP has been set specifically for the

72
03:49.120 --> 03:50.240
default Azure

73
03:50.240 --> 03:51.920
profile.

74
03:51.920 --> 03:56.450
And if we scroll down to our interfaces, you might notice a slight difference

75
03:56.450 --> 03:57.040
here that

76
03:57.040 --> 03:59.560
we still have our VPN zero.

77
03:59.560 --> 04:05.040
This template name, if we look at it in more detail is going to be the default
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:59.560 --> 04:05.040
This template name, if we look at it in more detail is going to be the default

78
04:05.040 --> 04:06.120
Azure template

79
04:06.120 --> 04:08.840
specifically for VPN zero.

80
04:08.840 --> 04:13.430
And then if we look at the interfaces, we see that this one is for gigabit

81
04:13.430 --> 04:15.700
ethernet one.

82
04:15.700 --> 04:21.240
And if we look at this one, we see that this is for gigabit ethernet two.

83
04:21.240 --> 04:26.400
This is just how we configure it for cloud on ramp for Microsoft Azure.

84
04:26.400 --> 04:30.940
Now if we look down here at the bottom under our 512, this one is simply config
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:26.400 --> 04:30.940
Now if we look down here at the bottom under our 512, this one is simply config

85
04:30.940 --> 04:31.560
uring the

86
04:31.560 --> 04:38.080
VPN 512 interface, but there are no actual interfaces associated with this

87
04:38.080 --> 04:38.640
since this

88
04:38.640 --> 04:44.560
gets deployed into Azure as a virtual appliance.

89
04:44.560 --> 04:51.790
So cloud on ramp is deployed into Azure a little bit differently than it is to

90
04:51.790 --> 04:52.360
AWS and

91
04:52.360 --> 04:54.240
Google Cloud.

92
04:54.240 --> 04:56.760
Let's go ahead and hit cancel again.

93
04:56.760 --> 04:59.520
Next we'll take a look at the Google Cloud template.

94
04:59.520 --> 05:02.440
Once again, it's going to be almost the same.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:59.520 --> 05:02.440
Once again, it's going to be almost the same.

95
05:02.440 --> 05:09.310
If we scroll down for OMP, we have a default GCP template and down for

96
05:09.310 --> 05:11.000
interfaces.

97
05:11.000 --> 05:15.800
We simply have a VPN zero and a VPN 512.

98
05:15.800 --> 05:20.880
And the only one we really have an interface under is the VPN zero.

99
05:20.880 --> 05:24.800
Once again, we'll look at these default template names just for reference.

100
05:24.800 --> 05:29.440
So this one is the default GCP for VPN zero.

101
05:29.440 --> 05:34.670
If we look at the interface, this one is using the default GCP for VPN zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:29.440 --> 05:34.670
If we look at the interface, this one is using the default GCP for VPN zero

102
05:34.670 --> 05:35.800
specifically

103
05:35.800 --> 05:39.520
for interface, gigabit ethernet one.

104
05:39.520 --> 05:45.610
And last but not least for VPN 512, we see that again, this is just a default G

105
05:45.610 --> 05:46.800
CP template,

106
05:46.800 --> 05:49.920
but specifically for VPN 512.

107
05:49.920 --> 05:52.720
So that's all we need as far as templates.

108
05:52.720 --> 05:56.860
Of course, if you want to, you can always come over to feature templates and we

109
05:56.860 --> 05:57.480
can actually

110
05:57.480 --> 06:02.500
just click here on the default templates to filter this and all of those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:57.480 --> 06:02.500
just click here on the default templates to filter this and all of those

111
06:02.500 --> 06:03.520
templates we

112
06:03.520 --> 06:07.080
just looked at are listed right here.

113
06:07.080 --> 06:12.140
So if you want more detail on the actual feature templates, we can look into

114
06:12.140 --> 06:13.120
them here.

115
06:13.120 --> 06:17.680
So just for an example, we can come right over here on this one for Azure.

116
06:17.680 --> 06:22.890
We can view this and we can see what's configured for this particular feature

117
06:22.890 --> 06:23.880
template.

118
06:23.880 --> 06:28.650
Things like it's for gigabit ethernet to if we scroll down, we see that the

119
06:28.650 --> 06:29.360
address

120
06:29.360 --> 06:33.160
is set to be learned dynamically and so on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
06:29.360 --> 06:33.160
is set to be learned dynamically and so on.

121
06:33.160 --> 06:37.240
So again, you can get more detail on these feature templates as well.

122
06:37.240 --> 06:39.800
However, they are built appropriately by default.

123
06:39.800 --> 06:43.280
So there's no real reason to change these.

124
06:43.280 --> 06:47.890
So in this video, we just jumped in and took a quick look at the templates that

125
06:47.890 --> 06:48.400
you need

126
06:48.400 --> 06:55.120
to make for cloud on ramp for AWS, Azure and Google Cloud.

127
06:55.120 --> 06:59.200
Again, these device templates do not exist by default.

128
06:59.200 --> 07:02.320
I created them when we built this environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:59.200 --> 07:02.320
I created them when we built this environment.

129
07:02.320 --> 07:07.330
However, the feature templates do exist and we can simply use the default

130
07:07.330 --> 07:08.840
feature templates

131
07:08.840 --> 07:12.800
that are provided with SD WAN manager.

132
07:12.800 --> 07:17.470
Now that we have our templates set up, let's jump in in the next video and take

133
07:17.470 --> 07:17.800
a more

134
07:17.800 --> 07:22.850
detailed look at how to verify an environment that's already up and running

135
07:22.850 --> 07:23.880
with all three

136
07:23.880 --> 07:25.160
cloud providers.