So for the host transport nodes in our nested environment,
we're going to use ESXIA and ESXIB as the two hosts,
which are going to have the NSX software or the NSX bits added to them.
So from the NSX manager, we select the cluster that these two hosts are in.
And as far as their configuration with our existing infrastructure for
networking,
here's what I did for ESXIA for the tunnel endpoint.
We're going to use 11, 11, 11, 11 with a 24-bit mask and a default gateway.
I've got one. We're also as part of that going to use VLAN 101. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I've got one. We're also as part of that going to use VLAN 101.
So I want to make sure the top of rack switch supports that.
And then for ESXIB, although it could be in the same exact subnet as ESXIA,
for learning purposes, I want to make sure I separated them.
So I put ESXIB with an IP address of 22, 22, 22 with a 24-bit mask
with a default gateway of .1 on that 22.22.22 network.
And the default gateway functionality is being provided by my top of rack
switch,
which is up here, which is also a really important reason to make sure we have
those VLANs supported and have the routing in place. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
those VLANs supported and have the routing in place.
And then on ESXIB, I'm using VLAN 102.
Once again, we could use the same VLAN, but to help differentiate them,
especially in the lab environment, when you pack it captures and so forth,
to see the distinct IP addresses and know exactly who owns those tunnel end
points is super useful.
Also for ESXIA, I'm using VMNIC 2 and for ESXIB, I'm going to be using VMIC 3.
So here to draw little arrows there that would look like this ESXIA is going to
be
using this uplink and ESXIB is going to be using this uplink. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
using this uplink and ESXIB is going to be using this uplink.
Now, because they're separate hosts, we could have also chosen to use the same
exact uplink on each of the hosts, but again, just to clarify who's going to
using what I
chose to implement it like this.
So as part of the configuration for the ESXI host to become transport nodes and
specify exactly which uplinks and VLANs we're going to use that's used as part
of an uplink profile.
So when I deployed ESXIA and ESXIB, I use an uplink profile that specified I
want to use one uplink.
And then I mapped that uplink over to the uplink I wanted them to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then I mapped that uplink over to the uplink I wanted them to use.
And as far as the lab environment, one of the first things we'd want to do
after we
deploy this is to verify from our top of rack switch that we can reach those
addresses.
So for my top of rack switch, I should be able to reach the 11, 11, 11, 11
address
and the 22, 22, 22, 22 address if everything is working correctly and these two
ESXI hosts are configured as host transport nodes.
So let me walk you through the verification of all that right now.
So to do that, I need to bring up the NSX manager as well.
So the NSX manager, which is running right here on my physical host, it has a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the NSX manager, which is running right here on my physical host, it has a
virtual
IP address associated with it of .10 on my management network.
So let's go there now.
So here is the login to the NSX manager.
I'll go ahead and log in and then here in the NSX manager, if we click on the
system
tab and then the left, if we expand fabric, here we have our profiles and then
a sub
for uplink profiles.
And here's the uplink profile I used in combination with ESXIA, which is going
to use VLAN 101 and uplink to.
And then here is the uplink profile I created that we're going to use in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then here is the uplink profile I created that we're going to use in
combination
with ESXI B, which we're using VLAN 102 and VM Mc3.
So I deploy the host, we'll go to fabric and hosts and we'll expand our cluster
here.
And let's just grab ESXIA as an example.
We'll click on the three dots and click right here on configure NSX.
So there's this management IP address for ESXIA.
We'll click on next and then we'll expand the configuration here.
So here's where I specified I want to use this uplink profile.
And then down below, here's where I map the uplink profile over to the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then down below, here's where I map the uplink profile over to the actual
name
of the uplink on the distributed switch.
So if we went back to this switch, the lab one NSX host, that let's do it real
quick.
So back in the OGAIT.lab vSphere client environment, if we go to our networking
here, if we click on our switch right here, lab one NSX host, we right click
and then
we'll go to settings and edit settings and uplinks.
And this right here, I've got my four uplinks named correctly.
So here, this is lab VM Nick two and that's the uplink we're choosing to map WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here, this is lab VM Nick two and that's the uplink we're choosing to map
as part of our uplink profile for ESXIA.
And then when we get to ESXIA B, we're going to go ahead and choose lab three
VM
Nick three for its mapping for its uplink profile.
So we'll click on cancel there.
Let's go back to the NSX manager.
And again, we're looking at the details for ESXIA.
So it's got this static IP address of 11 11 11 11 with the default gateway
and in dot one with a 24 bit mask, we scroll down.
Here's the logical uplink that we named inside of NSX and there is the name of
the uplink on our virtual distributed switch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the uplink on our virtual distributed switch.
It's also showing us a visual right here as well.
So we'll click on cancel and click on yes, we want to cancel and let's go take
a look
at ESXIA B on the three dots, click on configure NSX, click on next.
Let's go ahead and expand that.
So this is using an uplink profile called lab host V one oh two VM
three and then we're mapping that over to lab VM three on the actual virtual
distributed switch and if he's grown up a little bit here,
showing us the IP address we're using there and the mask and the default
gateway.
So we should be able to ping the addresses for the total endpoints on both ESX WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we should be able to ping the addresses for the total endpoints on both ESX
IA
and B from our top of RAC switch.
So here at the top of RAC switch, we did a ping to 11 11 11 11 11.
That's the total endpoint address for ESXIA.
We should also be able to ping 22 that 22 that 22 that 22, which is the
tunnel endpoint address for ESXIA B.
And since they're both reachable from the top of RAC switch,
that's a terrific indication that everything is working all the way from our
virtualized ESXIA host down here with their tunnel endpoint addresses all the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
virtualized ESXIA host down here with their tunnel endpoint addresses all the
way
to our top of RAC switch, which is going to the routing for the transport
networks.
So now that we've addressed the lab
topology to support our two host transport nodes in the next video, let's take
a
look at how we're going to implement our edge nodes in our nested topology.
So I'll see you in the next video for exactly that.