So in our topology, I currently have these four VMs that are currently running
and ready.
I'd like to deploy a couple more. One is the server or device that we can place
here on
segment 10 that we can use for additional testing. I'm also going to place one
additional VM right
here up on VLAN 23. Again, that we can also use for testing. So to do that, we
'll use the vSphere
client. I'll right click on the data center. And then from the dropdown, click
here and deploy
OVF template, click on local files, then I'll click here on upload files. I've
got a little DSL OVA
now. I don't know whether or not this has VMware tools on it. So we'll just pay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
now. I don't know whether or not this has VMware tools on it. So we'll just pay
attention that as
we deploy it regarding how we bring it up or bring it down. So with this dls O
VA selected, we'll click
on next and I'm going to name this little VM server on segment 10. And then I'm
going to go ahead
and place that in the folder called VMs for testing. Click on next. As far as
who's going to host
this, I want it to be one of our host transport nodes. Let's put this on ESXIA,
click on next.
And here's the description for it. It's a really tiny DSL. And this is the
entity or person who
created it. Fantastic. So I'll go ahead and click on next. And then I'll put it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
created it. Fantastic. So I'll go ahead and click on next. And then I'll put it
on a local data store,
click on next. And then I want to make sure I put this guy on the right segment
. So we'll click on
browse for its network interface. And let's go ahead and put it on segment 10
yellow. Perfect.
We'll click on OK. And then click on next. And we'll confirm our work. So it's
going to go on ESXIA
on the local data store. It's being connected to segment 10. Fantastic. And we
'll click on finish.
So that is in the process of deploying fantastic. We'll let that finish in the
background. And while WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
background. And while
we're waiting for that, let's go ahead and create one more VM. And let's put it
up on the VLAN 23.
So I'm going to take one of these VMs. Let's just grab that one right here,
which is running
right click and say, let's just clone it. That's one of the benefits of vSphere
. So we'll go ahead
and click on clone and then clone to a virtual machine. And we'll call this VM
dash 23 meeting.
It's going to be a VM sitting up. Once it's all set up, VLAN 23 on the 23.1.2
network.
So as far as where we're going to place this in our folders, we'll place it
also in the VMs
for testing folder, click on next. And as far as the compute resource, this one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for testing folder, click on next. And as far as the compute resource, this one
doesn't actually need
host transport notes. We could put it on ESXIA or ESXIB or we could go ahead
and put it on a host
in our management cluster. Let's go ahead and click on ESXID. So because we're
not going to be
putting this VM on an overlay segment as part of NSX, it won't matter too much.
So we'll ignore
that click on next and we'll put on the local data store click on next, then we
'll customize
the network configuration. And we'll click these two checkboxes to give us the
opportunity to
put this VM on the correct subnet in this case, the VLAN 23 network and then go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
put this VM on the correct subnet in this case, the VLAN 23 network and then go
ahead and power it
on. So we'll click on next and for the network adapter and browse. Oh, I just
realized. I don't
know a port group that goes to VLAN 23. So let me go ahead just for a moment
and put this on the
management port group. Click OK, click on next, click on finish. And let's also
create a port
group where I can move that to for VLAN 23. And then for this distributed
switch called
DS for NSX, that'll work. We'll go ahead and right click. Then we'll click on
distributed port
group and then we'll click on new distributed port group. And I'm just going to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
group and then we'll click on new distributed port group. And I'm just going to
name this VLAN 23.
And then click on next. And then I want to see all the details. So I'm going to
go ahead and say
this is belonging to VLAN 23. That way I'll be trunked down to my physical
network. So it can
work and click on next and then next and then next. And I'm only going to use
VM NIC 2. So I'm
going to take VM NIC 3 out of the picture here for this specific port group,
click on next and
finish and boom. We now have that new port group which is right there. And if WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
finish and boom. We now have that new port group which is right there. And if
we look at the
topology here for the actual switch by going to configure and topology, here's
our port group,
VLAN 23, associated with VLAN 23. So we'll do is we'll modify that VM and move
it over to that
port group. So here for VM 23, I'm going to right click and just give a nice
fair even shake. I'm
going to click on power, do a shutdown, the guest OS, click on yes because it's
running VMWare tools.
Fantastic. So we'll give that a moment to power off. And now let's power it off
. We'll right click
and click on edit settings. And then we'll go ahead and move the network
adapter over to the correct
port group. So we'll click on browse. We'll modify the network interface card, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
port group. So we'll click on browse. We'll modify the network interface card,
put it on the right
port group, click on OK, confirm our work, click on OK. And then we'll power it
back on by right
clicking and clicking power and power on or we could use the power on button
above. This is DRS
saying, hey, please put it on ESX ID. We'll say great, click on OK. And the
reason it's recommending
that is because the data store for VM 23 is also on the local data store for ES
X ID. All right,
so that's powering up. And let's launch a web console here. And let's just do a
couple quick
tests. So do I have config? And sure enough, it has an IP address 231270. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
tests. So do I have config? And sure enough, it has an IP address 231270.
Fantastic. And if we do a
route command, if I type it in right, do a route command, we also have a
default gateway, which
it did a reverse lookup for, but that's the IP address right there. It's 23.1.2
.1 is our default
gateway. And again, there's our actual IP address. So because this guy is
sitting out on this
pseudo public network outside of gateway zero, it should be able to go ahead
and ping internet
resources. So let's verify that real quick with a ping to 8888. And that looks WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
resources. So let's verify that real quick with a ping to 8888. And that looks
great. And we'll do
control C, we can also do a trace route to 8888. Just to confirm we're really
going out there,
I'll do control C there. That looks great as well. So we verified our VM 23
that it can get out to
the internet. Let's also verify the server we just placed and identify what its
IP address is.
So prior to that, the server on segment 10, let's just verify its network
connectivity.
So logically, it's connected to segment 10. So let's power on that server. So
we'll power it on.
And then we can verify that it got an IP address via DHCP on that 10 10 zero WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we can verify that it got an IP address via DHCP on that 10 10 zero
network.
Then once we verify that, we can also document what that IP address is. So let
me go ahead and
right click on that little VM. And we'll click on open remote console. And here
it is on its initial
boot right here. And this little VM does not have VMware tools. So I'll just be
a little bit
careful about how I shut it down or powered off because I don't have the VMware
tools on this little
teeny VM. And as a result, I don't want to just crash it. So here, showing that
the IP address is
10 10 zero 13, let me make that a little bit bigger. There we go. There's a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
10 10 zero 13, let me make that a little bit bigger. There we go. There's a
little bit better
view of that. So 10 10 zero 13, we could also confirm that by opening up a
shell here and verifying it
from the command line as well. So if we click down here to open up a shell, and
we type in if can
fake here, sure enough, our IP address is 10 10 zero 13 if we type in route
press enter, our default
gateway is 10 10 zero one. So at this point, we should be able to ping 23 dot 1
dot 2 dot 60.
That's the virtual IP address on our gateway zero. And let me go ahead and put WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's the virtual IP address on our gateway zero. And let me go ahead and put
in a pseudo ping
to 23 dot 1 dot 2 dot 60. And that works. And because we're exchanging routing
information
up with our external gateway, if we try to ping that address 23 dot 1 dot 2 dot
1,
that should also work as well. That's also a good confirmation that we're
advertising our
subnets to 10 10 and 10 20 up to our external router, because if we weren't our
external router
would not have the knowledge of how to forward back. All right, so we can
update our topology
with those IP addresses, the server based on what we just saw is at dot 13 on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with those IP addresses, the server based on what we just saw is at dot 13 on
the 10 10 zero network.
And also a little VM here on the 23 network is at 23 dot 1 dot 2 dot 70. That's
its IP address.
So in our game plan, we've updated our topology and we have a couple of VMs
that we've had
for testing. So in our next video, let's go ahead and now implement and test
source net for traffic
being sourced from VMs down here as they try to go out to the public internet.
So I'll see you in
the next video for exactly that.
[BLANK_AUDIO]