So, based on our game plan, our first step is to create a brand new transport
zone for
the type VLAN, as opposed to type overlay.
Also, I think we should take just a moment right before we create that new
transport
zone just to verify for a moment that we currently have our distributed routers
in place and
that those distributed routers exist on our host transport nodes as well as our
edge transport
nodes.
So, I'll go ahead and power up these four VMs and let's go verify.
So, here are the four VMs that's going to go to the network tab for a moment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, here are the four VMs that's going to go to the network tab for a moment
and let's
verify that the right VMs are on the right segments.
So, if we click on segment 10 yellow and go to VMs, there is VM 1 and 3.
Fantastic.
If we go to pink, there is 2 and 4.
So, let me go back here and let me power them up a couple at a time.
So, I'm going to go to the VMs for testing, click on the VMs tab and I want to
power up
these two first and that way they get the first two IP addresses in the pool
and that
way they have the actual IP addresses that match their names.
So, I go ahead and right click and click on power and we'll power them on and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, I go ahead and right click and click on power and we'll power them on and
then we'll
go to the second two VMs.
That would be VM 3 and VM 4 on the 10 and 27, that's respectively with the .11
and .21,
we'll right click and power those on as well by clicking on power, clicking
power on and
those are powering up as well.
And let's also do a spot check just to verify they got the IP addresses that we
expect.
So, one way of doing that and also a great way to verify our basic
infrastructure is
go to plan and troubleshoot here in the NSX manager on the left, we'll click on
traffic WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
traffic
analysis right there and then we'll click on get started here for trace flow.
And then for the virtual machines, if we use the drop down here and we select
VM 1, for
example and on the right we select VMs and select VM 4 to spot check.
Here at the bottom it's showing us the actual IP addresses.
So, up here is the name of the VM and down here is the actual IP address and
its MAC address,
same thing here for VM 4 and its IP address looks spot on.
We could also verify some traffic just by clicking on trace and verifying that
's working. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
's working.
And while that's cranking away, VM 1 is over here on host A, VM 4 is over here
on host
B.
So, as a result ESXIA should do all of the routing decisions and then
forwarding over the tunnel
because the layer 2 address associated with VM 4 is owned and reachable over
here at
ESXIA B.
So, if we look at the output of trace flow here and do a spot check, all the
routing should
be done from VM 1's perspective all the way to over here to the pink subnet and
sure enough
that's ESXIA and then the final packet was delivered over the tunnel to ESXIA B WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's ESXIA and then the final packet was delivered over the tunnel to ESXIA B
.
So, if we click on the host for the VM 4, it should show ESXIA B.
That looks fantastic.
And if we close that and look at the play by play, this would all confirm that
for us
as well.
Also, let's take a moment and just verify on a couple of our nodes that they
all have
copies of the distributed routers.
So, let's do a spot check on edge 1 and let's also spot check here on ESXIA.
Again, just to verify that the distributed routers for tier 0 and gateway A and
gateway
B exist on both those transport nodes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
B exist on both those transport nodes.
So, here at the top we have an SSH connection over to edge 1 at the bottom of
the SSH over
to ESXIA.
So, on ESXIA we'll type in NSX CLI to go to the NSX CLI press enter and then
down here
I'll go ahead and anything I type down here in the command window is going to
go to both
sessions immediately.
So, we'll go ahead and clear the screen a little bit and let's do a get gate
ways.
You can also type in get logical routers.
Either way is great.
So, here on the edge I've got these three UUIDs which represent the UUIDs for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So, here on the edge I've got these three UUIDs which represent the UUIDs for
gateway
0, gateway A and gateway B and I have the same UUIDs down here on ESXIA.
So, effectively we have the same distributed routers and then this VRF0 up on
the edge is
the routing table for the VM itself.
That's how it gets to the transport network and all that good stuff.
So, if we want to look at the routing table here for example on gateway A we
could go
ahead and type in get gateway space and then put the UUID for gateway A which
is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is going
to be the same on both of these devices because it's the same distributed
routers we'll paste
that in.
Then we'll say forwarding and that will show us the forwarding table for that
virtual router.
But as far as routing goes it has a route to the 10100 network.
We also have a route for the 1064 network and that's the route from gateway A
that goes
up to gateway 0.
This is also showing a default route on gateway A with the next top of 106400
which is the
IP address up on gateway 0 for the inter router link between gateway A and
gateway 0. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
gateway 0.
So this interface right there on our gateway 0 that would have the IP address
of 106400
and that's the next top from gateway A's perspective we're here on the default
route.
So the tier 1 gateways get a default route when they're connected to a tier 0
gateway
that uses the tier 0 gateway as the next top for the default route.
So once again if we do a get gateways the three distributed routers for tier 0
and our
two tier 1s are present on both our edge transport nodes and also our host
transport
nodes.
So based on our plan let's start off by creating a brand new VLAN back WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So based on our plan let's start off by creating a brand new VLAN back
transport zone and we'll
also train our two edges that they should be associated with that new transport
zone.
So to do that here in the NSX manager we're going to go to system.
So at the top we'll click on system.
So currently we have two host transport nodes and two edge transport nodes
fantastic and
to create a new transport zone on the left we're going to expand fabric if it's
not already
expanded and then we'll click right here on transport zones.
So they have some default transport zones that are already here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So they have some default transport zones that are already here.
There's our overlay transport zone we created earlier and what we're going to
do now is
create a new transport zone but it's going to be type VLAN for VLAN backed
segments that
can go in that as opposed to overlay.
So we'll go ahead and click here and add transport zone.
We'll give it an aim let's call it our VLAN backed easy so when we see it we'll
know what
it is and for the type we don't want it to be a transport zone that's
supporting overlay
segments we want it to be a transport zone that's supporting VLAN backed
segments like WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
our VLAN 0 segment which we're going to create.
And for this new VLAN backed transport zone that we are creating if we want to
limit it
based on which VLANs it's willing to support for the actual segments we could
specify here
or if you want to leave it wide open we could leave it wide open.
So for our purposes I'm just going to make this brand new transport zone type V
LAN and
that's the only specifications I'm putting in everything else I'll take the
defaults
and we'll click on safe and boom we now have this new transport zone called our
VLAN back
TZ however it has absolutely no segments in it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
TZ however it has absolutely no segments in it.
So we look over here in the column for segments you'll notice it's all zeroed
out because there's
no segments currently associated with this VLAN backed transport zone.
[BLANK_AUDIO]