WEBVTT

1
00:00.000 --> 00:02.720
So when we left off, we verify that we have some OSPF

2
00:02.720 --> 00:05.560
neighborhoodships to verify that we could expand our tier

3
00:05.560 --> 00:08.960
zero gateway, go down to OSPF, expand that, and then click

4
00:08.960 --> 00:12.160
on the hyperlink view right next to OSPF neighbors.

5
00:12.160 --> 00:15.040
Just to verify we have our OSPF neighbors in place.

6
00:15.040 --> 00:18.280
So here are the OSPF neighbors from the perspective of

7
00:18.280 --> 00:21.360
gateway zero and is two respective edge nodes that are

8
00:21.360 --> 00:22.240
supporting it.

9
00:22.240 --> 00:25.160
However, what we haven't done yet is told the external world,

10
00:25.160 --> 00:28.680
the external routers to share information with the edge

11
00:28.680 --> 00:31.560
nodes and we haven't told the gateway zero via its edge
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.680 --> 00:31.560
nodes and we haven't told the gateway zero via its edge

12
00:31.560 --> 00:34.360
nodes to share information with the external routers.

13
00:34.360 --> 00:37.080
So to train the tier zero gateway to start advertising routes,

14
00:37.080 --> 00:39.800
we can go ahead and click on the three dots, then click on

15
00:39.800 --> 00:43.000
edit and then scroll down below the OSPF section.

16
00:43.000 --> 00:45.880
We have a section here for route redistribution.

17
00:45.880 --> 00:48.280
So on this T zero gateway, we currently have routes for the

18
00:48.280 --> 00:49.560
1010 zero network.

19
00:49.560 --> 00:52.360
We're learning those via gateway A, we also have routes for the

20
00:52.360 --> 00:53.320
1020 network.

21
00:53.320 --> 00:55.160
We're learning those via gateway B.

22
00:55.160 --> 00:58.280
And what we can do is we can redistribute those into OSPF.

23
00:58.280 --> 01:01.400
And that way our external OSPF buddies, for example, the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.280 --> 01:01.400
And that way our external OSPF buddies, for example, the

24
01:01.400 --> 01:04.280
40 gate at dot one and the multi layer switch at dot

25
01:04.280 --> 01:07.880
136, they can both now start learning about those routes.

26
01:07.880 --> 01:10.360
So here under the route redistribution section, I'm going to

27
01:10.360 --> 01:13.480
go ahead and first of all, click on via OSPF.

28
01:13.480 --> 01:16.120
I'm going to go ahead and say yes and click on save.

29
01:16.120 --> 01:19.160
And then furthermore, I'm going to go ahead and go into route

30
01:19.160 --> 01:20.680
redistribution and click on set.

31
01:20.680 --> 01:23.160
So for the name, I'm going to give it a friendly name of

32
01:23.160 --> 01:27.560
those class, seg 10 and seg 20 subnets.

33
01:27.560 --> 01:29.720
And then for the destination, I don't want it to be BGP.

34
01:29.720 --> 01:31.080
I want it to be OSPF.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.720 --> 01:31.080
I want it to be OSPF.

35
01:31.080 --> 01:34.520
And then for the actual route redistribution, we'll click here on set.

36
01:34.520 --> 01:35.960
And we have two major sections.

37
01:35.960 --> 01:39.320
We have routes directly related to our tier zero gateway.

38
01:39.320 --> 01:41.880
And we also have routes related to our tier one subnet.

39
01:41.880 --> 01:46.280
So if we wanted to take the tier one subnets, including the 1010

40
01:46.280 --> 01:49.800
and 1020, we simply click this checkbox right there and boom.

41
01:49.800 --> 01:50.840
That's going to do it for us.

42
01:50.840 --> 01:54.200
So once we save this, this should cause the routes, the 1010 and

43
01:54.200 --> 01:59.400
the 1020 subnet routes to be advertised via OSPF to our external routers.

44
01:59.400 --> 02:02.520
In fact, before I click on apply, let's go take a look at the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:59.400 --> 02:02.520
In fact, before I click on apply, let's go take a look at the

45
02:02.520 --> 02:06.520
routing table on our multi-layer switch and verify that we don't yet

46
02:06.520 --> 02:09.960
have routes for the 1010 network or the 1020 network.

47
02:09.960 --> 02:13.320
And also before we head over to the top of rack switch.

48
02:13.320 --> 02:16.680
And we also just confirm here that the tier zero gateway,

49
02:16.680 --> 02:18.840
which we're currently looking at the routing table for,

50
02:18.840 --> 02:21.800
it knows about how to reach the 1010 zero and 1020 zero.

51
02:21.800 --> 02:25.240
However, if we minimize that and we go over to my multi-layer switch.

52
02:25.240 --> 02:27.160
So this is our top of rack switch here.

53
02:27.160 --> 02:29.880
And we do a show IP route press enter.

54
02:29.880 --> 02:32.200
In fact, let me just go ahead and filter that a little bit and say,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:29.880 --> 02:32.200
In fact, let me just go ahead and filter that a little bit and say,

55
02:32.200 --> 02:36.360
please show me only output that includes a slash 24.

56
02:36.360 --> 02:38.920
And that'll thin the output just a little bit fair enough.

57
02:38.920 --> 02:42.200
So on this external router, this multi-layer switch running OSPF,

58
02:42.200 --> 02:47.480
it does not yet know about how to reach the 1010 subnet or the 1020 subnet.

59
02:47.480 --> 02:49.080
That's not in its routing table.

60
02:49.080 --> 02:50.680
So back here in the ASX manager,

61
02:50.680 --> 02:52.280
focusing on our tier zero gateway,

62
02:52.280 --> 02:55.720
with the connected interfaces and segments now checked under advertised tier

63
02:55.720 --> 02:56.600
one subnets,

64
02:56.600 --> 02:57.880
let's click on apply.

65
02:57.880 --> 03:02.120
And then we'll click on add and apply and save.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:57.880 --> 03:02.120
And then we'll click on add and apply and save.

66
03:02.120 --> 03:03.560
And we'll just keep clicking.

67
03:03.560 --> 03:07.720
Yes, yes, yes until it gives us a final acknowledgement that it's all done.

68
03:07.720 --> 03:10.680
So if we click on collapse all, we are now good to go.

69
03:10.680 --> 03:14.360
So just to check our work, we expand our tier zero gateway

70
03:14.360 --> 03:16.120
and go into route redistribution.

71
03:16.120 --> 03:18.040
We are doing route redistribution, the details.

72
03:18.040 --> 03:20.040
If we click on the hyperlink, it'll show us the details

73
03:20.040 --> 03:22.120
and we'll redistribute them into OSPF.

74
03:22.120 --> 03:24.040
So now if we go back to the multi-layer switch,

75
03:24.040 --> 03:27.080
which previously didn't have routes to the 1010 or 1020,

76
03:27.080 --> 03:30.680
if we hit the upper key and do the same exact command again, check it out.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:27.080 --> 03:30.680
if we hit the upper key and do the same exact command again, check it out.

77
03:30.680 --> 03:34.840
Now we have dynamically learned via OSPF those two routes.

78
03:34.840 --> 03:37.880
And if we want to forward packets to either of those destinations,

79
03:37.880 --> 03:40.520
the 1010 zero anything or the 1020 zero anything,

80
03:40.520 --> 03:43.480
we are going to be handing off to the next top at dot 61,

81
03:43.480 --> 03:47.480
which in our topology is the active edge router at dot 61.

82
03:47.480 --> 03:50.520
Well, edge two is acting currently as a standby.

83
03:50.520 --> 03:55.080
So from here, we can do a ping, for example, to 10 dot 10 dot zero dot 10.

84
03:55.080 --> 03:57.880
And that is the IP address of VM1, we'll press center

85
03:57.880 --> 03:59.400
and we have connectivity there.

86
03:59.400 --> 04:00.920
Also, while we're here on this multi-layer switch,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:59.400 --> 04:00.920
Also, while we're here on this multi-layer switch,

87
04:00.920 --> 04:03.720
let me create a quick loopback interface interface.

88
04:03.720 --> 04:05.400
We'll call it loopback nine.

89
04:05.400 --> 04:09.000
And we'll give the IP address of 99 dot 99 dot 99 dot 99 dot 99.

90
04:09.000 --> 04:11.640
And I'll go ahead and give that a 32-bit mask.

91
04:11.640 --> 04:13.560
And then I'll also include it as part of OSPF.

92
04:13.560 --> 04:16.840
So it's advertised IP OSPF one, and we'll put that

93
04:16.840 --> 04:18.920
and we'll put this logical interface in area zero.

94
04:18.920 --> 04:22.520
And then we'll exit out and do a show IP OSPF interface brief,

95
04:22.520 --> 04:25.640
just to verify that that interface is now included as part of OSPF.

96
04:25.640 --> 04:28.440
And as a result, because we're now advertising that in OSPF,

97
04:28.440 --> 04:31.560
our tier zero gateway should automatically be learning about that network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
04:28.440 --> 04:31.560
our tier zero gateway should automatically be learning about that network.

98
04:31.560 --> 04:33.880
So we can verify that by going back to edge one

99
04:33.880 --> 04:37.000
and then typing in get gateways and then just going into the VRF

100
04:37.000 --> 04:38.600
or services router here.

101
04:38.600 --> 04:41.160
So that's VRF four and then it'll do a get route.

102
04:41.160 --> 04:43.880
And sure enough, there's the OSPF learned route right there.

103
04:43.880 --> 04:46.520
So from the tier zero gateway, we're in the VRF for it right now.

104
04:46.520 --> 04:50.760
If we did a ping to 99 dot 99 dot 99 dot 99 dot 99.

105
04:50.760 --> 04:53.240
And that should work because we have a route now to get there.

106
04:53.240 --> 04:56.520
Also, if we brought up one of our little VMs, this is the VM10.

107
04:56.520 --> 04:59.400
VM10 has a default gateway pointing to gateway B.

108
04:59.400 --> 05:02.840
Gateway B has a default route that leads up to gateway zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
04:59.400 --> 05:02.840
Gateway B has a default route that leads up to gateway zero

109
05:02.840 --> 05:06.120
and gateway zero, which we're currently looking at the routing table here for.

110
05:06.120 --> 05:11.000
It has a route to that 99 99 99 with that next top of our multi-layer switch.

111
05:11.000 --> 05:14.040
Which if we scroll up just a little bit, is it dot 136?

112
05:14.040 --> 05:16.840
So that means this little VM should also be able to ping that address,

113
05:16.840 --> 05:22.040
with type in ping 99 dot 99 dot 99 dot 99 press center and survey says,

114
05:22.040 --> 05:23.240
no worries whatsoever.

115
05:23.240 --> 05:24.840
So we'll go ahead and do a control C.

116
05:24.840 --> 05:27.400
And the last thing I'd also like to do is I'd like to train

117
05:27.400 --> 05:30.760
my external networked environment to advertise a default route.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:27.400 --> 05:30.760
my external networked environment to advertise a default route.

118
05:30.760 --> 05:33.960
So currently we have a statically learned default route

119
05:33.960 --> 05:35.960
and it has an AD of 150.

120
05:35.960 --> 05:38.920
So OSPF has an AD of 110.

121
05:38.920 --> 05:42.840
So if we train my external network to advertise a default route via OSPF,

122
05:42.840 --> 05:46.600
this top route right here, the default route should be replaced in the routing

123
05:46.600 --> 05:47.080
table

124
05:47.080 --> 05:48.840
with the route learned via OSPF.

125
05:48.840 --> 05:52.780
And so the easiest way for me to do that right here is to do it from the multi-

126
05:52.780 --> 05:53.560
layer switch,

127
05:53.560 --> 05:55.560
which is currently participating in OSPF.

128
05:55.560 --> 05:57.080
So let's do a config T.

129
05:57.080 --> 06:00.440
In the Cisco world, that's how we go into configuration mode on this platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:57.080 --> 06:00.440
In the Cisco world, that's how we go into configuration mode on this platform.

130
06:00.440 --> 06:04.440
And then from here, we'll go into router OSPF, that same process ID number

131
06:04.440 --> 06:08.280
and say default information originate and press enter.

132
06:08.280 --> 06:11.960
What that says is, hey, dear Mr. Multi-layer Switch, if you have a default

133
06:11.960 --> 06:13.080
route, which it does,

134
06:13.080 --> 06:16.120
please go ahead and advertise that into OSPF.

135
06:16.120 --> 06:20.470
And as a result, our tier zero gateway has now learned about a default route

136
06:20.470 --> 06:22.360
with a better AD of 110.

137
06:22.360 --> 06:25.240
And as a result, that should be the new default route in the routing table.

138
06:25.240 --> 06:27.400
So I'll go ahead and bring that back down the size.

139
06:27.400 --> 06:31.200
Let's go back to our edge device, make that full screen, and let's hit the app
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
06:27.400 --> 06:31.200
Let's go back to our edge device, make that full screen, and let's hit the app

140
06:31.200 --> 06:31.640
arrow key.

141
06:31.640 --> 06:34.920
So a moment ago, when we looked at the routing table for gateway zero,

142
06:34.920 --> 06:37.960
it showed the static route with the default route, which has an AD and

143
06:37.960 --> 06:39.560
administrative distance of 150.

144
06:39.560 --> 06:43.080
But because now we're advertising a default route and it's coming in via OSPF,

145
06:43.080 --> 06:47.000
it has a better or lower AD if we press enter now with a get route.

146
06:47.000 --> 06:51.670
So notice now that we still have a default route, but now it's being learned

147
06:51.670 --> 06:52.200
via OSPF.

148
06:52.200 --> 06:54.840
This is the route in our routing table for the gateway zero.

149
06:54.840 --> 06:58.530
And that's because this route, learned via OSPF, has a lower and better

150
06:58.530 --> 06:59.560
administrative distance

151
06:59.560 --> 07:02.360
than our static route, which we set at 150.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
06:59.560 --> 07:02.360
than our static route, which we set at 150.

152
07:02.360 --> 07:05.400
So from a client's perspective, and this is my little VM right here,

153
07:05.400 --> 07:09.960
we should be able to ping any of the addresses on the 192.1 state one network.

154
07:09.960 --> 07:14.360
So we did a ping to 192.168.1.1.

155
07:14.360 --> 07:19.480
That's working because my router at .1 also has the routing information on how

156
07:19.480 --> 07:20.360
to forward back now

157
07:20.360 --> 07:22.520
to 1010 and 1020, those subnets.

158
07:22.520 --> 07:28.640
If we tried to ping 136, which is the interface on the MOCALAYER switch up

159
07:28.640 --> 07:28.680
there, that works great.

160
07:28.680 --> 07:32.480
And once again, if we tried to ping the loop back of 9999, that also works
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
07:28.680 --> 07:32.480
And once again, if we tried to ping the loop back of 9999, that also works

161
07:32.480 --> 07:33.320
because we have routing

162
07:33.320 --> 07:37.530
in both directions, meaning this client knows how to forward in the direction

163
07:37.530 --> 07:38.120
of that network

164
07:38.120 --> 07:40.520
and so does the entire infrastructure up to that point.

165
07:40.520 --> 07:43.860
And then the target, in this case, the loopback interface on the MOCALAYER

166
07:43.860 --> 07:44.360
switch

167
07:44.360 --> 07:48.880
has routing information on how to route back down to the 1010 or 1020 subnets,

168
07:48.880 --> 07:49.480
respectively.

169
07:49.480 --> 07:52.740
So now that we've taken a look at the concepts and configuration and

170
07:52.740 --> 07:54.200
verification of OSPF,

171
07:54.200 --> 07:58.120
in the next section, I'd like to offer you a little challenge to help reinforce

172
07:58.120 --> 07:59.000
our skills.