So let's start off with the big picture of
what we hope to accomplish.
Then we'll put a specific game plan together to get it done.
So currently we have these two ESXI hosts A and B,
which are acting as Host Transport Nodes.
And effectively what that means is they can
support NSX segments.
They can also build a tunnel between each other
to encapsulate and forward the traffic back and forth.
Again, that tunnel would be a Geneve tunnel.
Now, since the last skill where we deployed the ESXI host,
I had a little meltdown in my rack,
and so I had to reorganize a few things
and I had to rebuild it all from scratch. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I had to rebuild it all from scratch.
So here is my current topology, which is similar to
how we left it in the previous skill.
So we have ESXI-A and ESXI-B,
they currently have tunnel endpoints,
which I've statically configured
as 11, 11, 11, 11 here on ESXI-A
and 22 22, 22, 22 over here
on ESXI-B.
And I thought to myself "Self, if I was learning this,
what would I want to see as tunnel endpoints?"
I thought I would want see some very different IP addressing
and that way it'd be very clear
whenever we see this IP address to remember, it's associated WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
whenever we see this IP address to remember, it's associated
as a TEP, tunnel endpoint, with ESXI-A.
And this one over here is a tunnel endpoint for ESXI-B.
And each of those tunnel endpoints are associated
with a VM kernel adapter.
And in our implementation here, NSX chose
to use VMK10 on both sides
for their respective layer three interfaces.
And that's where that IP address is assigned.
The 11, 11, 11, 11 here on ESXI-A,
to the VM kernel adapter 10,
and over on ESXI-B, the 22, 22, 22, 22, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and over on ESXI-B, the 22, 22, 22, 22,
which is the tunnel end point over here on ESXI-B,
it's associated with VM kernel 10 over here as well.
So what I thought would be valuable
to do is let's validate those as we go
through this together just to make sure that
what we think is in place really is there.
So here is the login to the vSphere Client.
So I'll go ahead and log in.
And then while that's initializing, let's go over
to the NSX manager and we'll log in here, as well.
So here in the NSX manager, let's go to system
by clicking on the system tab up here at the top.
Now on the left we have system overview,
it's showing us that we have one NSX management node WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it's showing us that we have one NSX management node
and that's the NSX manager 11.
And then we have two transport nodes
that we added in a previous set of videos,
that's ESXI-A and B.
And we have three transport zones.
One of those we created on our own and the other two were
provided by default.
And on the left, if we click here on "appliances",
here it's showing us that our cluster is stable.
We only have one NSX manager node here,
but everything looks green.
And if we click here on "view details", we can confirm
that all the services are up and ready.
So we'll go ahead and close that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll go ahead and close that.
And then with systems still selected at the top on the left,
if we expand fabric, if we now go to hosts,
we can verify the details for ESXI hosts
that have been enabled as Host Transport Nodes.
Let's expand the cluster called Host Transport Nodes.
And here we have ESXI-A and ESXI-B.
And under IP addresses, if we click
where it says "two more",
it's showing us we have three addresses.
So the 192, 168, 1, 181, that's the management address.
The 10, 4, 0, 181 is an IP address associated with a
VM kernel adapter that I'm using for access to an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
VM kernel adapter that I'm using for access to an
iSCSI data store.
And this third one right here is the tunnel endpoint.
And if we go down to ESXI-B
and we click right here where it says "two more"
to see the addresses, there's 22, 22, 22, 22.
And to validate that also, we can go over
to the vSphere Client.
So here on the vSphere Client, if we go over to the host
and clusters view and we go to ESXI-A
and we go to configure.
And then here in the middle pane, if we go down
to VMkernel adapters, we can just verify that, as well.
So here's VMK10 with the IP address of 11, 11, 11, 11. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here's VMK10 with the IP address of 11, 11, 11, 11.
Lemme go ahead and make that column a little bit bigger.
There we go. That looks a little better.
So here for VMK10, click here on "IP settings",
there's its IP address with the 24 bit mask
and the default gateway is at 11.11.11.1.
And if you take a look at ESXI-B
and take a look at its VM kernel 10 adapter,
it's at 22, 22, 22, 22
with a default gateway of 22.22.22.1.
So this represents the Geneve tunnel that they can use
to encapsulate and de-encapsulate respectively, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to encapsulate and de-encapsulate respectively,
as they forward traffic back
and forth on behalf of the VMs on the various segments.
And when they build that tunnel,
they're gonna be using the transport network
to carry the actual packets.
So if these two ESXI hosts A and B are in different racks,
we could do something like this,
have the top of rack switches here, where ESXI-A is,
and a couple top of rack switches over here
where ESXI-B is.
And maybe we have the Uplink two go here,
And the Uplink three go here.
And Uplink two go here, and Uplink three go here
for redundancy.
So those are our top of rack switches. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So those are our top of rack switches.
I'll call it TORA for rack A. And maybe this is rack B.
So I've got a top of rack switches for rack B
and we're gonna have some connectivity between those.
So let me go ahead and put a router here.
So we can have a spine leaf architecture with the top
of rack switches being the leaf.
And then this device right here
that's gluing them all together with routing acting
as the spine, or one of our multilayer switches
that's participating as part of the spine layer.
And that would provide us fall tolerance from this ESXI
host going to two different switches here.
And the same thing for ESXI-B with two Uplinks going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the same thing for ESXI-B with two Uplinks going
to two different switches.
This could be switch one and switch two in rack A.
And this is the top of rack switch one
and two over here in rack B.
So just to confirm this, in our lab environment here we're
regarding the transport network,
lemme give you a sneak peek into the world of my top
of rack switch, which again is being implemented
by a Cisco Catalyst switch.
So lemme bring that in. Here it is right here.
So if I did a show IP route
for 11.11.11.11.
Press enter,
that's gonna show me from the routing table which route it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's gonna show me from the routing table which route it
would use to reach that destination address,
which is the tunnel endpoint over on ESXI-A.
And if we do the same thing
for show IP route for 22.22.22.22,
we should also have a route for that, as well.
In addition, I should also be able to ping those
because I have routes for them.
So let's do a ping to 11.11.11.11,
that's the tunnel endpoint for ESXI-A.
And if we do a ping to
22.22.22.22, that's the tunnel endpoint for ESXI-B.
So if I do a show IP route, I've got routes WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if I do a show IP route, I've got routes
for the 11 11 11 network and also the 22 22 22 network.
And in my lab environment, I'm doing the entire routing
through one catalyst switch.
And then I intentionally used multiple VLANs
and different subnets just to help reflect the concept
that these two ESXI hosts don't have
to be on the same subnet.
AKA, they don't have to be on the same layer two
broadcast domain for tunnel traffic to go back and forth
between them.
And let's also talk about and confirm the Uplinks
that our ESXI hosts are gonna use if they're gonna access WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that our ESXI hosts are gonna use if they're gonna access
the transport network to build these tunnels,
or in this case the single tunnel between ESXI-A
and ESXI-B with one TEP each.
In NSX we specify which Uplinks to use
and which VLANs to use in combination with those Uplinks
by creating and then using an Uplink profile.
And that Uplink profile is gonna specify for the ESXI host,
which Uplink or Uplinks we're gonna be using.
And we're also gonna specify as part
of the Uplink profile, which VLAN to use.
So my switched environment for all the connections
that are coming up to the ESXI host,
they're all set up as trunks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
they're all set up as trunks.
So that way if we wanna support any VLANs on the physical
network, we can use those right here.
So let's measure on the switch.
We have everything from one to 200 as far as VLANs go.
And we're trunking on all ports.
So if we have connections that go
to our trunked infrastructure right here,
that means we could choose to use any individual VLANs
we want to with 8020.1 Q trunking.
So for example, in our Uplink profile,
if we said we wanna use Uplink2
and we wanna use VLAN 101, we would specify that as part WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we wanna use VLAN 101, we would specify that as part
of the Uplink profile, including the fact we use this name
called Uplink2 and we wanna use VLAN 1.
And then when we configure ESXI-A or reconfigure
for that matter, ESXI-A,
we can simply specify that Uplink profile
and as a result, it'll use the specified Uplink that we map
to off of the physical host.
It'll also go ahead and use the VLAN that we specify
as part of the Uplink profile.
So if we specify it in the Uplink profile
that we wanna use VLAN 101 and Uplink2,
this ESXI Host Transport Node,
as it communicates on the transport network, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as it communicates on the transport network,
is gonna be tagging all the frames that go out the Uplink
with a 8020.1 Q tag of 101.
And that way the receiving switch on the physical network
can associate that with the correct layer two
broadcast domain and then perform the routing, for example,
to get from the 11, 11, 11s address base
to the 22, 22, 22 address base.