So let's head over to the NSX manager.
Let's go to Trace Flow.
We'll verify it there.
We can also capture the trace flow and see what it looks like
as that traffic is going over the transport network.
So here in the NSX manager, we'll go to Plan and Troubleshoot.
On the left, we'll go down to Traffic Analysis.
And then we'll click right here in the Trace Flow on Get Started.
And for this trace, we'll go ahead and use ICMP.
That would be great.
The source VM will be VM number one.
And for the destination, this time we're going to use an IP address.
So instead of saying type virtual machine, we'll say type is the IP Mac. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So instead of saying type virtual machine, we'll say type is the IP Mac.
And then we'll specify layer three only.
I don't care about the destination layer two address.
And for the destination IP address, it's going to be 192.168.1.1.
And that looks great.
And we'll click on Trace.
And also in the background on my transport network,
I'm actually capturing this traffic as well.
So we'll verify the path here.
And then we'll also be able to see on the transport network
what that encapsulated payload looks like.
And here we go.
So traffic source from 10, 10, 0, 10 with a Vessation of 192.168.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So traffic source from 10, 10, 0, 10 with a Vessation of 192.168.1.
It first went into the network on ESXIA, who injected the packet
on behalf of that client that IP address.
So then it went through a distributed firewall, which allowed the packet to
flow.
And then it went through segment 10.
Then it got logically routed through Gateway A.
That's here still happening on ESXIA.
And then it got routed between the tier one Gateway A and the tier zero Gateway
.
Again, all of this happening in the brains of ESXIA with its distributed router
function.
If we scroll down.
And then we come to the part of our story where it needs to forward to that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then we come to the part of our story where it needs to forward to that
next top address of the services router.
And to do that, it needs to encapsulate it and forward it over to edge one.
So if we expand the columns here a little bit, so we can read a little bit
better.
For the tunnel, it sourced it from its tunnel endpoint.
That's ESXIA and forwarded it to the edge node, which is the tunnel endpoint of
3333 for edge one.
And now, as far as who's doing the work, it's now edge one.
So here it's showing the edge one, it received it, and then it made a routing
decision on behalf of the tier zero Gateway. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
decision on behalf of the tier zero Gateway.
And then it went through an edge firewall, which by default is permitting all
traffic.
And it was sent out dot 61.
And that's the IP address associated with edge one, who is the active router.
Now, one of the cool things is because Trace will actually send the traffic.
And because I was capturing it on my transport network, we can take a look at
that traffic in transit.
So let me bring in that capture.
It is right here. So I started a display filter for ICMP because that's what we
chose.
And let's look at the details for this packet.
So in this packet capture, the first four entries here is my distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in this packet capture, the first four entries here is my distributed switch
that captured all this traffic and routed it over to my management computer
here at dot 151.
So the actual beginning of our transport traffic begins here.
So there's the layer two dresses involved.
Here's the layer three addresses for ESXIA going to the edge one.
Inside of that, it was UDP to the well known port of 6 0 8 1 is used for genie
ve tunneling.
Then we have the genieve header.
So if we open that up here, it's showing us the virtual network identifier, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we open that up here, it's showing us the virtual network identifier,
which is 6 7 5 8 4.
Let's take a quick peek at our topology real quick.
So that indeed is 6 7 5 8 4.
That is the V and I number for that next top where 169 254 0 dot 2 lives and
its corresponding layer two address.
So then when edge one received it and de encapsulated it, then the actual
payload is carried next.
So for the ethernet header, it shows as being sourced from this layer two
address.
So that layer two dress would be the layer two dress used by the DR function on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that layer two dress would be the layer two dress used by the DR function on
gateway zero on that common 169 254 segment between it and the services router.
So just for grins, we did a get gateways.
That's the EU ID for our tier zero distributed router.
So if you want to verify its interfaces and their MAC addresses, we could go
ahead and type in this get gateway that you ID and followed by interfaces press
enter.
And then for that common link between the DR on tier zero and the SR on tier
zero, I'm looking for this 169 254 address and there is the corresponding layer WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
zero, I'm looking for this 169 254 address and there is the corresponding layer
two address.
So that was the source address that was being carried in the payload.
And to see the layer two address, we're going to need to go over to an edge
router that has the SR. So let's do that real quick.
So here is edge one. Let's do a quick get gateways.
And then for the services router, which is VRF four, let's just go into VRF
four by typing in VRF four press enter and we'll do the command get interfaces.
So we're looking for the IP address 169 254 0 dot two.
There it is.
And there's the corresponding layer two address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And there's the corresponding layer two address.
So in the payload that we've sent over to edge one is showing the source layer
two dress as the layer two dress associate with this interface that has the dot
one IP address on gateway zero.
And for the destination layer two dress as the layer two dress of the services
router that corresponds to the IP address and again, dot two.
And that plays out right here perfectly source address is from the DR and the
destination address is the SR at which point the logical services router then
looked at the destination address and then made its own four. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
looked at the destination address and then made its own four.
and forward the packet on its way.
[BLANK_AUDIO]