WEBVTT

1
00:00.000 --> 00:02.040
So let's head over to the NSX manager.

2
00:02.040 --> 00:03.240
Let's go to Trace Flow.

3
00:03.240 --> 00:04.240
We'll verify it there.

4
00:04.240 --> 00:07.440
We can also capture the trace flow and see what it looks like

5
00:07.440 --> 00:09.840
as that traffic is going over the transport network.

6
00:09.840 --> 00:13.560
So here in the NSX manager, we'll go to Plan and Troubleshoot.

7
00:13.560 --> 00:15.960
On the left, we'll go down to Traffic Analysis.

8
00:15.960 --> 00:18.680
And then we'll click right here in the Trace Flow on Get Started.

9
00:18.680 --> 00:21.240
And for this trace, we'll go ahead and use ICMP.

10
00:21.240 --> 00:21.960
That would be great.

11
00:21.960 --> 00:24.400
The source VM will be VM number one.

12
00:24.400 --> 00:27.360
And for the destination, this time we're going to use an IP address.

13
00:27.360 --> 00:32.000
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

13
00:27.360 --> 00:32.000
So instead of saying type virtual machine, we'll say type is the IP Mac.

14
00:32.000 --> 00:33.560
And then we'll specify layer three only.

15
00:33.560 --> 00:35.560
I don't care about the destination layer two address.

16
00:35.560 --> 00:40.200
And for the destination IP address, it's going to be 192.168.1.1.

17
00:40.200 --> 00:41.440
And that looks great.

18
00:41.440 --> 00:42.680
And we'll click on Trace.

19
00:42.680 --> 00:45.360
And also in the background on my transport network,

20
00:45.360 --> 00:47.800
I'm actually capturing this traffic as well.

21
00:47.800 --> 00:49.600
So we'll verify the path here.

22
00:49.600 --> 00:52.320
And then we'll also be able to see on the transport network

23
00:52.320 --> 00:54.400
what that encapsulated payload looks like.

24
00:54.400 --> 00:55.920
And here we go.

25
00:55.920 --> 01:01.520
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

25
00:55.920 --> 01:01.520
So traffic source from 10, 10, 0, 10 with a Vessation of 192.168.1.

26
01:01.520 --> 01:05.920
It first went into the network on ESXIA, who injected the packet

27
01:05.920 --> 01:08.320
on behalf of that client that IP address.

28
01:08.320 --> 01:12.190
So then it went through a distributed firewall, which allowed the packet to

29
01:12.190 --> 01:12.880
flow.

30
01:12.880 --> 01:14.720
And then it went through segment 10.

31
01:14.720 --> 01:17.200
Then it got logically routed through Gateway A.

32
01:17.200 --> 01:19.680
That's here still happening on ESXIA.

33
01:19.680 --> 01:24.420
And then it got routed between the tier one Gateway A and the tier zero Gateway

34
01:24.420 --> 01:24.640
.

35
01:24.640 --> 01:28.080
Again, all of this happening in the brains of ESXIA with its distributed router

36
01:28.080 --> 01:28.640
function.

37
01:28.640 --> 01:29.920
If we scroll down.

38
01:29.920 --> 01:32.660
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

38
01:29.920 --> 01:32.660
And then we come to the part of our story where it needs to forward to that

39
01:32.660 --> 01:34.720
next top address of the services router.

40
01:34.720 --> 01:38.320
And to do that, it needs to encapsulate it and forward it over to edge one.

41
01:38.320 --> 01:41.200
So if we expand the columns here a little bit, so we can read a little bit

42
01:41.200 --> 01:41.520
better.

43
01:41.520 --> 01:43.680
For the tunnel, it sourced it from its tunnel endpoint.

44
01:43.680 --> 01:48.270
That's ESXIA and forwarded it to the edge node, which is the tunnel endpoint of

45
01:48.270 --> 01:49.920
3333 for edge one.

46
01:49.920 --> 01:53.120
And now, as far as who's doing the work, it's now edge one.

47
01:53.120 --> 01:56.880
So here it's showing the edge one, it received it, and then it made a routing

48
01:56.880 --> 02:00.400
decision on behalf of the tier zero Gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:56.880 --> 02:00.400
decision on behalf of the tier zero Gateway.

49
02:00.400 --> 02:03.800
And then it went through an edge firewall, which by default is permitting all

50
02:03.800 --> 02:04.240
traffic.

51
02:04.240 --> 02:06.480
And it was sent out dot 61.

52
02:06.480 --> 02:11.280
And that's the IP address associated with edge one, who is the active router.

53
02:11.280 --> 02:14.560
Now, one of the cool things is because Trace will actually send the traffic.

54
02:14.560 --> 02:18.160
And because I was capturing it on my transport network, we can take a look at

55
02:18.160 --> 02:19.760
that traffic in transit.

56
02:19.760 --> 02:21.360
So let me bring in that capture.

57
02:21.360 --> 02:25.600
It is right here. So I started a display filter for ICMP because that's what we

58
02:25.600 --> 02:25.920
chose.

59
02:25.920 --> 02:28.720
And let's look at the details for this packet.

60
02:28.720 --> 02:33.520
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

60
02:28.720 --> 02:33.520
So in this packet capture, the first four entries here is my distributed switch

61
02:33.520 --> 02:37.610
that captured all this traffic and routed it over to my management computer

62
02:37.610 --> 02:38.960
here at dot 151.

63
02:38.960 --> 02:42.640
So the actual beginning of our transport traffic begins here.

64
02:42.640 --> 02:44.480
So there's the layer two dresses involved.

65
02:44.480 --> 02:49.680
Here's the layer three addresses for ESXIA going to the edge one.

66
02:49.680 --> 02:54.170
Inside of that, it was UDP to the well known port of 6 0 8 1 is used for genie

67
02:54.170 --> 02:54.880
ve tunneling.

68
02:54.880 --> 02:56.480
Then we have the genieve header.

69
02:56.480 --> 03:00.320
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

69
02:56.480 --> 03:00.320
So if we open that up here, it's showing us the virtual network identifier,

70
03:00.320 --> 03:02.560
which is 6 7 5 8 4.

71
03:02.560 --> 03:04.960
Let's take a quick peek at our topology real quick.

72
03:04.960 --> 03:07.520
So that indeed is 6 7 5 8 4.

73
03:07.520 --> 03:13.680
That is the V and I number for that next top where 169 254 0 dot 2 lives and

74
03:13.680 --> 03:15.360
its corresponding layer two address.

75
03:15.360 --> 03:19.770
So then when edge one received it and de encapsulated it, then the actual

76
03:19.770 --> 03:21.680
payload is carried next.

77
03:21.680 --> 03:25.180
So for the ethernet header, it shows as being sourced from this layer two

78
03:25.180 --> 03:25.920
address.

79
03:25.920 --> 03:30.370
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

79
03:25.920 --> 03:30.370
So that layer two dress would be the layer two dress used by the DR function on

80
03:30.370 --> 03:36.240
gateway zero on that common 169 254 segment between it and the services router.

81
03:36.240 --> 03:38.560
So just for grins, we did a get gateways.

82
03:38.560 --> 03:41.040
That's the EU ID for our tier zero distributed router.

83
03:41.040 --> 03:44.980
So if you want to verify its interfaces and their MAC addresses, we could go

84
03:44.980 --> 03:50.050
ahead and type in this get gateway that you ID and followed by interfaces press

85
03:50.050 --> 03:50.640
enter.

86
03:50.640 --> 03:56.240
And then for that common link between the DR on tier zero and the SR on tier

87
03:56.240 --> 04:01.480
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

87
03:56.240 --> 04:01.480
zero, I'm looking for this 169 254 address and there is the corresponding layer

88
04:01.480 --> 04:02.160
two address.

89
04:02.160 --> 04:05.440
So that was the source address that was being carried in the payload.

90
04:05.440 --> 04:08.730
And to see the layer two address, we're going to need to go over to an edge

91
04:08.730 --> 04:11.320
router that has the SR. So let's do that real quick.

92
04:11.320 --> 04:14.560
So here is edge one. Let's do a quick get gateways.

93
04:14.560 --> 04:18.700
And then for the services router, which is VRF four, let's just go into VRF

94
04:18.700 --> 04:23.560
four by typing in VRF four press enter and we'll do the command get interfaces.

95
04:23.560 --> 04:26.920
So we're looking for the IP address 169 254 0 dot two.

96
04:26.920 --> 04:27.680
There it is.

97
04:27.680 --> 04:30.240
And there's the corresponding layer two address.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
04:27.680 --> 04:30.240
And there's the corresponding layer two address.

98
04:30.240 --> 04:34.970
So in the payload that we've sent over to edge one is showing the source layer

99
04:34.970 --> 04:39.270
two dress as the layer two dress associate with this interface that has the dot

100
04:39.270 --> 04:41.160
one IP address on gateway zero.

101
04:41.160 --> 04:44.670
And for the destination layer two dress as the layer two dress of the services

102
04:44.670 --> 04:47.960
router that corresponds to the IP address and again, dot two.

103
04:47.960 --> 04:52.380
And that plays out right here perfectly source address is from the DR and the

104
04:52.380 --> 04:56.950
destination address is the SR at which point the logical services router then

105
04:56.950 --> 05:00.200
looked at the destination address and then made its own four.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:56.950 --> 05:00.200
looked at the destination address and then made its own four.

106
05:00.200 --> 05:03.200
and forward the packet on its way.

107
05:03.200 --> 05:13.200
[BLANK_AUDIO]