So now that we've had some time to consider these questions and this scenario,
let's discuss
together a few ideas. Now there's not just one perfect answer. There's several
different options
that we could use for IP addressing. And here's what I would recommend for
various servers.
We probably want those to have a specific IP address every single time. So for
our servers,
it's very likely we're going to have statically configured IP addresses. So we
know exactly what
they are. Maybe this guy is at dot 11 and this over here is at dot 12. And if WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
they are. Maybe this guy is at dot 11 and this over here is at dot 12. And if
we didn't want to
do static addressing, we could also go through the steps of setting up static
bindings. Where in
our DHCP services, we gather the information on the layer two address or if
these are VMs,
we can hard code those layer two addresses and then associate those in the HCP
with a certain IP
address. And that way when they go through the door process, they would get the
exact IP address
that we wanted them to every single time. But most of the time devices like
servers and printers
and routers and firewalls, those types of devices are commonly going to have a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and routers and firewalls, those types of devices are commonly going to have a
statically configured
IP address. So I'd say as far as options, that is definitely one of our options
. The other option,
of course, is DHCP assigned addresses. And if we don't care specifically about
what IP address
they have on a certain subnet, we could just go ahead and just create a pool of
addresses and
hand out from that pool. So if this is the 10 dot 30 address space, for example
, with a 24 bit
mask, when we configure DHCP services, we could say, let's hand out, for
example, let's say 11, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
example, let's say 11,
all the way through actually, we probably wouldn't want to do 11 because we're
already using that
there. So let me back that out and let's say 15 through 254. And that would
supply lots and
lots of room for our dynamically assigned IP address clients. It would also
allow 14 addresses at
the front end of that to be used as statically assigned addresses or set up as
a reservation.
Now also as part of implementing this in an NSX environment, we have if this is
a segment and
there's no gateway here, what are our options? Well, one option would be we
could create our own WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
could create our own
DHCP server. So we could have a VM that we've connected to that segment. And we
could have that
local DHCP server hand out IP addresses. And that would not be using the NSX
DHCP services,
but just the DHCP services on whatever this VM is, maybe it's a Windows machine
or Linux machine,
or some other platform that provides DHCP services. So that would be one option
. Now another option,
in an NSX environment would be segment based DHCP services, which we configured
as part of our
demonstrations up to this point. So if we say, hey, for this segment, let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
demonstrations up to this point. So if we say, hey, for this segment, let's
call it segment 30,
that we want to use segment based DHCP services, we can logically provide DHCP
services for this
segment, even though it doesn't have a directly connected gateway to it. Also
from an NSX perspective,
one thing we could not do is we could not use the NSX flavor DHCP relay. And
that's because we
don't have any gateways connected to the segment. And as a result, we can't use
NSX's flavor of
DHCP relay. However, what we could do if we had our own logical device
connected here, so let's say WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
connected here, so let's say
we have a logical router as a VM, and we wanted to implement DHCP relay
services on this interface,
on that VM, who can then forward the DHCP messages out to the external DHCP
server,
that would work. However, it also defeats the purpose of a non-routable segment
. So if we don't
have that router there, that pretty much eliminates any option for DHCP relay
services,
because we don't have a router connected to that segment. So in conclusion,
although there isn't
just one exactly perfect answer, I think probably a good solution would be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just one exactly perfect answer, I think probably a good solution would be
static IP addresses
on the servers. And then for the DHCP clients in an NSX environment, we can
simply use segment-based
DHCP services to dynamically hand out the IP addresses to those clients. And
based on the other
considerations with no gateways connected and non-routable segments, we wouldn
't be able to use
DHCP relay nor gateway-based DHCP services. Once again, because they're simply
not connected over
here to the segment. I have had a lot of fun in this set of videos regarding WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here to the segment. I have had a lot of fun in this set of videos regarding
DHCP services and
an NSX environment, and I look forward to seeing you, my friend, in another set
of videos very,
very soon. Until then, I hope this has been informative, and I'd like to thank
you for viewing.