Let's go ahead and take a look
at our current topology
at exactly what uplink profiles are being used
by ESXI-A and ESXI-B,
and then we can go back in and document it right here.
So here in the NSX Manager,
we're currently on the System tab.
And then under Fabric we're looking at the hosts.
I'm gonna go ahead and collapse this column over to the left
to give us a little more real estate right here.
And let's take a look at the details for ESXI-A.
So we could either go in and start editing it
or we could click right here on View Details.
Either way would be great.
So for the details of this E ESXI host, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for the details of this E ESXI host,
if we scroll to the right,
and then I'm gonna use the right arrow there.
It's showing us which uplink we're using.
So we can see right here
that it's using vmnic2 as its uplink.
And if we click over here on Host Switch right there,
so this is a hyperlink,
it'll show us the details about the host switch.
And right there it's showing us the uplink profile.
So if we expand that,
it's using the uplink profile called v101 vmnic 2.
So that's the name of the uplink profile.
And here it's showing us the logical name in NSX
and the uplink on the distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the uplink on the distributed switch
that again leads to a physical uplink on an ESXI host.
And that's right here.
So here it's confirming the uplink.
and to verify exactly which VLAN we're using,
Let's go take a closer look at that uplink profile
that ESXI-A is currently using.
So to do that, I'll go ahead
and close the detailed view here of ESXI-A
and I'll expand the left-hand side.
So still on the System tab up here on the left
in the Fabric section, let's go down to Profiles.
And the profile that we had associated with that
was this one right here.
I made a whole bunch just so we could easily WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I made a whole bunch just so we could easily
swap them out if we need to.
So this is the uplink profile called v101 vmnic 2.
I named it that when I created it.
And if we expand that,
and here it's confirming for us for the transport VLAN,
that's the VLAN that's gonna be supporting the endpoints
for our tunnels, it's gonna be using VLAN 101.
And so if we scroll down here,
here we have the label in NSX called vmnic2.
And then when we configured ESXI-A
and we associated this uplink profile with it,
we also mapped this logical name right here, vmnic2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we also mapped this logical name right here, vmnic2,
with the uplink name on the distributed switch.
So what that means is that we are using uplink 2.
I'll go ahead and circle that.
And as we send frames into the physical network,
we're adding the 802.1Q tag of 101.
And that way when the physical infrastructure,
in our case, the top-of-rack switch receives that,
and again this port is trunking,
it'll then know that that frame is associated with
and belongs to VLAN 101.
Also, let's take a quick peek at ESXI-B
just to verify which uplinks and VLANs it's using. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
just to verify which uplinks and VLANs it's using.
And based on that IP address
that we're using on the tunnel endpoint,
that is not in the same VLANs.
So let's go take a look.
So back to the NSX Manager we go
with the System tab selected.
Let's go under Fabric and click on Host,
which is gonna show us not only our host
but also those hosts that have been configured
as ESXI host transport nodes.
So here is ESXI-B right here.
We'll go ahead and scroll to the right a little bit
and click on View Details for ESXI-B.
And here is a visual. Fantastic.
We'll scroll to the right.
And here for Host Switch,
if we click on the hyperlink there,
this is showing us that we're using an uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this is showing us that we're using an uplink profile
called v102 with vmnic 2.
So we already verified the actual uplink.
And based on the uplink profile,
that one very likely is saying use VLAN 102 for the tagging.
So to confirm that, we can go to Close, close that,
and then go down to Profiles.
Again, that's under System and Profiles.
And there is v102 vmnic 2,
which indeed is using Transport VLAN 102.
So let's document that on our topology as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's document that on our topology as well.
So over here on ESXI-B, it's using vmnic2.
To go to its top-of-rack switch,
AND again, that port on the top-of-rack switch
is set up as an 802.1Q trunk.
And the VLAN we're using is VLAN 102.
So for 802.1Q tagging,
for the frames that are being sent to the switch,
it's gonna have the tag of 102.
Also, what this implies is that for VLAN 101,
we're using the IP adressing space of 11.11.11.0,
with a 24-bit mask
based on what we saw earlier at the switch.
And for VLAN 102, we're using the IP address base WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for VLAN 102, we're using the IP address base
of 22.22,.22.0 with a 24-bit mask.
And we have a routing function in the physical network
between those two subnets.
Also, in a production environment,
it's super likely we're gonna have
a whole bunch of redundancy here.
So if we had, for example,
three or four spine-layer switches,
so I'll go ahead and draw this as a spine-layer switch,
if we had, you know, some others here,
we'll call this A and B and C,
we would have full connectivity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we would have full connectivity
from each of our leaf-layer devices
to each of our spine-layer devices.
So we'd also have connections from this spine
over to this leaf and this spine to this leaf.
So every leaf is gonna have a full set of connections
to all the spine-layer devices.
And all these spine switches
are gonna have a full compliment of connections
to all the leaf switches.
And what we are not going to implement
in a spine-leaf architecture
is we are not gonna connect two leaf switches
directly together.
So that part we don't implement physically
or logically for that matter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or logically for that matter.
So let me go ahead and remove it.
And that helps us to make sure
that we have a scalable spine-leaf architecture.
So if this switch right here,
we'll call it top-of-rack switch A,
needs to talk to top-of-rack switch B over here,
these two top-of-rack switches acting at the leaf layer
are gonna have to be forwarded through a switch,
which is providing routing functionality from a switch
that's in the spine layer.
So I thought that would be helpful
just to confirm and document,
so that way there's less of a mystery
on the physical infrastructure
as far as the transport network WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as far as the transport network
forwarding traffic back and forth.
So lemme clean that up just a little bit.
So with ESXI-A and ESXI-B over here,
ESXI-A is using for its uplink the vmnic2
and using VLAN 101 for the transport network connectivity,
and ESXI-B is using its vmnic2 here and VLAN 102.
Also, now that we've confirmed and documented that,
lemme clean that up a little bit as well.
Now, our objective for this set of videos
is to implement a couple of overlay segments.
So here's what we're gonna do.
We're gonna implement overlay segment 10, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We're gonna implement overlay segment 10,
which is in this yellow color here.
And we're also gonna implement an overlay segment called 20.
And from a vSphere perspective,
it kinda looks like just a port group
on a distributed switch;
although because it's an overlay segment provided by NSX,
these two ESXI hosts don't have to be
on the common same layer 2 broadcast domain.
They can be racks away from each other
or even physical locations away from each other,
and then they can take the traffic
and tunnel it as needed to go back and forth.
So as an example, let's imagine we have this VM right here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So as an example, let's imagine we have this VM right here
that's gonna be connected to segment 10,
and this VM right here
which is gonna be connected to segment 20.
And these two VMs are being hosted on ESXI-A.
And then over here on ESXI-B,
it's also hosting a couple of VMs.
And for this VM we'll connect it to the segment 10.
And for this VM we'll connect it to the NSX segment 20,
just like that.
And there's something magical that has to be put in place
IF we want an IP network to function.
And that magical element is IP addresses.
So let's put a plan for that together as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's put a plan for that together as well.
So here's what I propose we do for IP addressing
for any VMs that are connected to the overlay segment 10.
Let's use for segment 10, we'll label that real quick there.
And for segment 10 here in yellow,
let's use the address space of 10.0.0.0.
And for simplicity, let's use an eight-bit mask.
So 10-anything, we'll use on the overlay segment called 10.
And then for the overlay segment called 20,
which is here in pink,
let's go ahead and use the adressing space of 20.0.0.0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's go ahead and use the adressing space of 20.0.0.0,
again with an eight-bit mask.
And that way when we see 10-anything we'll realize, oh,
that's the IP adressing space we're using on segment 10.
If we see 20-anything,
we'll know that's the IP adressing space
we're using on segment 20.
So lemme go ahead and reconnect these devices.
So we'll put this VM on segment 10.
We'll put this VM on segment 20.
And similar treatment over here on the VMs
running on ESXI-B,
we'll put this VM right here on segment 10
and this VM on segment 20.
So when we associate a VM with a segment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So when we associate a VM with a segment,
from a vSphere perspective,
it just looks like associated with a port group.
Because in the vSphere client, that's what it looks like.
It looks like just a logical port group
that you could associate a vmnic with.
Also, as part of our game plan,
because we already have this zone,
this transport zone called Our A-B overlay transport zone
that ESXI and ESXI-B are associated with,
that way, if we create,
or when we create these two new overlay segments,
if we associate them with this transport zone,
they'll both be available;
both segments will be available for both of our ESXI hosts WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
both segments will be available for both of our ESXI hosts
who are also supporting that zone.
So now that we have our game plan together
and we've verified our existing topology,
in the next video,
let's create our first NSX overlay segment.
And that's gonna be segment number 10.