WEBVTT

1
00:00.000 --> 00:04.310
So in this video, I'm going to take just a moment and let's enable OSPF on this

2
00:04.310 --> 00:09.360
external devices at .1 and also while we're at it, let me also enable OSPF on a

3
00:09.360 --> 00:10.340
second device.

4
00:10.340 --> 00:13.260
And that's going to be a multi-layer switch.

5
00:13.260 --> 00:16.540
And it also happens to do the same top of rack switch, this providing the

6
00:16.540 --> 00:20.520
transport network and the routing on the transport network between any of the

7
00:20.520 --> 00:23.600
transport nodes, whether edge nodes or host transport nodes.

8
00:23.600 --> 00:26.830
Anytime we're sending traffic back and forth over the Geneva tunnels, it's

9
00:26.830 --> 00:30.240
actually being performed in the background by this multi-layer switch, but it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.830 --> 00:30.240
actually being performed in the background by this multi-layer switch, but it

10
00:30.240 --> 00:33.600
also has a connection to this 192.1 state 1 network.

11
00:33.600 --> 00:35.100
It also supports OSPF.

12
00:35.100 --> 00:38.720
So what we're going to do is we're going to configure this device and enable it

13
00:38.720 --> 00:40.900
for OSPF and will enable this device for OSPF.

14
00:40.900 --> 00:43.800
So this one, if we do it first should be the designated router.

15
00:43.800 --> 00:46.200
This should become the backup designated router.

16
00:46.200 --> 00:49.930
So the edge nodes should be forming full adjacencies to each of the DR

17
00:49.930 --> 00:56.200
functions. So to the DR and BDR from edge 1 and from edge 2 to the DR and BDR.

18
00:56.200 --> 01:00.800
And edge 1 is going to be using .61 and edge 2 is using .62.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:56.200 --> 01:00.800
And edge 1 is going to be using .61 and edge 2 is using .62.

19
01:00.800 --> 01:04.490
Also for fun and because it's pretty quick to do, I'd like to also show you

20
01:04.490 --> 01:08.900
walking through the configuration of the OSPF on this device and this device.

21
01:08.900 --> 01:12.980
So behind the scenes, this device is really a 4 to 8 firewall and this device

22
01:12.980 --> 01:16.710
over here is a multi-layer switch with a VLAN 1 interface with a VLAN 1

23
01:16.710 --> 01:19.400
interface is logically connected right here.

24
01:19.400 --> 01:23.070
So without further ado, let's take a look at these two devices and enable OSPF

25
01:23.070 --> 01:24.400
on them respectively.

26
01:24.400 --> 01:28.070
So this is the graphical user interface for the 4 to 8 firewall, which is

27
01:28.070 --> 01:33.310
acting as our physical device at .1 on the 192.1 state 1 network and we are in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:28.070 --> 01:33.310
acting as our physical device at .1 on the 192.1 state 1 network and we are in

28
01:33.310 --> 01:35.100
the OSPF configuration here.

29
01:35.100 --> 01:39.520
And currently this firewall is not configured for OSPF. So let's go ahead and

30
01:39.520 --> 01:41.200
let's set it up so for areas.

31
01:41.200 --> 01:45.950
We'll click here on Create New and let's go ahead and use area 0, 0, 0, 0,

32
01:45.950 --> 01:47.600
click on OK and boom.

33
01:47.600 --> 01:51.770
Now it knows about area zero or will once we click here on apply and then for

34
01:51.770 --> 01:55.360
including networks as part of OSPF, I'm going to click right here and create

35
01:55.360 --> 01:59.460
new and I want to enable at least the network address space that's being used

36
01:59.460 --> 02:04.100
by this firewall as it connects to the 192.1 state 1 network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:59.460 --> 02:04.100
by this firewall as it connects to the 192.1 state 1 network.

37
02:04.100 --> 02:08.020
So I'm going to go ahead and specify that for area zero. I want to go ahead and

38
02:08.020 --> 02:14.360
include any interfaces on this gateway that begin with 192.168.1 anything and I

39
02:14.360 --> 02:16.100
'll go and put a slash 24 there.

40
02:16.100 --> 02:19.960
So effectively what that means to this device is that hey any interfaces that

41
02:19.960 --> 02:24.100
begin with 192.1 state 1, go ahead and include them as part of OSPF.

42
02:24.100 --> 02:28.920
So I'll click on OK and then I'll click on apply and let's go back to our

43
02:28.920 --> 02:31.100
interface for the NSX manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:28.920 --> 02:31.100
interface for the NSX manager.

44
02:31.100 --> 02:34.930
So here at the NSX manager on the tier zero gateway previously when we looked

45
02:34.930 --> 02:37.100
at the tier zero gateway and we looked at the details.

46
02:37.100 --> 02:40.590
If we went down to the OSPF section and under OSPF neighbors and clicked on

47
02:40.590 --> 02:44.100
view, we just saw the two edges, but check this out.

48
02:44.100 --> 02:48.700
Now we see a couple more hearings. So this top one right here that I've

49
02:48.700 --> 02:52.440
highlighted is edge one setting up a neighborhood and getting all dialed in

50
02:52.440 --> 02:57.550
with the device at 192.168.1.1, which is my physical 48 firewall acting as a

51
02:57.550 --> 02:59.100
physical layer three router.

52
02:59.100 --> 03:03.350
And then I have edge two right here that is peering up with that same IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:59.100 --> 03:03.350
And then I have edge two right here that is peering up with that same IP

53
03:03.350 --> 03:07.550
address, which once again is my physical layer three routing device. In my case

54
03:07.550 --> 03:09.100
, it's the 48 firewall.

55
03:09.100 --> 03:12.690
Now when I clicked on the original link here, it cut it in the state called X-D

56
03:12.690 --> 03:13.100
ART.

57
03:13.100 --> 03:16.590
So on the way to becoming fully adjacent neighbors, it's a lot like going

58
03:16.590 --> 03:20.100
through school, hit to start with grade school and college, etc.

59
03:20.100 --> 03:24.590
So with OSPF, we're going to go through states like the init state and the two

60
03:24.590 --> 03:29.100
way state and the X-DART and X-Change until we finally get to the full state.

61
03:29.100 --> 03:32.750
So when I clicked on the link to show the neighbors, at that point where we cut
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:29.100 --> 03:32.750
So when I clicked on the link to show the neighbors, at that point where we cut

62
03:32.750 --> 03:36.390
it, it was edge one and edge two going through the various states and we cut it

63
03:36.390 --> 03:37.100
at X-DART.

64
03:37.100 --> 03:41.530
So if we clicked right here on the refresh icon, which I'll do right now, if

65
03:41.530 --> 03:45.610
everything went well, our state should be full, which implies a fully adjacent

66
03:45.610 --> 03:46.100
state.

67
03:46.100 --> 03:50.940
So edge one has a fully adjacent neighborship with my physical router and so

68
03:50.940 --> 03:52.100
does edge two.

69
03:52.100 --> 03:56.930
Now let me leave this screen up as it is and let's also bring in one more OSPF

70
03:56.930 --> 04:00.100
speaking device and that's going to be our multi layer switch.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:56.930 --> 04:00.100
speaking device and that's going to be our multi layer switch.

71
04:00.100 --> 04:03.160
So this is a Cisco catalyst multi layer switch. And so if we go into

72
04:03.160 --> 04:06.850
configuration mode on this multi layer switch, if we want to start the routing

73
04:06.850 --> 04:12.550
process for OSPF on this platform, the command is router space OSPF space, and

74
04:12.550 --> 04:13.100
then we have to give it a process ID.

75
04:13.100 --> 04:17.240
So I'll give it process ID one and for interface VLAN one, which is my logical

76
04:17.240 --> 04:18.100
interface.

77
04:18.100 --> 04:23.180
I'm using to connect to that 192.168.1 network. I'm going to simply say IP OSPF

78
04:23.180 --> 04:25.100
space of question mark.

79
04:25.100 --> 04:28.300
I'm going to specify the OSPF process ID of one that I just created a few

80
04:28.300 --> 04:32.100
moments ago, then I'll specify that I want this interface to be in area zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:28.300 --> 04:32.100
moments ago, then I'll specify that I want this interface to be in area zero.

81
04:32.100 --> 04:37.150
And then if we do show IP OSPF neighbors and I type in summary and press enter,

82
04:37.150 --> 04:38.100
it's going to show us our current status.

83
04:38.100 --> 04:41.460
So at the time I issued the command, I already had these two that just popped

84
04:41.460 --> 04:43.100
in these two full adjacencies.

85
04:43.100 --> 04:46.100
And that's from edge one and edge two based on their IP addresses there.

86
04:46.100 --> 04:49.100
And then I have a third one right here that was still forming.

87
04:49.100 --> 04:52.690
And I see down here that it's completely formed. So now I should have three

88
04:52.690 --> 04:54.100
full adjacencies.

89
04:54.100 --> 04:56.100
So I've got a full adjacency with all three of them.

90
04:56.100 --> 05:01.100
So with the physical device that's my 48 there at one dot one, it is a DR.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:56.100 --> 05:01.100
So with the physical device that's my 48 there at one dot one, it is a DR.

91
05:01.100 --> 05:07.100
And then for my full adjacency, I have to 6162 those devices are DR others.

92
05:07.100 --> 05:10.100
That's because they didn't want to do the DR or the BDR role.

93
05:10.100 --> 05:12.100
And that's why they're showing as DR others.

94
05:12.100 --> 05:16.100
And then we did a show IP OSPF interface brief here on this KELA switch.

95
05:16.100 --> 05:21.520
It's also showing us that on this interface interface VLAN one that it on this

96
05:21.520 --> 05:24.100
interface, which has the IP address ending in 136.

97
05:24.100 --> 05:27.100
It is acting as a BDR on the segment.

98
05:27.100 --> 05:33.160
So the physical 40 gate device is our DR. This multi layer switch is the BDR
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
05:27.100 --> 05:33.160
So the physical 40 gate device is our DR. This multi layer switch is the BDR

99
05:33.160 --> 05:38.100
and the two edge nodes at dot 61 and 62 are acting as DR others.

100
05:38.100 --> 05:44.260
So on this segment here 192.168.1.0. We've got our 40 gate at dot one. It's the

101
05:44.260 --> 05:45.100
DR.

102
05:45.100 --> 05:49.120
We have the multi layer switch. It's at dot 136. It's acting as the backup

103
05:49.120 --> 05:50.100
designated router.

104
05:50.100 --> 05:55.110
And then we have our two edge nodes, edge one and edge two and there at dot 61

105
05:55.110 --> 05:56.100
and 62.

106
05:56.100 --> 06:00.120
And collectively those two edge nodes are providing the functionality of our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
05:56.100 --> 06:00.120
And collectively those two edge nodes are providing the functionality of our

107
06:00.120 --> 06:02.100
services router on gateway zero.

108
06:02.100 --> 06:06.400
So if we went back to the GUI interface on the NSX manager and we said, hey,

109
06:06.400 --> 06:10.140
please show us the OSPF adjacency is what we should see is we should see full

110
06:10.140 --> 06:14.100
adjacency is here and here and here and here.

111
06:14.100 --> 06:17.200
And then between edge one and edge two, as we said before, they should be in

112
06:17.200 --> 06:18.100
the two way state.

113
06:18.100 --> 06:22.100
So let's go verify that back in the NSX manager. So back in the NSX manager,

114
06:22.100 --> 06:26.580
all I'm going to do right here is simply click on refresh and survey says there

115
06:26.580 --> 06:27.100
we go.

116
06:27.100 --> 06:31.730
So edge one has a full adjacency with 136, which is our multi layer switch and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
06:27.100 --> 06:31.730
So edge one has a full adjacency with 136, which is our multi layer switch and

117
06:31.730 --> 06:34.100
so does edge two. So I'm going to close that.

118
06:34.100 --> 06:38.150
Now, if we went back to our topology here for a moment and we took a close look

119
06:38.150 --> 06:43.100
at the routing table here on our tier zero gateway, even though we have OSPF,

120
06:43.100 --> 06:46.650
neighborships and adjacencies all set up, it doesn't mean that we're

121
06:46.650 --> 06:48.100
advertising anything.

122
06:48.100 --> 06:50.930
So if we're going to take a look at the tier zero gateway and its routing table

123
06:50.930 --> 06:56.100
, it would pretty much be identical as to what it was before we enabled OSPF.

124
06:56.100 --> 06:59.610
So now here in the VRA for a services router, if we didn't get route and press

125
06:59.610 --> 07:02.100
enter, in those that we have the same routes that we had previously.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
06:59.610 --> 07:02.100
enter, in those that we have the same routes that we had previously.

126
07:02.100 --> 07:05.390
So our next logical step that is to go ahead and start training both our

127
07:05.390 --> 07:09.880
gateway zero and also our external OSPF routers to start advertising the routes

128
07:09.880 --> 07:12.100
that they want to advertise into OSPF.

129
07:12.100 --> 07:16.100
And that gives us the benefit of learning routes via OSPF.

130
07:16.100 --> 07:18.100
So we'll take that next logical step in the next video.

131
07:18.100 --> 07:20.320
video.