So if you've taken a moment
to consider those questions for the customer,
let's compare our thoughts together
regarding those questions.
Number one, if we're trying to explain or elaborate
on what are the differences between
an ESXi host transport node and an edge transport node.
Let's start off with some of the things they have in common.
They both have the ability, over a transport network,
to tunnel traffic back and forth.
So we could have tunnel traffic between two edge nodes,
we could have tunnel traffic
between two host transport nodes WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
between two host transport nodes
and we could also have tunnel traffic
between a host transport node and an edge transport node,
depending on where the traffic needs to be forwarded.
So that's one of the commonalities
between an edge and a host transport node
is that they both are involved in the data plane
for forwarding traffic
and they can both build the GENEVE tunnels
using tunnel endpoint addresses.
Now, in the event that we want to add a router
to go ahead and route, for example,
between segment 10 and segment 20,
I'll draw those right here and here respectively. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll draw those right here and here respectively.
If we need to route between those two subnets,
effectively the IP address being associated
with those two segments,
we can use a logical router function.
And the ESXi hosts can do that on their own
and that's referred to as a distributed router.
So if we're implementing this logical distributed router,
and it lives here on ESXi-A
and that distributed router lives here on ESXi-B,
it also lives up on edge-1,
so it has all the information for all the ports
and interfaces and IP addresses and layer two addresses
associated with that distributed router, and so does edge-2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
associated with that distributed router, and so does edge-2.
If we're just forwarding traffic for these two hosts,
between these various VMs on those different segments,
that can all be done by the ESXi host themselves
and we do not at that moment need a edge transport node.
Even though they could do it,
there's no need to forward the traffic to a little VM
that's running as one of our edge nodes to do the routing
and then forward it back down to destination
or back down to the same host
because the ESXi host here can do the routing logically
and it can send it over to ESXi-B if it needs to.
So the next logical question from the customer might be, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the next logical question from the customer might be,
well, why exactly then do we even need
these edge transport nodes
if the ESXi host transport nodes
can do all the logical routing
and the forwarding between them?
And the answer is,
any time that we need some type of service
or function that an ESXI host cannot provide on its own.
So we can kinda think of the edge transport nodes
as a resource to go to when the ESXi host needs some help
and can't do the work on its own.
And some of those functions where an ESXi host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And some of those functions where an ESXi host
can't do the job on its own would be
high availability solutions.
As we did in the demo,
we took a look at setting up this gateway function
as active standby, and as a result,
that's gonna require the use
of our edge transport node cluster
with two transport nodes in it
that can provide that fault tolerance.
So in the case of active standby, that'd be a function
that our edge transport node cluster
could provide the fault tolerance for.
So that'd be one example
of where the ESXi host needs some help.
Another example would if we need to forward traffic WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Another example would if we need to forward traffic
out of our local NSX virtualized router environment
to the external world.
So if we need to send traffic out, for example,
to the internet or to another data center
outside of our NSX router environment,
that'd be another example when the edge transport node
would be called upon, so we'll call it external routing.
And also, as we're adding those additional services
and adding those functions at the edge transport nodes,
we're also implementing another logical services router
on those transport nodes so they can provide those services.
Some other services that we mentioned WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Some other services that we mentioned
would be VPNs and centralized DHCP services
and things like network address translation,
and there's several others.
And most of the time we're gonna be implementing
the edge transport nodes as VMs.
Now the exception to that would be
if the customer, for example,
is doing external routing out to the internet
or to some other external network,
and let's just say we have like
40 gigabits per second of traffic
that we need to forward through there,
the actual implementation of the edge transport nodes,
if they're setup as VMs,
may not be able to handle that quantity of data. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
may not be able to handle that quantity of data.
So as a result, at that point,
instead of using VMs for our edge transport nodes,
we may choose a bare metal option
and have some physical hardware
acting as edge transport nodes
to do that forwarding of traffic
out to the external network.
But whether we're using the VMs as edge transport nodes,
using their respective uplinks,
or we have some dedicated hardware
doing that functional forwarding, the logic is the same.
And that is that the edge transport node
is providing services and functionality
that a host transport node on its own WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that a host transport node on its own
doesn't have the ability to do,
and that's why we're implementing
this additional type of transport node,
the edge transport node.
So thanks for joining me in these videos in this skill,
and also for this validation section.
And when you're ready, I'll see you, my friend,
in the very next skill.
Until then, I hope this has been informative
and I'd like to thank you for viewing.