WEBVTT

1
00:00.000 --> 00:07.000
Next up, let's go ahead and configure on-prem router 2.

2
00:07.000 --> 00:12.000
Now once again, this is configuration that we have seen numerous times now.

3
00:12.000 --> 00:17.000
So again, we'll just bring the configuration up in notepad++,

4
00:17.000 --> 00:20.000
give it a quick review, paste it onto the router,

5
00:20.000 --> 00:23.000
and then do some baseline verification.

6
00:23.000 --> 00:27.000
So let's go ahead and get started configuring on-prem router 2.

7
00:27.000 --> 00:32.750
So this is the configuration that we're going to be putting on on-prem router 2
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:27.000 --> 00:32.750
So this is the configuration that we're going to be putting on on-prem router 2

8
00:32.750 --> 00:33.000
.

9
00:33.000 --> 00:38.000
As we can see up here at the top, we have all of our iCv2 information,

10
00:38.000 --> 00:43.000
our proposal, our policy, our keyring, and our profile.

11
00:43.000 --> 00:47.400
If we scroll down a little bit, we can see that we're adding our IPsec

12
00:47.400 --> 00:48.000
information,

13
00:48.000 --> 00:51.000
so we have our transform set and our profile.

14
00:51.000 --> 00:56.000
Then we're adding a loopback 0 interface, enabling OSPF on it,

15
00:56.000 --> 01:00.000
router 2 did not previously have a loopback interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
01:00.000 --> 01:03.000
Then we're creating our tunnel 2 interface,

17
01:03.000 --> 01:08.000
going to the elastic IP of AWS router 2,

18
01:08.000 --> 01:12.000
and finally we're just configuring our OSPF router ID.

19
01:12.000 --> 01:14.000
So this is what we're going to paste in.

20
01:14.000 --> 01:19.000
Let's jump over to router 2, put this configuration on the device.

21
01:19.000 --> 01:21.000
So we'll simply copy it.

22
01:21.000 --> 01:24.000
Then on on-prem router 2, we're going to configuration mode,

23
01:24.000 --> 01:29.000
paste in all of that configuration, and that will do some verification.

24
01:29.000 --> 01:32.000
Let's start with the show IP interface brief,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:29.000 --> 01:32.000
Let's start with the show IP interface brief,

25
01:32.000 --> 01:38.000
and the first thing to note is that our tunnel 2 is in fact up up.

26
01:38.000 --> 01:41.000
Well, let's verify that it's actually passing traffic.

27
01:41.000 --> 01:46.000
Let's do a ping of the 169.254.21.1,

28
01:46.000 --> 01:50.000
which is AWS R2's address.

29
01:50.000 --> 01:52.000
So we see this as successful.

30
01:52.000 --> 01:56.000
Let's also do a show IP OSPF neighbors,

31
01:56.000 --> 02:00.000
and we can see that we have a neighborhood with AWS R2
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
02:00.000 --> 02:05.000
across the tunnel 2 interface, and with router 1

33
02:05.000 --> 02:10.000
across the local gigabit 2 interface here at the headquarters.

34
02:10.000 --> 02:13.000
Let's do a show IP route OSPF.

35
02:13.000 --> 02:17.000
And the main thing we're looking for here is not necessarily the specific

36
02:17.000 --> 02:18.000
routes at this point.

37
02:18.000 --> 02:23.000
However, note that some of these routes are going out the tunnel 2 interface,

38
02:23.000 --> 02:26.000
which means they're going to AWS.

39
02:26.000 --> 02:29.000
And some of them are going across gigabit 2,

40
02:29.000 --> 02:34.000
which means they're going locally up to on-prem router 1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
02:29.000 --> 02:34.000
which means they're going locally up to on-prem router 1.

41
02:34.000 --> 02:37.000
So we do have paths going both ways.

42
02:37.000 --> 02:42.000
The main thing I'm trying to point out here is that on-prem router 2

43
02:42.000 --> 02:46.000
could potentially be using on-prem router 1

44
02:46.000 --> 02:50.000
as a backup if its own local tunnel went down.

45
02:50.000 --> 02:54.000
However, if we go over to AWS R2,

46
02:54.000 --> 02:58.000
and here we say show IP OSPF neighbors,

47
02:58.000 --> 03:04.000
notice the only neighbor it has is on-prem router 2 across the tunnel.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:58.000 --> 03:04.000
notice the only neighbor it has is on-prem router 2 across the tunnel.

48
03:04.000 --> 03:09.000
Since that's the only neighbor, if I do a show IP router OSPF,

49
03:09.000 --> 03:14.000
well, the only potential path that AWS R2 has

50
03:14.000 --> 03:18.000
is across the tunnel 2 interface.

51
03:18.000 --> 03:22.000
The reason this is important is it means that AWS R1

52
03:22.000 --> 03:27.000
doesn't know that it can get to headquarters through AWS R2

53
03:27.000 --> 03:33.000
and AWS R2 doesn't know that it can get to headquarters through AWS R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
03:27.000 --> 03:33.000
and AWS R2 doesn't know that it can get to headquarters through AWS R1.

54
03:33.000 --> 03:37.000
So we don't have any redundancy really at this point,

55
03:37.000 --> 03:42.000
not for the tunnels, not for the devices, not for our first hop redundancy.

56
03:42.000 --> 03:47.000
So although we do have a redundant tunnel up between redundant routers,

57
03:47.000 --> 03:50.000
we don't truly have any redundancy going on yet

58
03:50.000 --> 03:54.000
until we get some routing working here on the AWS side.

59
03:54.000 --> 03:57.000
That's exactly what we're going to be doing next.

60
03:57.000 --> 04:14.420
[ Silence ]