In this video, I'd like you to do
a quick verification of this existing topology
where we left off in a previous skill
where we have two segments, segment 10, segment 20,
and we also have two VMs on segment 10
and two VMs on segment 20.
So I just wanna verify our existing topology
before we start adding onto it and including a new gateway.
So here in the vSphere client, let's first of all verify
that we have our network segments.
We'll click right here on the network tab
and then under our distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that we're using for NSX.
Here we have our two port groups.
We have segment 10 yellow and segment 20 pink.
So there, right here, they both look good.
And then also we can verify which VMs are connected there
by clicking on the VMs tab.
So with the networking selected, then selecting one
of our segments here, we can see
what the VMs tab selected up here on the right
that we have host A VM on segment 10
and also host B VM on segment 10.
And those are both on A and B respectively.
And let's just peek at our topology
to make sure that's what we intended.
So here in our topology we have host A VM segment 10 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here in our topology we have host A VM segment 10
right here and host BVM segment 10 right here.
That looks good.
So this guy's on host A and this one's on host B.
And then we should also have host A VM segment 20
running here on ESXi-A.
And then here host B VM segment 20
should be running on ESXi-B.
So let's verify those two as well by looking at this segment
and taking a look at the two VMs that are attached.
So we'll make a road trip down to segment 20
and our first one there is host a VM on segment 20,
which is being hosted on ESXi-A, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which is being hosted on ESXi-A,
and then host B VM on segment 20,
which is being hosted on segment B.
Fantastic, so let's go ahead and power those on.
Let me go back to the VMs and templates view.
Let me click on this folder VMs for testing.
We'll go ahead and click on the VMs tab
and select 'em all at once and right click
and just say power and power on.
So because there's DHCP services
and those two different segments, segment 10 and segment 20,
and the clients are automatically set
to get IP addresses via DHCP, they should be good to go. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to get IP addresses via DHCP, they should be good to go.
So let's verify.
Let's go to the VMC and host A on segment 10
and let's open up a web console there
and we'll confirm it's IP address within if config.
And that looks good.
It's IP address is 10.10.0.11
And let's go to host B VM here on segment 10
and click on web console.
And let's do an if config here,
verified its IP address.
So this was a 10.10.0.10.
The one over at host A is at 10.10.0.11 as we just saw.
So let's do a ping real quick.
Alright, so we've just done some basic validation
that our infrastructure is in place WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that our infrastructure is in place
and that would include that we have these four VMs
that are currently running these two over here
on two different segments.
These two are here on two different segments.
So all the devices on segment 10 can talk to each other.
All the devices on segment 20 can communicate
with each other except they can't get outside
of their local segment because two reasons,
they don't have a default gateway configured yet.
And secondly, we don't have a default gateway yet either
that it even exists as a distributed router inside of NSX.
Also, as a verification of what we have in place,
we could go to several places WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we could go to several places
and ask, we could use the NSX CLI, we could go
to the NSX manager, we could go to our transport nodes,
we could go to our edge nodes.
And pretty much,
even though the syntax is slightly different
at each of those devices,
the information is very useful.
And that is, for example, we can ask any of those devices,
"Hey, what logical switches do you know about?"
That's a fancy way or an older way I should say,
of saying a segment.
We could also say, "Hey, what logical routers do you have?"
Which is a older way of saying which gateways exist.
So as NSX continues to migrate to newer and newer versions WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So as NSX continues to migrate to newer and newer versions
and newer code, they are migrating more away from some
of the older commands, like get logical router
and they're moving forward to the commands.
They're gonna be similar to like get gateway.
So let's open up an SSH session over here to ESXi-A
and do a couple quick verifications
and that will give us an opportunity to see before
and after look regarding the distributed router
that we're gonna be adding.
So now that we're SSHed over
to the EXI host called ESXi-A,
we'll then move over to the NSX CLI WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we'll then move over to the NSX CLI
by typing in NSX CLI and pressing enter.
And boom, now we're sitting
at the NSX command line interface
on this NSX host transport node.
So here we can issue commands like get logical switch
and no space and a question mark.
And that's showing us
that we could use the command logical switches
or we could do a logical switch.
Then put further information
about a specific logical switch.
So if we do a get logical switches, this command right here,
this is showing us the logical layer two broadcast domains WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
provided by NSX.
So these are also referred to as segments.
And the reason that this ESXi host
knows about these two segments
is because it has been included as part of NSX
as a host transport node
and it has VMs that are connected to both those segments.
So if an ESXi host is not supporting a transport zone,
where a segment exists,
that logical switch wouldn't show up.
And also as NSX moves forward,
they're moving towards a new slightly modified command sets.
So we could use a get segment command, still do get segment,
no space and a question mark. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
no space and a question mark.
And this is showing us
that we could use the command segments
to see a list of segments
or we could type in segment and the UUID
or the VNI and go further.
So if we do a get segments,
look at the output here, it's identical.
Just think of it as a more current way
of issuing the command get logical switches
'cause at the end of the day, they're very, very similar.
And as time goes forward,
they're migrating towards the new commands.
So to contrast that, if you do a get logical switches
and press enter, if the output looks very, very similar,
that's because it is.
So those are our two segments. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So those are our two segments.
So how do we know if we have a distributed router
on this NSX host transport node?
Well, we could issue the command get space logical routers.
That'd be one option.
So currently it's saying you have no logical routers,
but a more current way of doing that same output
is doing a get gateways, which is also showing us
that we have no logical layer three routers set up yet.
Again, that was looking here at ESXi-A
and also just be aware
if we did have a logical layer three gateway set up,
but this ESXi host didn't have any segments WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
but this ESXi host didn't have any segments
that were connected to that logical gateway,
NSX wouldn't bother putting a copy
or an instance of a distributed router
on an ESXi transport node if it didn't need it.
However, if we do have a logical gateway set up
and it's supporting segment 10
and this host transport node has VMs on that segment,
it's at that moment, that's what's going to cause NSX
to have a copy, if you will,
of that distributed router function located
on this transport nodes.
So this transport node can make its own routing decisions WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this transport node can make its own routing decisions
between those two segments.