WEBVTT

1
00:00.000 --> 00:07.280
So now that our tunnel is up, running, and functional, our next step to

2
00:07.280 --> 00:08.000
actually get this

3
00:08.000 --> 00:12.520
fully working is going to be to provide some form of routing so that each

4
00:12.520 --> 00:13.440
router knows

5
00:13.440 --> 00:16.640
which subnet is available through the other routing.

6
00:16.640 --> 00:19.680
So we could use static or dynamic routing here.

7
00:19.680 --> 00:21.160
We're going to use dynamic routing.

8
00:21.160 --> 00:24.440
I'm going to deploy OSPF specifically.

9
00:24.440 --> 00:26.240
It's going to be a very simple configuration.

10
00:26.240 --> 00:29.640
We're just going to put all of the interfaces in area zero.

11
00:29.640 --> 00:32.520
We're going to be doing fancy going on with OSPF.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.640 --> 00:32.520
We're going to be doing fancy going on with OSPF.

12
00:32.520 --> 00:36.430
Also note, if you're following along here, if you want to use a different

13
00:36.430 --> 00:37.260
dynamic routing

14
00:37.260 --> 00:41.470
protocol that you're more familiar with, that's fine as well as long as we get

15
00:41.470 --> 00:42.120
some form of

16
00:42.120 --> 00:43.920
routing up and running.

17
00:43.920 --> 00:45.960
But again, we're going to use OSPF.

18
00:45.960 --> 00:50.640
So let's go ahead and jump in and get that configured.

19
00:50.640 --> 00:54.120
So our first step here will simply be to enable the process.

20
00:54.120 --> 00:57.120
So we'll just do router OSPF process one.

21
00:57.120 --> 00:59.680
We'll also set its router ID.

22
00:59.680 --> 01:03.060
We're going to create a loopback in just a moment and we'll hard code the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.680 --> 01:03.060
We're going to create a loopback in just a moment and we'll hard code the

23
01:03.060 --> 01:03.680
router ID

24
01:03.680 --> 01:05.680
to the loopback address.

25
01:05.680 --> 01:10.940
Technically OSPF would pick the loopback for its router ID anyway, but I always

26
01:10.940 --> 01:11.480
like to

27
01:11.480 --> 01:12.760
hard code it.

28
01:12.760 --> 01:16.400
That way if you do add other loopbacks in the future or something like that, it

29
01:16.400 --> 01:16.840
doesn't

30
01:16.840 --> 01:18.600
affect your router ID.

31
01:18.600 --> 01:20.800
So we'll go ahead and configure that.

32
01:20.800 --> 01:24.880
Then we'll create that loopback zero interface I was just talking about.

33
01:24.880 --> 01:29.840
We'll give it that same IP address and we'll just make that a host address

34
01:29.840 --> 01:30.920
slash 32 and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.840 --> 01:30.920
slash 32 and

35
01:30.920 --> 01:35.760
we'll turn on IP OSPF one in area zero.

36
01:35.760 --> 01:41.250
We also need to enable this for gigabit two, which is our land facing interface

37
01:41.250 --> 01:41.480
and of

38
01:41.480 --> 01:46.850
course for tunnel one, which is well, frankly, sort of the point of this

39
01:46.850 --> 01:47.920
exercise.

40
01:47.920 --> 01:50.480
We want to run OSPF over the tunnel.

41
01:50.480 --> 01:56.000
So let's go ahead and exit our configuration and go over to AWS R one.

42
01:56.000 --> 01:59.520
This is going to be substantially the same configuration.

43
01:59.520 --> 02:02.480
Of course, the router ID will be different.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:59.520 --> 02:02.480
Of course, the router ID will be different.

44
02:02.480 --> 02:05.360
We're going to make this side 200 for the loopbacks.

45
02:05.360 --> 02:07.840
Again, we'll create that loopback interface.

46
02:07.840 --> 02:13.800
The IP address is going to be the 10 dot 200 dot one dot one and again, a slash

47
02:13.800 --> 02:14.160
32.

48
02:14.160 --> 02:20.200
We'll bring this into OSPF same with gigabit two and tunnel one.

49
02:20.200 --> 02:24.880
Exit configuration and let's do some verification.

50
02:24.880 --> 02:28.480
First we can do a show IP OSPF interface brief.

51
02:28.480 --> 02:33.390
We see here that we have in fact enabled OSPF on the appropriate interfaces,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:28.480 --> 02:33.390
We see here that we have in fact enabled OSPF on the appropriate interfaces,

52
02:33.390 --> 02:34.520
loopback zero,

53
02:34.520 --> 02:37.200
tunnel one and gigabit two.

54
02:37.200 --> 02:42.120
We can also see here that tunnel one already has a neighbor ship.

55
02:42.120 --> 02:46.480
Now gigabit two is still in the wait phase because that's a broadcast network.

56
02:46.480 --> 02:51.240
Therefore, it's attempting to elect a DR, although of course, there's no other

57
02:51.240 --> 02:51.520
routers

58
02:51.520 --> 02:53.200
out there to compete with it.

59
02:53.200 --> 02:58.040
But after about 40 seconds, that should go to DR.

60
02:58.040 --> 03:01.720
And we can see here that it did it elected itself as the DR.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:58.040 --> 03:01.720
And we can see here that it did it elected itself as the DR.

61
03:01.720 --> 03:03.480
So this is looking good.

62
03:03.480 --> 03:08.920
If we do a show IP OSPF neighbor, we should be neighbors across tunnel one with

63
03:08.920 --> 03:09.600
on-prem

64
03:09.600 --> 03:12.840
router one and we can see that we are.

65
03:12.840 --> 03:18.870
Let's also do a show IP router OSPF and we see that we're learning the LAN side

66
03:18.870 --> 03:18.960
, which

67
03:18.960 --> 03:22.560
is the 10 dot 10 dot 10 dot zero slash 24.

68
03:22.560 --> 03:26.620
And we're also learning about router ones loopback interface that we configured

69
03:26.620 --> 03:26.640
.

70
03:26.640 --> 03:29.240
So so far, this is looking good.

71
03:29.240 --> 03:33.200
Let's verify this on on-prem router one as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:29.240 --> 03:33.200
Let's verify this on on-prem router one as well.

72
03:33.200 --> 03:36.340
We'll verify the interfaces real quickly, even though of course we've sort of

73
03:36.340 --> 03:36.760
seen the

74
03:36.760 --> 03:39.080
evidence that they're correct.

75
03:39.080 --> 03:40.440
But here they are.

76
03:40.440 --> 03:41.960
We don't have to verify the neighbor ship.

77
03:41.960 --> 03:46.600
We do know that that's up, but let's go ahead and verify the routes.

78
03:46.600 --> 03:50.040
Make sure that we're getting the correct routes from the other side.

79
03:50.040 --> 03:54.370
And we see here that we are in fact getting the 10 dot 20 dot 10 dot zero slash

80
03:54.370 --> 03:55.200
24, which

81
03:55.200 --> 03:59.200
is our subnet 10 over in the AWS cloud.

82
03:59.200 --> 04:05.000
Of course, we're also learning AWS R ones loopback interface as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:59.200 --> 04:05.000
Of course, we're also learning AWS R ones loopback interface as well.

83
04:05.000 --> 04:09.840
One other thing to verify, although we did see it on the show IP OSPF interface

84
04:09.840 --> 04:10.040
brief,

85
04:10.040 --> 04:15.070
but if we were to say show IP OSPF interface tunnel one to get a little more

86
04:15.070 --> 04:16.680
detail, notice

87
04:16.680 --> 04:23.420
that this does in fact default to a point to point network type and it defaults

88
04:23.420 --> 04:23.640
to a

89
04:23.640 --> 04:25.760
cost of a thousand.

90
04:25.760 --> 04:30.040
That's actually relatively high for OSPF.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:25.760 --> 04:30.040
That's actually relatively high for OSPF.

91
04:30.040 --> 04:36.240
This is done because generally tunnels are meant to be backup links.

92
04:36.240 --> 04:40.800
You would prefer another interface to forward the traffic instead.

93
04:40.800 --> 04:45.750
Now in this case, the tunnel is the only path making the cost honestly sort of

94
04:45.750 --> 04:46.760
irrelevant.

95
04:46.760 --> 04:51.160
If this cost doesn't fit into your design, of course, it can be changed.

96
04:51.160 --> 04:53.960
I just wanted to show you some of these defaults.

97
04:53.960 --> 04:59.070
Like any other point to point interface, it also defaults to the hello timer of

98
04:59.070 --> 05:00.320
10 seconds
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:59.070 --> 05:00.320
10 seconds

99
05:00.320 --> 05:04.120
and the dead timer of 40 seconds.

100
05:04.120 --> 05:08.880
So now that we have our dynamic routing up and running, why don't we jump in to

101
05:08.880 --> 05:09.160
SRV

102
05:09.160 --> 05:14.910
one and do some testing both to the internet and through our VPN to make sure

103
05:14.910 --> 05:15.760
all of our

104
05:15.760 --> 05:17.640
traffic is flowing the way we want it to.

105
05:17.640 --> 05:25.400
[BLANK_AUDIO]