So in this video I'd like to do a quick verification
of the infrastructure.
So even though I am using some nested virtualization here
at the very backend on the physical network,
we need to make sure we have those VLANs in place,
including VLAN 101 and VLAN 102.
And I also wanna make sure I have routing in place
between 10 11 11
and 10 22 22 here on the physical network.
So for the physical infrastructure,
one of my devices is a Cisco Catalyst switch.
So let's go to the interface on the Cisco Catalyst switch
and let's verify our physical infrastructure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and let's verify our physical infrastructure.
Alright, so here on this Catalyst series switch
from Cisco system, let's do a show VLAN brief.
I wanna make sure I have VLANs 101 and 102
and I currently, do they exist?
That's a good thing if we want that traffic to be forwarded.
And let's also verify my logical
layer three routed interfaces on this multi-layer switch
because we're gonna need to route traffic
between the subnets on VAN 101 and 102.
So if we wanna use the 10 dot 11 dot 11 address base
and 10 dot 22 dot 22, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and 10 dot 22 dot 22,
I wanna make sure I have routing capabilities
on my physical network between those.
Let's do a show IP interface brief.
And I'm gonna say please exclude anything
that has the word u n a s s i in it short for unassigned
and oh, I'm glad I checked.
Look at that. So these are my logical layer three interfaces
on this multi-layer switch.
And if we wanna use 101 or 102,
I've got those IP addresses,
the default gateways in different VLANs.
So I need to rearrange my IP addresses here
for a little bit. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for a little bit.
So to do that I'm gonna go into configuration mode.
I'm gonna say please default interface VLAN 105.
That's gonna wipe out the IP address there.
And let's also wipe out the one on 106
because I wanna use those same IP addresses
on interface VLAN 101 and 102 respectively.
So now if we do a show IP interface brief,
and I'm doing a little due command
because I'm in configuration mode.
So we'll do a show IP interface brief pipe.
Please exclude anything that has word unassigned in it
and fantastic. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and fantastic.
So now I can assign the addresses here to interface
via that 101 and 102.
So previously, if I had attempted that,
it would've said you have an overlap IP address
with two different interfaces
on the same subnet in the same VRF.
So let's go to interface VLAN 101
and we'll give the IP address of 10 dot 11 dot 11 dot one
with a 24 bit mask and we'll go into interface VLAN 102
and give it the IP address of 10 dot 22 dot 22 dot one.
And so we'll use that IP address as the default gateway
because this multilayer switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because this multilayer switch
will be acting as the default gateway.
We'll give that a 24 bit mask
and then we'll do a quick verification
with the show IP route just to verify
that those are in the routing table.
So here we have the 10 11 11 network
being supported by interface VLAN 101,
and then we have the 10 22 22 network.
And that's being supported by interface VLAN 102
each for their respective VLANs.
And those IP addressing spaces
are in those respective VLANs.
And on a Cisco switch, the interface VLAN 102
is logically like hovering in VLAN 102. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is logically like hovering in VLAN 102.
The same thing for interface VLAN 101.
That logical layer three address is hovering existing
in VLAN 101.
So any devices in VLAN 101 can use that IP address
10 11 11 one
as their default gateway when they need to forward traffic.
Alright, so I'm glad we checked.
Alright, so now the infrastructure currently has VLANs 101
and 102.
Plus there's a default gateway at dot one
on both of the IP subnets associated with those two VLANs.
And the other thing I wanna do is verify WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the other thing I wanna do is verify
that my ports involved connecting to ESXi-A
and ESXi-B that I'm supporting trunking.
Now again, behind the scenes
I am doing nested virtualization,
but at the end of the day a lot of that traffic
does actually hit my physical network.
So I also wanna make sure
that on my physical network I have these ports
set up as trunks.
So back at the switch we do a show interface trunk
and press enter.
Pretty much all these ports are trunking
and allowing all these VLANs.
So every port that is connected up to an ESXi host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So every port that is connected up to an ESXi host
is trunking and here are the VLANs that are being supported.
Most important here are the VLANs 101 and 102,
which we'll be using for each of our ESXi host
as they're being updated to becoming transport nodes in NSX.
So from the physical perspective
on the physical transport network, this looks great.
So regarding checking the physical infrastructure,
which I'm super glad that we did,
so we now have a default gateway on the 10 11 11 network
and also the 10 22 22 network.
Now as part of configuring our ESXi hosts WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now as part of configuring our ESXi hosts
and training them on which uplinks they should use.
It's also gonna ask us at that point as part of the profile,
which VLAN we wanna use for the transport.
And that information is configured
as part of an uplink profile
that we're gonna associate with our host.
So, on ESXi-A, we'll create an uplink profile
that tells it to go ahead and use VM NIC two as the active
and VM NIC as the standby.
Very similar treatment for ESXi-B over here.
However, we will need a separate uplink profile for each
because we want ESXi-A to use VLAN 101 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
because we want ESXi-A to use VLAN 101
and the address space of 10 11 11.
And we want ESXi-B to use VLAN 102
and have an IP address for its tunnel endpoint
on the 10 22 22 network.
Now, there is also an option
for configuring both of our ESXi hosts,
or a whole cluster of ESXi hosts at the same time.
At which point we would use a host profile
that includes which uplink profiles to use,
which are going to include which VLANs to use.
So there's a few options regarding configuring ESXi host
as transport nodes in bulk. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as transport nodes in bulk.