So it is time to create
our first overlay segment,
and that is this one right here, Overlay Segment 10.
We'll make sure that when we create it,
it's included as part of this transport zone
called Our A-B overlay Transport Zone.
So, with this topology and that idea in mind,
let's get to work in creating this new overlay segment.
Also, as a quick verification of what is about to change
when we create this new segment,
let's go to the vSphere Client.
We're currently there.
Let's go to the Networking tab.
And if we click on this distribute switch
called DS for NSX, and we click on Configure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
called DS for NSX, and we click on Configure.
And then I love this view, the Topology view
that gives a visual representation.
We have two uplinks associated with that distributed switch,
but there are no port groups
that we can use to connect clients to.
However, that's gonna change because once we create
the NSX segment for Segment 10, it'll show up here,
very similar to how a port group would show up.
So, let's head over to the graphical user interface
for the NSX Manager.
So, that is right here.
And to create a new segment,
what we're gonna do is click on the Networking tab up here.
And that provides us a beautiful network overview WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that provides us a beautiful network overview
with no Tier-O Gateways, no Tier-1 Gateways, no Segments.
(chuckles) And we're gonna change
that segment thing right now by creating one.
So, still with Networking selected
on the left hand side under Connectivity,
we'll click right here on Segments.
And with Segments selected and the tab for NSX selected,
we'll click right here on Add Segment.
So now, we have the opportunity to add a new NSX segment.
Now, we could do an overlay segment, which we're about to.
There's also an option for a VLAN-backed segment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's also an option for a VLAN-backed segment,
which we'll do in a later set of videos.
So for now, with Add Segment selected,
let's go ahead and name it.
And let's call it Seg 10
and I'm also gonna put the label of Yellow on there.
And that way when we see it,
we can correlate it better to our topology.
So, Segment 10 Yellow.
Let me also go ahead and move the left hand side
outta the way a little bit.
It'll give us a little more room here.
And currently we don't have any logical gateways set up.
So, we're not gonna link this segment to any gateways.
It's just gonna be a segment in NSX
that our ESXi transport host can use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that our ESXi transport host can use.
And we also need to associate this segment
we're about to create with the appropriate transport zone.
So, we wanna go ahead and use the dropdown here.
And here is our A-B Overlay Transport Zone.
And you'll notice that a segment
can only be associated with one zone.
So if we want a overlay segment,
we're gonna make sure we're including that segment.
This one we're creating right here in a transport zone
that is of type overlay as well.
So, here is our A-B Overlay Transport Zone.
And really, that's all we need to do at this point.
So we can just scroll down a little bit, click on Save. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we can just scroll down a little bit, click on Save.
And it's asking, "Do you wanna continue editing this?"
We'll go ahead and click on No.
And then, let's take a look at the details.
There's not too much here except for the fact it has a name.
It also has a zone that it's a member of.
And our two ESXi hosts
are both supporting that transport zone.
So, that means this segment should be available
to be used by VMs on either ESXi-A or ESXi-B.
So I'm gonna go ahead and click on Collapse All.
So here's our one segment.
Also, if we expand the left hand side here,
now we go to Network Topology.
Check this out. Oh, this is so exciting. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Check this out. Oh, this is so exciting.
I can almost not contain myself.
Here, we have a visual representation
of our network topology. (chuckles)
And so far in NSX,
it's just one segment called Seg 10 Yellow.
If we zoom in a little bit here, we can drag it around.
We can also drag it using this option here.
Either way is great. And so, there it is.
So, no VMs are connected, but it does exist.
So, if we made a road trip over to our vSphere Client.
This Seg 10 Yellow segment would show up WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and it kinda looks like a port group
under our distributed switch.
In fact, let's go take a look.
So, here in the vSphere Client
with the Network tab selected here,
if we look at our distributed switch for NSX,
we now have this new Seg 10 Yellow.
So, if we click on the distributed switch
and we go to configure and look at the topology,
and again, it kinda looks and feels like a port group
that you could associate VMs with,
except instead of being a normal port group,
this is a NSX segment, which is able
to span multiple ESXI hosts even on different subnets.
And the ESXi hosts supporting the segment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the ESXi hosts supporting the segment
are able to tunnel back and forth as needed
to forward the VM's traffic.
So, if we clicked on this Seg 10 Yellow
and take a look at the details
as far as what uplinks it's using.
It's using vmnic2 on both ESXi-A and ESXi-B.
And it's not using vmnic3.
And that's because the uplink profiles
that we associated with ESXi-A and B
didn't say to use vmnic3.
But instead they're using a single vmnic.
And that's vmnic2 on each of their respective hosts.
And in association with that, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And in association with that,
ESXi-A is using VLAN101 on its vmnic2,
and ESXi-B is using VLAN102
as we looked at in the earlier video.
Now, if we clicked on this Segment 10 here
inside the vSphere Client,
let's take a look at a few details here.
If we click on the Summary tab, it has this big N,
which represents it's an NSX segment.
There's also a smaller n right there in the icon.
And this is showing us the VNI,
that's a Virtual Network Identifier,
and that's 68608 that's assigned by NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that's 68608 that's assigned by NSX.
It's also showing us that this segment
belongs to this transport zone.
It's also showing us that the NSX Manager
who is managing and responsible for this segment
is reachable at 192.168.1.10.
That's the virtual IP address
we set up for NSX Management Cluster.
Here's the distributed switch
that this new segment is associated with.
And as we scroll down, it's also showing us
how many host transport nodes, effectively,
the ESXi hosts would have been enabled for NSX
are associated and have access to this new segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
are associated and have access to this new segment.
Also, if we go to the Configure tab,
unlike a normal distributed port group,
there's nothing really we can configure here
because all the configuration for this segment
is gonna be done over in NSX.
But once again, here it's showing the VNI number,
it's showing us the transport zone it belongs to,
and it's showing us the name of the segment as well.
If we clicked on hosts,
it would show us all the hosts associated with that segment.
So, ESXi-A and B are both host transport nodes
that have access to that segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that have access to that segment.
So, we could run VMs on those hosts
and have those VMs for their network connectivity
connect to that segment.
And then as far as VMs go, we have no VMs
that are yet associated with that segment.