WEBVTT

1
00:00.000 --> 00:10.000
Hello and welcome to configure iOS XE VPN redundancy in AWS.

2
00:10.000 --> 00:17.000
Our main goal in this skill is going to be to provide redundancy for the VPN

3
00:17.000 --> 00:19.000
that we created in the previous skill.

4
00:19.000 --> 00:24.920
So this means that we're going to start by deploying a redundant catalyst 8000

5
00:24.920 --> 00:28.000
V into our AWS VPC.

6
00:28.000 --> 00:33.250
We're then going to configure a redundant tunnel between that redundant
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:28.000 --> 00:33.250
We're then going to configure a redundant tunnel between that redundant

7
00:33.250 --> 00:37.000
catalyst and another router at our headquarters.

8
00:37.000 --> 00:40.000
We're going to be configuring router two.

9
00:40.000 --> 00:45.570
Then we're going to configure the IGP or the interior gateway protocol to

10
00:45.570 --> 00:50.660
actually be able to handle those routes on the AWS side to provide redundancy

11
00:50.660 --> 00:52.000
for the tunnel.

12
00:52.000 --> 00:56.000
But at that point, not quite yet for the device.

13
00:56.000 --> 01:02.330
We'll then configure a traditional FHRP or first hop redundancy protocol at our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:56.000 --> 01:02.330
We'll then configure a traditional FHRP or first hop redundancy protocol at our

14
01:02.330 --> 01:04.000
headquarters site.

15
01:04.000 --> 01:07.080
And the main reason we're going to do this is, well, first we need it at

16
01:07.080 --> 01:13.000
headquarters, but also to show how it doesn't work in AWS.

17
01:13.000 --> 01:19.880
Then we'll configure what we do need to configure for AWS, which is catalyst

18
01:19.880 --> 01:27.860
8000 V redundancy, which actually interacts with the AWS APIs to handle first

19
01:27.860 --> 01:34.000
hop redundancy within the VPC, particularly by manipulating the routing tables.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
01:27.860 --> 01:34.000
hop redundancy within the VPC, particularly by manipulating the routing tables.

20
01:34.000 --> 01:44.950
Now, as you can hear, that's a lot of stuff. So it's fun, but we got to jump in

21
01:44.950 --> 01:47.140
and get started. So I'll see you in the next video where we're going to look at

22
01:47.140 --> 01:49.000
our topology and figure out what our game plan is going to be.

23
01:49.000 --> 01:57.240
[BLANK_AUDIO]