So, our last step
is now to go ahead to the NSX Manager
and specify that we want to take ESXi-A and ESXi-B
and configure them for NSX
to effectively make them host transport notes.
So, let's go to the NSX Manager and let's do that right now.
So, back here at the NSX Manager,
we're now logged in once again.
If we click on the System tab,
which is where we need to go to add host currently,
we have one NSX management node
and no host transport nodes, but that is about to change.
So, to add our ESXi host and bring them into the fold, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, to add our ESXi host and bring them into the fold,
what we're gonna do is with the System tab selected,
on the left-hand side,
we'll expand Fabric if it's not already expanded,
and then click right here on Hosts.
So, this interface is slightly updated
and different than it was like with 4.0.
So, they move things a little bit around
as they've updated the software,
but that's where you go currently in the interface.
So, System, Hosts.
And currently, it's showing us all the clusters
that it knows about courtesy of vCenter.
So, we integrated a compute manager in an earlier step WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, we integrated a compute manager in an earlier step
and as a result of vCenter
and the integration there between NSX and vCenter,
that's why it knows that these hosts exist.
So, we wanna configure NSX on these two hosts.
So, if we wanted to do them in one fell swoop,
what we could do is we could go to Transport Node Profiles,
click on add Transport Node Profile,
and then put all the details here.
And then, simply when we bring the whole cluster in,
specify this Transport Node Profile.
However, for the demo,
what I'd like to do is walk through this one by one.
And that way, we can also specify WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that way, we can also specify
individual Uplink Profiles, one for ESXi-A
and a different one for ESXi-B,
which include different subnets and different VLANs.
So, that's what we're gonna do here.
So, lemme go ahead
and minimize this on the left to move it over a little bit.
Gives us a little more room.
And so, instead of clicking here and saying,
I want to configure NSX for the entire cluster,
I'm gonna go ahead and start with ESXi-A by selecting that.
And then, with ESXi-A selected right there,
we'll click configure NSX.
So, now, it's walking us through the wizard.
So, we'll click on next.
It's asking us WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's asking us
about which distributed switch in vSphere we wanna use.
So, currently, we have a visual
over here on the right. (chuckles)
So, we'll click on add host switch,
and then from the dropdown,
we'll specify the distributed switch we wanna use.
So, the VDS for management,
we're using that for management only.
And the DS for NSX,
that's the distributed switch we just created.
That's the one we wanna use as part of NSX.
And then, for the transport zones,
we'll go ahead and click here.
And we are gonna use our A-B Overlay transport zone.
So, when we configure host B, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, when we configure host B,
we'll also have it included
in supporting this transport zone.
And we could add multiple transport zones
that this ESXi host is gonna support.
I'll just use this one for now.
And then, for the Uplink Profile, we'll click here.
And we'll specify the Uplink Profile
we wanna use with E ESXi-A,
which is gonna use vmnic 2 as the active uplink
and vmnic 3 as the standby.
It's also gonna be using VLAN 101 for its transport,
and that's all configured as part of the Uplink Profile.
So, we'll select that Uplink Profile,
and then we'll continue configuring.
So, as far as the IP address type, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, as far as the IP address type,
we want IPv4 or IPv6 for the tunnel endpoint.
And we're gonna be using IPv4.
And now, it says, okay, great,
what kind of IP address do you wanna use?
Do you wanna use an IP address from a pool?
So, we could pull from our pool,
for example, the Pool 10.11.11.11.
Or we could say, you know what?
I wanna go ahead and use a static IP address,
and then just configure it right here.
So, initially, I'd like to go ahead
and use a static IP address of 10.11.11.11.
So, that way, when we see it, we'll know,
oh, that is the tunnel endpoint for ESXi-A. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
oh, that is the tunnel endpoint for ESXi-A.
It'll be very clear,
because it'll be the only tunnel endpoint
in that subnet of 10.11.11.
So, if we hit the Tab key
and now wants to know the default gateway, so 10.11.11.1.
That's my layer three logical IP address
on the multilayer switch that ESXi-A can go ahead and use
for routing to reach the other tunnel endpoint,
which will be on ESXi-B.
And then, for the mask, it's a 24 bit mask that we're using.
So, we'll put that in in dotted decimal.
And then, we'll scroll down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then, we'll scroll down.
And now, here is where we're going
to associate the two network interface cards.
So, these labels right here are the two labels
that we used as part of our Uplink Profile.
And these here represent the labels
that we have on the distributed switch.
So, for vmnic 2, I wanna go ahead and use DS vmnic 2.
That's the label for the first uplink
on the distributed switch.
And we're gonna use DS vmnic 3 as the second uplink.
So, again, these are the labels here on the left
from the actual Uplink Profile,
and these are the labels WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and these are the labels
of the uplinks in the distributed switch.
And so, we're mapping them together.
And we'll scroll down, and then we'll click on add.
So, that add was for the mapping of the VDS uplinks
to the actual uplinks inside of the Uplink Profile in NSX.
And then, over here on the right, check it out.
It gives us a beautiful diagram of exactly that.
So, it's showing us the labels here.
And these labels on the bottom are the labels in NSX.
And the labels above that are the labels
associated with the actual distributed switch itself.
All right, so we'll click on finish and it is on its way. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right, so we'll click on finish and it is on its way.
So, for ESXi-A,
if we click right here on the NSX Configuration section,
it's at 6% and it's gonna go through this entire list
as it does the configuration.
I say it, as NSX Manager
implements this configuration over on ESXi-A.
So, I'm gonna repeat the process for ESXi-B,
except we're gonna simply use a different Uplink Profile,
but we'll use the one that we created just for ESXi-B.
So, we'll select ESXi-B,
we'll click here on configure NSX,
and then we'll go through the menu here as well.
We can do this one a little bit faster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We can do this one a little bit faster.
So, we'll specify the host switch.
We wanna use the DS for NSX.
We wanna go ahead and support this transport zone.
We wanna use this Uplink Profile called ESXi-B.
And for the IP dressing, we wanna use a static address.
And then, for the IP address for ESXi-B,
we're gonna use 10.22.22.22.
And then, the default gateway is gonna be 10.22.22.1.
And the subnet mask is a 24 bit mask,
so we'll put that in as well.
Then, we'll scroll down and then we'll do the mappings here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then, we'll scroll down and then we'll do the mappings here.
So, on the Uplink Profile for ESXi-B,
I call the two uplink labels dos and tres.
And now, here, we'll specify the actual uplinks
on the distributed switch
that we wanna map to those uplinks.
So, I'm gonna use vmnic 2 and vmnic 3 and click on add.
And then, it gives us the graphic over here on the right.
Fantastic. And we'll click on finish.
All right, so it is on its way.
So, it is at this step
and it'll be going through all these steps as well.
Now, once it's done,
it's gonna create new VMkernel adapters on our ESXi host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it's gonna create new VMkernel adapters on our ESXi host
that will act as the logical layer three endpoint
for the tunnels with the IP addresses
that we specified as part of the configurations.
So, if we popped over to the vSphere client
and we went to our host, let's go to ESXi-A
and let's go to Configure.
And let's take a look at VMkernel adapters.
Currently, it has two VMkernel adapters.
One I'm using for management,
one I'm using for access to an iSCSI data store.
And if we look at ESXi-B, very similar,
it's got one VMkernel adapter zero
associated with its management IP address, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
associated with its management IP address,
another vmk1 that's associated with the iSCS network
for access to the iSCS data store.
However, when NSX is done
with the configuration on these two hosts,
effectively making them host transport nodes,
it's gonna have additional VMkernel adapters
on each one of them, including a VMkernel adapter.
I think it starts with vmk10.
It's gonna have a VMkernel adapter of 10
with the address that we signed for the tap.
So, for ESXi-A,
it's gonna be a new VMkernel adapter with 10.11.11.11.
And for ESXi-B, it's gonna be a new VMkernel adapter WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for ESXi-B, it's gonna be a new VMkernel adapter
with the IP address of 10.22.22.22.
So, whenever those ESXi hosts need to send traffic
to send through their tunnel,
they'll be using the layer three interfaces
associated with the tunnel endpoints
or the tunneling of the traffic between the two hosts.
So, if we hop back to the NSX Manager,
let me expand the left-hand column real quick.
Just to remind us where we would configure this,
we go to System, on the left under Fabric, go to Hosts,
and then click on the ESXi host you wanna configure,
and then click on configure NSX and you're off to the races.
Now, in the event that you do wanna do a whole cluster WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, in the event that you do wanna do a whole cluster
at the same time, you can simply put a check mark
next to the cluster, click on configure NSX.
It'll ask us what Transport Node Profiles we wanna use.
We could actually create one right here
by clicking on Create New,
or we could use one that we already created.
And effectively, the Transport Node Profile
has all the details such as the Uplink Profile to use,
which distributed switch to use,
the mappings between the distributed switch, uplink ports,
and the uplinks as part of the Uplink Profile.
So, we could pre-configure all of that right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, we could pre-configure all of that right here,
and then use that when we're configuring a cluster.
In fact, while we're waiting for the deployment to finish,
let's just create a transport node profile,
so you can see what it looks like.
So, we'll call this a TP for transport profile for cluster.
And then, regarding the host switch we're gonna use,
we'll go ahead and click on add to add one.
We'll specify that we're gonna use our vCenter.
Then, we'll specify the DS for NSX,
same exact type of information
we supplied individually for each of our ESXi hosts.
But now, we're doing it in a profile that we could use,
sort of like a template
to do a whole bunch of hosts at the same time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to do a whole bunch of hosts at the same time.
Then, for the transport zones, we could say we want,
based on this template, if it's used,
to use that transport zone or support that transport zone.
We could then select the Uplink Profile.
So, we choose the Uplink Profile we want them to use.
And then, based on that Uplink Profile,
we could go ahead and specify the uplinks we wanna use.
So, there's DS vmnic 2 and DS vmnic 3.
For the labels on the Uplink Profile of 2 and 3.
And because in this Uplink Profile,
we have two active uplinks, if we use this,
it would have two tunnel endpoint addresses WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it would have two tunnel endpoint addresses
for each of the hosts that we apply this to.
And then, for IPv4 address assignment,
because as a template, we don't have the option
of a static address assignment,
because we're gonna be applying this
to a whole bunch at the same time.
So, we can say, please use the IPv4 pool.
And then if we use that option,
choose the pool we wanna pull from.
And then, we did the mappings right here.
And then, we'll go ahead and click on add,
and then click on apply and click on save.
So, now, we have this transport profile set up
with a lot of those questions answered.
So, if we went back to our clusters in the future,
if we wanna configure a cluster, for example, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if we wanna configure a cluster, for example,
let's say we wanna configure
all the devices in this management cluster.
We put a checkbox here for the management cluster,
click on configure NSX.
It's gonna ask us which Transport Node Profile we wanna use.
We'll select that one. Then, we click on save.
And then, it would apply those settings
that we have in that transport profile
to all of the hosts in that cluster.
So, for our demo, I don't wanna configure
any of the two ESXi hosts
in our management cluster with NSX,
because we're gonna save that just for the two
that are in the host transport nodes cluster. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that are in the host transport nodes cluster.
So, we'll let that completely finish.
Looks like ESXi-A is mostly done.
Now, currently, the status here shows as Unknowns.
We'll click on refresh.
And what we're looking for
is we want green across the board here
for the NSX configuration and also for the status.
So, it may take 15 to 20 minutes
to fully initialize and be ready to go.
We could also scroll to the right,
and there's an option here for View Details.
So, if we click on that, it's looking pretty positive.
It's getting closer and closer.
So, here's the name and the IP addresses involved.
So, this address right here, the 10.11.11.11, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, this address right here, the 10.11.11.11,
that's the tunnel endpoint address.
This can be used for the GENEVE tunnel.
And then, over here, we have a nice visual.
So, if we scroll to the right a little bit,
it's gonna show us the switch we're using,
the vSphere switch,
the distributed switch we're using as part of NSX.
It's also showing us the uplinks.
So, here we have the two labels
for Use-vmnic-2 and Standby-3.
And specifically, they're being mapped to the uplinks
that lead to vmnic 2 and vmnic 3 on ESXi-A.
And then, if we click on Monitor, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then, if we click on Monitor,
it shows us details about that ESXi host,
including system memory
and connectivity to the NSX controller.
And that's all great.
Now, also because it is mostly configured,
oh, look at that, says Down, let's click on refresh here.
So, what we're looking for is Success and Up.
So, looks like it's completely done for both ESXi hosts.
So for it's IP dresses, if we click here,
it's gonna show us the IP addresses in use.
So, that's an IP address
it has on its management interface on vmk0.
This is an IP address
that I have associated with vmk1 for iSCSI access.
And this is the IP address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And this is the IP address
that it has on the new VMkernel adapter
that NSX deployed on this ESXi host.
So, if we're gonna do the same thing for ESXi-B
and click here on 1 more, it should have that IP address
for its tunnel endpoint at 10.22.22.22.
And if we go over to the vSphere client for a moment
and take a look at those two hosts,
if we click on ESXi-A and click on Configure
and VMkernel adapters,
there we have vmk10 with the IP address, 10.11.11.11.
And if we go to ESXi-B,
there's its IP address of 10.22.22.22. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
there's its IP address of 10.22.22.22.
So, if we go back to the NSX Manager,
and now under System,
if we clicked on System Overview here on the left,
we now have still one NSX management node,
and now we have two host transport nodes,
and that's ESXi-A and ESXi-B, which are ready to rock.
Now, the challenge is with these hosts,
if we click on host here on the left-hand side under fabric,
and we expand the host transport nodes cluster,
even though they have their tunnel endpoints,
check this out.
Under Tunnels, it says tunnels Not Available. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Under Tunnels, it says tunnels Not Available.
Now, one of the reasons
there may not be any tunnels in place
is because we don't need any tunnels at the moment.
We don't have any NSX overlay segments.
We don't have any VMs connected to those segments.
So, the ESXi hosts are saying,
well, you know, we have the tunnel endpoints.
We could build the tunnels,
but we really don't need to at this point,
until we have a NSX overlay segment to support.
And have no fear, because in the next skill,
we'll walk through the process
of creating a segment, an overlay segment,
putting some VMs on that segment,
and take a look at that tunnel take off. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and take a look at that tunnel take off.
We'll also have a better opportunity
once we create a segment to analyze the traffic flow
as traffic is being sent back and forth
between two ESXi transport nodes
in an NSX environment using a GENEVE tunnel.