WEBVTT

1
00:00.000 --> 00:05.080
All right, so for traffic flow from this device to this IP address right here,

2
00:05.080 --> 00:05.160
from

3
00:05.160 --> 00:09.520
this VMs perspective, to reach that non-local network of 23.1.2, it's not the

4
00:09.520 --> 00:09.820
network

5
00:09.820 --> 00:12.640
we're directly connected to, it would use its default gateway.

6
00:12.640 --> 00:16.670
So the first hop would be this interface address right here on Gateway B, which

7
00:16.670 --> 00:19.680
is 10.20.0.1.

8
00:19.680 --> 00:23.010
And then Gateway B would make a forwarding decision using a default route that

9
00:23.010 --> 00:23.400
it gets

10
00:23.400 --> 00:27.300
when it's connected to a tier zero gateway, and it would forward up here to the

11
00:27.300 --> 00:27.560
DR, the

12
00:27.560 --> 00:29.920
distributed router up here at Gateway 0.

13
00:29.920 --> 00:33.490
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

13
00:29.920 --> 00:33.490
And then for the routing of that traffic out to the external network, logically

14
00:33.490 --> 00:33.680
, that's

15
00:33.680 --> 00:37.440
going to be routed over to our services router for our tier zero gateway zero.

16
00:37.440 --> 00:41.140
And then it's that services router that has a connectivity out to this network

17
00:41.140 --> 00:42.320
23.1.2.

18
00:42.320 --> 00:45.840
So it would make the forwarding decision out to the next hop here at .1.

19
00:45.840 --> 00:49.880
So that would be the logical flow of traffic from this VM to that IP address.

20
00:49.880 --> 00:53.190
Now for the next question regarding which transport nodes are involved, it's

21
00:53.190 --> 00:53.480
going to

22
00:53.480 --> 00:57.470
start off with VM2 because it's running on host A, we're going to have host A

23
00:57.470 --> 00:57.760
as the

24
00:57.760 --> 01:01.600
transport node that'll make the routing decisions for Gateway B.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:57.760 --> 01:01.600
transport node that'll make the routing decisions for Gateway B.

25
01:01.600 --> 01:04.970
However, realizing it needs to go over to the services router and that host A

26
01:04.970 --> 01:05.520
does not

27
01:05.520 --> 01:09.590
have a copy of that services router, but the edge does host A is then going to

28
01:09.590 --> 01:10.040
go ahead

29
01:10.040 --> 01:15.280
and tunnel the traffic over here to edge one from 11, 11, 11, et cetera.

30
01:15.280 --> 01:19.050
It's tunnel endpoint address over here to 33, et cetera, which is edge one's

31
01:19.050 --> 01:19.800
tunnel endpoint

32
01:19.800 --> 01:23.350
address at which point edge one would de-encaps like that, continue to make the

33
01:23.350 --> 01:24.360
routing decision

34
01:24.360 --> 01:27.520
and forward it out to that next hop at .1.

35
01:27.520 --> 01:30.720
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

35
01:27.520 --> 01:30.720
So the transport nodes will be host A and the next transport node would be edge

36
01:30.720 --> 01:31.120
one because

37
01:31.120 --> 01:32.680
that's the only one we have here.

38
01:32.680 --> 01:36.320
So the two transport nodes would be host A first and then edge one.

39
01:36.320 --> 01:41.200
Now the cool thing is we can also verify that by going to the NSX manager and

40
01:41.200 --> 01:42.000
using trace

41
01:42.000 --> 01:43.000
flow.

42
01:43.000 --> 01:46.510
So here in the NSX manager, if we go to plan and troubleshoot right there and

43
01:46.510 --> 01:47.080
then on the

44
01:47.080 --> 01:50.740
left, we go down under troubleshooting tools to traffic analysis and then here

45
01:50.740 --> 01:51.280
in the tile

46
01:51.280 --> 01:55.450
for trace flow, we'll click get started and we'll use the default protocol of

47
01:55.450 --> 01:56.000
ICMP and

48
01:56.000 --> 02:00.620
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

48
01:56.000 --> 02:00.620
for the source, we'll choose VM2 and for the destination, we're going to go

49
02:00.620 --> 02:01.160
ahead and

50
02:01.160 --> 02:02.160
not use a VM.

51
02:02.160 --> 02:05.540
So we'll specify we want to send it to an IP address and we'll leave off the

52
02:05.540 --> 02:06.080
layer two

53
02:06.080 --> 02:07.080
information.

54
02:07.080 --> 02:11.300
So we'll choose layer three and just put the IP address of 23.1.2.1 and then we

55
02:11.300 --> 02:11.720
'll click

56
02:11.720 --> 02:14.120
on trace and then we'll let that crank it out.

57
02:14.120 --> 02:18.230
And so that's actually injecting the traffic on the network and it'll show us

58
02:18.230 --> 02:18.520
whether or

59
02:18.520 --> 02:20.040
not it was successful or not.

60
02:20.040 --> 02:22.960
And it'll also show us the transport nodes involved.

61
02:22.960 --> 02:27.080
And based on our predictions, we're expecting it'll be ESXIA and also edge one.

62
02:27.080 --> 02:30.810
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

62
02:27.080 --> 02:30.810
So here's the play by play indicating it started off on ESXIA as a transport

63
02:30.810 --> 02:31.200
host who

64
02:31.200 --> 02:35.800
then forwarded it over to the edge one at the total endpoint of 33, et cetera.

65
02:35.800 --> 02:39.040
And then the edge continued the routing decisions through gateway zero.

66
02:39.040 --> 02:42.400
There's also some net rules in place and then it was finally delivered.

67
02:42.400 --> 02:47.520
So as far as the transport nodes involved go, we have our host transport node

68
02:47.520 --> 02:48.000
ESXIA and

69
02:48.000 --> 02:50.880
also our edge transport node edge one.

70
02:50.880 --> 02:54.830
So thanks for joining me in this set of videos as we've introduced the use of a

71
02:54.830 --> 02:55.480
services

72
02:55.480 --> 02:59.430
router for some services that only edge nodes can provide including

73
02:59.430 --> 03:00.800
connectivity from our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:59.430 --> 03:00.800
connectivity from our

74
03:00.800 --> 03:04.240
NSX routed environment out to an external network segment.

75
03:04.240 --> 03:07.680
And I look forward to seeing you my friend in another skill very, very soon.

76
03:07.680 --> 03:11.850
Until then, I hope this has been informative and I'd like to thank you for

77
03:11.850 --> 03:12.240
viewing.

78
03:12.240 --> 03:22.240
[BLANK_AUDIO]