So, in this video,
I'd like to walk through creating a pool
of addresses that can be used
if we're using VLAN 101,
and other pool of addresses
that we can use for tunnel endpoints
if we're using the network 10.22.22, and VLAN 102.
And then once we've created those pools of addresses
that can be used,
we'll also walk through the creation
of some uplink profiles.
We simply say,
hey, which VLAN do we want to use
for the transport network?
And which uplinks do we want to go ahead
and use on the ESXi hosts?
So, to do this, we're going to log into the NSX Manager, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, to do this, we're going to log into the NSX Manager,
and we're going to use the virtual IP address
that we set up,
which is at .10 on the management network.
So, I'll log in as admin, supply the password,
and click log in.
Also, one of the other things I definitely want to do
before we get too far along is
I want to make sure that this VM,
this NSX Manager VM,
is set to automatically power up
when my ESXi host comes up.
So, let's go back to the vSphere client just
for a moment.
And here at the vSphere client,
go back to the host and clusters view.
We'll go to our management cluster.
We'll go to ESXIC, and we'll go to configure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll go to ESXIC, and we'll go to configure.
Then in this middle column,
we'll go down to VM startup shutdown.
And currently, this is showing with this tab,
the automatic ordered and automatic.
Yeah, this little NSX Manager VM is not set for any kind
of automatic startup.
So currently, it's set up for manual startup,
which means it's not going to automatically power on
if I have to reboot the NSX host
for any reason.
So, to solve that, I'm going to click on edit.
And I'm going to go ahead and click here
on manual startup and select the NSX Manager VM, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
on manual startup and select the NSX Manager VM,
where the automatic startup is currently disabled.
And I'm going to go ahead and click here on move to.
And I want to move this to the automatic ordered.
So, it's removed from this list now.
Now it's under the automatic order
and it's in startup order number one.
Fantastic.
So, I want to make that change before we go any further
because it can take like 10 to 15 minutes
for this little VM to fully initialize.
And so, if it automatically is going to start it every time
the host is rebooted,
it's going to save me some frustration later.
So, with that set, I'll click on OK. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, with that set, I'll click on OK.
And then just to verify here,
if we click on the automatic ordered,
it's showing up right there.
That looks great.
All right, so what we want to do is go back
to the NSX Manager.
So, here we have the NSX Manager.
And let's go ahead and create some IP pools.
So, to do that, we're going to click
on the networking tab right here at the top.
Here is giving us a nice network overview.
We have pretty much nothing going on
as far as layer three routing or anything else.
So, what we're going to scroll down on the left,
we're going to go down under IP management
and click right here on IP address pools. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and click right here on IP address pools.
And then there's no IP address pools by default.
So, let's go ahead and create some.
So, click here on add IP address pool.
And let's name this pool.
I'm going to go ahead and call it 10.11.11.
So, I'll remember what it is just by looking at it.
And then we'll click right here
on set underneath the subnets column.
We'll click add subnet.
And let's do a range of addresses.
And how about for this one?
We'll do 10.11.11.151
through 10.11.11.200.
And that'll be 50 addresses that are available. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that'll be 50 addresses that are available.
Then also specify the length of the mask
with the cider notation.
So, it'll be in the 10.11.11.0 with a /24.
We'll hit tab.
And then for the gateway address, this is important
because if we have a device that gets an IP address
on the 10.11.11 network,
and it needs to route or reach some other destination,
it's going to need a default gateway.
So, the switch that we configured in the previous video,
it's at 10.11.11.1.
And that's the IP address we configured on it.
It'll act as the default gateway.
And then for the DNS servers, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then for the DNS servers,
we'll put the management DNS server
at 192.168.1.100.
We also want to make sure
that that's going to be reachable
by a client if it needs it.
And then for the DNS suffix,
let's go ahead and use ogit.local.
That's the suffix I'm using in my lab here.
All right.
So, we'll click on add.
And then we'll click on apply down here.
And then we'll click on save.
And boom, we now have a pool called pool 10.11.11.
Let's make one more
for the 10.22.22 network address space. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for the 10.22.22 network address space.
So, we'll click on the add IP address pool.
We'll call it pool 10.22.22.
We'll tab over a couple of times.
Click on set right here for the subnets
and click on add subnet.
And then click on IP ranges.
And let's use the range of 10.22.22.
And to be consistent,
let's just use 151 through 10.22.22.200.
And 50 addresses will be more
than enough for my lab environment.
And then for the network address space that we're in,
I'll specify it's 10.22.22.0 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll specify it's 10.22.22.0
with a 24-bit mask.
And then we'll specify the default gateway, 10.22.22.1.
That's the switched virtual interface
that we looked at in the previous video
on my multilayer switch on the physical network.
So, my DNS server is 192.168.1.100.
And the DNS suffix is ogit.local.
So, the actual DNS suffix
and the DNS server is going to be too critical
for our ESXi host if they're using this IP address space.
But what will be important is the default gateway should
the need to route or reach
another tunnel endpoint, for example, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
another tunnel endpoint, for example,
from ESXi A to ESXi B or vice versa,
that's on a different subnet.
So, I'll click on add here and click on apply,
and click on save.
And now we have two pools of addresses,
one called 10.11.11, one called 10.22.22,
which are both available.
So over here,
it says this second one is not yet initialized.
So, we'll click on the refresh button and boom,
now it's ready to go.
Now, the way we communicate to an ESXi host
about which of the uplinks it should use
for the NSX traffic,
we are going to use what's called an uplink profile. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we are going to use what's called an uplink profile.
So, that'll be our next step,
and let's create three of them.
We'll create one uplink profile that says
to ESXi-A use these two ports
and VLAN 101.
We'll create one uplink profile
that we're going to use with ESXi-B that's going to say
use these two uplinks and VLAN 102.
We'll also specify the appropriate IP address.
We'll also create a third uplink profile in the event
that we want to configure a whole cluster
of ESXi hosts as transport nodes
all at the same time.
And if we do that, we then could refer
to the common uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to the common uplink profile
that they would then both use.
So, let's go back to the NSX manager
and let's create our uplink profiles.
So back here at the NSX manager,
the question is where are the uplink profiles kept?
Where do we go to configure them?
And the answer to that is by going here to system.
And here at the top with system selected on the left,
we are going to expand the fabric
section here.
And with fabric expanded,
we're going to click right here on profiles.
So, here are profiles.
Instead of using one of the default ones WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Instead of using one of the default ones
that's currently in place, let's create one.
In fact, we're going to create three.
We're going to create one for ESXi-A, one for ESXi-B,
and also one that we could use
if we're configuring a whole cluster at the same time.
So, for this first one, let's call it ESXi-A uplink V101
to represent that we are going
to be using VLAN 101 for the transport network
if this uplink profile is called upon.
And then if we're using link aggregation,
think of like link aggregation control protocol
and ether channel bundles in the world of Cisco. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and ether channel bundles in the world of Cisco.
If you have those set up and you want
to use those link aggregation groups,
you could specify them here in my lab environment.
I'm simply using single interfaces.
So, we're going to go down to teamings
and we're going to simply use
the default teaming method.
So, here the current default method here
is failover order.
So, it's going to use the active uplinks,
whatever we have set here, followed by standby.
So, if we want to change that, we could double click,
and you could say I want to load balance
based on source or load balance based
on source MAC address.
But for our purposes, we want to failover order,
and I want to use a single uplink because WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I want to use a single uplink because
that's going to give us a single tap, a total endpoint,
and that's going to make it much easier to track.
So, for ESXi-A,
let's go ahead and call the first active uplink.
Let's call it use-VMNIC-2.
And that's also going to help remind me
which interface on the distributed switch I want
to go ahead and use, which is going to be VMNIC 2
for the first one, then for the standby.
I'm going to go ahead and give this a label
and I'm going to call this standby.
And I'll put a dash three
there just to remind myself this can be VMNIC 3.
So, these labels are just associated WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, these labels are just associated
with this uplink profile, and they don't really
mean anything until we use this uplink profile,
specifically called ESXi-A uplink with V101.
And we apply that in association with a transport host.
So currently we have a name,
we've specified the active and standby links here,
the labels for them anyway.
And then down here,
we also want to specify the transport VLAN to use.
So, for ESXi-A, if we want it to use VLAN 101
for the transport network, we want to go ahead
and put the transport VLAN 101 right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and put the transport VLAN 101 right here.
And because with the current flavor of NSX,
if we're using a virtual distributed switch
in vSphere, which we are, and it has a huge MTU,
we don't need to do anything
about the MTU right here because the MTU, as it says,
is not applicable for a virtual distributed switch.
But at the same time, we also want to make sure
that in the physical environment that
we can support frames larger than the default of 1500.
So, in the physical environment,
I've got my Cisco switch set up
to support 9,000 for the MTU.
And when we deploy our distributed switch in vSphere, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And when we deploy our distributed switch in vSphere,
we'll also set up a larger than default MTU as well.
So, we'll click on add, and then we will check our work.
So, for this profile called ESXi-A uplink with V101,
we're using the transport VLAN of 101.
Fantastic.
And then we scroll down,
we have our active uplink label
and our standby uplink label set up.
And that looks great.
So, let's make one more for ESXi-B.
So, we'll click on plus, and we'll go ahead
and say this is going to be ESXi-B, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and say this is going to be ESXi-B,
and I see a little copy paste action there with VLAN 102.
I'll scroll down.
I want to use VLAN 102 for the transport
for this profile because we're going to associate
this with ESXi-B.
And for the actual uplinks,
let's go ahead for the active uplink, let's go ahead
and use DOS to remind myself in Spanish
that I want to use uplink number two.
And for the standby, we'll use trace,
which is going to help mostly remind me
that we are going to be using VMNIC 3.
So again, in the uplink profiles, these are just labels, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So again, in the uplink profiles, these are just labels,
which when we apply the uplink profiles,
we'll associate with the actual uplinks
on our distributed switch.
So, we'll go ahead and click on add,
and then we'll verify our work.
So, for this uplink profile, ESXi-B uplink with V102,
our VLAN is 102.
That looks great.
And for the teamings, I've got the first label
and second label for the active and standby.
That looks fantastic.
And let's make one more that if we choose
to deploy a whole cluster of ESXi hosts
and make them transport nodes, we could refer to this. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and make them transport nodes, we could refer to this.
So, we'll call this uplinks for cluster.
And again, I don't have any link aggregation going on,
so I'll go ahead for the teamings
and I'll say for the teamings,
let me go ahead
and specify that instead of using a failover order,
I wanna do load balancing.
And let me put them both right here.
So, I'll put two comma three, just as labels once again,
to remind myself of which VM NICs,
I hope to actually associate with those.
And I intentionally made the actual labels here different
on each of the uplink profiles.
So, if we are going to use this uplinks for cluster profile, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, if we are going to use this uplinks for cluster profile,
what VLAN do we want to use?
Let's just double up on VLAN 101.
So, I'm going to add that to the title as well,
just to remind myself when I see it
about exactly which VLAN we're going to be using.
If we choose to use this uplink profile called uplinks
for cluster V101, and we'll click on add,
then I'll verify my work there by clicking on it,
and just verifying transport VLAN 101,
and labels two and three for two active uplink.
So, if we did use this uplink profile,
because we have two active uplinks, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because we have two active uplinks,
it's going to end up with two tunnel endpoint addresses,
one for each of the active uplinks.
So, at this point, we have our uplink profiles created.
We haven't applied them yet to either of the ESXi host,
but we'll get to that.
But we do have the uplink profiles ready in the wings.
We also have a couple of pools of IP addresses
that we can pull from one in the 10.11.11 range,
one in the 10.22.22 range.
And so, for our next step,
we are gonna create a new overlay transport zone.
And just like our uplink profiles, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And just like our uplink profiles,
they're really not going to be doing too much until
we associate these objects,
including the uplink profiles and the transport zones,
until we associate them
with an ESXi host that's been enabled for NSX,
which is now going to be called a host transport node.
So again, this is all in preparation
for the actual deployment where we'll configure
our ESXi host.
So, join me in the next video
as we create a brand-new transport zone
that we can use as part of our configuration.