WEBVTT

1
00:00.000 --> 00:08.760
So our next step here is going to be to create our SD-WAN template for our AWS

2
00:08.760 --> 00:10.080
routers.

3
00:10.080 --> 00:14.780
Now this is going to be a fairly basic template, however, we do have to make

4
00:14.780 --> 00:15.640
sure we accomplish

5
00:15.640 --> 00:17.120
a few things.

6
00:17.120 --> 00:21.600
The biggest thing is to not cut ourselves off from being able to connect to the

7
00:21.600 --> 00:22.160
router.

8
00:22.160 --> 00:26.000
So we need to make sure we configure our VPN zero interface.

9
00:26.000 --> 00:31.020
We need to make sure its IP address is pulled from DHCP because that's what the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.000 --> 00:31.020
We need to make sure its IP address is pulled from DHCP because that's what the

10
00:31.020 --> 00:32.320
cloud expects.

11
00:32.320 --> 00:37.850
Even if we set the IP address to the same address that AWS is going to give us,

12
00:37.850 --> 00:38.440
connectivity

13
00:38.440 --> 00:44.760
does not seem to work properly unless it actually pulls its address from DHCP.

14
00:44.760 --> 00:49.080
That's why we configured our devices to have the addresses that we want.

15
00:49.080 --> 00:52.840
So we're going to allow it to pull its address from DHCP and then we're going

16
00:52.840 --> 00:53.560
to configure

17
00:53.560 --> 00:59.540
our VPN 10 so that we have reachability from our on-prem network all the way

18
00:59.540 --> 01:00.440
out to our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.540 --> 01:00.440
out to our

19
01:00.440 --> 01:02.160
AWS environment.

20
01:02.160 --> 01:07.480
So let's go ahead and jump in to SD-WAN manager.

21
01:07.480 --> 01:13.600
So we'll start off here on the monitor devices page where we left off in the

22
01:13.600 --> 01:14.740
last video because

23
01:14.740 --> 01:20.680
you can see it's been a few moments here and now the health of AWS R1 gets that

24
01:20.680 --> 01:23.000
green checkbox

25
01:23.000 --> 01:29.260
and we now have CPU load and memory utilization information available from AWS

26
01:29.260 --> 01:30.040
R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:29.260 --> 01:30.040
R1.

27
01:30.040 --> 01:34.120
So that said, let's go ahead and jump in and begin configuring our templates.

28
01:34.120 --> 01:37.280
So for this, we're going to go over here to configuration.

29
01:37.280 --> 01:39.160
We're going to go to templates.

30
01:39.160 --> 01:44.140
The first thing I want to point out here is we have the WAN edge site 100

31
01:44.140 --> 01:45.120
template which

32
01:45.120 --> 01:48.080
is currently applied to two devices.

33
01:48.080 --> 01:53.010
That's the template that is currently managing on-prem router one and on-prem

34
01:53.010 --> 01:53.960
router two.

35
01:53.960 --> 01:59.440
Then we have AWS template, Azure template and GCP template.

36
01:59.440 --> 02:02.720
These are templates that we use for cloud on-ramp.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:59.440 --> 02:02.720
These are templates that we use for cloud on-ramp.

37
02:02.720 --> 02:06.400
I just have them here so that I have them convenient.

38
02:06.400 --> 02:10.800
What we're going to do is make a new template for our manual deployment.

39
02:10.800 --> 02:16.180
Now for this, we're actually going to make a new feature template to handle VPN

40
02:16.180 --> 02:16.520
zero.

41
02:16.520 --> 02:21.060
Now this isn't necessarily strictly required but it gives us more flexibility

42
02:21.060 --> 02:21.800
in the future

43
02:21.800 --> 02:23.960
if we want to change things.

44
02:23.960 --> 02:28.210
So to do this, we want to come over here to feature templates and what we're

45
02:28.210 --> 02:28.440
going to

46
02:28.440 --> 02:33.610
do is we're going to take this VPN zero site 100 template and we're going to go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:28.440 --> 02:33.610
do is we're going to take this VPN zero site 100 template and we're going to go

47
02:33.610 --> 02:34.080
to our

48
02:34.080 --> 02:39.800
action menu over here and we're simply going to say to copy it.

49
02:39.800 --> 02:44.520
What we're going to do is we're going to change this to be for site 20.

50
02:44.520 --> 02:46.160
We'll copy it.

51
02:46.160 --> 02:51.160
We can see down here at the bottom, we now have our VPN zero for site 20.

52
02:51.160 --> 02:55.000
If we click on this and we go to edit, we can see that of course it has the

53
02:55.000 --> 02:55.560
name and

54
02:55.560 --> 02:58.680
description that we just put in when it's being copied.

55
02:58.680 --> 03:01.880
VPN is set to zero as it should be.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:58.680 --> 03:01.880
VPN is set to zero as it should be.

56
03:01.880 --> 03:04.400
There's not really much configured in here.

57
03:04.400 --> 03:09.440
The one thing that is in here is a static default route.

58
03:09.440 --> 03:11.960
So we want to make sure that this is accurate.

59
03:11.960 --> 03:16.300
Since we copied it from the on-prem, this is actually going to default to being

60
03:16.300 --> 03:17.120
incorrect.

61
03:17.120 --> 03:19.040
So we want to hit edit.

62
03:19.040 --> 03:23.750
We want to go to the next top and we can see that this is incorrect for the sub

63
03:23.750 --> 03:24.200
nets we

64
03:24.200 --> 03:26.920
just created in AWS.

65
03:26.920 --> 03:32.240
We would actually want this to be 10 dot 20 dot one dot one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:26.920 --> 03:32.240
We would actually want this to be 10 dot 20 dot one dot one.

66
03:32.240 --> 03:38.830
That's what the AWS Internet Gateway is going to be on the VPN zero or outside

67
03:38.830 --> 03:39.920
interface.

68
03:39.920 --> 03:42.520
So we'll go ahead and hit save changes.

69
03:42.520 --> 03:47.720
We'll save these changes to the route and we'll hit update on our template.

70
03:47.720 --> 03:50.160
That's really all that's in this template.

71
03:50.160 --> 03:54.700
So now we can come back up here to device templates and we'll create our new

72
03:54.700 --> 03:55.480
template.

73
03:55.480 --> 03:58.920
We'll create from a feature template for the device model.

74
03:58.920 --> 04:02.280
This of course is going to be the C8000V.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:58.920 --> 04:02.280
This of course is going to be the C8000V.

75
04:02.280 --> 04:08.080
The device role is going to be SD-WAN edge for the template name.

76
04:08.080 --> 04:12.720
We'll call it AWS edge router for the template.

77
04:12.720 --> 04:17.520
How about template for AWS edge devices?

78
04:17.520 --> 04:20.120
Then we'll scroll down here a little bit.

79
04:20.120 --> 04:23.640
Cisco system and Cisco logging can be left at their default.

80
04:23.640 --> 04:29.060
Now the Cisco AAA, we have to be careful here because by default, this is going

81
04:29.060 --> 04:30.480
to override
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:29.060 --> 04:30.480
to override

82
04:30.480 --> 04:36.020
the authentication that AWS is already putting on the router, allowing us to

83
04:36.020 --> 04:37.200
log in with our

84
04:37.200 --> 04:39.160
SSH key.

85
04:39.160 --> 04:42.400
So we want to make sure we set this to something that we know.

86
04:42.400 --> 04:46.590
I'm going to use this template called local user that I've used in other skills

87
04:46.590 --> 04:47.320
throughout

88
04:47.320 --> 04:48.640
this course.

89
04:48.640 --> 04:52.590
That's just going to have admin with the password we've been using through the

90
04:52.590 --> 04:53.000
whole

91
04:53.000 --> 04:54.000
course.

92
04:54.000 --> 04:58.080
One, two, three, four capital Q capital W E R.

93
04:58.080 --> 05:04.120
So it's simply going to create a local account as admin so we can still log in.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:58.080 --> 05:04.120
So it's simply going to create a local account as admin so we can still log in.

94
05:04.120 --> 05:06.900
Also we want to make sure that our OMP is set right.

95
05:06.900 --> 05:11.680
We can see that this is actually set correctly for the default for AWS.

96
05:11.680 --> 05:13.720
So that's going to be okay.

97
05:13.720 --> 05:17.400
We can scroll down for VPN zero.

98
05:17.400 --> 05:20.800
We want to change this to the one we just created.

99
05:20.800 --> 05:27.830
We want to set this to VPN zero site 20 and this is very important for the VPN

100
05:27.830 --> 05:29.120
interface.

101
05:29.120 --> 05:34.620
We want to change this to be a pre created feature template we have here called
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:29.120 --> 05:34.620
We want to change this to be a pre created feature template we have here called

102
05:34.620 --> 05:35.320
gigabit

103
05:35.320 --> 05:37.680
one DHCP.

104
05:37.680 --> 05:41.360
Now there's really nothing fancy in that feature template.

105
05:41.360 --> 05:45.770
It's simply specifying gigabit ethernet one and the IP address is set to be

106
05:45.770 --> 05:46.520
pulled from

107
05:46.520 --> 05:49.760
DHCP instead of static.

108
05:49.760 --> 05:56.320
Now for VPN 512, you could of course configure VPN 512 if you desire.

109
05:56.320 --> 05:57.320
We're not going to do that.

110
05:57.320 --> 06:02.350
We're not going to set up out of band management inside of AWS because quite
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:57.320 --> 06:02.350
We're not going to set up out of band management inside of AWS because quite

111
06:02.350 --> 06:03.920
frankly, AWS itself

112
06:03.920 --> 06:06.960
sort of gives us out of band management already.

113
06:06.960 --> 06:08.920
So we don't really need to configure that.

114
06:08.920 --> 06:11.680
You could of course, if you wanted to.

115
06:11.680 --> 06:17.000
The next thing we want to do is configure our service VPN VPN 10.

116
06:17.000 --> 06:22.180
So let's go ahead and hit add VPN VPN 10 already exists again because it's

117
06:22.180 --> 06:23.960
already applied

118
06:23.960 --> 06:26.280
to our on-prem routers.

119
06:26.280 --> 06:29.000
So we'll simply choose VPN 10 again.

120
06:29.000 --> 06:31.800
This is a fairly empty configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
06:29.000 --> 06:31.800
This is a fairly empty configuration.

121
06:31.800 --> 06:34.680
It simply specifies a VPN number of 10.

122
06:34.680 --> 06:37.360
We'll go ahead and hit add.

123
06:37.360 --> 06:38.920
We'll hit next.

124
06:38.920 --> 06:43.440
Then here we need to add a Cisco VPN interface ethernet.

125
06:43.440 --> 06:48.000
And here we want to choose the inside interface, which is gigabit two.

126
06:48.000 --> 06:52.750
And again, we have a pre-made template that we created ahead of time, which is

127
06:52.750 --> 06:53.280
simply

128
06:53.280 --> 06:58.560
gigabit ethernet two also pulling its address from DHCP.

129
06:58.560 --> 07:03.520
So this will put the inside interface into VPN 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
06:58.560 --> 07:03.520
So this will put the inside interface into VPN 10.

130
07:03.520 --> 07:05.560
So let's go ahead and hit add.

131
07:05.560 --> 07:07.720
That should be all we need to put in this template.

132
07:07.720 --> 07:09.880
So let's go ahead and hit create.

133
07:09.880 --> 07:13.100
Because of course, other things you could change in the template, but right now

134
07:13.100 --> 07:14.160
our goal is

135
07:14.160 --> 07:18.400
simply to get a VPN set up between the two locations.

136
07:18.400 --> 07:21.000
So now we have this AWS edge router.

137
07:21.000 --> 07:26.120
The next thing we have to do, of course, is apply it to AWS R one.

138
07:26.120 --> 07:29.040
So we'll come over here to attach devices.

139
07:29.040 --> 07:35.040
We'll choose AWS R one, add it to the list, hit attach.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
07:29.040 --> 07:35.040
We'll choose AWS R one, add it to the list, hit attach.

140
07:35.040 --> 07:36.880
And then we have to fill in the information.

141
07:36.880 --> 07:39.920
Now, you can see here, this is a little bit repetitive.

142
07:39.920 --> 07:44.440
If this confuses you a little bit, it's pulled the information off the device

143
07:44.440 --> 07:45.360
that's on there

144
07:45.360 --> 07:48.520
from the base configuration that we put on there.

145
07:48.520 --> 07:52.200
But it's asking what it should do when it applies the template.

146
07:52.200 --> 07:56.510
Now we put the same thing in our initial config that we want when it applies

147
07:56.510 --> 07:57.560
the template.

148
07:57.560 --> 08:00.960
So in this case, it's actually going to be the exact same thing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
07:57.560 --> 08:00.960
So in this case, it's actually going to be the exact same thing.

149
08:00.960 --> 08:04.280
We're going to set the host named AWS R one.

150
08:04.280 --> 08:09.640
We're going to set the system IP to 10.255.20.1.

151
08:09.640 --> 08:13.920
And for the site ID, this is going to be site ID 20.

152
08:13.920 --> 08:18.190
Once we have that in, our status goes to a green check mark, simply indicating

153
08:18.190 --> 08:18.520
that we've

154
08:18.520 --> 08:20.800
supplied all the necessary information.

155
08:20.800 --> 08:22.440
So we hit next.

156
08:22.440 --> 08:24.080
We'll say configure devices.

157
08:24.080 --> 08:26.680
It's going to configure, of course, that one router.

158
08:26.680 --> 08:29.160
We'll give this just a moment to complete.

159
08:29.160 --> 08:34.240
And we see here that the template has been successfully attached.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
08:29.160 --> 08:34.240
And we see here that the template has been successfully attached.

160
08:34.240 --> 08:40.580
So in this video, we created our template and we applied it to AWS R one,

161
08:40.580 --> 08:41.920
including its

162
08:41.920 --> 08:49.160
VPN zero interface, some login information, and of course, configuring VPN 10.

163
08:49.160 --> 08:53.530
The next thing to do, of course, is to jump in and make sure that all of this

164
08:53.530 --> 08:54.280
is actually

165
08:54.280 --> 08:54.760
functional.

166
08:54.760 --> 09:04.760
[BLANK_AUDIO]