WEBVTT

1
00:00.000 --> 00:08.160
So now that our tunnel is up functional and tested, it's now time to test our

2
00:08.160 --> 00:08.880
end-to-end

3
00:08.880 --> 00:11.680
connectivity across that tunnel.

4
00:11.680 --> 00:15.800
But before we can do that, we need to have a way for the routers to learn what

5
00:15.800 --> 00:16.440
networks

6
00:16.440 --> 00:19.720
are available on the far side of the tunnel.

7
00:19.720 --> 00:22.280
So there's a couple ways to do this, of course.

8
00:22.280 --> 00:26.460
As I mentioned at the end of the last video, we could use just static routing

9
00:26.460 --> 00:26.920
or maybe

10
00:26.920 --> 00:32.250
we could use BGP or OSPF, even EIGRP, we can pretty much use any form of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:26.920 --> 00:32.250
we could use BGP or OSPF, even EIGRP, we can pretty much use any form of

11
00:32.250 --> 00:33.120
routing we

12
00:33.120 --> 00:34.280
want here.

13
00:34.280 --> 00:36.040
So I just want to make sure we're clear.

14
00:36.040 --> 00:39.800
I'm going to use OSPF just because I have to pick one.

15
00:39.800 --> 00:43.680
However, if you use a different routing protocol in your environment and you're

16
00:43.680 --> 00:44.360
more familiar

17
00:44.360 --> 00:46.800
with that, feel free to use that here instead.

18
00:46.800 --> 00:50.480
But I'm going to show you how to set it up with OSPF and then we'll verify that

19
00:50.480 --> 00:50.800
we have

20
00:50.800 --> 00:53.800
the routes learned from the far side of the tunnel.

21
00:53.800 --> 00:55.200
Let's jump in and get started.

22
00:55.200 --> 01:02.880
So again, we'll start here on on prem R1 and what we want to do here is simply
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:55.200 --> 01:02.880
So again, we'll start here on on prem R1 and what we want to do here is simply

23
01:02.880 --> 01:03.560
go into

24
01:03.560 --> 01:04.560
router OSPF.

25
01:04.560 --> 01:06.600
We'll use process one.

26
01:06.600 --> 01:09.720
It really doesn't matter what process we use here.

27
01:09.720 --> 01:12.520
It's usually a good idea to set the router ID.

28
01:12.520 --> 01:16.280
So we'll set this to 10.100.1.1.

29
01:16.280 --> 01:20.400
We're also going to create a loop back interface here, which is also generally

30
01:20.400 --> 01:22.360
a good idea for

31
01:22.360 --> 01:26.760
management and other purposes and we'll set the IP address on this to actually

32
01:26.760 --> 01:27.320
match the

33
01:27.320 --> 01:29.720
OSPF router ID.

34
01:29.720 --> 01:35.600
So we'll again set this to 10.100.1.1 and we'll make this a slash 32.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.720 --> 01:35.600
So we'll again set this to 10.100.1.1 and we'll make this a slash 32.

35
01:35.600 --> 01:39.560
We'll also bring this into OSPF.

36
01:39.560 --> 01:42.880
So we'll simply say IP OSPF 1 area zero.

37
01:42.880 --> 01:46.280
We're just going to put everything into area zero right now.

38
01:46.280 --> 01:49.640
Our environment's not really big enough to warrant more than one area.

39
01:49.640 --> 01:53.480
So we'll just bring all of our interfaces into area zero.

40
01:53.480 --> 01:57.700
So then we'll go into interface gigabit to remember this is our client facing

41
01:57.700 --> 01:58.600
interface.

42
01:58.600 --> 02:02.800
So this is the one we really want advertised to the other side.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:58.600 --> 02:02.800
So this is the one we really want advertised to the other side.

43
02:02.800 --> 02:06.200
So we'll go ahead and bring that into OSPF as well.

44
02:06.200 --> 02:10.890
Now there aren't any OSPF neighbors out our gigabit to or even our loop back

45
02:10.890 --> 02:12.480
zero interface.

46
02:12.480 --> 02:17.590
So from a pure routing protocol perspective, we can also make these passive

47
02:17.590 --> 02:18.280
interfaces

48
02:18.280 --> 02:19.360
and such.

49
02:19.360 --> 02:22.840
There's some things we can do to tweak our routing protocol, but that's not

50
02:22.840 --> 02:23.200
really our

51
02:23.200 --> 02:24.760
focus right now.

52
02:24.760 --> 02:29.220
So for now, we're just going to do a basic implementation of OSPF, nothing

53
02:29.220 --> 02:29.880
fancy.

54
02:29.880 --> 02:34.600
And of course, we also need to enable it on our tunnel one interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:29.880 --> 02:34.600
And of course, we also need to enable it on our tunnel one interface.

55
02:34.600 --> 02:38.440
So that should take care of enabling OSPF on all of those interfaces.

56
02:38.440 --> 02:44.010
If we do a show IP OSPF interface brief, we see here that OSPF is currently

57
02:44.010 --> 02:44.760
enabled

58
02:44.760 --> 02:50.520
on the loop back zero, the tunnel one and the gigabit to interface.

59
02:50.520 --> 02:54.800
So now let's go over and configure Azure R1.

60
02:54.800 --> 02:59.480
It's almost the same configuration except for the address for the router ID and

61
02:59.480 --> 02:59.760
the loop

62
02:59.760 --> 03:01.480
back zero interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:59.760 --> 03:01.480
back zero interface.

63
03:01.480 --> 03:05.680
So we'll just paste this configuration in and then we'll do our show IP OSPF

64
03:05.680 --> 03:06.400
interface

65
03:06.400 --> 03:07.880
brief.

66
03:07.880 --> 03:11.300
We see here that again, our loop back zero tunnel one and gigabit two

67
03:11.300 --> 03:12.560
interfaces are enabled

68
03:12.560 --> 03:19.320
for OSPF and we actually have a neighbor ship over the tunnel one interface.

69
03:19.320 --> 03:21.920
We do a show IP OSPF neighbor.

70
03:21.920 --> 03:25.640
We see that our neighbor ship to on prem R1 is actually up.

71
03:25.640 --> 03:29.800
The state is full over the tunnel one interface.

72
03:29.800 --> 03:35.840
If we do a show IP OSPF interface for tunnel one, few things we can see here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:29.800 --> 03:35.840
If we do a show IP OSPF interface for tunnel one, few things we can see here.

73
03:35.840 --> 03:37.480
We see that again, the tunnel is up.

74
03:37.480 --> 03:39.800
The line protocol is up.

75
03:39.800 --> 03:45.280
We see that the default OSPF network type here is point to point and the tunnel

76
03:45.280 --> 03:45.720
has a

77
03:45.720 --> 03:49.120
default cost of 1000.

78
03:49.120 --> 03:54.490
We also see that the default hello timer is 10 seconds and the default dead

79
03:54.490 --> 03:55.320
timer is

80
03:55.320 --> 03:56.760
40.

81
03:56.760 --> 04:02.230
We can also do a show IP route OSPF and we see that we're actually learning two
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:56.760 --> 04:02.230
We can also do a show IP route OSPF and we see that we're actually learning two

82
04:02.230 --> 04:02.920
routes

83
04:02.920 --> 04:05.640
from the other side across the tunnel.

84
04:05.640 --> 04:11.140
One of those of course being the client subnet over on the on prem side and the

85
04:11.140 --> 04:11.680
other one

86
04:11.680 --> 04:16.040
being the loop back interface of on prem R1.

87
04:16.040 --> 04:21.970
At this point, everything with our routing protocol seems to be functioning

88
04:21.970 --> 04:22.280
correctly.

89
04:22.280 --> 04:26.120
In this video, we got our dynamic routing protocol.

90
04:26.120 --> 04:31.040
In this case, OSPF, again, remember, you can use any routing protocol you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:26.120 --> 04:31.040
In this case, OSPF, again, remember, you can use any routing protocol you

91
04:31.040 --> 04:31.760
prefer, but

92
04:31.760 --> 04:35.440
we got this up and running over our tunnel interface.

93
04:35.440 --> 04:39.840
We can tell that our routing protocol is in fact supported across the tunnel.

94
04:39.840 --> 04:41.240
Our neighborships come up.

95
04:41.240 --> 04:42.880
We've learned routes.

96
04:42.880 --> 04:46.400
Everything is working fine with our dynamic protocol.

97
04:46.400 --> 04:51.890
So next, let's jump into our end devices and see if we actually have end to end

98
04:51.890 --> 04:52.960
reachability.

99
04:52.960 --> 04:55.960
(mouse clicking)