WEBVTT

1
00:00.000 --> 00:11.320
Let's begin by deploying that redundant catalyst 8000V into our VPC on AWS.

2
00:11.320 --> 00:15.640
We're going to be deploying this in much the same way we did the first one.

3
00:15.640 --> 00:20.880
We'll create our interfaces, we'll deploy the AMI, map these things together,

4
00:20.880 --> 00:21.000
give it

5
00:21.000 --> 00:24.880
an outside address and then configure the router itself.

6
00:24.880 --> 00:30.560
Now one thing we are going to do here which isn't probably strictly necessary
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:24.880 --> 00:30.560
Now one thing we are going to do here which isn't probably strictly necessary

7
00:30.560 --> 00:31.160
but I like

8
00:31.160 --> 00:33.720
to do it for consistency.

9
00:33.720 --> 00:40.730
From time to time vendors such as Cisco will update the AMIs that Amazon is

10
00:40.730 --> 00:41.840
offering to

11
00:41.840 --> 00:43.520
their customers.

12
00:43.520 --> 00:48.770
So sometimes when you go to deploy the 8000V even though you search for it

13
00:48.770 --> 00:49.560
exactly the

14
00:49.560 --> 00:54.680
same way you did the first time you might get a different version of code.

15
00:54.680 --> 00:57.990
So what we're going to do in this case is rather than just doing it right

16
00:57.990 --> 00:58.600
through the

17
00:58.600 --> 01:04.960
catalog we're going to search for the actual AMI image of our first router.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:58.600 --> 01:04.960
catalog we're going to search for the actual AMI image of our first router.

18
01:04.960 --> 01:09.490
Now as I said this probably isn't strictly necessary but I do like to use

19
01:09.490 --> 01:10.320
consistent

20
01:10.320 --> 01:13.680
versions of code just for consistency.

21
01:13.680 --> 01:17.980
We don't need one router acting slightly different than the other or anything

22
01:17.980 --> 01:19.440
along those lines.

23
01:19.440 --> 01:21.000
So that's what we're going to do.

24
01:21.000 --> 01:27.800
Let's go ahead and jump in and get started we'll start on AWS.

25
01:27.800 --> 01:32.150
So starting off here on the EC2 dashboard the first thing we're going to do is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:27.800 --> 01:32.150
So starting off here on the EC2 dashboard the first thing we're going to do is

26
01:32.150 --> 01:32.640
create

27
01:32.640 --> 01:34.680
our network interfaces.

28
01:34.680 --> 01:38.200
So we'll scroll down here to network and security.

29
01:38.200 --> 01:41.000
We'll come down here to network interfaces.

30
01:41.000 --> 01:43.880
We'll come up here to create network interface.

31
01:43.880 --> 01:46.680
We'll create the outside interface first.

32
01:46.680 --> 01:49.920
So for the subnet that would be subnet one.

33
01:49.920 --> 01:52.400
We need to make sure we give it the appropriate IP address.

34
01:52.400 --> 01:55.520
So this is going to be 10.20.1.

35
01:55.520 --> 01:58.240
And this is going to be 253.

36
01:58.240 --> 02:02.480
And for the security groups this is outside so internet traffic.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:58.240 --> 02:02.480
And for the security groups this is outside so internet traffic.

37
02:02.480 --> 02:04.960
This is going to be SG1.

38
02:04.960 --> 02:07.360
We'll hit create network interface.

39
02:07.360 --> 02:08.360
We'll rename it.

40
02:08.360 --> 02:12.120
This is going to be R2 underscore gigabit one.

41
02:12.120 --> 02:14.960
And we want to click on action.

42
02:14.960 --> 02:17.520
We want to change the source destination check.

43
02:17.520 --> 02:19.720
We need to turn this off.

44
02:19.720 --> 02:24.720
We'll hit save and then we'll create our second network interface.

45
02:24.720 --> 02:29.040
This one will be in subnet 10.

46
02:29.040 --> 02:33.480
Its address is going to be 10.20.10.253.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:29.040 --> 02:33.480
Its address is going to be 10.20.10.253.

47
02:33.480 --> 02:35.240
This is for inside land traffic.

48
02:35.240 --> 02:37.680
So it will be an SG land.

49
02:37.680 --> 02:39.320
We'll hit create.

50
02:39.320 --> 02:43.240
We'll rename it R2 underscore gigabit two.

51
02:43.240 --> 02:48.540
And again under actions we will choose the source destination check and turn

52
02:48.540 --> 02:49.680
that off.

53
02:49.680 --> 02:52.840
Now we'll navigate to instances.

54
02:52.840 --> 02:58.180
And if you don't already have this information, if we select router one down at

55
02:58.180 --> 02:58.640
the bottom

56
02:58.640 --> 03:04.790
here under details, if we scroll down a bit, we can actually see the AMI name
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:58.640 --> 03:04.790
here under details, if we scroll down a bit, we can actually see the AMI name

57
03:04.790 --> 03:05.840
of this image

58
03:05.840 --> 03:07.600
that we want to deploy.

59
03:07.600 --> 03:10.400
So that's the image that we're going to be using.

60
03:10.400 --> 03:13.520
So let's go ahead and deploy that AMI.

61
03:13.520 --> 03:15.880
So we'll say launch instances.

62
03:15.880 --> 03:19.400
We'll call this AWS R2.

63
03:19.400 --> 03:22.900
Then in the search window, we'll simply put in the name of the AMI that we want

64
03:22.900 --> 03:23.160
to search

65
03:23.160 --> 03:25.800
for hit enter.

66
03:25.800 --> 03:28.480
We have one hit under the community AMIs.

67
03:28.480 --> 03:30.280
We'll click on that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:28.480 --> 03:30.280
We'll click on that.

68
03:30.280 --> 03:32.760
And this is the image we want to use right here.

69
03:32.760 --> 03:35.080
So we'll go ahead and hit select.

70
03:35.080 --> 03:40.040
Notice it's actually telling us that this image has a newer version available.

71
03:40.040 --> 03:42.920
It's asking if I want to view the newest version.

72
03:42.920 --> 03:46.760
Like I mentioned, I would prefer to keep the code consistent.

73
03:46.760 --> 03:51.120
So that's actually up to you and your policies, of course, but we're going to

74
03:51.120 --> 03:52.100
stick with this

75
03:52.100 --> 03:53.100
image.

76
03:53.100 --> 03:55.880
So it's the same as the one that we already have running.

77
03:55.880 --> 03:58.640
So that said, let's move on.

78
03:58.640 --> 04:03.280
For the instance type, you can use the one that you want for our environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:58.640 --> 04:03.280
For the instance type, you can use the one that you want for our environment.

79
04:03.280 --> 04:06.920
A T3 medium will be fine.

80
04:06.920 --> 04:07.920
Choose your key pair.

81
04:07.920 --> 04:11.200
Of course, if you don't have one, you'll need to create one.

82
04:11.200 --> 04:14.320
Then for the network settings, we're going to say edit.

83
04:14.320 --> 04:16.520
It's going to go into our only VPC.

84
04:16.520 --> 04:21.520
So VPC one, the subnet here is just for the first interface.

85
04:21.520 --> 04:23.160
We'll leave it at subnet one.

86
04:23.160 --> 04:24.160
That's fine.

87
04:24.160 --> 04:28.000
We'll leave the auto assign public disabled.

88
04:28.000 --> 04:29.600
We'll be assigning that ourselves.

89
04:29.600 --> 04:33.270
A little bit interesting thing we have to do here is we have to select existing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:29.600 --> 04:33.270
A little bit interesting thing we have to do here is we have to select existing

90
04:33.270 --> 04:33.840
security

91
04:33.840 --> 04:39.520
group, but then not actually select one on the drop down.

92
04:39.520 --> 04:43.280
That's because we're going to go into advanced network configuration.

93
04:43.280 --> 04:47.190
And for network interface one, we're going to select the interface that we

94
04:47.190 --> 04:48.840
already created.

95
04:48.840 --> 04:54.780
Now notice, since we had selected subnet one up above, it's only showing us

96
04:54.780 --> 04:55.840
interfaces

97
04:55.840 --> 04:58.480
that belong to subnet one.

98
04:58.480 --> 04:59.480
And that's fine.

99
04:59.480 --> 05:02.680
In this case, we want router two, gigabit one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
04:59.480 --> 05:02.680
In this case, we want router two, gigabit one.

100
05:02.680 --> 05:05.960
We'll leave the rest of this blank because it's already configured on the

101
05:05.960 --> 05:07.920
interface itself.

102
05:07.920 --> 05:09.720
But we do want to add a network interface.

103
05:09.720 --> 05:12.680
We want two interfaces on this router.

104
05:12.680 --> 05:14.840
So let's scroll down some more.

105
05:14.840 --> 05:18.010
For interface two, notice it's showing us all of the interfaces because it

106
05:18.010 --> 05:18.560
doesn't know

107
05:18.560 --> 05:20.080
what subnet.

108
05:20.080 --> 05:24.790
So for this one, we want router two, gigabit two, which is the bottom one

109
05:24.790 --> 05:25.840
listed here.

110
05:25.840 --> 05:29.890
Now an interesting thing here, notice that it tried to fill in the subnet, but

111
05:29.890 --> 05:30.560
it's red
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:29.890 --> 05:30.560
it's red

112
05:30.560 --> 05:34.840
because it's telling us you can't do that for an existing interface.

113
05:34.840 --> 05:37.520
And to that, we say, okay, but I didn't do it.

114
05:37.520 --> 05:42.200
So all we have to do is click on this and just change it back to select.

115
05:42.200 --> 05:44.080
And it'll be fine.

116
05:44.080 --> 05:47.120
For some reason, the GUI here tries to fill that in.

117
05:47.120 --> 05:50.000
And well, as you can see, it just shouldn't be.

118
05:50.000 --> 05:52.280
So all of the rest of this looks fine.

119
05:52.280 --> 05:55.080
Let's go ahead and say launch instance.

120
05:55.080 --> 05:57.320
So this says successful.

121
05:57.320 --> 05:59.560
Let's go back to instances.

122
05:59.560 --> 06:03.840
We'll refresh this since our AWS router two is not listed.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
05:59.560 --> 06:03.840
We'll refresh this since our AWS router two is not listed.

123
06:03.840 --> 06:06.920
So now it's here, but it's still initializing.

124
06:06.920 --> 06:11.620
Let's give this just a moment to fully boot up past its status checks and then

125
06:11.620 --> 06:12.240
we'll move

126
06:12.240 --> 06:13.240
on.

127
06:13.240 --> 06:14.240
Okay.

128
06:14.240 --> 06:15.480
So it's been a few moments.

129
06:15.480 --> 06:19.520
We see that AWS R2 is now up and running.

130
06:19.520 --> 06:21.760
Both status checks are passed.

131
06:21.760 --> 06:27.120
So the next thing we need to do is map one of our elastic IPs to the outside

132
06:27.120 --> 06:28.080
interface

133
06:28.080 --> 06:29.800
on router two.

134
06:29.800 --> 06:35.200
So over under network and security, we'll choose elastic IPs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
06:29.800 --> 06:35.200
So over under network and security, we'll choose elastic IPs.

135
06:35.200 --> 06:40.040
I already have one created for this just for the sake of consistency.

136
06:40.040 --> 06:44.980
However, if you don't have one, go ahead and allocate an elastic IP address at

137
06:44.980 --> 06:45.360
this

138
06:45.360 --> 06:46.520
point.

139
06:46.520 --> 06:51.800
I'm going to use this one I already have pre-configured R2 gigabit one.

140
06:51.800 --> 06:56.480
So we'll go ahead and select that address under actions.

141
06:56.480 --> 06:58.680
We'll say to associate it.

142
06:58.680 --> 07:02.320
We'll associate to a specific network interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
06:58.680 --> 07:02.320
We'll associate to a specific network interface.

143
07:02.320 --> 07:07.750
That network interface will be router two gigabit one for the private IP

144
07:07.750 --> 07:08.640
address.

145
07:08.640 --> 07:10.960
It'll be the address we gave it.

146
07:10.960 --> 07:15.880
And just in case it's already been associated in the past, we'll click on allow

147
07:15.880 --> 07:16.400
it to be

148
07:16.400 --> 07:19.480
re-associated with all of that configured.

149
07:19.480 --> 07:24.650
We'll simply say associate and it's been allocated successfully with all of

150
07:24.650 --> 07:26.040
this configured.

151
07:26.040 --> 07:32.650
We should be able to go over an SSH into this device now using this elastic IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
07:26.040 --> 07:32.650
We should be able to go over an SSH into this device now using this elastic IP

152
07:32.650 --> 07:33.800
address.

153
07:33.800 --> 07:39.440
So as you can see, we've now successfully SSH into router two.

154
07:39.440 --> 07:44.840
And what we're going to do now is we want to put our baseline configuration on

155
07:44.840 --> 07:44.920
this that

156
07:44.920 --> 07:49.800
includes a lot of things, including our net and our IP set.

157
07:49.800 --> 07:55.160
So let's bring up notepad++, give a quick look at the configuration.

158
07:55.160 --> 07:58.800
This is all things that we have done in previous skills.

159
07:58.800 --> 08:03.160
So if you're not familiar with any of these pieces, I would suggest going back
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
07:58.800 --> 08:03.160
So if you're not familiar with any of these pieces, I would suggest going back

160
08:03.160 --> 08:03.840
and reviewing

161
08:03.840 --> 08:07.640
those skills to know what these different pieces are.

162
08:07.640 --> 08:12.280
So again, let's take a quick look at notepad++ and the configuration we're

163
08:12.280 --> 08:13.120
going to put

164
08:13.120 --> 08:15.640
here on router two.

165
08:15.640 --> 08:19.960
So a lot of these settings at the top are just standard configuration.

166
08:19.960 --> 08:24.050
If we scroll down a little bit, we can see all of our Ike version two

167
08:24.050 --> 08:25.280
configuration with

168
08:25.280 --> 08:30.080
our proposal, our policy, our keyring and our profile.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
08:25.280 --> 08:30.080
our proposal, our policy, our keyring and our profile.

169
08:30.080 --> 08:32.000
We scroll down a little bit more.

170
08:32.000 --> 08:38.930
We can see the IPsec configuration with our transform set and our IPsec profile

171
08:38.930 --> 08:38.960
.

172
08:38.960 --> 08:41.920
We also see where we're configuring tunnel two.

173
08:41.920 --> 08:46.440
Now truth be told, there's only one tunnel here on router two.

174
08:46.440 --> 08:50.240
However, we called it tunnel two just because we have a different router with a

175
08:50.240 --> 08:51.000
tunnel one

176
08:51.000 --> 08:52.000
on it.

177
08:52.000 --> 08:55.360
This, of course, could have also just been tunnel one.

178
08:55.360 --> 08:59.000
I did it to hopefully bring in some clarity.

179
08:59.000 --> 09:03.600
If we look at our interfaces here, we see that they're being configured for NAT
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

179
08:59.000 --> 09:03.600
If we look at our interfaces here, we see that they're being configured for NAT

180
09:03.600 --> 09:03.840
.

181
09:03.840 --> 09:07.840
So we have our IP NAT inside our IP NAT outside.

182
09:07.840 --> 09:10.880
Both interfaces are getting their address from DHCP.

183
09:10.880 --> 09:15.920
We're bringing up gigabit two and we're enabling OSPF on it.

184
09:15.920 --> 09:19.760
OSPF itself is a fairly simple configuration.

185
09:19.760 --> 09:24.760
As is the NAT, it's just overloading everything on the outside interface.

186
09:24.760 --> 09:28.670
And then of course, we just have some basic configuration under our VTY lines

187
09:28.670 --> 09:29.200
and we're

188
09:29.200 --> 09:31.640
configuring an NTP server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
09:29.200 --> 09:31.640
configuring an NTP server.

189
09:31.640 --> 09:37.640
So all of this said, let's just paste this whole configuration into router two.

190
09:37.640 --> 09:41.600
So highlight all of it, copy it and go to router two.

191
09:41.600 --> 09:45.940
So now that we've pasted in the configuration, let's go ahead and do some

192
09:45.940 --> 09:47.120
verification.

193
09:47.120 --> 09:49.800
Let's do a show IP interface brief.

194
09:49.800 --> 09:53.520
We see that everything looks good here, except of course, tunnel two, because

195
09:53.520 --> 09:54.080
we haven't

196
09:54.080 --> 09:57.320
configured our onsite router to yet.

197
09:57.320 --> 10:00.040
But these interfaces generally look okay.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

197
09:57.320 --> 10:00.040
But these interfaces generally look okay.

198
10:00.040 --> 10:03.760
If we ping a dot eight dot eight dot eight, we see this router can successfully

199
10:03.760 --> 10:04.200
get out

200
10:04.200 --> 10:06.000
to the internet.

201
10:06.000 --> 10:11.360
And if we ping Cisco.com, we see that we have DNS name resolution.

202
10:11.360 --> 10:16.280
So as we can see, everything's looking good here on AWS router two.

203
10:16.280 --> 10:20.540
The next thing we're going to have to do is configure the on-prem router to,

204
10:20.540 --> 10:20.760
which is

205
10:20.760 --> 10:23.280
of course the other side of this tunnel.

206
10:23.280 --> 10:25.520
So that's exactly what we're going to do next.