So for DHCP services, for this segment,
let's go ahead and set up DHCP relay so that as clients come online,
if they want to get an IP address signed dynamically,
our gateways can take that request and forward it up to a DHCP server.
With the tier one, gateways acting as a relay.
Now I have a DHCP server at this address,
10.21.0.1 on VLAN 21, but currently,
the topology doesn't have any access to VLAN 21.
So to reach this little DHCP server here on VLAN 21 at this address,
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
let's create a little external network segment here at site one for VLAN 21.
There'll be a VLAN-backed external segment,
and then we'll create an interface using, let's just use edge one.
So there'll be site one, edge one, VLAN 21, and for the IP address, let's use .
61.
So we'll create this interface to connect to this external network,
and that's where my DHCP server is living right there at 10.21.0.1.
So if we have DHCP relay enabled here and a client boots up into the discover,
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
that relay agent will forward it through the network up to this DHCP server.
And when that discover message is forwarded up to the server,
it's going to indicate what network it came from,
including using the source address off of the 10 network.
So T1 here has the address of 10.10.0.1.
So using as part of the message that's forwarded to the DHCP server,
it can identify, oh, this came from the 10.10 network.
I'll look and see whether or not I have IP addressing associated with the 10.10
network.
And if so, it can relay the offer back through the gateway,
who will then forward it back to the client.
And that's how the discover offer request acknowledgement process WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's how the discover offer request acknowledgement process
goes back and forth between a VM or a client that wants an IP address
dynamically,
and the DHCP server that's not also on that local subnet
by leveraging the DHCP relay function.
And for a deeper dive into DHCP relay,
please feel free to check out our separate skill dedicated to DHCP in an NSX
environment
where we walk through that step by step.
So to make this happen in our topology,
let's create the external VLAN 21 segment.
We'll create this logical interface on our T0 gateway to reach it.
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
And then we'll enable NSX for DHCP relay so those messages can be forwarded.
So here at the NSX global manager, we'll go to segments.
And let's create a new segment.
So we'll click on add segment.
So for this segment, we'll go ahead and name it site one
because that's where it's going to be.
EXT to remind me it's an extra segment, and I'll put V21.
And then for the location, we'll specify this for site one.
And for the transport zone, it picked up the default VLAN transport zone.
But if we wanted to use a different one from the dropdown,
we could choose a different transport zone if we wanted to.
Under these one, we currently have set as the default. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Under these one, we currently have set as the default.
And then over here for VLAN, I'll put in VLAN 21.
And then we'll scroll down and click on save.
All right, so there is our new external segment.
And we can also do a similar treatment over at site two with whatever VLAN
we're using to reach the DHCP server over there as well.
And for fault tolerance in a production environment,
we'd probably want the ability when needed to reach a DHCP server at either
site.
So for the demo, I'm going to use this one external network segment at site one
only,
just for brevity. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just for brevity.
And now that we have that created, let's go back to our tier zero gateway
and provide some connectivity over there.
So with tier zero gateway select on the left,
here's our existing stretch tier zero gateway.
If we open it up, it currently has four interfaces.
There's two at site one and two at site two.
And what we're going to do is we're going to click on edit to edit the details
for our tier zero gateway, go back down to the interfaces, click on set,
and we're going to add one more.
So we'll click on add interface.
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
Let's call this S1 short for site one, E1, because we use edge one for this.
And this is going to be for VLAN 21.
So I'll put that in the notes there.
And then it's going to be dot 61.
And for the location, this is going to be at site one.
And for the IP address, let's use 10 dot 21 dot zero dot and let's use 61
with a 24-bit mask.
And this is going to be connected to segment site one external V 21, just like
that.
And then for the edge node, we want to use, let's just use edge one.
So we could also set up some fault tolerance with additional edge nodes.
However, for the demo, excuse a single logical interface connected through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
However, for the demo, excuse a single logical interface connected through the
T zero gateway
to that external segment.
So we'll scroll down, click on save.
And just as a sanity check, let's go back to edge one.
And let's just verify that we can ping 10, 21, 0 dot 1, which is my DHCP server
.
So back to edge one, we go.
We'll type in get gateways to verify what the VRF is.
So there's our services router.
It's still VRF 13.
So we'll type in VRF 13 to go into that VRF.
Let's do a get route.
And we should have a directly connected network of 10 dot 21. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we should have a directly connected network of 10 dot 21.
There it is right there.
Fantastic.
We could also use the command get forwarding to verify that we have that
directly connected network.
Fantastic.
We do.
And let's go ahead and do a ping over to 10 dot 21 dot 0 dot 1.
That's my DHCP server.
Just to verify that we have connectivity and that it's up and those both look
good.
And also let me share with you the details for that DHCP server because I also
want to
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
verify it has a pool of addresses it can hand out on the 10 10 zero network
space.
So here is that device right there.
It happens to be a little virus router.
And let's do a show configuration and I want the format to be the commands
press enter.
And let me scroll down to the relevant DHCP section for us.
And that's this one right here.
So these five lines right here represent the DHCP services for the 10 10 zero
network.
So the default gateway it's going to hand out as 10 10 0 1.
The DNS server information is 888 the lease is going to be a thousand seconds.
And the range is from 151 all the way through 200. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the range is from 151 all the way through 200.
So if everything works correctly with our DHCP relay functionality, we should
get a
night address by our clients within that range.
All right, so we've verified connectivity after that network segment.
Let's click on close.
So I'm going to go ahead and I'm going to close my editing to make sure I don't
have
any edits left open.
I don't fantastic.
So back at the NSX global manager with the networking tab selected on the left
hand side
under settings will click on networking profiles.
And then furthermore, the main pane right here will click on the sub tab for
DHCP.
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
So we'll click on DHCP and there's the old DHCP server profiles that we had
previously.
We're not using those.
So I'm going to go ahead and delete them so they're no longer part of any
configuration
that we have regarding DHCP and with them both deleted.
Let me refresh that.
I know we have a nice fresh clean slate.
So let's click on add DHCP profile.
We're going to use DHCP relay.
So let's call this relay for site one because that's where we're going to use
it.
And for the profile type, we're going to do DHCP relay and the actual server is
at 10
dot 21 dot 0 dot 1.
We verified we could ping that already. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We verified we could ping that already.
So that's great news and we'll click on safe.
All right, so there's our DHCP relay and let's go ahead and associate that with
our segment.
So let's go back to our segments.
We'll go down here to stretch segment 10.
We'll click on the three dots, click on edit and then we'll go over to the DHCP
section
and click here on set DHCP config.
Here we'll specify DHCP relay and that's asking for the profile.
So we'll go ahead and choose the profile that we just made the relay for site
one, which
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
is pointing to that server at 10 21 0 1 and we'll click on apply.
Then we'll scroll down and we'll click on safe and then we'll close editing.
Now one of the telltale signs that indicates that you have DHCP services set up
is that
here in these subnets column, if this is a hyperlink where you can click on it,
that
indicates that DHCP services are enabled.
So if we click on this hyperlink, it takes us here and shows us the DHCP config
.
For example, if we went back in just for a moment and did edit and then here we
clicked
on delete DHCP config and got rid of it and then we scrolled down and saved it
and we
closed that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
closed that.
Click it out.
Now that 10 10 0 1 is just the IP address associated on that interface for this
common
segment.
However, it's not a hyperlink.
So that's the telltale sign that DHCP services are not set up.
So let's go back in, click on three dots, click on edit, click on set DHCP
config.
Once again, say we want to use a DHCP relay for that segment and then we'll
specify the
profile we want to use and then click on apply, click on save, close editing
and now we have
that hyperlink right there, which would take us to the DHCP configuration.
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
So if we look at our game plan, we are at this point right here where we could
just say,
well, I hope it works or better yet we could go in and verify that it is
working.
And that's exactly what you and I get to do in the next video.
So I'll see you there in just a moment.