WEBVTT

1
00:00.000 --> 00:03.890
So based on our game plan, we are going to go ahead and implement DHCP really

2
00:03.890 --> 00:07.000
services for the existing DHCP service

3
00:07.000 --> 00:11.000
that's currently running on my router here at 23.1.2.1.

4
00:11.000 --> 00:16.220
Now the reason I'm actually choosing to use this device as the DHCP server is

5
00:16.220 --> 00:18.000
because we already have our routing in place.

6
00:18.000 --> 00:23.000
We already have OSPF configured between our tier zero gateway and this device.

7
00:23.000 --> 00:25.000
We did that in a previous set of videos.

8
00:25.000 --> 00:28.360
And that means that when we have a client, for example, let's go ahead and put

9
00:28.360 --> 00:29.000
a new client here.

10
00:29.000 --> 00:33.000
When VM5 does a discover message, this gateway is going to see it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.000 --> 00:33.000
When VM5 does a discover message, this gateway is going to see it.

11
00:33.000 --> 00:36.440
It's going to encapsulate that discover message, forwarded it up to the IP

12
00:36.440 --> 00:38.000
address specified as the server.

13
00:38.000 --> 00:41.000
In this case, it's going to be 23.1.2.1.

14
00:41.000 --> 00:44.000
It'll be sourced from this IP address, 1010.0.1.

15
00:44.000 --> 00:48.280
At which point this device acting as a DHCP server can grab an IP address that

16
00:48.280 --> 00:52.000
's available from the appropriate pool for the 1010.0 subnet,

17
00:52.000 --> 00:55.000
forwarded back down to the relay, who can then forward it down to the client.

18
00:55.000 --> 00:58.680
So that discover, offer, request, acknowledgement process will go back and

19
00:58.680 --> 01:01.000
forth between the real DHCP server and the client
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.680 --> 01:01.000
forth between the real DHCP server and the client

20
01:01.000 --> 01:05.000
and the relay function on the gateway here in the case of segment 10.

21
01:05.000 --> 01:08.440
Or in the case of segment 20, it'd be gateway B, providing that middleman

22
01:08.440 --> 01:12.000
function between the real DHCP server up here and the clients down here.

23
01:12.000 --> 01:15.000
So that's our game plan for implementing DHCP relay.

24
01:15.000 --> 01:19.000
Now there are a couple of guidelines that we really should pay attention to

25
01:19.000 --> 01:21.000
before we just go in and start configuring.

26
01:21.000 --> 01:25.000
And one is some prereqs supplied by VMware.

27
01:25.000 --> 01:29.000
So here is the NSX admin guide for NSX 4.1.

28
01:29.000 --> 01:34.040
If we take a peek over here at DHCP, we'll click there and let's scroll down a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:29.000 --> 01:34.040
If we take a peek over here at DHCP, we'll click there and let's scroll down a

29
01:34.040 --> 01:35.000
few pages.

30
01:35.000 --> 01:38.000
So here in the admin guide for NSX, we're getting DHCP.

31
01:38.000 --> 01:42.000
It mentions the use of DHCP relay, which we're about to do.

32
01:42.000 --> 01:45.810
Also, setting up DHCP server for a segment and also setting up DHCP server

33
01:45.810 --> 01:47.000
based on gateways.

34
01:47.000 --> 01:51.310
And if we scroll down a little bit, I just want to share with you a couple of

35
01:51.310 --> 01:52.000
prereqs.

36
01:52.000 --> 01:55.000
So if we scroll down here, here's the one I want to share with you.

37
01:55.000 --> 01:58.950
And it's dating here that if we do have DHCP server or DHCP relay configured on

38
01:58.950 --> 02:04.200
a VLAN segment, on a virtual switch, we want to say accept or yes to allow for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:58.950 --> 02:04.200
a VLAN segment, on a virtual switch, we want to say accept or yes to allow for

39
02:04.200 --> 02:08.700
age transmits for NSX segments for virtual distributed switch 6.6 and later,

40
02:08.700 --> 02:12.000
which is our case, we want to enable Mac learning.

41
02:12.000 --> 02:16.000
So both those options are under the security section for our switch.

42
02:16.000 --> 02:19.960
So to enhance our chances for success, I'm going to enable both those features

43
02:19.960 --> 02:22.000
right now using the vSphere client.

44
02:22.000 --> 02:25.420
So here in the vSphere client, here's our distributed switch we're using as

45
02:25.420 --> 02:26.000
part of NSX.

46
02:26.000 --> 02:31.000
And we have a couple of overlay segments, seg 10 yellow, seg 10 pink.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:26.000 --> 02:31.000
And we have a couple of overlay segments, seg 10 yellow, seg 10 pink.

47
02:31.000 --> 02:34.210
And if we go to the summary tab here for each of those, it's also showing us

48
02:34.210 --> 02:37.000
the VNI number for each of those and the transport zone they're in.

49
02:37.000 --> 02:38.000
Fantastic.

50
02:38.000 --> 02:40.000
And then I have a couple of normal port groups.

51
02:40.000 --> 02:43.000
I've got one called DPG leads to VM NIC 3.

52
02:43.000 --> 02:45.000
I've got another one right here for VLAN 23.

53
02:45.000 --> 02:49.400
And what I want to do is I want to set the security for all the native port

54
02:49.400 --> 02:51.000
groups here on this distributed switch.

55
02:51.000 --> 02:54.000
And I want to make sure I'm allowing forage transmits.

56
02:54.000 --> 02:56.000
And I also want to enable Mac learning.

57
02:56.000 --> 02:58.590
So to do that, the most efficient way possible, I'm going to grab the switch

58
02:58.590 --> 03:02.000
itself, right click, and then click here on distributed port group.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:58.590 --> 03:02.000
itself, right click, and then click here on distributed port group.

59
03:02.000 --> 03:05.000
And then from the drop down, I'll click on manage, distributed port groups.

60
03:05.000 --> 03:07.520
That way, if you have 20 or 30 port groups, you can do them all at one fell

61
03:07.520 --> 03:08.000
swoop.

62
03:08.000 --> 03:11.000
So I'm going to go ahead and say, I want to modify just the security sections

63
03:11.000 --> 03:13.000
for each of those port groups.

64
03:13.000 --> 03:16.000
Click on next, give me a list of all the applicable port groups.

65
03:16.000 --> 03:17.000
These are the two here.

66
03:17.000 --> 03:19.000
I'll go ahead and select those, click on next.

67
03:19.000 --> 03:23.000
So here, the security section for forage transmits, I want to say accept.

68
03:23.000 --> 03:26.000
And then for Mac learning, I want to enable and that's it.

69
03:26.000 --> 03:29.000
So click on next and finish and that is done.

70
03:29.000 --> 03:32.000
We're now in good striking position for our future demos.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:29.000 --> 03:32.000
We're now in good striking position for our future demos.

71
03:32.000 --> 03:33.000
All right, let me minimize that.

72
03:33.000 --> 03:36.000
And let's go to the NSX manager.

73
03:36.000 --> 03:39.400
So up to this point in our previous videos, I had implemented some DHCP

74
03:39.400 --> 03:42.000
services just to make it quicker for clients to get IP addresses.

75
03:42.000 --> 03:46.250
But because I want to do all of this with you from scratch, let's go ahead and

76
03:46.250 --> 03:50.500
remove any current existing DHCP services that I might have had in place

77
03:50.500 --> 03:51.000
previously.

78
03:51.000 --> 03:54.480
So to do that, we're going to go to our segments and to get there, we're going

79
03:54.480 --> 03:57.000
to go to networking on top and on the left, we'll click on segments.

80
03:57.000 --> 04:00.200
And then for the yellow segment, we'll go ahead and click on the three dots,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:57.000 --> 04:00.200
And then for the yellow segment, we'll go ahead and click on the three dots,

81
04:00.200 --> 04:01.000
click on edit.

82
04:01.000 --> 04:04.620
Then right over here, we have options for editing the DHCP config or deleting

83
04:04.620 --> 04:05.000
it.

84
04:05.000 --> 04:09.990
I'm going to click on delete, click on delete again, scroll down, click on save

85
04:09.990 --> 04:11.000
, and click on close editing.

86
04:11.000 --> 04:14.000
And repeat that process for the 1020 network.

87
04:14.000 --> 04:17.420
So we'll click on the three dots, click on edit over on the right for segment

88
04:17.420 --> 04:18.000
20.

89
04:18.000 --> 04:22.980
I'm going to click on delete any DHCP config and delete again, scroll down,

90
04:22.980 --> 04:26.000
click on save, and then click on close editing.

91
04:26.000 --> 04:31.000
All right, so we have no DHCP services configured for segment 10 or segment 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:26.000 --> 04:31.000
All right, so we have no DHCP services configured for segment 10 or segment 20.

92
04:31.000 --> 04:34.270
And in addition, I'm going to go ahead and the left here with networking on the

93
04:34.270 --> 04:36.000
top selected on the left and scroll down.

94
04:36.000 --> 04:40.000
And under settings, I've got a section right here called networking profiles.

95
04:40.000 --> 04:43.000
So on the bottom left here, I'm going to click on networking profiles.

96
04:43.000 --> 04:46.000
And then on the top, I've got a sub tab right here for DHCP.

97
04:46.000 --> 04:50.260
And now that we're no longer using this DHCP server profile that I put in place

98
04:50.260 --> 04:54.240
beforehand for convenience because we're no longer using it on any of our

99
04:54.240 --> 04:57.540
segments, we're going to click on the three dots here, click on delete, and

100
04:57.540 --> 04:58.000
click on delete.

101
04:58.000 --> 05:00.000
And then I'm going to click on refresh.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:00.000 --> 05:05.000
And so right now we have absolutely no DHCP services whatsoever.

103
05:05.000 --> 05:09.510
So back at our game plan, we want to go ahead and have a DHCP relay and have

104
05:09.510 --> 05:11.000
these gateways forward.

105
05:11.000 --> 05:15.590
Any discover messages they see here on segment 10 or segment 20 and forward

106
05:15.590 --> 05:19.000
them up to my DHCP server up here at 23.1.2.1.

107
05:19.000 --> 05:23.260
So the first step in making that happen is we are going to configure a DHCP

108
05:23.260 --> 05:28.520
profile, a specific type of DHCP profile for relays, and specify what the IP

109
05:28.520 --> 05:31.000
address is of our actual DHCP server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
05:28.520 --> 05:31.000
address is of our actual DHCP server.

110
05:31.000 --> 05:34.000
So again, in my case, is at 23.1.2.1.

111
05:34.000 --> 05:39.270
Actually, before we do that, we also just take a moment and make sure that we

112
05:39.270 --> 05:42.000
can reach and ping that IP address.

113
05:42.000 --> 05:46.000
So we set that up in that external connectivity up in a previous skill.

114
05:46.000 --> 05:50.000
As one of verify we have reachability to that IP address 23.1.2.1.

115
05:50.000 --> 05:53.490
I also want to verify that this router currently does have the configuration to

116
05:53.490 --> 05:58.000
support the subnets for 10, 10, and 10, 20 from a DHCP server perspective.

117
05:58.000 --> 06:02.000
So let's do a quick check of connectivity and the pools right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:58.000 --> 06:02.000
So let's do a quick check of connectivity and the pools right now.

118
06:02.000 --> 06:04.000
So let's go ahead and do it from edge one.

119
06:04.000 --> 06:08.000
If we do a get gateways and press enter, they'll show us our gateways.

120
06:08.000 --> 06:11.000
So let's go to our services router right here, which is VRF number two.

121
06:11.000 --> 06:13.000
So we'll type in VRF two.

122
06:13.000 --> 06:16.000
Another we're in the room effectively for VRF two.

123
06:16.000 --> 06:19.000
Let's do a get forwarding and we scroll up.

124
06:19.000 --> 06:21.650
So I have a whole bunch of IP addresses that we're using for the benefit of

125
06:21.650 --> 06:23.000
network address translation.

126
06:23.000 --> 06:28.000
And there is our default route and the next top is 23.1.2.1.

127
06:28.000 --> 06:30.000
So we should be able to ping that IP address as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:30.000 --> 06:35.000
So here in VRF two, let's do a ping to 23.1.2.1.

129
06:35.000 --> 06:37.000
Just to verify our connectivity.

130
06:37.000 --> 06:38.000
Fantastic.

131
06:38.000 --> 06:40.000
I'll do a control C to stop that.

132
06:40.000 --> 06:43.160
And now that we've verified that we have that connectivity to that IP address,

133
06:43.160 --> 06:47.000
let's also verify the DHCP services on that gateway.

134
06:47.000 --> 06:50.000
So here we are at the console for this gateway slash firewall.

135
06:50.000 --> 06:54.420
And to verify that we have DHCP services set up on it, I'm going to do a show

136
06:54.420 --> 06:55.000
configuration space.

137
06:55.000 --> 06:57.000
And let's make it easy to look at.

138
06:57.000 --> 07:01.000
Let's do a commands and I'll hit space bar a few times to go to the end.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
06:57.000 --> 07:01.000
Let's do a commands and I'll hit space bar a few times to go to the end.

139
07:01.000 --> 07:03.000
And let's scroll up a little bit.

140
07:03.000 --> 07:09.000
And I'm looking for DHCP services for the 10, 10 and the 10, 20 networks.

141
07:09.000 --> 07:13.120
So the highlighted part right here and the colors is because of secure CRT and

142
07:13.120 --> 07:14.000
the color scheme I'm using.

143
07:14.000 --> 07:17.000
But the actual output is what we're focused on.

144
07:17.000 --> 07:22.280
So these five lines here are DHCP services for the 10, 10, zero network with a

145
07:22.280 --> 07:28.510
range of 151 all the way through 200 and a default gateway of 10, 10, 01 and a

146
07:28.510 --> 07:30.000
DNS server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

147
07:30.000 --> 07:32.000
And these next five lines right here.

148
07:32.000 --> 07:36.000
These are the configurations for DHCP services for subnet 20 with their

149
07:36.000 --> 07:40.210
respective default gateway address, a DNS server they can use and the range of

150
07:40.210 --> 07:42.000
151 through 200.

151
07:42.000 --> 07:46.000
So our next step is to create a DHCP relay profile.

152
07:46.000 --> 07:47.000
And it's pretty simple.

153
07:47.000 --> 07:51.000
It basically says this is the server at 23.1.2.1.

154
07:51.000 --> 07:54.000
So let's create that DHCP relay profile right now.

155
07:54.000 --> 07:57.500
So to do that here in the NSX manager will click on the networking tab right

156
07:57.500 --> 07:58.000
here.

157
07:58.000 --> 08:01.000
And then on the left, we'll scroll all the way down and under settings.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:58.000 --> 08:01.000
And then on the left, we'll scroll all the way down and under settings.

158
08:01.000 --> 08:03.000
We have a section called network profiles.

159
08:03.000 --> 08:07.930
And I've also noticed that over various iterations of NSX, including four dot

160
08:07.930 --> 08:09.000
zero and four dot one.

161
08:09.000 --> 08:12.000
Sometimes they move things around a little bit.

162
08:12.000 --> 08:15.920
So as of four dot one, which is what we're using right now, if we have network

163
08:15.920 --> 08:21.340
profile selected, then this main section here, we have a sub tab right here for

164
08:21.340 --> 08:22.000
DHCP.

165
08:22.000 --> 08:25.000
And this is where we can configure our DHCP profile.

166
08:25.000 --> 08:30.000
So this is the same place we go to create a server profile or a relay profile.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
08:30.000 --> 08:35.000
So we'll click on DHCP, click right here and add DHCP profile.

168
08:35.000 --> 08:40.000
And then we'll give it a name, let's call it our relay at 23.1.2.1.

169
08:40.000 --> 08:42.000
Just the way I see it, I'll remember where it is.

170
08:42.000 --> 08:46.000
And then the profile type is going to be a DHCP relay.

171
08:46.000 --> 08:48.000
So we'll choose DHCP relay right there.

172
08:48.000 --> 08:52.310
And then it wants to know what is the IP address of your DHCP server that you

173
08:52.310 --> 08:55.000
want the gateways to forward these DHCP messages to.

174
08:55.000 --> 08:58.000
And our server is at 23.1.2.1.

175
08:58.000 --> 08:59.000
And that's it.

176
08:59.000 --> 09:00.000
So that looks good.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
09:00.000 --> 09:01.000
And we'll click on save.

178
09:01.000 --> 09:07.010
And there is our relay profile called our relay at 23.1.2.1, which if we use

179
09:07.010 --> 09:12.000
that profile, it'll mean the server we want to forward packets to is 23.1.2.1.

180
09:12.000 --> 09:17.360
So now that we have the DHCP relay profile configured, now it exists, how do we

181
09:17.360 --> 09:22.560
actually train and a [garbled] that for clients down here on segment 10, that they

182
09:22.560 --> 09:25.000
should have their DHCP messages relayed up to that server.

183
09:25.000 --> 09:32.240
And the same thing for segment 20. And the answer is we're going to go to these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
09:25.000 --> 09:32.240
And the same thing for segment 20. And the answer is we're going to go to these

184
09:32.240 --> 09:33.000
segments themselves and specify that we want to use this DHCP relay profile.

185
09:33.000 --> 09:37.000
And that's going to effectively train gateway A and gateway B that, oh, you

186
09:37.000 --> 09:37.000
know what?

187
09:37.000 --> 09:41.850
If I see these DHCP discover messages, I'm going to go ahead and encapsulate

188
09:41.850 --> 09:47.150
them using my source IP address on the respective 10 network and route that

189
09:47.150 --> 09:49.000
packet up to the DHCP server.

190
09:49.000 --> 09:53.000
And then the DHCP server can go ahead and respond back with an offer.

191
09:53.000 --> 09:58.040
So let's go ahead and configure segment 10 and segment 20 to use the DHCP relay

192
09:58.040 --> 10:00.000
profile that we just created.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
10:00.000 --> 10:03.560
So back in the NSX manager, one scan will go to networking and then on the left

194
10:03.560 --> 10:06.000
under connectivity, we'll click on segments.

195
10:06.000 --> 10:10.430
So here is segment 10 and segment 20. Let's go ahead and configure segment 10

196
10:10.430 --> 10:11.000
first.

197
10:11.000 --> 10:15.000
So we'll click on the three dots next to segment 10 and click on edit.

198
10:15.000 --> 10:19.830
And then here on the far right where we deleted any existing DHCP configuration

199
10:19.830 --> 10:23.000
, a few moments ago, we'll click right here to set DHCP config.

200
10:23.000 --> 10:27.100
And the first thing is asking us right here at the top on the top left is which

201
10:27.100 --> 10:28.000
type of DHCP.

202
10:28.000 --> 10:31.000
Do you want this to be a DHCP relay? The answer is yes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
10:28.000 --> 10:31.000
Do you want this to be a DHCP relay? The answer is yes.

203
10:31.000 --> 10:35.930
Or do you want to use a segment DHCP server? Or do you want to use a gateway

204
10:35.930 --> 10:37.000
DHCP server?

205
10:37.000 --> 10:39.000
So for this demo, we want a DHCP relay.

206
10:39.000 --> 10:42.570
You'll notice there's not a whole bunch of choices down here, but we do have an

207
10:42.570 --> 10:45.000
option right here to choose a specific profile.

208
10:45.000 --> 10:48.350
So we'll click here for DHCP profile and then select the profile we made just a

209
10:48.350 --> 10:49.000
moment ago.

210
10:49.000 --> 10:53.000
So we're going to specify our relay at 23.1.2.1 by selecting it.

211
10:53.000 --> 10:56.700
And that's it. And we'll click on apply. And then we'll scroll down a little

212
10:56.700 --> 10:58.000
bit, click on save.

213
10:58.000 --> 11:01.210
And then we'll click here on close editing. And that concludes our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

213
10:58.000 --> 11:01.210
And then we'll click here on close editing. And that concludes our

214
11:01.210 --> 11:04.000
configuration of DHCP relay for segment 10.

215
11:04.000 --> 11:08.460
We'll repeat that here for segment 20 by clicking on the three dots, clicking

216
11:08.460 --> 11:09.000
on edit.

217
11:09.000 --> 11:12.000
And then over here on the right, click on set DHCP config.

218
11:12.000 --> 11:17.000
So here we also want segment 20 to go ahead and have DHCP relay services.

219
11:17.000 --> 11:20.680
And we'll point to the same profile, which effectively points to the server at

220
11:20.680 --> 11:22.000
23.1.2.1.

221
11:22.000 --> 11:26.000
And we'll click on apply. And then we'll scroll down and we'll click on save.

222
11:26.000 --> 11:29.260
And it'll scroll down and click on close editing. And so now that we have

223
11:29.260 --> 11:33.000
configured DHCP relay services for segment 10 and segment 20,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

223
11:29.260 --> 11:33.000
configured DHCP relay services for segment 10 and segment 20,

224
11:33.000 --> 11:37.720
we also verified basic connectivity up to our device at .1 on the 23.1.2

225
11:37.720 --> 11:40.000
network, which is acting as our DHCP server.

226
11:40.000 --> 11:44.000
We can either assume that it works or we can test it.

227
11:44.000 --> 11:48.000
And that's exactly what we're going to do, the testing part in the next video.

228
11:48.000 --> 11:50.000
So I'll see you there in just a moment.

229
11:50.000 --> 12:00.000
[BLANK_AUDIO]