WEBVTT

1
00:00.000 --> 00:01.960
In this video, I'd love to do two things.

2
00:01.960 --> 00:06.200
Number one, I'd like to do a quick review of the concept of an NSX Federation.

3
00:06.200 --> 00:09.200
Now, we covered the basics of it in a previous skill.

4
00:09.200 --> 00:11.800
So if you haven't checked out that one yet, I would encourage you to see that

5
00:11.800 --> 00:12.400
skill first.

6
00:12.400 --> 00:16.080
And then after we do a quick review of NSX Federation, I'd like to put a game

7
00:16.080 --> 00:16.800
plan together

8
00:16.800 --> 00:21.640
for implementing stretched gateways and also stretched segments that go across

9
00:21.640 --> 00:22.800
multiple sites.

10
00:22.800 --> 00:27.320
And as a quick review of an NSX Federation, we are going to use a global

11
00:27.320 --> 00:29.000
manager, like this one right here,

12
00:29.000 --> 00:32.700
and in a production environment, we'd have a cluster of global managers for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.000 --> 00:32.700
and in a production environment, we'd have a cluster of global managers for

13
00:32.700 --> 00:33.600
fault tolerance.

14
00:33.600 --> 00:37.850
And then that global manager would manage our local managers at site one and

15
00:37.850 --> 00:38.400
site two.

16
00:38.400 --> 00:42.170
And one of the major benefits of using a global manager is that as we tunnel

17
00:42.170 --> 00:43.400
traffic back and forth

18
00:43.400 --> 00:47.250
between the edges at these sites, where they're going to be using the remote

19
00:47.250 --> 00:48.000
tunnel endpoints,

20
00:48.000 --> 00:51.000
when doing so, the edges can actually fragment the traffic.

21
00:51.000 --> 00:56.380
And as a result, we don't need a larger than normal MTU because we can do the

22
00:56.380 --> 00:57.000
fragmentation.

23
00:57.000 --> 01:02.340
And we don't have to have less than or equal to 10 milliseconds of latency
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:57.000 --> 01:02.340
And we don't have to have less than or equal to 10 milliseconds of latency

24
01:02.340 --> 01:03.000
between the global manager

25
01:03.000 --> 01:07.000
and the edges because the local edges are managed by their local managers.

26
01:07.000 --> 01:10.330
So the play-by-play is the global manager interacts with the local managers and

27
01:10.330 --> 01:12.000
the local managers

28
01:12.000 --> 01:14.000
interact with their specific edges.

29
01:14.000 --> 01:17.270
And once again, because we're not directly dealing from the global manager down

30
01:17.270 --> 01:19.000
to the edges at site one

31
01:19.000 --> 01:22.710
or with the edges at site two, we don't have to have that extremely low latency

32
01:22.710 --> 01:23.000
.

33
01:23.000 --> 01:27.110
So for our game plan, as we take this existing infrastructure that we set up in

34
01:27.110 --> 01:28.000
our previous skill

35
01:28.000 --> 01:31.000
regarding NSX federations, for our game plan, let's do the following.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:28.000 --> 01:31.000
regarding NSX federations, for our game plan, let's do the following.

36
01:31.000 --> 01:34.560
The first thing we get to do is we're going to do some cleanup of some of the

37
01:34.560 --> 01:35.000
existing gateways

38
01:35.000 --> 01:37.000
and segments that are in our current topology.

39
01:37.000 --> 01:39.000
So that won't take too long to do.

40
01:39.000 --> 01:42.600
And also it'll give us the opportunity to walk through how to do that from the

41
01:42.600 --> 01:44.000
global manager.

42
01:44.000 --> 01:47.750
So you and I, we can go ahead and sit here at the global manager and do all the

43
01:47.750 --> 01:48.000
configurations

44
01:48.000 --> 01:52.000
and access the local managers via the global manager.

45
01:52.000 --> 01:55.390
And for our second step, let's create some new external segments, some VLAN

46
01:55.390 --> 01:56.000
back segments

47
01:56.000 --> 02:00.000
for connectivity to the external networks at both site one and site two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:00.000 --> 02:03.550
So for site one, we're going to go ahead and create an external VLAN back

49
02:03.550 --> 02:05.000
segment to support VLAN 23.

50
02:05.000 --> 02:09.220
And for the VLAN back segment to the external network over at site two, it's

51
02:09.220 --> 02:11.000
going to be using VLAN 24.

52
02:11.000 --> 02:13.000
So I'll make a little note there in our game plan.

53
02:13.000 --> 02:16.150
And then with those two external segments in place, we'll then go ahead and

54
02:16.150 --> 02:19.000
create a stretched tier zero gateway.

55
02:19.000 --> 02:22.000
That can be available to both site one and site two.

56
02:22.000 --> 02:25.800
And as part of that configuration, we'll configure interfaces that connect to

57
02:25.800 --> 02:27.000
the external networks.

58
02:27.000 --> 02:31.600
And in doing so for this tier zero gateway right here at site one, we'll have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:27.000 --> 02:31.600
And in doing so for this tier zero gateway right here at site one, we'll have

59
02:31.600 --> 02:33.000
two edge interfaces

60
02:33.000 --> 02:35.000
provided by edge one and edge two.

61
02:35.000 --> 02:37.000
And let's use this naming convention right here.

62
02:37.000 --> 02:43.000
So S one means site one, E one means edge one, V 23 represents VLAN 23.

63
02:43.000 --> 02:46.400
And 61 is going to help remind me what I want to use as the last octet for the

64
02:46.400 --> 02:47.000
IP address

65
02:47.000 --> 02:49.000
on that 23.1.2 network.

66
02:49.000 --> 02:53.000
And very similar treatment over here at site two, which also has two edge nodes

67
02:53.000 --> 02:53.000
.

68
02:53.000 --> 02:57.000
So it's site two for edge one and edge two, both will be on VLAN 24.

69
02:57.000 --> 03:00.000
And I'll use the IP addresses dot 61 and dot 62.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:00.000 --> 03:05.150
So this logical shared tier zero gateway is going to have four interfaces to

71
03:05.150 --> 03:06.000
over here at site one

72
03:06.000 --> 03:08.000
and two over here at site two.

73
03:08.000 --> 03:12.570
Now, in addition to having interfaces on this tier zero gateway, we'd also want

74
03:12.570 --> 03:15.000
to make sure that we have the routing in place.

75
03:15.000 --> 03:19.380
So as part of our game plan, we could configure border gateway protocol between

76
03:19.380 --> 03:21.000
the tier zero gateway

77
03:21.000 --> 03:25.000
and the external networks off of VLAN 23 and 24 respectively.

78
03:25.000 --> 03:29.170
Or we could just create a default route here for the tier zero for the benefit

79
03:29.170 --> 03:30.000
of site one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:30.000 --> 03:33.000
and a default route for the tier zero gateway at site two.

81
03:33.000 --> 03:36.310
So the cool thing is that even though we have this shared T zero stretched

82
03:36.310 --> 03:37.000
gateway,

83
03:37.000 --> 03:41.740
we can specify exactly which interfaces and which routing and so forth we want

84
03:41.740 --> 03:43.000
to use at each site.

85
03:43.000 --> 03:47.610
And if we ever want to have these VMs VM blue and VM green here at these two

86
03:47.610 --> 03:48.000
sites,

87
03:48.000 --> 03:51.000
if we want them to be able to go to the internet, we also need to make sure

88
03:51.000 --> 03:52.000
that we set up network address translation

89
03:52.000 --> 03:56.080
here at the T zero gateway at site one and also that at the tier zero gateway

90
03:56.080 --> 03:57.000
at site two.

91
03:57.000 --> 04:01.000
So let's also set up network address translation specifically source that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:57.000 --> 04:01.000
So let's also set up network address translation specifically source that.

92
04:01.000 --> 04:04.640
And the cool thing is about doing this with an NSX federation is I can walk you

93
04:04.640 --> 04:06.000
through the step by step

94
04:06.000 --> 04:11.000
for doing the interfaces and the routing and the net on a per site basis,

95
04:11.000 --> 04:14.000
even though we're talking about the same logical gateway.

96
04:14.000 --> 04:17.530
And then once we have that tier zero gateway set up, let's create a tier one

97
04:17.530 --> 04:18.000
gateway.

98
04:18.000 --> 04:19.000
That'd be this guy right here.

99
04:19.000 --> 04:23.000
And we'll connect this tier one gateway to the tier zero gateway.

100
04:23.000 --> 04:26.390
Another cool thing to notice that if we have a tier zero gateway that's

101
04:26.390 --> 04:28.000
stretched across four or five sites,

102
04:28.000 --> 04:33.000
we don't have to have the tier one gateway below that at all the same sites.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
04:28.000 --> 04:33.000
we don't have to have the tier one gateway below that at all the same sites.

103
04:33.000 --> 04:37.120
So for example, if the tier zero is stretched across five sites, we get out of

104
04:37.120 --> 04:39.000
tier one gateway at two of the sites,

105
04:39.000 --> 04:42.550
so one way of thinking about that is if we have like five or six sites, there's

106
04:42.550 --> 04:44.000
like one and two and three and four.

107
04:44.000 --> 04:48.000
And I'll go ahead and put little blocks there to represent those sites.

108
04:48.000 --> 04:51.840
We could create a tier zero that's available at all four sites and then we

109
04:51.840 --> 04:55.000
could go ahead and we could narrow it down as we go.

110
04:55.000 --> 04:59.000
So for example, maybe says our tier zero gateway and then for the tier one, for

111
04:59.000 --> 04:59.000
example,

112
04:59.000 --> 05:02.000
maybe we only want to at site one, two and three.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:59.000 --> 05:02.000
maybe we only want to at site one, two and three.

113
05:02.000 --> 05:05.560
So we make that available to one, two and three, but it's not available at site

114
05:05.560 --> 05:06.000
four,

115
05:06.000 --> 05:10.000
which reminds me of a common phrase my mom would use like many decades ago.

116
05:10.000 --> 05:14.540
She'd say, Keith, take a jacket because you can always take it off, but you can

117
05:14.540 --> 05:16.000
't put it on if you don't have it.

118
05:16.000 --> 05:20.000
So if you have the T zero available everywhere, we can then pick and choose

119
05:20.000 --> 05:21.000
where we're going to have the T ones.

120
05:21.000 --> 05:24.000
We don't have to have the same T ones available at all those sites.

121
05:24.000 --> 05:27.680
So for our lab environment here, I only have two sites and we're going to have

122
05:27.680 --> 05:30.000
our T zero available at both sites
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:30.000 --> 05:33.000
and both of the tier one available at both sites as well.

124
05:33.000 --> 05:36.390
And then after we have that tier one set up, we'll also go ahead and create our

125
05:36.390 --> 05:37.000
segment.

126
05:37.000 --> 05:39.000
So we'll create segment 10 there.

127
05:39.000 --> 05:42.280
Now, one other element that we probably want also if we have clients that are

128
05:42.280 --> 05:44.000
getting IP addresses dynamically

129
05:44.000 --> 05:47.000
is we'd probably also want to enable DHCP services.

130
05:47.000 --> 05:50.680
Now, as you already know from our previous skills, if we're enabling DHCP

131
05:50.680 --> 05:51.000
services,

132
05:51.000 --> 05:54.700
it's going to require the services of an edge node in the background to do that

133
05:54.700 --> 05:55.000
.

134
05:55.000 --> 05:58.750
And one of our caveat is that when we're using NSX federations and we have a

135
05:58.750 --> 06:00.000
stretched gateway,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:00.000 --> 06:04.320
one of the limitations is that with a stretched gateway, for example, this tier

137
06:04.320 --> 06:06.000
one gateway that's available at multiple sites,

138
06:06.000 --> 06:11.000
we don't have the option of using a gateway based DHCP server.

139
06:11.000 --> 06:15.000
But what we can do for the segment is we can set up a DHCP relay.

140
06:15.000 --> 06:21.190
So as part of our plan, I've got a little external DHCP server at 10.21.0.1,

141
06:21.190 --> 06:23.000
which is on VLAN 21.

142
06:23.000 --> 06:26.370
And to actually reach that server, we're also going to need to create another

143
06:26.370 --> 06:29.000
external segment for VLAN 21

144
06:29.000 --> 06:32.510
and then use that additional segment with one of our edge nodes for another
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
06:29.000 --> 06:32.510
and then use that additional segment with one of our edge nodes for another

145
06:32.510 --> 06:34.000
interface on our tier zero gateways

146
06:34.000 --> 06:38.150
so that we can actually reach that DHCP server. So we'll set that up as well

147
06:38.150 --> 06:39.000
when we get to that point.

148
06:39.000 --> 06:42.230
And then once it's all set up, we should be able to bring up the blue VM and

149
06:42.230 --> 06:43.000
the green VM

150
06:43.000 --> 06:46.350
and they should be able to ping each other. They should also go ahead and be

151
06:46.350 --> 06:48.000
able to access the Internet

152
06:48.000 --> 06:50.000
presuming that we've done all these steps correctly.

153
06:50.000 --> 06:53.580
And as a public service announcement and also to keep it real, I just want to

154
06:53.580 --> 06:56.000
remind you that we have covered

155
06:56.000 --> 07:00.420
most of these concepts before regarding setting up the concept of a T zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
06:56.000 --> 07:00.420
most of these concepts before regarding setting up the concept of a T zero

156
07:00.420 --> 07:01.000
gateway and a T one gateway

157
07:01.000 --> 07:06.170
and same DHCP services. So most of the work that we do here in configuring is

158
07:06.170 --> 07:07.000
going to be very similar

159
07:07.000 --> 07:10.350
as what we've done previously. But this time, we're going to be doing it from

160
07:10.350 --> 07:11.000
the global manager.

161
07:11.000 --> 07:15.710
And it'll be a great reinforcement of many of those concepts. And I do want to

162
07:15.710 --> 07:17.000
point out that this should not be

163
07:17.000 --> 07:21.620
your first introduction to the world of NSX and these components. It's going to

164
07:21.620 --> 07:23.000
be more of a reinforcement at this point.

165
07:23.000 --> 07:27.550
So if you need a deeper dive into setting up external segments or tier zero

166
07:27.550 --> 07:29.000
gateways or tier one gateways

167
07:29.000 --> 07:33.010
just on a local manager, please check out our other sets of videos and skills
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
07:29.000 --> 07:33.010
just on a local manager, please check out our other sets of videos and skills

168
07:33.010 --> 07:36.000
prior to this one as part of this course.

169
07:36.000 --> 07:40.000
So with that in mind, our very next step in getting this game plan kicked off

170
07:40.000 --> 07:42.000
is to do some cleanup of the existing topology,

171
07:42.000 --> 07:46.530
which is what you and I get to do in the very next video. So I'll see you there

172
07:46.530 --> 07:48.000
in just a moment.