WEBVTT

1
00:00.000 --> 00:08.450
So our next step is going to be to prepare our AWS environment to receive the

2
00:08.450 --> 00:08.880
catalyst

3
00:08.880 --> 00:10.560
8000V.

4
00:10.560 --> 00:15.090
And what that really entails is we're going to need a VPC in order to put the

5
00:15.090 --> 00:16.440
router in.

6
00:16.440 --> 00:20.270
We're going to need at least two subnets, one for the inside, one for the

7
00:20.270 --> 00:22.080
outside interface.

8
00:22.080 --> 00:26.000
Of course, if you were going to create more interfaces, you could of course use

9
00:26.000 --> 00:26.960
more subnets.

10
00:26.960 --> 00:29.440
Two was going to be enough for us.

11
00:29.440 --> 00:35.210
And then we're also going to deploy a workstation into AWS that's going to act
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.440 --> 00:35.210
And then we're also going to deploy a workstation into AWS that's going to act

12
00:35.210 --> 00:35.920
as that jump

13
00:35.920 --> 00:38.320
box that we had on our diagram.

14
00:38.320 --> 00:42.580
So in other words, a target that we have so we can test our reachability once

15
00:42.580 --> 00:43.040
we get

16
00:43.040 --> 00:44.480
this all up and running.

17
00:44.480 --> 00:49.840
So all of that said, let's jump in to AWS.

18
00:49.840 --> 00:54.760
So the first thing we want to do here in the AWS console is let's go ahead and

19
00:54.760 --> 00:56.600
go to VPCs.

20
00:56.600 --> 01:03.160
We can actually see here under VPCs that at the moment we have zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:56.600 --> 01:03.160
We can actually see here under VPCs that at the moment we have zero.

21
01:03.160 --> 01:06.600
So let's go ahead and create a VPC.

22
01:06.600 --> 01:09.400
We'll just simply click on the button right up here.

23
01:09.400 --> 01:13.720
For now, we'll make the VPC only will make each component separately.

24
01:13.720 --> 01:20.800
And then for the name, let's just call this SD win for the CIDR block.

25
01:20.800 --> 01:25.920
This is going to be 10 about 20.0.0/16.

26
01:25.920 --> 01:30.360
Because again, we're going to be using this as site 20 in our environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:25.920 --> 01:30.360
Because again, we're going to be using this as site 20 in our environment.

27
01:30.360 --> 01:34.200
So we'll make our IP addressing match accordingly.

28
01:34.200 --> 01:37.720
And then the rest of these settings, we can leave it there default.

29
01:37.720 --> 01:41.040
We'll simply now hit create VPC.

30
01:41.040 --> 01:42.120
This will take just a moment.

31
01:42.120 --> 01:45.880
We can see up here at the top that it has been successful.

32
01:45.880 --> 01:49.940
So the next thing we're going to want to do, let's go over here to the left and

33
01:49.940 --> 01:50.360
go to

34
01:50.360 --> 01:51.920
subnets.

35
01:51.920 --> 01:55.680
We're going to want one subnet for the outside interface that's going to be

36
01:55.680 --> 01:56.600
effectively connecting

37
01:56.600 --> 01:58.200
to the internet.

38
01:58.200 --> 02:02.610
And then we're going to want another subnet for the inside where our jump box
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:58.200 --> 02:02.610
And then we're going to want another subnet for the inside where our jump box

39
02:02.610 --> 02:03.240
or our work

40
02:03.240 --> 02:05.200
station is going to live.

41
02:05.200 --> 02:09.720
So first thing we want to do, we'll hit create subnet.

42
02:09.720 --> 02:15.200
We'll choose to put this in the VPC we just created for the subnet settings.

43
02:15.200 --> 02:18.320
We'll make the outside subnet first.

44
02:18.320 --> 02:20.760
We'll just make that subnet one.

45
02:20.760 --> 02:25.520
For the availability zone, you'll want to choose something close to you.

46
02:25.520 --> 02:31.320
For me, the best choice is us East one a so that's what I'm going to choose for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:25.520 --> 02:31.320
For me, the best choice is us East one a so that's what I'm going to choose for

47
02:31.320 --> 02:31.480
the

48
02:31.480 --> 02:32.640
cider block.

49
02:32.640 --> 02:36.640
It's of course going to be the 10 dot 20 dot zero dot zero slash 16.

50
02:36.640 --> 02:39.240
But then we have to make the subnet block.

51
02:39.240 --> 02:44.880
This one will make 10 dot 20 dot one dot zero slash 24.

52
02:44.880 --> 02:47.920
Once again, the rest of this should be okay at the defaults.

53
02:47.920 --> 02:52.320
So we'll just go to the very bottom here and create subnet.

54
02:52.320 --> 02:54.920
Once again, we see at the top that was successful.

55
02:54.920 --> 02:57.880
So let's go ahead and make our second one.

56
02:57.880 --> 03:00.640
Once again, we choose our VPC.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:57.880 --> 03:00.640
Once again, we choose our VPC.

57
03:00.640 --> 03:09.100
This one will make subnet 10 same availability zone and for the subnet block 10

58
03:09.100 --> 03:09.920
dot 20 dot

59
03:09.920 --> 03:13.560
10 dot zero slash 24.

60
03:13.560 --> 03:15.840
We'll go ahead and create the subnet.

61
03:15.840 --> 03:19.480
Now here it's only showing us the subnet 10 because of the filter.

62
03:19.480 --> 03:23.290
But if we clear the filter here, we can actually see all of our subnets and we

63
03:23.290 --> 03:23.800
see that we

64
03:23.800 --> 03:30.320
now have our two subnets created with the appropriate IPV for cider ranges.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:23.800 --> 03:30.320
now have our two subnets created with the appropriate IPV for cider ranges.

65
03:30.320 --> 03:33.640
Now the next thing we have to do for these VPCs because we do want them to be

66
03:33.640 --> 03:34.080
able to

67
03:34.080 --> 03:38.560
reach the internet is we're going to have to add an internet gateway.

68
03:38.560 --> 03:42.760
So let's go over here to internet gateways.

69
03:42.760 --> 03:46.480
Up here at the right, we'll hit create internet gateway.

70
03:46.480 --> 03:49.040
And the name here isn't really all that important.

71
03:49.040 --> 03:55.320
We'll just call this like internet gateway one, create the internet gateway.

72
03:55.320 --> 03:59.020
Now notice here on the success line where it says that we've successfully

73
03:59.020 --> 03:59.720
created the

74
03:59.720 --> 04:06.170
internet gateway, it also conveniently gives us this button here to attach it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:59.720 --> 04:06.170
internet gateway, it also conveniently gives us this button here to attach it

75
04:06.170 --> 04:06.840
to a VPC

76
04:06.840 --> 04:09.480
because that's one of the steps we have to do.

77
04:09.480 --> 04:13.560
Our internet gateway has to be attached to a VPC.

78
04:13.560 --> 04:15.560
So let's go ahead and do that.

79
04:15.560 --> 04:20.200
And again, all we have to do is select the VPC that we created.

80
04:20.200 --> 04:22.760
We'll attach the internet gateway.

81
04:22.760 --> 04:25.320
And that's now been successful as well.

82
04:25.320 --> 04:29.400
Now one final thing we're going to have to do here for routing to get this all

83
04:29.400 --> 04:29.800
up and

84
04:29.800 --> 04:34.640
running initially is we're now going to have to go to route tables.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:29.800 --> 04:34.640
running initially is we're now going to have to go to route tables.

85
04:34.640 --> 04:39.270
And notice that right now we have one route table, we could probably get away

86
04:39.270 --> 04:39.880
with one

87
04:39.880 --> 04:42.560
route table the way we're going to be building this.

88
04:42.560 --> 04:46.500
However, generally speaking, you're probably going to want a separate route

89
04:46.500 --> 04:48.120
table per subnet.

90
04:48.120 --> 04:50.680
So I'm just going to go ahead and build it that way.

91
04:50.680 --> 04:53.360
We'll use this route table that's already here.

92
04:53.360 --> 04:55.800
And we'll simply rename this.

93
04:55.800 --> 04:58.920
We'll make this the route table for subnet one.

94
04:58.920 --> 05:03.440
And there's a couple of things we have to do to make this for subnet one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:58.920 --> 05:03.440
And there's a couple of things we have to do to make this for subnet one.

95
05:03.440 --> 05:07.360
First, come down here to subnet associations.

96
05:07.360 --> 05:12.800
And then under the explicit subnet association, we hit edit over here to edit

97
05:12.800 --> 05:14.640
the subnet association.

98
05:14.640 --> 05:18.280
And we're going to associate it with subnet one.

99
05:18.280 --> 05:20.760
Well, let's say with associations.

100
05:20.760 --> 05:24.960
So now that route table is associated with subnet one.

101
05:24.960 --> 05:30.160
And the main reason we needed this is if we look at the routes, there's only
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:24.960 --> 05:30.160
And the main reason we needed this is if we look at the routes, there's only

102
05:30.160 --> 05:32.040
one route by default.

103
05:32.040 --> 05:38.140
And that's for our local address base, the 10 dot 20 dot zero, zero slash 16 to

104
05:38.140 --> 05:40.320
be locally reachable.

105
05:40.320 --> 05:43.760
Well, we need to teach this how to get to the internet.

106
05:43.760 --> 05:45.760
So we need a default route.

107
05:45.760 --> 05:48.360
So let's go ahead and hit edit routes.

108
05:48.360 --> 05:50.120
We'll add a route.

109
05:50.120 --> 05:52.720
We will, in fact, add the default.

110
05:52.720 --> 05:57.520
The target is going to be the internet gateway we just created.

111
05:57.520 --> 06:01.940
And on the dropdown here, we simply choose the internet gateway, internet
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:57.520 --> 06:01.940
And on the dropdown here, we simply choose the internet gateway, internet

112
06:01.940 --> 06:05.080
gateway one that we created earlier.

113
06:05.080 --> 06:08.600
Once that's done, we hit save changes.

114
06:08.600 --> 06:11.040
Then we'll go back to route tables.

115
06:11.040 --> 06:13.520
We're going to create a new route table.

116
06:13.520 --> 06:17.320
This one will be subnet 10.

117
06:17.320 --> 06:20.960
It's, of course, going to be in our SD WAN VPC.

118
06:20.960 --> 06:23.200
We'll hit create route table.

119
06:23.200 --> 06:26.200
And essentially, we have to take the same basic steps.

120
06:26.200 --> 06:33.570
So under the routes here, we can edit the routes, add a route, add the default
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

120
06:26.200 --> 06:33.570
So under the routes here, we can edit the routes, add a route, add the default

121
06:33.570 --> 06:36.280
and point it to our internet gateway.

122
06:36.280 --> 06:39.720
This way, both subnets can get out to the internet later.

123
06:39.720 --> 06:44.280
We'll be modifying this routing, but this is what we're going to be doing for

124
06:44.280 --> 06:44.280
now.

125
06:44.280 --> 06:49.030
Under subnet associations, this one, we're going to edit the association and it

126
06:49.030 --> 06:51.960
's going to be associated with subnet 10.

127
06:51.960 --> 06:56.540
So if we go back to route tables, we now see that we have both of our route

128
06:56.540 --> 07:00.800
tables associated with the appropriate subnets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:56.540 --> 07:00.800
tables associated with the appropriate subnets.

129
07:00.800 --> 07:05.840
Now, one other thing we'll need as we move forward is a security group.

130
07:05.840 --> 07:10.070
So if we come over here to security and we go to security groups, we could, of

131
07:10.070 --> 07:12.520
course, use this one that's here by default,

132
07:12.520 --> 07:15.280
or we can say to create a security group.

133
07:15.280 --> 07:18.000
Let's just call it SG one.

134
07:18.000 --> 07:21.680
We're, of course, going to just assign our VPC.

135
07:21.680 --> 07:26.520
If we scroll down, we see the default is to not have any inbound rules.

136
07:26.520 --> 07:31.120
And for the outbound rules, it's going to allow all traffic.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
07:26.520 --> 07:31.120
And for the outbound rules, it's going to allow all traffic.

137
07:31.120 --> 07:34.800
So that should be OK for the outbound for the inbound.

138
07:34.800 --> 07:37.000
Let's go ahead and add a rule.

139
07:37.000 --> 07:43.280
Let's start with allowing SSH and we'll allow that from anywhere.

140
07:43.280 --> 07:45.680
And then we'll add another rule.

141
07:45.680 --> 07:49.080
And this is just so we can do some ping verification.

142
07:49.080 --> 07:55.040
Let's do all ICMP version four and again from everywhere.

143
07:55.040 --> 07:58.750
You, of course, could be more specific with this if you want, but this will be

144
07:58.750 --> 08:00.280
enough to get us started.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
07:58.750 --> 08:00.280
enough to get us started.

145
08:00.280 --> 08:04.440
So let's scroll down and create the security group.

146
08:04.440 --> 08:08.350
As you can see here, it doesn't like the fact that I did not give it a

147
08:08.350 --> 08:09.240
description.

148
08:09.240 --> 08:12.320
As you can see, this is not an optional field.

149
08:12.320 --> 08:17.920
So we'll simply call this SD when security group.

150
08:17.920 --> 08:20.160
Once again, let's create it.

151
08:20.160 --> 08:24.600
Now that we have our description in there, we can create the security group.

152
08:24.600 --> 08:28.370
So now that the networking is set up, the next thing we want to do is deploy a

153
08:28.370 --> 08:29.440
workstation.

154
08:29.440 --> 08:31.400
This will only take a second.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
08:29.440 --> 08:31.400
This will only take a second.

155
08:31.400 --> 08:33.840
Let's go over here to EC2.

156
08:33.840 --> 08:36.000
I have a quick bar for it.

157
08:36.000 --> 08:38.480
We'll simply say launch instance.

158
08:38.480 --> 08:43.200
We'll call this AWS workstation one.

159
08:43.200 --> 08:46.120
Now you could just use Amazon Linux if you want.

160
08:46.120 --> 08:48.160
I personally prefer Ubuntu.

161
08:48.160 --> 08:53.880
So I'm going to choose Ubuntu 20.04 long term support is fine.

162
08:53.880 --> 08:55.960
The architecture is fine.

163
08:55.960 --> 08:59.160
The instance type of a T2 micro was going to be perfectly fine.

164
08:59.160 --> 09:03.200
Again, this is just for a test set for the key name.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
08:59.160 --> 09:03.200
Again, this is just for a test set for the key name.

165
09:03.200 --> 09:08.080
I'm going to choose a key that I already have created so I can log into this

166
09:08.080 --> 09:08.320
easily.

167
09:08.320 --> 09:12.400
Under network settings, what we have to be careful of here is in our case,

168
09:12.400 --> 09:13.120
notice it's

169
09:13.120 --> 09:15.960
trying to put it on subnet one.

170
09:15.960 --> 09:17.840
It's actually not what we want.

171
09:17.840 --> 09:20.000
So we're going to want to edit this.

172
09:20.000 --> 09:22.640
There's a couple of things here we're going to want to change.

173
09:22.640 --> 09:24.280
First of course is the subnet.

174
09:24.280 --> 09:28.480
We want this on subnet 10, which is the client network.

175
09:28.480 --> 09:33.890
The auto assign public IP, you could do this if you want, but I actually have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
09:28.480 --> 09:33.890
The auto assign public IP, you could do this if you want, but I actually have

176
09:33.890 --> 09:34.920
some elastic

177
09:34.920 --> 09:38.520
IPs that I already have saved for this.

178
09:38.520 --> 09:42.530
If you don't have any elastic IPs, you could assign one here under the auto

179
09:42.530 --> 09:43.440
assign public

180
09:43.440 --> 09:46.680
IP, but I'm going to leave that disabled.

181
09:46.680 --> 09:51.120
I'm also going to tell it to use an existing security group and choose the one

182
09:51.120 --> 09:51.560
that I

183
09:51.560 --> 09:52.600
just created.

184
09:52.600 --> 09:56.240
So we'll just say security group one.

185
09:56.240 --> 10:01.830
The other thing you can do is under advanced configuration, we can specify the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
09:56.240 --> 10:01.830
The other thing you can do is under advanced configuration, we can specify the

186
10:01.830 --> 10:02.720
primary IP

187
10:02.720 --> 10:08.030
address here so that it gets the same address all the time and it's an address

188
10:08.030 --> 10:08.840
that we want

189
10:08.840 --> 10:10.040
it to be.

190
10:10.040 --> 10:14.440
So we want this to be 10.20.10.100.

191
10:14.440 --> 10:17.410
Now of course, we don't have to put a subnet mask here or anything because it's

192
10:17.410 --> 10:17.800
going to

193
10:17.800 --> 10:21.680
pull that from the subnet that we're putting it in.

194
10:21.680 --> 10:24.680
So overall, everything here looks correct.

195
10:24.680 --> 10:25.920
We scroll down.

196
10:25.920 --> 10:30.470
The storage is going to be okay and we don't need to change any of the advanced
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
10:25.920 --> 10:30.470
The storage is going to be okay and we don't need to change any of the advanced

197
10:30.470 --> 10:31.320
details.

198
10:31.320 --> 10:33.960
We can just say launch instance.

199
10:33.960 --> 10:38.810
We see here it's successfully launched so we can go back to instances and we'll

200
10:38.810 --> 10:39.160
give

201
10:39.160 --> 10:42.360
this just a second to fully boot.

202
10:42.360 --> 10:46.400
So after just a few seconds, we see that our instant state is now running and

203
10:46.400 --> 10:47.080
the status

204
10:47.080 --> 10:49.000
check has been passed.

205
10:49.000 --> 10:52.140
Now the next things I'm going to do are sort of optional, but I find them a

206
10:52.140 --> 10:53.020
little bit easier

207
10:53.020 --> 10:55.840
to work with AWS if you do these things.

208
10:55.840 --> 11:00.040
So the first thing I'm going to do is I'm going to come down here to network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

208
10:55.840 --> 11:00.040
So the first thing I'm going to do is I'm going to come down here to network

209
11:00.040 --> 11:00.200
interfaces.

210
11:00.200 --> 11:03.940
And this network interface that was just created for our workstation, I'm going

211
11:03.940 --> 11:05.080
to rename it

212
11:05.080 --> 11:08.120
so it's easier to identify later.

213
11:08.120 --> 11:13.880
So we'll just call it something like AWS workstation one ethernet zero.

214
11:13.880 --> 11:18.110
The other thing we're going to do is as I mentioned, I have some elastic IPs

215
11:18.110 --> 11:18.680
saved that

216
11:18.680 --> 11:21.040
I use for connecting to these.

217
11:21.040 --> 11:25.310
So what I'm going to do is come down here to elastic IPs and we see I have one

218
11:25.310 --> 11:25.760
saved

219
11:25.760 --> 11:27.760
here for my jump box.

220
11:27.760 --> 11:31.640
So I'm just going to click on this, come up to actions.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

220
11:27.760 --> 11:31.640
So I'm just going to click on this, come up to actions.

221
11:31.640 --> 11:37.200
I'm going to associate the elastic IP address, two way network interface.

222
11:37.200 --> 11:41.880
I'm going to choose the network interface that we just created with our work

223
11:41.880 --> 11:42.040
station.

224
11:42.040 --> 11:45.160
And then it's going to show us that private address.

225
11:45.160 --> 11:49.320
And I'm going to say that this can be reassociated just because it's been used

226
11:49.320 --> 11:50.000
before.

227
11:50.000 --> 11:52.080
So I'm going to say associate.

228
11:52.080 --> 11:53.920
We see that was successful.

229
11:53.920 --> 11:59.090
So if everything is working as it's supposed to, I should now be able to SSH

230
11:59.090 --> 11:59.720
into that

231
11:59.720 --> 12:01.240
jump box.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
11:59.720 --> 12:01.240
jump box.

232
12:01.240 --> 12:05.160
So as we can see here, I was able to successfully connect.

233
12:05.160 --> 12:11.140
We also see that it does have its proper IP address, the 10 dot 20 dot 10 dot

234
12:11.140 --> 12:11.480
100.

235
12:11.480 --> 12:17.320
We could do something like set the host name to AWS workstation one.

236
12:17.320 --> 12:22.680
If we exit, log back in, we can now see it takes the host name.

237
12:22.680 --> 12:27.020
And if we want to be a test outbound internet connectivity by saying to ping

238
12:27.020 --> 12:27.760
eight dot eight

239
12:27.760 --> 12:29.520
dot eight dot eight.

240
12:29.520 --> 12:34.440
We see that successful and we can also verify its routing table.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

240
12:29.520 --> 12:34.440
We see that successful and we can also verify its routing table.

241
12:34.440 --> 12:36.200
We do a route minus N.

242
12:36.200 --> 12:40.600
It tells us that it doesn't actually have that command, but that we can install

243
12:40.600 --> 12:41.000
it.

244
12:41.000 --> 12:43.640
So we'll go ahead and install that command.

245
12:43.640 --> 12:45.560
We'll do a route minus N.

246
12:45.560 --> 12:50.190
And we can see here that currently the default gateway is set to 10 dot 20 dot

247
12:50.190 --> 12:51.800
10 dot one,

248
12:51.800 --> 12:55.520
which is that internet gateway that we created.

249
12:55.520 --> 13:02.840
So now our AWS environment is ready for the Cisco catalyst 8000 V. And that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

249
12:55.520 --> 13:02.840
So now our AWS environment is ready for the Cisco catalyst 8000 V. And that's

250
13:02.840 --> 13:03.080
of course

251
13:03.080 --> 13:05.960
exactly what we're going to deploy in the next video.