So in this video,
I'd like to go ahead and take care of both of these items
because one is just a couple clicks
and that is to create a brand new overlay transport zone
inside of NSX.
So that'll be just a couple clicks to create one.
And then secondly,
let's go over to the vSphere client using vCenter
and let's create a new distributed switch in vCenter
that we will then use in the future for the purposes of NSX.
And when we do so, let's also set the MTU
to an MTU of 9000,
which goes above and beyond the requirement
of a minimum of 1700 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of a minimum of 1700
because of the encapsulation requirement
with the tunnel end points as part of the GENEVE tunnels.
So if we set the MTU to 9000,
we'll have plenty of room to spare.
So back to the NSX manager we go,
so we left off under System and Profiles
and Uplink Profiles, and we created three uplink profiles,
which are right here.
And to create a brand new transport zone,
we're gonna stay right here at System.
But on the left under Fabric,
we're gonna go down one more below Profiles
to Transport Zones.
So there is a default overlay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So there is a default overlay
and VLAN backed transport zone,
but we're gonna create our own.
So let's go ahead and click on Add Transport Zone,
and let's call this Our A-B Overlay TZ, for transport zone.
And that way when we see it, we'll know,
"Oh, that's the one we created."
And then for the type of transport zone, there's two types.
One that's gonna support NSX segments
that are overlay segments
where the traffic is being tunneled or can be tunneled,
and the other's four VLAN-backed NSX segments. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the other's four VLAN-backed NSX segments.
So what we're gonna do is we're gonna set up
a new transport zone called this
that is gonna support overlay network segments.
So think of the overlay as the process
of using the GENEVE tunnels
to take VMs traffic or user's traffic,
encapsulate it and be able to send it over the tunnel.
So once we have this new overlay zone created,
then we can specify which ESXi host transport nodes
are gonna be supporting and included as part of this zone.
And then furthermore, when we create overlay segments,
we can associate those segments within a zone. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we can associate those segments within a zone.
So all we have to do is name it, specify the type,
and we don't have to specify any limitations
regarding VLANs or anything else,
and we'll click on Save.
So there it is right there.
And for the second part of this video,
we are going to create our distributed switch
that we're then going to use with NSX.
So to create the distributed switch,
we'll use the vSphere client connected to vCenter
to create that distributed switch,
and we'll name it DS for NSX,
and we'll set the MTU to 9000.
So we're gonna hop over to the vSphere Client.
So here at the vSphere Client, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here at the vSphere Client,
we're logged on as Administrator@VSPHERE.LOCAL.
Here in the vSphere Client,
we'll click on the Networking tab.
And we currently have one virtual distributed switch.
It's called VDS for management.
And what we wanna do is we wanna create
a new distributed switch.
So to do that, we'll right click on our DataCenter
from the dropdown, we'll click on Distributed Switch,
and from the submenu, we'll click on New Distributed Switch.
And based on our game plan, we'll call it DS for NSX,
and click on Next.
And then we'll choose the latest, greatest version
of the distributed switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of the distributed switch.
Fantastic.
we'll click on Next.
And as far as the settings,
for this distributed switch,
we want to have at least two uplinks.
So I'm gonna go ahead and say two uplinks
are gonna be included as part of this distributed switch.
And then I also am not, for the moment,
going to create a default port group
and there's a couple reasons for that.
One, we could.
We could create a default port group,
but I'm gonna have all of the segments
that show up as part of NSX,
they're gonna show up as if they are port groups
under this distributed switch.
So they're called segments,
but they kinda look and feel a lot like port groups. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
but they kinda look and feel a lot like port groups.
So I'm not gonna create a default port group
and click on next and then click on finish.
So now, if we go do our distributed switch,
I also wanna make sure that we set it up
with an MTU of 9000.
So I'm gonna right click on our distributed switch
and click on the Settings option here,
click on Edit Settings right there.
And then specify under Advanced
that we want it to not use the default of 1500 bytes,
but rather 9000.
And that will more than cover the requirement of 1700.
And then also while we're here,
I'm gonna enable Link Layer Discovery Protocol, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm gonna enable Link Layer Discovery Protocol,
both sending and receiving,
and then also for our uplinks,
instead of calling 'em Uplink 1 and Uplink 2,
I wanna make it really clear
when you see these and when we map the uplink profiles
to the uplinks on the distributed switch,
I wanna be very clear on which ones these are.
So here, I'm gonna label this as DS vmnic 2,
and here, I'm gonna call the second one DS vmnic 3,
And that way when you see those terms, you'll know,
"Oh, those are the actual names of the uplinks WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
"Oh, those are the actual names of the uplinks
on the distributed switch."
And then we'll take a further step in a moment
and we'll bring on our ESXi host
and map those two uplinks
to their respective vmnic 2 and vmnic 3 interfaces.
So let me just check my work real quick here.
So under General, we're good.
Advanced, 9000.
Link Layer Discovery Protocol, both directions.
And then two uplinks, that looks great.
So we'll click on Okay.
And now for that distributed switch,
if we click on Configure
and we click on Topology, there it is,
so we have this logical distributed switch,
absolutely no port groups whatsoever here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
absolutely no port groups whatsoever here
for VMs or for VM kernel adapters.
And over here on the right, we have two labels,
but there's no network interface cards
associated with either one of them.
So to fix that, we are going to onboard our two ESXi host,
A and B, and have them both participate
with this distributed switch.
So to do that,
we're gonna go ahead back to the distributed switch,
right click on that distributed switch,
and from the dropdown click Add and Manage Hosts.
And then here, we'll click on add hosts
because we currently don't have any hosts WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because we currently don't have any hosts
that are using this distributed switch.
We'll click on next.
And then let's bring in A and B.
So host C and D are both in our management cluster,
and we really don't need them
to use this distributed switch.
We're just gonna have A and B use it.
So we'll select A and B, we'll click on Next.
And then regarding which of the physical uplinks
we want to associate, it's a good thing I named them.
So if we go to vmnic 2 here
and use the dropdown DS vmnic 2 is the label
on the distributed switch,
which we are gonna map to vmnic 2 on both those hosts. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
which we are gonna map to vmnic 2 on both those hosts.
And then for vmnic 3, we're gonna map that
to this uplink label called DS vmnic 3.
And that looks good too.
We'll click on Next.
And I'm not gonna bring over any VM kernel adapters.
I'm gonna leave them where they're at.
And I'm also not gonna migrate any virtual machines.
I'm gonna leave them where they're at,
and we'll click on Next.
Here's a summary, two hosts with two adapters each
for a total of four physical adapters being mapped
as part of this distributed switch.
And we'll click on Finish,
and we'll go ahead and refresh this.
And now if we expand the uplinks here,
we have this labeled DS vmnic 2 with two uplinks, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we have this labeled DS vmnic 2 with two uplinks,
one on esxi-a and B using vmnic 2 on each.
And then for the labeled DS vmnic 3,
we have two uplinks, one on esxi-a and one on esxi-b.
That looks great.
We can also verify that
with the distributed switch selected,
clicking on Hosts, verifying we have the two hosts here,
that looks great.
We could also go to the individual hosts,
then we'll select esxi-a
click on Configure and Virtual switches,
and there it is right there.
So currently, there's no port groups
or anything else using that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or anything else using that.
And if we look at esxi-b, very similar.
If we go to esxi-c,
it doesn't have that new distributed switch at all
because we didn't associate that distributed switch
with esxi-c or esxi-d.
So now if we go back to the Networking tab,
we have this new distributed switch called DS for NSX.
If we click on Configure and Topology,
gives a bird's eye view of the network interface cards,
the vmnics on each of the ESXi hosts
that are participating as part of that distributed switch.
And that means that our last step is this one right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that means that our last step is this one right here,
where we're going to go to the NSX manager
and specify that we want to include ESXi-A and ESXi-B
and install the NSX software on them,
thus making them host transport nodes in our NSX ecosystem.
So we'll go ahead and do the deployment of the NSX
on those two hosts in the very next video.
So I'll see you there in just a moment.