All right, so for traffic flow from this device to this IP address right here,
from
this VMs perspective, to reach that non-local network of 23.1.2, it's not the
network
we're directly connected to, it would use its default gateway.
So the first hop would be this interface address right here on Gateway B, which
is 10.20.0.1.
And then Gateway B would make a forwarding decision using a default route that
it gets
when it's connected to a tier zero gateway, and it would forward up here to the
DR, the
distributed router up here at Gateway 0.
And then for the routing of that traffic out to the external network, logically WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then for the routing of that traffic out to the external network, logically
, that's
going to be routed over to our services router for our tier zero gateway zero.
And then it's that services router that has a connectivity out to this network
23.1.2.
So it would make the forwarding decision out to the next hop here at .1.
So that would be the logical flow of traffic from this VM to that IP address.
Now for the next question regarding which transport nodes are involved, it's
going to
start off with VM2 because it's running on host A, we're going to have host A
as the
transport node that'll make the routing decisions for Gateway B. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
transport node that'll make the routing decisions for Gateway B.
However, realizing it needs to go over to the services router and that host A
does not
have a copy of that services router, but the edge does host A is then going to
go ahead
and tunnel the traffic over here to edge one from 11, 11, 11, et cetera.
It's tunnel endpoint address over here to 33, et cetera, which is edge one's
tunnel endpoint
address at which point edge one would de-encaps like that, continue to make the
routing decision
and forward it out to that next hop at .1.
So the transport nodes will be host A and the next transport node would be edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the transport nodes will be host A and the next transport node would be edge
one because
that's the only one we have here.
So the two transport nodes would be host A first and then edge one.
Now the cool thing is we can also verify that by going to the NSX manager and
using trace
flow.
So here in the NSX manager, if we go to plan and troubleshoot right there and
then on the
left, we go down under troubleshooting tools to traffic analysis and then here
in the tile
for trace flow, we'll click get started and we'll use the default protocol of
ICMP and
for the source, we'll choose VM2 and for the destination, we're going to go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for the source, we'll choose VM2 and for the destination, we're going to go
ahead and
not use a VM.
So we'll specify we want to send it to an IP address and we'll leave off the
layer two
information.
So we'll choose layer three and just put the IP address of 23.1.2.1 and then we
'll click
on trace and then we'll let that crank it out.
And so that's actually injecting the traffic on the network and it'll show us
whether or
not it was successful or not.
And it'll also show us the transport nodes involved.
And based on our predictions, we're expecting it'll be ESXIA and also edge one.
So here's the play by play indicating it started off on ESXIA as a transport WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here's the play by play indicating it started off on ESXIA as a transport
host who
then forwarded it over to the edge one at the total endpoint of 33, et cetera.
And then the edge continued the routing decisions through gateway zero.
There's also some net rules in place and then it was finally delivered.
So as far as the transport nodes involved go, we have our host transport node
ESXIA and
also our edge transport node edge one.
So thanks for joining me in this set of videos as we've introduced the use of a
services
router for some services that only edge nodes can provide including
connectivity from our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
connectivity from our
NSX routed environment out to an external network segment.
And I look forward to seeing you my friend in another skill very, very soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.
[BLANK_AUDIO]