So based on our game plan, we're going to create a couple real quick static
bindings as part of DHCP services for our VM web, which is right here.
We'll give it the IP address of 10, 10, 0, 10. And then down here VM dash DB,
we'll give it the IP address of 10, 20, 0, 20.
And again, because these are already DHCP clients, if we set up the
reservations for those specific IP addresses based on their layer two Mac
addresses, whenever they power up and ask for a DHCP address, they'll be given
the IP address that we have set up for their static binding.
So to set up the static DHCP bindings, because they're provided courtesy of NSX WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So to set up the static DHCP bindings, because they're provided courtesy of NSX
, we're going to go to the NSX manager to configure them.
So here in the NSX client, one of the quickest and easiest ways of verifying
both of their Mac addresses in preparation for setting up static bindings in
DHCP would be to use trace flow.
So we go to plan and troubleshoot, and we'll be on the left, go down to traffic
analysis right there, and then click on getting started with trace flow.
From here, we can say, I want to go ahead and do a connectivity test, and I'm
going to say from web, going over to the database server, and then showing us WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
going to say from web, going over to the database server, and then showing us
the Mac addresses right here.
So there's a quick and easy way of getting those. I'm going to go ahead and
just right click on the Mac address for VM web, and then copy that and then jot
that down.
So I've got that documented. I'm also going to go ahead and copy and paste the
Mac address that's currently being used by VM dash DB.
So I'll right click on it, click on copy, and save that as well. So now that I
know what the two Mac addresses are, to set up the DHCP services, we'll go to
the networking tab, and then we'll go to the respective segments.
So under connectivity, we'll click on segments, and let's start off with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So under connectivity, we'll click on segments, and let's start off with
segment 10, and that's where our VM web server is.
So we'll double click to edit the details for segment 10, and over here where
it says edit DHCP config, that's exactly what we want to do.
So we'll click on edit DHCP config, and then we have our tabs under IPv4 server
for static bindings. So we'll click on static bindings, and we'll click here to
add an IPv4 static binding.
And for this name, I'm going to call it DB dash web, and I take that Mac
address, which I saved earlier, paste it in right here.
And then the IP address I want to give it is 10.10.0.10 based on our plan is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then the IP address I want to give it is 10.10.0.10 based on our plan is
default gateway should be 10.10.0.1, and that's the logical interface on our
tier one gateway A, and for the host name, I don't need to fill that in.
So let's go ahead and also set the lease for a little bit lower. I'll set that
the 600 seconds.
So even though it depends on the operating system, most DHCP clients are going
to renew their lease halfway in.
So that'll keep some activity going on at least every 300 seconds.
As this client renews its IP address, it'll be given the 10.10.0.10 every
single time, assuming this is successful. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
single time, assuming this is successful.
So we'll go ahead and click on add, and then click on apply, and scroll down
and click on save.
And then for the segment, we'll scroll down and click on save, and then click
on close editing.
And let's do the similar treatment for our database VM, which is on segment 20.
So for segment 20, we'll click on the three dots, click on edit, then over on
the right, we'll edit the DHCP configuration, and then we'll click on the sub
tab here for static bindings, then we'll add a static binding.
We'll call this one VM dash DB.
I'll take the MAC address that I saved earlier, we'll paste that in, and the IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll take the MAC address that I saved earlier, we'll paste that in, and the IP
address we want that database server to have is 10.20.0.20, and its default
gateway is going to be the logical segment 20 interface address on gateway B,
which is 10.20.0.1.
So we'll put that in 10.20.0.1, and for the least time, I'm going to set that
to a lower value there for my lab environment, and then we'll go ahead and
scroll down and click on add, and then we'll click on apply right there, and
then scroll down a little bit, click on save,
regarding the segment as a whole, and then we'll scroll down and click on close WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
regarding the segment as a whole, and then we'll scroll down and click on close
editing.
So because I only have a 600 second lease and the client should be renewing
their lease, at least every 300 seconds, if I've waited long enough, those
clients should automatically have their newly assigned IP addresses of 10.10.0.
10, and 10.20.0.20.
So one easy way to verify that is we could go once again to plan and troublesh
oot, and go down to traffic analysis, go to trace flow, click here and get
started, and then from here specify VM web on the left, and on the right, VMDB, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
started, and then from here specify VM web on the left, and on the right, VMDB,
and they currently have the old addresses.
So let me power off and power on those VMs, and when they come up, they should
get the newly assigned IP address.
So back to the vSphere client we go, let's grab these two, and I'll right click
, and they are both running VMware tools, so click on power, and let me shut
them both down, gracefully click on yes, and we'll give that a moment to
complete.
Fantastic, they're both powered off, so I'll right click, and let's power them
both back on, and we'll also verify that they have the IP addresses that we
statically bound for them via DHCP services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
statically bound for them via DHCP services.
So VM web should be 10 10 0 10, and VM dash DB should be 10 20 0 20, if that's
how we configured it.
So let's open up consoles for each of those.
Let's open up a console for VM web.
So here's VM web in the upper left hand corner just to confirm we're on the
right device VM dash web, and if we do an I have config for Ethan at zero and
press enter, it's got the address 10 10 0 10.
And from here, if we did a ping over to 10 dot 20 dot 0 dot 20 and press enter,
if that works, that also implies a little control see there's stop that, that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if that works, that also implies a little control see there's stop that, that
also implies that VM dash DB has the IP address 10 20 0 20, but let's verify
that as well.
So back in the vSphere client will go to VM dash DB will open up a web console
to that, and we'll do an I have config for ethernet zero, and sure enough it's
10 20 20, and just for funless ping 10 dot 10 dot 10, and that looks great.
So now we have a specific IP address on VM web of 10 10 0 10 and a specific IP
address on VM dash DB up 10 dot 20 dot 0 dot 20. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
address on VM dash DB up 10 dot 20 dot 0 dot 20.
So now that we have our VMS in place and we have a couple static bindings for a
couple of our servers.
In the next video, let's set up our tags and assign those tags to our various V
MS.
So I'll see you in the next video for exactly that.