WEBVTT

1
00:00.000 --> 00:03.360
So for DHCP services, for this segment,

2
00:03.360 --> 00:07.360
let's go ahead and set up DHCP relay so that as clients come online,

3
00:07.360 --> 00:09.480
if they want to get an IP address signed dynamically,

4
00:09.480 --> 00:13.580
our gateways can take that request and forward it up to a DHCP server.

5
00:13.580 --> 00:15.940
With the tier one, gateways acting as a relay.

6
00:15.940 --> 00:18.440
Now I have a DHCP server at this address,

7
00:18.440 --> 00:21.600
10.21.0.1 on VLAN 21, but currently,

8
00:21.600 --> 00:24.320
the topology doesn't have any access to VLAN 21.

9
00:24.320 --> 00:28.900
So to reach this little DHCP server here on VLAN 21 at this address,

10
00:28.900 --> 00:32.960
let's create a little external network segment here at site one for VLAN 21.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.900 --> 00:32.960
let's create a little external network segment here at site one for VLAN 21.

11
00:32.960 --> 00:35.000
There'll be a VLAN-backed external segment,

12
00:35.000 --> 00:38.320
and then we'll create an interface using, let's just use edge one.

13
00:38.320 --> 00:43.520
So there'll be site one, edge one, VLAN 21, and for the IP address, let's use .

14
00:43.520 --> 00:44.120
61.

15
00:44.120 --> 00:47.240
So we'll create this interface to connect to this external network,

16
00:47.240 --> 00:52.040
and that's where my DHCP server is living right there at 10.21.0.1.

17
00:52.040 --> 00:57.240
So if we have DHCP relay enabled here and a client boots up into the discover,

18
00:57.240 --> 01:01.260
that relay agent will forward it through the network up to this DHCP server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:57.240 --> 01:01.260
that relay agent will forward it through the network up to this DHCP server.

19
01:01.260 --> 01:03.840
And when that discover message is forwarded up to the server,

20
01:03.840 --> 01:05.940
it's going to indicate what network it came from,

21
01:05.940 --> 01:08.980
including using the source address off of the 10 network.

22
01:08.980 --> 01:12.900
So T1 here has the address of 10.10.0.1.

23
01:12.900 --> 01:16.260
So using as part of the message that's forwarded to the DHCP server,

24
01:16.260 --> 01:18.900
it can identify, oh, this came from the 10.10 network.

25
01:18.900 --> 01:22.670
I'll look and see whether or not I have IP addressing associated with the 10.10

26
01:22.670 --> 01:22.940
network.

27
01:22.940 --> 01:25.980
And if so, it can relay the offer back through the gateway,

28
01:25.980 --> 01:27.740
who will then forward it back to the client.

29
01:27.740 --> 01:30.680
And that's how the discover offer request acknowledgement process
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:27.740 --> 01:30.680
And that's how the discover offer request acknowledgement process

30
01:30.680 --> 01:34.350
goes back and forth between a VM or a client that wants an IP address

31
01:34.350 --> 01:35.080
dynamically,

32
01:35.080 --> 01:38.520
and the DHCP server that's not also on that local subnet

33
01:38.520 --> 01:40.500
by leveraging the DHCP relay function.

34
01:40.500 --> 01:42.920
And for a deeper dive into DHCP relay,

35
01:42.920 --> 01:47.460
please feel free to check out our separate skill dedicated to DHCP in an NSX

36
01:47.460 --> 01:48.000
environment

37
01:48.000 --> 01:49.740
where we walk through that step by step.

38
01:49.740 --> 01:51.920
So to make this happen in our topology,

39
01:51.920 --> 01:54.240
let's create the external VLAN 21 segment.

40
01:54.240 --> 01:57.640
We'll create this logical interface on our T0 gateway to reach it.

41
01:57.640 --> 02:02.280
And then we'll enable NSX for DHCP relay so those messages can be forwarded.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:57.640 --> 02:02.280
And then we'll enable NSX for DHCP relay so those messages can be forwarded.

42
02:02.280 --> 02:05.740
So here at the NSX global manager, we'll go to segments.

43
02:05.740 --> 02:06.940
And let's create a new segment.

44
02:06.940 --> 02:08.520
So we'll click on add segment.

45
02:08.520 --> 02:11.120
So for this segment, we'll go ahead and name it site one

46
02:11.120 --> 02:12.520
because that's where it's going to be.

47
02:12.520 --> 02:16.860
EXT to remind me it's an extra segment, and I'll put V21.

48
02:16.860 --> 02:20.700
And then for the location, we'll specify this for site one.

49
02:20.700 --> 02:23.700
And for the transport zone, it picked up the default VLAN transport zone.

50
02:23.700 --> 02:26.200
But if we wanted to use a different one from the dropdown,

51
02:26.200 --> 02:29.640
we could choose a different transport zone if we wanted to.

52
02:29.640 --> 02:31.880
Under these one, we currently have set as the default.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:29.640 --> 02:31.880
Under these one, we currently have set as the default.

53
02:31.880 --> 02:35.140
And then over here for VLAN, I'll put in VLAN 21.

54
02:35.140 --> 02:37.580
And then we'll scroll down and click on save.

55
02:37.580 --> 02:40.280
All right, so there is our new external segment.

56
02:40.280 --> 02:44.720
And we can also do a similar treatment over at site two with whatever VLAN

57
02:44.720 --> 02:47.560
we're using to reach the DHCP server over there as well.

58
02:47.560 --> 02:49.360
And for fault tolerance in a production environment,

59
02:49.360 --> 02:54.230
we'd probably want the ability when needed to reach a DHCP server at either

60
02:54.230 --> 02:54.760
site.

61
02:54.760 --> 02:58.560
So for the demo, I'm going to use this one external network segment at site one

62
02:58.560 --> 02:58.960
only,

63
02:58.960 --> 03:00.260
just for brevity.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:58.960 --> 03:00.260
just for brevity.

64
03:00.260 --> 03:03.600
And now that we have that created, let's go back to our tier zero gateway

65
03:03.600 --> 03:05.640
and provide some connectivity over there.

66
03:05.640 --> 03:07.740
So with tier zero gateway select on the left,

67
03:07.740 --> 03:10.780
here's our existing stretch tier zero gateway.

68
03:10.780 --> 03:14.180
If we open it up, it currently has four interfaces.

69
03:14.180 --> 03:16.780
There's two at site one and two at site two.

70
03:16.780 --> 03:19.780
And what we're going to do is we're going to click on edit to edit the details

71
03:19.780 --> 03:23.980
for our tier zero gateway, go back down to the interfaces, click on set,

72
03:23.980 --> 03:25.380
and we're going to add one more.

73
03:25.380 --> 03:27.180
So we'll click on add interface.

74
03:27.180 --> 03:31.980
Let's call this S1 short for site one, E1, because we use edge one for this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:27.180 --> 03:31.980
Let's call this S1 short for site one, E1, because we use edge one for this.

75
03:31.980 --> 03:33.680
And this is going to be for VLAN 21.

76
03:33.680 --> 03:35.080
So I'll put that in the notes there.

77
03:35.080 --> 03:37.080
And then it's going to be dot 61.

78
03:37.080 --> 03:39.780
And for the location, this is going to be at site one.

79
03:39.780 --> 03:44.480
And for the IP address, let's use 10 dot 21 dot zero dot and let's use 61

80
03:44.480 --> 03:45.980
with a 24-bit mask.

81
03:45.980 --> 03:50.580
And this is going to be connected to segment site one external V 21, just like

82
03:50.580 --> 03:51.180
that.

83
03:51.180 --> 03:54.580
And then for the edge node, we want to use, let's just use edge one.

84
03:54.580 --> 03:57.480
So we could also set up some fault tolerance with additional edge nodes.

85
03:57.480 --> 04:01.720
However, for the demo, excuse a single logical interface connected through the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:57.480 --> 04:01.720
However, for the demo, excuse a single logical interface connected through the

86
04:01.720 --> 04:02.880
T zero gateway

87
04:02.880 --> 04:04.180
to that external segment.

88
04:04.180 --> 04:06.580
So we'll scroll down, click on save.

89
04:06.580 --> 04:10.980
And just as a sanity check, let's go back to edge one.

90
04:10.980 --> 04:16.630
And let's just verify that we can ping 10, 21, 0 dot 1, which is my DHCP server

91
04:16.630 --> 04:16.980
.

92
04:16.980 --> 04:18.780
So back to edge one, we go.

93
04:18.780 --> 04:22.380
We'll type in get gateways to verify what the VRF is.

94
04:22.380 --> 04:23.980
So there's our services router.

95
04:23.980 --> 04:25.180
It's still VRF 13.

96
04:25.180 --> 04:28.380
So we'll type in VRF 13 to go into that VRF.

97
04:28.380 --> 04:29.780
Let's do a get route.

98
04:29.780 --> 04:33.780
And we should have a directly connected network of 10 dot 21.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:29.780 --> 04:33.780
And we should have a directly connected network of 10 dot 21.

99
04:33.780 --> 04:34.780
There it is right there.

100
04:34.780 --> 04:35.780
Fantastic.

101
04:35.780 --> 04:39.380
We could also use the command get forwarding to verify that we have that

102
04:39.380 --> 04:40.780
directly connected network.

103
04:40.780 --> 04:41.780
Fantastic.

104
04:41.780 --> 04:42.780
We do.

105
04:42.780 --> 04:45.980
And let's go ahead and do a ping over to 10 dot 21 dot 0 dot 1.

106
04:45.980 --> 04:47.580
That's my DHCP server.

107
04:47.580 --> 04:51.580
Just to verify that we have connectivity and that it's up and those both look

108
04:51.580 --> 04:52.380
good.

109
04:52.380 --> 04:57.390
And also let me share with you the details for that DHCP server because I also

110
04:57.390 --> 04:57.580
want to

111
04:57.580 --> 05:02.290
verify it has a pool of addresses it can hand out on the 10 10 zero network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:57.580 --> 05:02.290
verify it has a pool of addresses it can hand out on the 10 10 zero network

112
05:02.290 --> 05:02.940
space.

113
05:02.940 --> 05:04.660
So here is that device right there.

114
05:04.660 --> 05:06.580
It happens to be a little virus router.

115
05:06.580 --> 05:10.640
And let's do a show configuration and I want the format to be the commands

116
05:10.640 --> 05:11.180
press enter.

117
05:11.180 --> 05:14.680
And let me scroll down to the relevant DHCP section for us.

118
05:14.680 --> 05:15.980
And that's this one right here.

119
05:15.980 --> 05:20.550
So these five lines right here represent the DHCP services for the 10 10 zero

120
05:20.550 --> 05:21.020
network.

121
05:21.020 --> 05:24.060
So the default gateway it's going to hand out as 10 10 0 1.

122
05:24.060 --> 05:28.100
The DNS server information is 888 the lease is going to be a thousand seconds.

123
05:28.100 --> 05:31.140
And the range is from 151 all the way through 200.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:28.100 --> 05:31.140
And the range is from 151 all the way through 200.

124
05:31.140 --> 05:34.420
So if everything works correctly with our DHCP relay functionality, we should

125
05:34.420 --> 05:34.540
get a

126
05:34.540 --> 05:37.100
night address by our clients within that range.

127
05:37.100 --> 05:39.580
All right, so we've verified connectivity after that network segment.

128
05:39.580 --> 05:40.900
Let's click on close.

129
05:40.900 --> 05:43.940
So I'm going to go ahead and I'm going to close my editing to make sure I don't

130
05:43.940 --> 05:44.020
have

131
05:44.020 --> 05:45.300
any edits left open.

132
05:45.300 --> 05:46.860
I don't fantastic.

133
05:46.860 --> 05:51.010
So back at the NSX global manager with the networking tab selected on the left

134
05:51.010 --> 05:51.620
hand side

135
05:51.620 --> 05:54.220
under settings will click on networking profiles.

136
05:54.220 --> 05:58.280
And then furthermore, the main pane right here will click on the sub tab for

137
05:58.280 --> 05:58.820
DHCP.

138
05:58.820 --> 06:03.090
So we'll click on DHCP and there's the old DHCP server profiles that we had
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
05:58.820 --> 06:03.090
So we'll click on DHCP and there's the old DHCP server profiles that we had

139
06:03.090 --> 06:04.020
previously.

140
06:04.020 --> 06:05.020
We're not using those.

141
06:05.020 --> 06:08.500
So I'm going to go ahead and delete them so they're no longer part of any

142
06:08.500 --> 06:09.300
configuration

143
06:09.300 --> 06:12.500
that we have regarding DHCP and with them both deleted.

144
06:12.500 --> 06:13.500
Let me refresh that.

145
06:13.500 --> 06:15.180
I know we have a nice fresh clean slate.

146
06:15.180 --> 06:17.620
So let's click on add DHCP profile.

147
06:17.620 --> 06:18.980
We're going to use DHCP relay.

148
06:18.980 --> 06:22.600
So let's call this relay for site one because that's where we're going to use

149
06:22.600 --> 06:22.940
it.

150
06:22.940 --> 06:27.310
And for the profile type, we're going to do DHCP relay and the actual server is

151
06:27.310 --> 06:27.900
at 10

152
06:27.900 --> 06:29.380
dot 21 dot 0 dot 1.

153
06:29.380 --> 06:30.780
We verified we could ping that already.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
06:29.380 --> 06:30.780
We verified we could ping that already.

154
06:30.780 --> 06:33.420
So that's great news and we'll click on safe.

155
06:33.420 --> 06:37.080
All right, so there's our DHCP relay and let's go ahead and associate that with

156
06:37.080 --> 06:38.180
our segment.

157
06:38.180 --> 06:39.660
So let's go back to our segments.

158
06:39.660 --> 06:42.100
We'll go down here to stretch segment 10.

159
06:42.100 --> 06:46.020
We'll click on the three dots, click on edit and then we'll go over to the DHCP

160
06:46.020 --> 06:46.540
section

161
06:46.540 --> 06:49.780
and click here on set DHCP config.

162
06:49.780 --> 06:53.940
Here we'll specify DHCP relay and that's asking for the profile.

163
06:53.940 --> 06:57.940
So we'll go ahead and choose the profile that we just made the relay for site

164
06:57.940 --> 06:58.100
one, which

165
06:58.100 --> 07:01.900
is pointing to that server at 10 21 0 1 and we'll click on apply.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
06:58.100 --> 07:01.900
is pointing to that server at 10 21 0 1 and we'll click on apply.

166
07:01.900 --> 07:06.140
Then we'll scroll down and we'll click on safe and then we'll close editing.

167
07:06.140 --> 07:09.390
Now one of the telltale signs that indicates that you have DHCP services set up

168
07:09.390 --> 07:09.740
is that

169
07:09.740 --> 07:15.300
here in these subnets column, if this is a hyperlink where you can click on it,

170
07:15.300 --> 07:15.300
that

171
07:15.300 --> 07:17.380
indicates that DHCP services are enabled.

172
07:17.380 --> 07:20.910
So if we click on this hyperlink, it takes us here and shows us the DHCP config

173
07:20.910 --> 07:21.140
.

174
07:21.140 --> 07:24.640
For example, if we went back in just for a moment and did edit and then here we

175
07:24.640 --> 07:25.140
clicked

176
07:25.140 --> 07:29.820
on delete DHCP config and got rid of it and then we scrolled down and saved it

177
07:29.820 --> 07:29.980
and we

178
07:29.980 --> 07:30.980
closed that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
07:29.980 --> 07:30.980
closed that.

179
07:30.980 --> 07:31.980
Click it out.

180
07:31.980 --> 07:36.100
Now that 10 10 0 1 is just the IP address associated on that interface for this

181
07:36.100 --> 07:36.540
common

182
07:36.540 --> 07:37.540
segment.

183
07:37.540 --> 07:38.540
However, it's not a hyperlink.

184
07:38.540 --> 07:41.300
So that's the telltale sign that DHCP services are not set up.

185
07:41.300 --> 07:45.360
So let's go back in, click on three dots, click on edit, click on set DHCP

186
07:45.360 --> 07:46.060
config.

187
07:46.060 --> 07:49.270
Once again, say we want to use a DHCP relay for that segment and then we'll

188
07:49.270 --> 07:49.860
specify the

189
07:49.860 --> 07:54.660
profile we want to use and then click on apply, click on save, close editing

190
07:54.660 --> 07:55.300
and now we have

191
07:55.300 --> 07:59.140
that hyperlink right there, which would take us to the DHCP configuration.

192
07:59.140 --> 08:01.770
So if we look at our game plan, we are at this point right here where we could
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

192
07:59.140 --> 08:01.770
So if we look at our game plan, we are at this point right here where we could

193
08:01.770 --> 08:02.220
just say,

194
08:02.220 --> 08:06.890
well, I hope it works or better yet we could go in and verify that it is

195
08:06.890 --> 08:07.820
working.

196
08:07.820 --> 08:10.980
And that's exactly what you and I get to do in the next video.

197
08:10.980 --> 08:12.820
So I'll see you there in just a moment.