WEBVTT

1
00:00.000 --> 00:04.500
So for this video, based on our plan, we are going to create this new overlay

2
00:04.500 --> 00:04.960
segment,

3
00:04.960 --> 00:08.710
segment 30, and we'll plan on using on top of that segment the IP addressing

4
00:08.710 --> 00:09.120
space of

5
00:09.120 --> 00:14.400
1030. And because we don't have any of our gateways directly connected to this

6
00:14.400 --> 00:15.000
segment,

7
00:15.000 --> 00:19.030
which is floating out here in space, we'll go ahead and set up DHCP services

8
00:19.030 --> 00:19.800
using segment

9
00:19.800 --> 00:23.320
DHCP server. And then we'll test it out by putting on a couple clients and

10
00:23.320 --> 00:23.880
verifying

11
00:23.880 --> 00:27.350
that they get an IP address and that they can talk to each other. So with that

12
00:27.350 --> 00:27.960
in mind,

13
00:27.960 --> 00:32.120
let's head over to the NSX manager. All right. And here we go. So in the NSX
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:27.960 --> 00:32.120
let's head over to the NSX manager. All right. And here we go. So in the NSX

14
00:32.120 --> 00:32.600
manager, we're

15
00:32.600 --> 00:36.840
going to click on networking. And on the left under connectivity, we'll click

16
00:36.840 --> 00:37.760
on segments.

17
00:37.760 --> 00:41.770
So currently we have the segment 10 segment 20 and our external VLAN back

18
00:41.770 --> 00:42.920
segment. And

19
00:42.920 --> 00:46.850
what we want to do is create a segment 30. So we'll click on add segment. So we

20
00:46.850 --> 00:47.120
'll call

21
00:47.120 --> 00:50.360
it segment 30, no gateway, just remind ourselves what we're doing with that.

22
00:50.360 --> 00:50.600
And then for

23
00:50.600 --> 00:53.610
the connected gateway, we're going to leave that at none. We don't want to

24
00:53.610 --> 00:54.320
connect this

25
00:54.320 --> 00:57.970
segment to any of our gateways. It's just a segment hanging out there all by

26
00:57.970 --> 00:58.520
itself.

27
00:58.520 --> 01:03.210
We'll include that as part of our AB overlay transport zone. And then we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:58.520 --> 01:03.210
We'll include that as part of our AB overlay transport zone. And then we'll

28
01:03.210 --> 01:03.800
scroll down

29
01:03.800 --> 01:07.440
and click on safe. So effectively, we have this beautiful segment called

30
01:07.440 --> 01:08.160
segment 30,

31
01:08.160 --> 01:11.630
no gateway. And it's not connected to any gateway. It's part of the transport

32
01:11.630 --> 01:12.120
zone.

33
01:12.120 --> 01:17.990
Now to provide DHCP services within NSX, we are going to create an NSX server

34
01:17.990 --> 01:18.840
profile.

35
01:18.840 --> 01:22.590
And based on our plan, we're going to specify that the server, this NSX virtual

36
01:22.590 --> 01:23.000
ized DHCP

37
01:23.000 --> 01:28.360
server is at six dot seven dot eight dot three with a slash 29 bit mask. So to

38
01:28.360 --> 01:28.720
configure

39
01:28.720 --> 01:32.800
this DHCP server profile, we're going to click on the networking tab on top. It
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:28.720 --> 01:32.800
this DHCP server profile, we're going to click on the networking tab on top. It

40
01:32.800 --> 01:33.040
's currently

41
01:33.040 --> 01:36.790
selected. And then the left will scroll all the way down. And under settings,

42
01:36.790 --> 01:37.080
here is

43
01:37.080 --> 01:40.660
a section called networking profiles. So we'll click on that right there on the

44
01:40.660 --> 01:41.600
bottom left.

45
01:41.600 --> 01:46.770
And then in this main pane here, we have a sub tab called DHCP. And by default,

46
01:46.770 --> 01:46.960
there

47
01:46.960 --> 01:51.350
are no DHCP profiles. And we just deleted the relay profile that we had there

48
01:51.350 --> 01:52.240
previously.

49
01:52.240 --> 01:56.710
So if we want a server based DHCP profile that we're going to use for segment

50
01:56.710 --> 01:57.680
based DHCP

51
01:57.680 --> 02:02.890
services, we simply click here on DHCP, and then click on add DHCP profile. And
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:57.680 --> 02:02.890
services, we simply click here on DHCP, and then click on add DHCP profile. And

52
02:02.890 --> 02:03.040
let's

53
02:03.040 --> 02:08.260
call it our NSX DHCP server. And we're going to use the server profile a couple

54
02:08.260 --> 02:08.680
of times.

55
02:08.680 --> 02:12.180
We're going to use it now as we configure DHCP services for a segment where

56
02:12.180 --> 02:13.520
there's no

57
02:13.520 --> 02:17.510
gateway involved. And then we'll use it again when we configure DHCP services

58
02:17.510 --> 02:18.320
that are gateway

59
02:18.320 --> 02:22.260
based. So our NSX DHCP server for the type is not a relay. We did that

60
02:22.260 --> 02:23.280
previously. We

61
02:23.280 --> 02:27.050
want this to be a DHCP server. And for our purposes here, we don't even have to

62
02:27.050 --> 02:27.520
put in

63
02:27.520 --> 02:32.660
an IP address for this virtualized NSX DHCP server. So if we hover here on the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:27.520 --> 02:32.660
an IP address for this virtualized NSX DHCP server. So if we hover here on the

64
02:32.660 --> 02:33.080
icon for

65
02:33.080 --> 02:36.450
information, here it indicates that if we put in address here, it's going to be

66
02:36.450 --> 02:36.720
used

67
02:36.720 --> 02:41.390
for the gateway DHCP services function. So for this video, as we're going to be

68
02:41.390 --> 02:41.680
using

69
02:41.680 --> 02:46.630
this for just segment DHCP services, this IP address isn't critical. And then

70
02:46.630 --> 02:46.960
furthermore

71
02:46.960 --> 02:50.480
goes on to say that if we do put an IP address here, it'll be used as the IP

72
02:50.480 --> 02:50.800
address for the

73
02:50.800 --> 02:54.890
server as part of gateway DHCP services. And also indicates that if we don't

74
02:54.890 --> 02:55.680
put any address

75
02:55.680 --> 03:00.040
whatsoever, it'll use the address starting in 100 dot 96. So based on our plan
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
02:55.680 --> 03:00.040
whatsoever, it'll use the address starting in 100 dot 96. So based on our plan

76
03:00.040 --> 03:00.480
and also

77
03:00.480 --> 03:04.220
based on the fact that we're going to using this profile for segment based DHCP

78
03:04.220 --> 03:04.960
services,

79
03:04.960 --> 03:09.340
as well as gateway based DHCP services, let's use our address of six dot seven

80
03:09.340 --> 03:10.880
dot eight dot three

81
03:10.880 --> 03:14.940
with a 29 bit mask, just like that. And then furthermore, we're going to

82
03:14.940 --> 03:16.400
specify which cluster

83
03:16.400 --> 03:20.520
of edge devices we want to use to support the DHCP services. So I'm going to go

84
03:20.520 --> 03:21.040
ahead and pick

85
03:21.040 --> 03:24.540
our edge cluster is the only one we have in our topology, and we'll click on

86
03:24.540 --> 03:25.600
safe. So there's

87
03:25.600 --> 03:30.350
this profile that says our NSX DHCP server logically is at six dot seven dot
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:25.600 --> 03:30.350
this profile that says our NSX DHCP server logically is at six dot seven dot

88
03:30.350 --> 03:32.000
eight dot three. So we're

89
03:32.000 --> 03:36.450
going to be using this DHCP profile for segment based DHCP services, as well as

90
03:36.450 --> 03:37.360
gateway based

91
03:37.360 --> 03:41.850
DHCP services. So now that this profile exists, we're going to associate this

92
03:41.850 --> 03:43.120
profile with our

93
03:43.120 --> 03:47.380
segment 30 we created a few minutes ago. So to associate this profile with that

94
03:47.380 --> 03:48.240
new segment,

95
03:48.240 --> 03:51.970
we'll go here to segments. So with networking selected up on top under

96
03:51.970 --> 03:53.280
connectivity, we'll click

97
03:53.280 --> 03:57.550
on segments. And then we're going to edit the details for our segment 30 no

98
03:57.550 --> 03:58.720
gateway segment.

99
03:58.720 --> 04:02.620
So to edit this segment, we'll simply click on the three dots and click on edit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
03:58.720 --> 04:02.620
So to edit this segment, we'll simply click on the three dots and click on edit

100
04:02.620 --> 04:03.680
. So here is our

101
04:03.680 --> 04:07.550
segment 30 no gateway. There's no gateway associated with it is part of the

102
04:07.550 --> 04:08.720
transport zone. And then

103
04:08.720 --> 04:13.360
over here on the right, we have a button for set DHCP config. So we'll click on

104
04:13.360 --> 04:14.240
that and notice

105
04:14.240 --> 04:17.420
here because this segment is not connected to any of our gateways, it's not

106
04:17.420 --> 04:18.880
connected to gateway A,

107
04:18.880 --> 04:23.150
it's not connected to gateway B as a result, as we look at the DHCP type and

108
04:23.150 --> 04:24.480
use the drop down,

109
04:24.480 --> 04:27.650
you'll notice we don't have a whole bunch of cool options. We don't have a

110
04:27.650 --> 04:28.320
relay option.

111
04:28.320 --> 04:33.130
We don't have a gateway DHCP server option. All we have is a segment DHCP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:28.320 --> 04:33.130
We don't have a gateway DHCP server option. All we have is a segment DHCP

112
04:33.130 --> 04:34.640
server. And that's it.

113
04:34.640 --> 04:38.110
So we'll go ahead and leave that choice there. And then for the profile from

114
04:38.110 --> 04:38.880
the drop down,

115
04:38.880 --> 04:43.490
we'll go ahead and choose our profile, which is our NSX DHCP server profile.

116
04:43.490 --> 04:44.160
And using an IP

117
04:44.160 --> 04:49.280
address of 6783 with a slash 29 bit mask for the logical DHCP server. So we'll

118
04:49.280 --> 04:49.920
select that.

119
04:49.920 --> 04:53.680
And then we get to put in all the details. So our focus in the skill is on DHCP

120
04:53.680 --> 04:54.960
services for IPv4.

121
04:54.960 --> 04:59.200
So with the IPv4 server tab selected here, the very first thing we want to do

122
04:59.200 --> 04:59.920
is enable it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:00.560 --> 05:05.280
By default is disabled. So we'll go ahead and enable DHCP configuration. And

124
05:05.280 --> 05:05.600
then next,

125
05:05.600 --> 05:08.960
I'd like to jump down here to DHCP ranges. We'll come back to the DHCP server

126
05:08.960 --> 05:09.920
address here in just

127
05:09.920 --> 05:15.550
a moment. So for DHCP ranges, based on our plan, we're going to use 10 dot 30

128
05:15.550 --> 05:17.360
dot 0 dot 151

129
05:17.360 --> 05:22.950
through 10 dot 30 dot 0 dot 200. And let's take a look at our plan just to

130
05:22.950 --> 05:24.400
confirm. So based on

131
05:24.400 --> 05:29.170
our plan, we want to go 150 through 200 for segment 30. Fantastic. And then for

132
05:29.170 --> 05:30.000
the IPv4 gateway,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
05:30.000 --> 05:32.560
it's not going to hand one out. That's partly because when we set the segment,

134
05:32.560 --> 05:33.520
we didn't specify any

135
05:33.520 --> 05:36.850
IP addressing information for the segment. And then for the least time, I'm

136
05:36.850 --> 05:38.320
going to go ahead and set

137
05:38.320 --> 05:42.460
this to 500 seconds, which is extremely low. However, in a lab environment

138
05:42.460 --> 05:43.440
where things are

139
05:43.440 --> 05:47.030
fairly fluid, like to have a shorter lifetime and the clients will go ahead and

140
05:47.030 --> 05:48.080
renew as often as

141
05:48.080 --> 05:51.960
they need to. And then for the DNS server, because this segment doesn't go

142
05:51.960 --> 05:52.960
anywhere, I'm not even

143
05:52.960 --> 05:56.100
going to hand out a DNS server for them to use. Although we could, I'm not

144
05:56.100 --> 05:57.360
going to because they

145
05:57.360 --> 06:00.680
can't reach anything off their local network anyway. So now let me chat with
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:57.360 --> 06:00.680
can't reach anything off their local network anyway. So now let me chat with

146
06:00.680 --> 06:02.160
you about the DHCP

147
06:02.160 --> 06:06.200
server address. Think of this like, what do you want your clients, your DHCP

148
06:06.200 --> 06:07.040
clients on this

149
06:07.040 --> 06:11.750
subnet to believe their DHCP server address is? So if the clients are getting

150
06:11.750 --> 06:13.040
IP addresses of 10

151
06:13.040 --> 06:17.340
30 0, 151 through 200, we'd want to pick some IP address that's available on

152
06:17.340 --> 06:18.240
that same subnet

153
06:18.240 --> 06:22.860
at 10 30 0. And that way, when clients need to renew the IP address or interact

154
06:22.860 --> 06:23.680
with the quote

155
06:23.680 --> 06:28.130
unquote DHCP server, they'll use whatever IP address we specify that DHCP

156
06:28.130 --> 06:30.000
server is reachable at. So
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
06:30.000 --> 06:34.490
for our purposes, let's say 10 dot 30 dot zero dot, let's use to how about that

158
06:34.490 --> 06:36.320
with a slash 24. So

159
06:36.320 --> 06:41.370
that way the clients will believe that their DHCP server is at 10 30 0 dot two.

160
06:41.370 --> 06:42.400
And that's what this

161
06:42.400 --> 06:45.900
part is used for right here, think of it like a fake out for the clients so

162
06:45.900 --> 06:46.880
they can think that

163
06:46.880 --> 06:51.700
their local DHCP server is right there on that same subnet at 10 30 0 dot two,

164
06:51.700 --> 06:52.800
although behind the

165
06:52.800 --> 06:58.400
scenes, these DHCP services are being provided for by edge notes. All right, so

166
06:58.400 --> 06:59.120
with that in place,

167
06:59.120 --> 07:03.140
we'll click on apply, and we'll scroll down and we'll click on save, and then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
06:59.120 --> 07:03.140
we'll click on apply, and we'll scroll down and we'll click on save, and then

168
07:03.140 --> 07:04.480
we'll click on close.

169
07:04.480 --> 07:07.520
And then right here, under network hearing and segments, you give us an option

170
07:07.520 --> 07:08.240
for looking at the

171
07:08.240 --> 07:12.290
details for the DHCP config right here. So for segment 30, we can click here

172
07:12.290 --> 07:12.800
just to confirm

173
07:12.800 --> 07:17.730
our settings. So a virtual IP address of 10 30 0 2, which will be the logical

174
07:17.730 --> 07:18.560
DHCP service

175
07:18.560 --> 07:22.450
function for that local segment, the range of addresses, the lease time, and we

176
07:22.450 --> 07:22.880
're not going to be

177
07:22.880 --> 07:26.820
handing out an IPV for default gateway, nor a DNS server, based on how we just

178
07:26.820 --> 07:27.920
configured it.

179
07:27.920 --> 07:31.570
All right, so we'll close that. And then if we click here on network topology,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

179
07:27.920 --> 07:31.570
All right, so we'll close that. And then if we click here on network topology,

180
07:31.570 --> 07:32.080
that'll also help

181
07:32.080 --> 07:35.970
reinforce where we're at. So let me go ahead and zoom in on this part right

182
07:35.970 --> 07:37.680
here, here's segment 30.

183
07:37.680 --> 07:41.920
And for the service, if we hover over that, it is DHCP services specifically

184
07:41.920 --> 07:44.320
segment DHCP services

185
07:44.320 --> 07:49.120
because we don't have a gateway, our DHCP service enabled on this segment. So

186
07:49.120 --> 07:49.920
the only option we

187
07:49.920 --> 07:55.090
had with a standalone segment like this for DHCP from NSX is the segment based

188
07:55.090 --> 07:55.920
DHCP server. Once

189
07:55.920 --> 07:59.780
again, because it's not connected to one of our gateways, we don't have the

190
07:59.780 --> 08:01.280
option of doing a relay
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

190
07:59.780 --> 08:01.280
option of doing a relay

191
08:01.280 --> 08:05.410
up to some other external DHCP server. And we don't have an option of using a

192
08:05.410 --> 08:06.720
gateway based DHCP

193
08:06.720 --> 08:11.200
server, because once again, this segment is not connected to a gateway. So now

194
08:11.200 --> 08:12.160
that we have a

195
08:12.160 --> 08:16.320
beautiful, beautiful segment 30, we've also enabled segment based DHCP services

196
08:16.320 --> 08:17.280
for that segment.

197
08:17.280 --> 08:22.080
In the next video, let's test it out and verify that it works.