So when we go to deploy our edge transport notes,
they're going to provide the features like
stateful services and VPNs and network address translation.
When we deploy those edge nodes in our nested environment,
we're going to place those down here on
our management ESXi host,
that's ESXi-management.
So we'll leave the responsibility for
ESXi-A and ESXi-B to act as host transport nodes.
Then on our management ESXi-host and our nested environment,
that's where we'll place both of our edges.
So edge one and edge two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So edge one and edge two.
Very similar to the logic I use for
the host transport nodes for the edges for edge one.
I want to make sure I use a specific IP address.
So let's use 33.33.33 etc.
For edge two, let's use 44.
With a default gateway of
.1 on each of those respective networks and the benefit in a lab environment,
of using specific tunnel endpoint addresses like that,
is that it's very clear when you do trace flow or you start
capturing packets off the network or off the wire,
it makes it that much easier to identify where traffic is flying from and to. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it makes it that much easier to identify where traffic is flying from and to.
Also for edge one, I use VLANs 103 and for edge two, I use VLAN 104.
That also means I want to make sure up here at my top of X switch,
I'm also supporting VLAN 103 and 104 because if I fail to support
either of those VLANs or the routing between those VLANs and the subnets that
they're
supporting, that's going to cause my transport network to fail.
So down here for edge one, we'll use VLAN 103 and let's use uplink 4.
And for edge two, we'll use VLAN 104 and uplink 5. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for edge two, we'll use VLAN 104 and uplink 5.
And that way we have nice clear separation.
Those two little edge VMs are going to use the uplinks that we specify as part
of the deployment.
And again, they could use the same exact uplink, that's not a problem.
However, for a lab environment and for learning purposes,
by separating them into two separate VLANs and having separate IP addressing
this very distinctive,
it's going to help clarify what is really going on as those edge nodes
communicate, talk with each other and as they interact with our host transport
nodes
as well.
So let me give you a peek at what that looks like both from the NSX manager and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let me give you a peek at what that looks like both from the NSX manager and
also from
the compute resource that's being used as the home for these two little VMs.
So here in the NSX manager with system selected and fabric expanded, let's go
down to notes
and we'll click on yes to leave our previous config.
So here are two edge nodes.
There are the management addresses for each of them.
There's the host that's supporting those two edge nodes.
And there's the tunnel endpoints for each of them as well.
So if we went into edit one of them, we'll click on one of them, click on the
pencil for edit.
There's the name of that edge node edge one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's the name of that edge node edge one.
If we scroll down, there's the transport zones that's supporting, which include
two that I
gave it and one because I set up an NSX federation earlier.
So add that to it.
Here's the uplink profile using VLAN 103 and VMnik 4.
There's the static IP address I configured for it.
And if we scroll down, here's where I mapped the name of the uplink profile
right here
with the port group that leads to VMnik 4.
And that's one of the benefits for your edge nodes of naming the port group
regarding which
uplinks it's using.
And that way you can choose the correct uplink that you want to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that way you can choose the correct uplink that you want to use.
So in the lab, I just use a single uplink, although in a production environment
for fault
tolerance and higher throughput, you could actually have multiple uplinks based
on the
uplink profile you want to use.
So no changes there.
If we click on cancel and we go to edge two here on the overview tab, it's
showing us
the transport zones, which host is running that VM, the management IP address
of the
VM, and if it clicks on monitor, we could take a look at how it's doing with
the resources
it's been given.
If you click here on tunnels, here you're showing it's a tunnel endpoint WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If you click here on tunnels, here you're showing it's a tunnel endpoint
address.
And currently we have a tunnel up to edge one, which is at 3333.
And there's the logical interface, fast path, Ethernet zero using Geneva tunnel
ing.
So my objective here in this set of videos and the skill was to walk you
through and
show you the details behind my nested lab environment.
So to help reinforce the concept that this is super useful in the next video, I
'd like
to do two things.
Number one, I'd like to go ahead and use this lab environment to go ahead and
create connectivity
from a VM on one of the segments out to the public internet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
from a VM on one of the segments out to the public internet.
And then secondly, I'd like to walk you through how to gracefully shut it all
down and snapshot
it.
So if we need to, we can come right back to the point that we left off and
everything
is good to go.