Because these two segment tray are segment 10 on the left and segment 20 right
here on the right because they both have a gateway connected to those segments.
We have effectively the option of using any one of our three DHP services
option.
We could set up DHP relay, which we did a couple videos ago.
We could set up segment based DHP services on a segment by segment basis or
because we have the gateways connected.
We now also have a third option and that is gateway based DHP services.
And to implement gateway based DHP services, we're going to start off with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And to implement gateway based DHP services, we're going to start off with
network segments which are connected to gateways which we currently have.
We're going to use a DHP server profile, which we already have in place, one
that points to a server, a logical NSX based DHP server at 673.
And then we'll simply use that DHP server for handing out IP addresses to these
segments.
So from a client's perspective on these networks, it looks like there's a local
DHP server.
One interesting thing, which will also confirm what they protocol analyzer is
that when we set up gateway DHP services, it acts and feels a lot like DHP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that when we set up gateway DHP services, it acts and feels a lot like DHP
relay because we're creating or pointing to this logical DHP server.
And if we look at the traffic, the traffic is going to look like it sourced
from the router interface, the gateway interface connected to the segment being
forwarded over that virtual IP address where this logical DHP server lives.
And how this differs from the DHP relay is that with DHP relay, we were
pointing to an existing external DHP server, where in this case, we're just
using a logical DHP server inside of our NSX architecture. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And from a protocol analysis perspective, it's going to look and feel a lot
like these gateways acting as DHP relays forwarding their request for DHP
services to this DHP server.
And then as far as configuring the actual ranges and scopes of IP addresses to
use on the subnets, we're going to configure those details on a segment by
segment basis.
So with that in mind, let's head over to the NSX manager and let's set up
gateway based DHP services to support the 10 10 and 10 20 networks.
So here in the NSX manager, we're going to go to the networking tab once again, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here in the NSX manager, we're going to go to the networking tab once again,
and let's scroll down and go to networking profiles.
And let's just confirm our existing DHP server profile. So this is pointing to
a logical DHP server at 6783 with a 29 bit mask.
And that's the logical IP address that's going to be used by the NSX logical D
HP server.
And currently this profile is in use with click here on the one where it says
where used, it shows us the segment it's applied to.
So because we already have this profile in place, we're simply going to use it
again as we implement gateway based DHP services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
again as we implement gateway based DHP services.
Let's head over to our tier one gateways and tell them to use this specific
profile, which uses this logical IP address for their DHP server.
So with networking still selected on the left hand side, we'll click on our
tier one gateways and let's edit our gateways.
So there's gateway A, we'll click on the three dots, click on edit, and then
here where it says DHP config, we'll simply click on set.
And then for the type, we use the drop down and choose DHP server, and then we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then for the type, we use the drop down and choose DHP server, and then we
'll choose the DHP server profile. We only have one.
And that's our NSX DHP server pointing to an IP address at 6783 with a default
lease of 86,400 seconds, which is one day.
So we'll click on apply and they'll do that same thing for gateway B once we
click on save here and then scroll down and click on close editing.
And we'll go ahead and collapse that and we'll modify gateway B. So we'll click
on the three dots for gateway B, click on edit from the sub menu. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then for DHP config, we'll click on set and from here, we'll say we want to
go ahead and use the DHP server and specify the profile that points to the
logical IP address 6783 with a slash 29 bit mask for the DHP server and click
on apply.
And then we'll click on save and then we'll scroll down and click on close
editing. So now if we went to network topology on the left and we zoomed in a
little bit, now we have on gateway A and gateway B two services.
One of those is gateway firewall rules, which comes free of charge on these
gateways, and then we also have DHP, which we just configured. And the same is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
gateways, and then we also have DHP, which we just configured. And the same is
true for gateway B.
So now that our two gateways are willing to support gateway based DHP services,
let's go ahead and tell segment 10 and segment 20 that we want them to go ahead
and use those services.
So to do that with networking still selected on the left, we'll click on
segments and let's edit segment 10 first. So we'll click on the three dots next
to segment 10, click on edit, and over here on the right, where it says set DHP
config will click that.
And then from here, we have three options. And the reason we have three options WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then from here, we have three options. And the reason we have three options
is because this segment is connected to a gateway. So we could do segment DHP
services or set up a DHP relay, or in our case, we want to use gateway based D
HP server.
So we'll click on the gateway DHP server, because we already specified the
profile of our NSX DHP server on the gateways. That's already present here is
showing us the IP address of the logical DHP server based on our profile.
And now it's asking us for the ranges. So we are focused here on the segment 10
. So we use a range of 10, 10, 150 through 10.10.0.200. That'll be enough for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
. So we use a range of 10, 10, 150 through 10.10.0.200. That'll be enough for
the default gateway. It's already provided 10, 10, 01, because that's the IP
address on the gateway interface connected to this segment.
So that'll be automatically served up to the clients. And for the lease time, I
'm going to go ahead and set up a short release of 600 seconds.
And then the DNS server, I'm going to hand out 888, just like that. And then if
we want to do static bindings, here's also where we would do that and click on
static bindings, click on add IPV for static binding. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
static bindings, click on add IPV for static binding.
And that way you can specify a specific IP address to hand out based on a
client specific layer to address. So I'm going to go ahead and leave that blank
at the moment, go back to settings, confirm our work and click on apply.
Then we'll scroll down, click on save, and click on close editing. Fantastic.
So segment 10 now has DHCP services. If we went to network topology and we
expanded segment 10 next to segment 20, you'll notice that segment 10 has one
service that's DHCP
while segment 20 doesn't yet. So let's solve that by going over to segments WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
while segment 20 doesn't yet. So let's solve that by going over to segments
once again, clicking on the three dots for segment 20 clicking on edit. And
then over here on the right, we'll click on set DHCP config right there.
Now, let's specify the type of DHP we want to use, and that is gateway based
DHCP services, the profiles already associated with our gateways. So that's the
one that shows up here. And then there's the DHCP server 6783. And then the
range here for segment 20 is going to be 10.20.0.150 through 10.20.0.200. And WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
range here for segment 20 is going to be 10.20.0.150 through 10.20.0.200. And
then I'll go ahead and use a short release time, like 600 seconds. And then for
DNS, we'll use 8.8.8.8.
So you want to have multiple DNS servers, simply add multiple DNS servers. And
for the default gateway, because this segment is connected to a gateway with a
IP address of 10.20.1 that is pre-populated for us right there.
And we'll be handed up to the clients as part of DHCP services. So we'll click
on apply, scroll down, click on save, and click on close. So as we look at our
segments over here where it says subnets, here for this segment based DHCP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
segments over here where it says subnets, here for this segment based DHCP
services, it says view DHCP config.
So if we click on there, it'll show us the details we set up for segment based.
And for the two that are gateway based on our subnets, if we click on the IP
address here, it's a hyperlink.
It'll show us the details for the DHCP services, including the virtual server
address, the range involved, the lease, the DNS server, and the default gateway
.
So we'll click on close. And let me bring back wire shark. And let me go ahead
and reset it and minimize that. And let's power on a couple of VMs connected to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and reset it and minimize that. And let's power on a couple of VMs connected to
these two segments.
So I propose we bring up VM one, which is being hosted on host A. And let's
also bring up VM four on a separate subnet here on segment 20, which is being
hosted by host B. So VM one and VM four.
So I'll power those guys on right now. So here is VM one, I'll launch remote
console for that. It's not powered on yet, but we'll bring up both windows,
then we'll power them on together.
And here is VM four, and we'll launch remote console there. Now, even though
these have in their names, the IP addresses that they were using, those are WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
these have in their names, the IP addresses that they were using, those are
about to change because our gateway DHCP services ranges are from 150 up to 200
.
And it will no longer be a dot 10. So here is VM one, I'll put that on the left
. And here is VM four. And then let's be power these on because they're both D H
GP clients.
We should see on the transport network, all that captured data. And again, the
output's gonna look a lot like D HGP relay services with the local gateways
logically routing the request to the server at six dot seven dot eight dot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
logically routing the request to the server at six dot seven dot eight dot
three.
So let's power on VM one, and we'll power on VM four. So those are both
powering up as we speak. So VM one and VM four. Now, good to go.
This is still a quick verification with an IF config. And that's at 10 10 0 50
VM one is. And if we go over to VM four and do an IF config press center, it's
at 10 20 0 150.
And just to verify everything's working here on VM one list to a ping to www.
google.com. And that's going to verify our default gateway, our routing and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
google.com. And that's going to verify our default gateway, our routing and
everything else.
And just for fun, let's do a trace route to www.google.com. Press center.
Fantastic. Just a verify our path. We'll do a control C there. And let's take a
look at the packet captures.
So for this first one, the source and destination address is showing us the
deepest, the most buried IP header information that it has.
And so that's being reflected right here. So this is a request, if you will,
being sourced from 10 10 0 1, which is the IP address on gateway A that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
being sourced from 10 10 0 1, which is the IP address on gateway A that's
connected to segment 10.
And it's being sent to that logical IP address of the DHCP server. So we looked
at our topology that would be from here going to six dot seven dot eight dot
three and again that address is just the logical IP address associated with the
NSX DHCP services.
And for the request from VM four, that should be sourced from 10 dot 20 dot 0 1
and be sent to the logical IP address of the DHCP server.
Also, if we look at the transport layer IP addresses involved here, this is
from ESXIA at 11 11, et cetera, going to edge one with his tunnel endpoint of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
from ESXIA at 11 11, et cetera, going to edge one with his tunnel endpoint of
33, et cetera.
And then for the offer, notice where it's actually going on the transport
network, this is from. And in the offer, it's going to have the information
about what's being offered to that client.
So there's the IP address being offered. There's the mask. Here's the default
gateway of 10 10 0 1.
There's the DNS server of 8 8 8 8 and our lease time is 600 seconds. The client WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's the DNS server of 8 8 8 8 and our lease time is 600 seconds. The client
followed that up with a request. That's right here saying I'll take it. So as
far as transport goes, that was coming from ESXIA.
And then the final acknowledgement from the server, which was from edge one
going down to ESXIA.
And in the details of this acknowledgement coming back from the server to the
client, the client believes that the DHCP server is really at six seven eight
three.
So then if you take a look at the next discover, this is coming from a VM that
's being hosted on ESXIA. So if we take a look at the transport network, this
traffic was being sent from ESXIA. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
traffic was being sent from ESXIA.
Be up to edge one based on the tunnel endpoint addresses. So this is the
discover, then there's the offer coming from the edge one back to ESXIA.
Be who de encapsulates it, forwards it to the client, then the clients says, I
'll take it. That's the request going from the client to the server.
And then the final acknowledgement from the server to the client saying, yep, I
know you got it. Please enjoy. And then if we wait long enough, because we have
a very short lease, the clients are renewing their lease.
And that's what's happening right here. So in this request, which is coming WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's what's happening right here. So in this request, which is coming
from the client at 10 10 0 50 being sent to what it believes is six seven eight
three.
And behind the scenes, it's being tunneled from ESXIA up to edge one. If we
look at the contents for that DHCP request effectively says, Hey, this is my IP
address.
And can I have it for a little bit longer, at which point the server responds
back with the acknowledgement? And as part of that information, we have a lease
time, which is set for another 600 seconds.
So if we look at the timestamps there between the first and that renewal, that
first one happened up here at 167. And then the renewal happened at 464. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
first one happened up here at 167. And then the renewal happened at 464.
So about 300 seconds. So based on these timestamps, the client did a renewal
effectively or a request for a renewal of its IP address at about half of its
lease.
So the lease was set for 600 seconds. And this client did a renewal about
halfway through that lease time. So now that we have configured and verified
the three options for working with DHCP services as part of NSX in the next
section.
I'd like to walk through a few exercises to help validate what we've learned
together. So I'll see you there in just a moment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
together. So I'll see you there in just a moment.
[BLANK_AUDIO]