So now that we have Segment 10 implemented
and tested and verified, let's go ahead
and walk through the process of creating segment 20.
So here we'll create a new VM
and we'll call it VM A 20.0.0.20.
And over here on the ESXiB side, we'll make VM B
and we'll put it at the IPS of 20.0.0.21,
and we'll include the new segment called Seg 20.
We'll include that as part
of our A B overlay transport zone,
and that way both ESXi-A and ESXi-B will have access to it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that way both ESXi-A and ESXi-B will have access to it
for the connection of the new VMs to that segment.
So without further ado,
let's implement our new overlay segment called Segment 20,
and we'll add our two VMs to it.
So here in the NSX manager,
we'll click on the networking tab
and that's where we would go to create another segment.
So currently we have one segment that's segment 10.
So we are gonna, on the left hand side, click on segments,
and then we'll click on add segment to create another one
and listening to SEG 20 pink.
And we don't have any logical layer three gateways yet WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we don't have any logical layer three gateways yet
even to associate with that new segment.
So we'll leave that empty.
But we will associate this new segment
with our overlay zone, and that's our A B overlay zone,
which both ESXi-A and B are both supporting
so that means this new segment should be available
to both those hosts as well.
So we'll scroll down and click on save.
And it's gonna ask us, do you wanna continue configuring?
We'll say no.
And now we have Seg 10 yellow and SEG 20 pink.
So let's head over to the vSphere client
and create a couple new VMs and attach both of them WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and create a couple new VMs and attach both of them
to this new network segment.
So here in the vSphere client, let's go to the network tab
just to verify that it does show up so there's segment 20.
So if we click on summary here,
it's showing us the VNI number right there,
which could be handy at the CLI
if we ever need to use the CLI.
It's showing us the transport zone that
that new segment belongs to.
It's also showing us right here
the actual name of the segment
and also down here that we have two transport nodes
that are currently supporting it.
If we click on configure, once again,
it doesn't give us options for really configuring it, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it doesn't give us options for really configuring it,
but rather to see the details regarding that segment.
So let's create a couple new VMs and connect them over
based on our plan.
So we'll go to our templates here,
right click on our tiny template
and click on new VM from this template.
And for the first one, we'll call it VM A space.
This is gonna be 20.0.0.20,
and I'm gonna put this in the folder called VMs for testing
and we'll click on Next.
Alright, as far as the compute resource,
we want this first one to be on ESXi-A. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we want this first one to be on ESXi-A.
So we'll select that and click on next.
And then we'll use the data store there, local on ESXi-A,
click on next and we'll customize it
to put in the right segment and then we'll power it on
when we're done with that.
And we'll click on next.
And so we wanna put this on segment 20.
So we'll browse, click on segment 20, click on okay.
And then just confirm
that we have the right network segment, which we do.
And we'll click on next.
That all looks good, we'll click on finish
and we'll do it one more time for the second VM
that we're gonna put on that pink segment.
So right click on our template. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So right click on our template.
From the menu, we'll click new VM from this template.
So we'll give it the name VM B 20.0.0.21,
and then we'll make sure we put that in a folder
called VMs for testing.
Click on next.
And then we wanna put this on the compute resource of ESXi-B
and click on next.
We'll use the local data store there.
Click on next to continue.
We'll click customize to make sure
we can put on the right network segment
and then we'll have it powered on when we're done with that.
We'll click on next.
And then we're gonna have the network adapter one
be placed on network Segment 20 pink. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
be placed on network Segment 20 pink.
We'll click on okay, and then we'll click on next.
That all looks good. We'll click on finish.
And then I'd like to go ahead and verify our work as well
just to make sure we have the right VMs
and the right host and the right segments.
And one easy way of doing that
is going to the networks tab up here,
selecting the Segment 20 pink,
and then over here clicking on VMs.
Also for the columns, I'd like to make sure
I have the host shown here.
If it's not shown, you can go to manage columns down here,
make sure that host is selected.
And this can confirm for us that we have VM 20 here
on ESXi-A, and VM 20 is running ESXi-B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on ESXi-A, and VM 20 is running ESXi-B
and they're both connected to segment 20
'cause that's where we started from over here on the left.
So with that in mind, let's go ahead
and bring up consoles to each of those.
So we'll bring a web console up for VM B.
And while we're here, let's configure an IP address
with a pseudo IF config ethernet zero.
And we want this one to be 20.0.0.21.
It's okay if it's gonna default to an eight bit mask.
That'll work.
Next, let's go ahead and open up a console for VMA 20.0.0.20
by clicking here on Launch Web Console. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
by clicking here on Launch Web Console.
And we'll give it an IP address as well.
And this IP address is gonna be 20.0.0.20
and we'll press enter.
And let me just confirm my work on both.
So here is the terminal window for 20.0.0.20
with the IP address of 20.0.0.20.
Fantastic!
And here is 2021 and it has the IP address of 2021.
So let's send some traffic back and forth.
So let's go to this PC at 20.0.0.20
and we'll do a ping over to 20.0.0.21 and press enter.
So that seems to be working great. We'll do a control C. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that seems to be working great. We'll do a control C.
And one other great way to verify
whether or not connectivity is gonna work across the segment
is by using a really cool option under plan
and troubleshoot here in the NSX manager.
Check this out.
With plan and troubleshoot select over on the left,
we're gonna click traffic analysis.
And then for trace flow right here,
we'll click on get started.
And from here we have a lot of options
for connectivity testing.
And so what I wanna do here is
I wanna select virtual machine on the left hand side,
and let's go ahead and pick 20.0.0.20 as a starting point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and let's go ahead and pick 20.0.0.20 as a starting point.
I'll scroll up here, it's also showing us the details,
including the Mac addresses involved.
And then for the destination, we'll go ahead and also use VM
and we'll go ahead and select 20.0.0.21.
So this is going to do connectivity testing
between this virtual machine and this one.
So I'll scroll down and click on trace
and we'll give that a moment to crank it out and it is done
and it's giving us a beautiful representation
of what happened so the VM here running on this host.
So if we click on that host, it shows us that's ESXi-A. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we click on that host, it shows us that's ESXi-A.
And if we click on this little VM,
it shows us that's the VM at 20.0.0.20.
Fantastic.
Then that traffic is logically going through this segment
and it's being delivered down to 20.0.0.21.
It's also showing us right here with the dotted line,
the compute resource that's supporting or running this VM.
So if we click here, that should be ESXi-B,
which it is fantastic.
Then for the play by play, if we scroll up here,
it's showing us all the details.
So the traffic was injected here at ESXi-A
via network adapter one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
via network adapter one.
Then it was processed
through a logical distributed firewall,
which by default permits the traffic.
That's why I was able to go.
And then it went to the physical network.
So they're showing us the tunneling
that took place from ESXi-A to B,
starting at the tunnel endpoint for ESXi-A.
And the endpoint of the tunnel was ESXi-B.
And then, ESXi-B received it via that same tunnel pair
and then we scrolled down.
Then it logically went through a distributed firewall rule,
which it passed because the default is allowing the traffic
and then the traffic was delivered successfully. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then the traffic was delivered successfully.
And again, here's a graphical representation of that,
and if you wanna see it full screen,
we could click right here as well.
And that shows us a full screen and you can actually zoom in
and add on that as well as needed.
Now also, because we had some traffic
actually going over our tunnels,
we go back to system up here on top
and on the left if we expand our fabric section right here
and look at hosts, and I'll go ahead
and minimize that left hand column.
So we're looking at host transport nodes.
They'll expand the cluster where ESXi-A and B are.
Now it's also gonna show us
that we have tunnels that are up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that we have tunnels that are up.
So if we click here on the tunnels,
here, we have a tunnel from ESXi-A's perspective
starting at 11.11.11 going over to 22, et cetera.
And that tunnel is up, and that's the GENEVE tunnel.
And the endpoint on the local side is VM K10.
That's the logical layer three interface
that ESXi is using for that end of the tunnel.
Another interesting note is that
if we had not brought up VMs and we not sent traffic across,
the tunnels are not always gonna be just generated
just because they can be.
They are brought up as they are needed.
So just be aware that in a new environment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So just be aware that in a new environment,
if you're not yet setting traffic
that needs to go over a tunnel,
it may not bother even creating the tunnels.
Also, I've noticed here in my lab environment
that sometimes it may take, I don't know, a few minutes
for the tunnel information
to be correctly reflected right here.
So if we go to the IP addresses,
the IP addresses for the tunnels may show up right here.
However, the actual tunnel itself may not show up
for a few minutes after that tunnel has been established.
So if we click right here on tunnels, that's a hyperlink
that can take us back to this page as well,
showing us the tunnel information. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
showing us the tunnel information.
And also because those tunnels are up and being used,
we should be able to ping the IP addresses of those tunnels
from the transport network.
For example, our top of rack switches.
So to verify that here at my top of rack switch,
if it did a ping over to 11.11.11.11, that should work.
Then we wanna ping ESXi-B's tunnel endpoint.
It's at 22.22.22.22, and that works as well.
It's also the physical network infrastructure
that's providing the routing between the endpoints. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's providing the routing between the endpoints.
So in my lab environment, that's this catalyst switch
providing that routing as well.
So regarding the creation and verification now
of our overlay segments, we are done.
We created overlay segment 10 and overlay segment 20.
We connected the VMs, we verified connectivity.
We went to the command line with the NSX CLI
both at an ESXi host and also at the NSX manager,
just to verify the details there.
And also to confirm, the NSX is acting
as the centralized control plane
and that the respective transport nodes
are gonna have a local control plane
with the information that they need WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with the information that they need
regarding forwarding like Mac tables and so forth.
So now that we've deployed two NSX overlay segments,
we can think of them like
two logical layer 2 broadcast domains,
even though we may have to in the background,
do some tunneling between them.
The next challenge is what about if we need clients
on the 10 network segment 10 to be able to access devices
or VMs over on segment 20, how do we route between them?
And the answer is we're gonna use a router,
but we're not gonna use a top of rack router to do that
because the top of rack router on the physical network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because the top of rack router on the physical network
is only dealing with the physical stuff.
And our overlay segments are purely a construct of NSX.
So as we proceed forward together
in building the infrastructure,
we can then proceed to the next step of actually carving out
and setting up those logical layer 3 routers
or in the world of NSX, referred to as gateways.
So we have all that to look forward to together.