In this video, you and I get to put a game plan together.
So the first game plan is going to be for DHCP relay services.
So for DHCP relay, we need an existing DHCP server in our topology.
So I currently have one.
It's kind of sneaky, but it's right here.
This device right here, which is acting as our gateway at 23.1.2.1
to the outside world, this device is also acting as a DHCP server.
So if this device is acting as our DHCP server for the 1010 network
down here in the 1020 network, we need to have a pool or a scope or range of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
down here in the 1020 network, we need to have a pool or a scope or range of
addresses
available for each of those subnets.
So currently I already have that in place.
And we'll double check at this device just to make sure it does have those
pools.
And it's got another pool or scope of IP addresses for the 10.20 network as
well.
And then for both of those, the default gateway on each of those respective
networks
that it's going to be handing out is .1.
Also, this device acting as a DHCP server, I believe, and we'll verify that as
well.
I believe it's also handing out information regarding which DNS server to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I believe it's also handing out information regarding which DNS server to use.
And so we'll verify that that's in place before we start relaying requests up
to it.
So for DHCP server, the actual real server is at 23.1.2.1.
And again, that's this device that's acting as a gateway and also a firewall.
And it also is acting as a DHCP server.
So as part of our configuration, we'll create a profile that says,
hey, the real server is at this IP address.
And then we can verify that that works by bringing up clients on these network
segments
and verify that they're getting IP addresses from that pool up here on our DHCP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and verify that they're getting IP addresses from that pool up here on our DHCP
server.
And then once we have that in place, we can go ahead and test and verify
from clients in either of these subnets to make sure they can dynamically get
an IP address,
leveraging the actual DHCP server that's in my existing network.
So once that's done, I'm going to go ahead and tear that down, remove all the
DHCP configuration.
And then the next thing I'd like to walk through the configuration and
verification of
is setting up a segment-based DHCP server.
And the use case for this is if we have a segment, let me go ahead and let me WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
use blue here.
Let me go ahead and put a segment here.
And let's create segment 30, which currently doesn't exist.
We'll create it from scratch.
It'll be an overlay segment.
And then as part of that, we'll configure DHCP services for the segment.
And as part of setting up DHCP services for a specific segment with segment-
based DHCP services,
we're also going to be referring to an IP address for a DHCP server.
But this time, it's just going to be a logical DHCP service that lives in the
mind of NSX.
So we could use any IP address that we wanted to.
In fact, if you don't put it in an IP address as part of the profile, it'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In fact, if you don't put it in an IP address as part of the profile, it'll
just go ahead and
make one up for you.
So as far as our plan, let's use the IP address for the segment-based DHCP
services of 6.7.8.3.
And let's throw on a 29-bit mask just to make it a little bit interesting.
And for the address based down here, let's use 10.30.0.0.
So if we bring up a couple of clients, they should both be able to get IP
addresses on the 1030
subnet. And we won't have to worry about DNS resolution. And we won't have to
worry about a
default gateway because there is no logical layer 3 routing happening with this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
default gateway because there is no logical layer 3 routing happening with this
segment that we're
just going to create as part of the demonstration of setting up segment-based
DHCP services.
So once we've tested and verified that, we'll remove that configuration.
And the third thing I'd like to configure and verify together is gateway-based
DHCP services.
And that'll support the 1010 network. And we'll also set up to support the 10.
20 network.
So the 1020 is segment 20 and the 1010 is segment 10.
Now, one thing you're going to notice is that when we configure these segment- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, one thing you're going to notice is that when we configure these segment-
based DHCP services
for a network segment that has absolutely no gateways connected, we don't even
get the option
of using a gateway-based DHCP server. Our only option is a segment-based DHCP
server.
However, when we have the gateways connected to those segments like segment 10
and segment 20,
we're going to have all of our options available. We can set up relays for
those subnets. We can
set up segment-based services for those subnets or because we have a gateway
attached, we can also
use gateway-based DHCP services. And as part of the configuration, it also is
going to use WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
going to use
a DHCP profile. And so we can actually double up on the profile up here. So we
just use the same
6.7.8.3 with a 29-bit mask. Now, that IP address is not reachable anywhere yet,
but once we created
DHCP profile and put it to work in combination with our segments, then that
logical IP address
becomes reachable and routable inside the mind of our gateways. And we'll
verify that as we move
forward as well. So as far as our plan as well, as far as ranges of addresses,
let's use 150 through
200 for the segment 30 with the segment-based DHCP services. And then for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
200 for the segment 30 with the segment-based DHCP services. And then for
segment 10, let's
use the range of 150 through 200 there as well. And also for the 1027net, which
is over here with
segment 20, let's use the range of 150 through 200. Also across the board, let
's also specify
for the gateway-based DHCP services that we want to use for a DNS server. Let's
use a Google server
at 8.8.8.8. And for the default gateway, we're going to use .1 on each of these
respective networks,
because that's the IP address here on our gateway-a.1 here on the 1010-0 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because that's the IP address here on our gateway-a.1 here on the 1010-0
network and .1 here over here
on the 1020-0 network.
[BLANK_AUDIO]