WEBVTT

1
00:00.000 --> 00:07.910
So having our tunnel up, running, and functional doesn't do us a whole lot of

2
00:07.910 --> 00:08.760
good in and

3
00:08.760 --> 00:10.000
of itself.

4
00:10.000 --> 00:14.180
If the routers don't know what networks are available on the other side of that

5
00:14.180 --> 00:14.800
tunnel.

6
00:14.800 --> 00:17.240
So for that, we need some form of routing.

7
00:17.240 --> 00:19.960
Now of course, there's a lot of different choices here.

8
00:19.960 --> 00:21.600
We could do static routing.

9
00:21.600 --> 00:24.320
We can use a dynamic routing protocol.

10
00:24.320 --> 00:27.600
Technically you could use something like policy-based routing.

11
00:27.600 --> 00:31.250
So we have a lot of choices, but what we're going to take a look at is just
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.600 --> 00:31.250
So we have a lot of choices, but what we're going to take a look at is just

12
00:31.250 --> 00:32.080
using dynamic

13
00:32.080 --> 00:36.040
routing and specifically we're going to use OSPF.

14
00:36.040 --> 00:38.950
And again, of course, in the dynamic routing family, there's a lot of choices

15
00:38.950 --> 00:39.400
there as

16
00:39.400 --> 00:40.400
well.

17
00:40.400 --> 00:42.400
But again, we're just going to use OSPF.

18
00:42.400 --> 00:47.310
In fact, we're going to use single area OSPF just using Area 0 because after

19
00:47.310 --> 00:47.800
all, our

20
00:47.800 --> 00:50.400
environment is really not very big here.

21
00:50.400 --> 00:55.460
So let's go ahead and jump in and configure just basic OSPF between our two

22
00:55.460 --> 00:56.720
routers, including

23
00:56.720 --> 01:03.530
bringing in the land segments on each side that we wish to advertise across the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:56.720 --> 01:03.530
bringing in the land segments on each side that we wish to advertise across the

24
01:03.530 --> 01:04.520
tunnel.

25
01:04.520 --> 01:09.080
So our first step here is to create a router OSPF process.

26
01:09.080 --> 01:12.400
So we'll just use router OSPF1.

27
01:12.400 --> 01:18.000
Also since it is considered best practice, we'll go ahead and set the OSPF

28
01:18.000 --> 01:18.840
router ID.

29
01:18.840 --> 01:22.400
And we're going to be creating a loopback interface in just a second.

30
01:22.400 --> 01:25.240
We're going to use the same address for both of these.

31
01:25.240 --> 01:28.920
And again, you can use whatever your addressing convention is.

32
01:28.920 --> 01:33.480
I'm going to make this 10.100.1.1 in my environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.920 --> 01:33.480
I'm going to make this 10.100.1.1 in my environment.

33
01:33.480 --> 01:35.880
Then we're going to create that interface loopback zero.

34
01:35.880 --> 01:39.630
I was just talking about these are always good to have for things like

35
01:39.630 --> 01:40.720
management and other

36
01:40.720 --> 01:42.280
purposes.

37
01:42.280 --> 01:47.880
And it's usually a good idea to make your OSPF router ID match one of your loop

38
01:47.880 --> 01:48.800
backs.

39
01:48.800 --> 01:51.160
We'll make this a slash 32.

40
01:51.160 --> 01:54.560
And then we'll also bring this into OSPF.

41
01:54.560 --> 01:58.240
It will simply say I POSPF1 area zero.

42
01:58.240 --> 02:02.130
Then of course, we need to bring in our gigabit two interface because this is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:58.240 --> 02:02.130
Then of course, we need to bring in our gigabit two interface because this is

43
02:02.130 --> 02:03.200
the client facing

44
02:03.200 --> 02:05.560
interface that has the network segment.

45
02:05.560 --> 02:08.320
We're trying to advertise to the other side.

46
02:08.320 --> 02:13.290
So once again, we bring it into area zero and just another quick note here at

47
02:13.290 --> 02:14.120
the moment.

48
02:14.120 --> 02:17.600
And this will change when we bring in redundancy and the challenge.

49
02:17.600 --> 02:21.890
But at least right now, there are no OSPF neighbors out the gigabit two

50
02:21.890 --> 02:22.880
interface.

51
02:22.880 --> 02:26.920
And of course, there never would be out the loopback interface.

52
02:26.920 --> 02:30.780
So if we really wanted to, we could do some optimization like making these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:26.920 --> 02:30.780
So if we really wanted to, we could do some optimization like making these

53
02:30.780 --> 02:31.960
passive interfaces

54
02:31.960 --> 02:33.520
in OSPF.

55
02:33.520 --> 02:37.680
This just being a lab and I was trying to just do a simple deployment of OSPF.

56
02:37.680 --> 02:40.120
I'm not going to worry about that right now.

57
02:40.120 --> 02:44.680
But we also need to enable this on the tunnel interface as well.

58
02:44.680 --> 02:46.560
That should be all we need to configure.

59
02:46.560 --> 02:52.610
So let's go do the exact same configuration on GCP R1 except of course for the

60
02:52.610 --> 02:53.440
router ID

61
02:53.440 --> 02:56.640
and the address of the loopback interface.

62
02:56.640 --> 03:00.060
So of course, like I said, the router ID and the address on the loopback
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:56.640 --> 03:00.060
So of course, like I said, the router ID and the address on the loopback

63
03:00.060 --> 03:01.640
interface are different.

64
03:01.640 --> 03:06.240
But other than that, this should take care of the OSPF configuration.

65
03:06.240 --> 03:11.040
So let's jump back over to on-prem R1 and do some verification.

66
03:11.040 --> 03:15.000
So let's start with the show IPOSPF interface brief.

67
03:15.000 --> 03:20.240
All we see here is that we do in fact have OSPF enabled on our loopback tunnel

68
03:20.240 --> 03:20.760
one and

69
03:20.760 --> 03:22.800
gigabit two interface.

70
03:22.800 --> 03:27.480
We see that over the tunnel one interface, we do in fact have a neighbor.

71
03:27.480 --> 03:32.480
If we want more information on that neighbor, we can say show IPOSPF neighbor.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:27.480 --> 03:32.480
If we want more information on that neighbor, we can say show IPOSPF neighbor.

72
03:32.480 --> 03:35.320
We see here that we do in fact have a neighbor ship.

73
03:35.320 --> 03:37.160
The state is full.

74
03:37.160 --> 03:41.320
Two GCP R1 across our tunnel one interface.

75
03:41.320 --> 03:46.320
If we want more information on that interface, we can say show IPOSPF interface

76
03:46.320 --> 03:48.040
tunnel one.

77
03:48.040 --> 03:49.440
Some things we see here.

78
03:49.440 --> 03:53.000
Of course, we still see that the tunnel is up up.

79
03:53.000 --> 03:57.350
But some of the important factors, we see that the default network type here is

80
03:57.350 --> 03:57.520
point

81
03:57.520 --> 03:58.520
to point.

82
03:58.520 --> 04:02.000
The default cost is set to a thousand.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:58.520 --> 04:02.000
The default cost is set to a thousand.

83
04:02.000 --> 04:07.720
And we see that our default hello timer is 10 and our dead interval is 40.

84
04:07.720 --> 04:13.400
So again, this is just more information about that interface that's running OSP

85
04:13.400 --> 04:13.760
F.

86
04:13.760 --> 04:18.080
Finally of course, the best test is going to be a show IP route.

87
04:18.080 --> 04:20.560
And we can filter by OSPF here.

88
04:20.560 --> 04:25.960
And we see that we're learning our two routes to the other side through tunnel

89
04:25.960 --> 04:26.560
one.

90
04:26.560 --> 04:32.040
We have the 10.40.10.0/24, which is the server subnet that we're actually
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:26.560 --> 04:32.040
We have the 10.40.10.0/24, which is the server subnet that we're actually

91
04:32.040 --> 04:33.640
trying to reach.

92
04:33.640 --> 04:40.100
Plus we see the 10.200.40.1/32, which is that loopback interface that we just

93
04:40.100 --> 04:41.640
created on GCP

94
04:41.640 --> 04:42.640
R1.

95
04:42.640 --> 04:46.240
So this appears that our dynamic routing is up and running.

96
04:46.240 --> 04:49.040
We have our neighborships, we're exchanging routes.

97
04:49.040 --> 04:52.680
So OSPF is functioning properly.

98
04:52.680 --> 04:57.860
So in this video, we got our dynamic routing, specifically OSPF, up and running

99
04:57.860 --> 04:58.480
between

100
04:58.480 --> 05:02.560
our two routers across our IP sec tunnel.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:58.480 --> 05:02.560
our two routers across our IP sec tunnel.

101
05:02.560 --> 05:07.060
Now that we have our routes being learned on each end, probably time to jump in

102
05:07.060 --> 05:07.680
and test

103
05:07.680 --> 05:12.400
end to end connectivity, which was the goal of this skill.

104
05:12.400 --> 05:14.680
So let's check that out in the next video.

105
05:14.680 --> 05:24.680
[BLANK_AUDIO]