WEBVTT

1
00:00.180 --> 00:01.410
So if you've taken a moment

2
00:01.410 --> 00:04.290
to consider those questions for the customer,

3
00:04.290 --> 00:06.480
let's compare our thoughts together

4
00:06.480 --> 00:07.560
regarding those questions.

5
00:07.560 --> 00:10.770
Number one, if we're trying to explain or elaborate

6
00:10.770 --> 00:12.330
on what are the differences between

7
00:12.330 --> 00:17.070
an ESXi host transport node and an edge transport node.

8
00:17.070 --> 00:19.620
Let's start off with some of the things they have in common.

9
00:19.620 --> 00:22.680
They both have the ability, over a transport network,

10
00:22.680 --> 00:24.810
to tunnel traffic back and forth.

11
00:24.810 --> 00:28.200
So we could have tunnel traffic between two edge nodes,

12
00:28.200 --> 00:29.700
we could have tunnel traffic

13
00:29.700 --> 00:31.440
between two host transport nodes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.700 --> 00:31.440
between two host transport nodes

14
00:31.440 --> 00:33.240
and we could also have tunnel traffic

15
00:33.240 --> 00:36.690
between a host transport node and an edge transport node,

16
00:36.690 --> 00:38.820
depending on where the traffic needs to be forwarded.

17
00:38.820 --> 00:40.500
So that's one of the commonalities

18
00:40.500 --> 00:44.190
between an edge and a host transport node

19
00:44.190 --> 00:46.230
is that they both are involved in the data plane

20
00:46.230 --> 00:47.460
for forwarding traffic

21
00:47.460 --> 00:49.620
and they can both build the GENEVE tunnels

22
00:49.620 --> 00:51.270
using tunnel endpoint addresses.

23
00:51.270 --> 00:53.880
Now, in the event that we want to add a router

24
00:53.880 --> 00:55.260
to go ahead and route, for example,

25
00:55.260 --> 00:57.540
between segment 10 and segment 20,

26
00:57.540 --> 01:00.450
I'll draw those right here and here respectively.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:57.540 --> 01:00.450
I'll draw those right here and here respectively.

27
01:00.450 --> 01:02.640
If we need to route between those two subnets,

28
01:02.640 --> 01:04.410
effectively the IP address being associated

29
01:04.410 --> 01:05.610
with those two segments,

30
01:05.610 --> 01:07.770
we can use a logical router function.

31
01:07.770 --> 01:11.040
And the ESXi hosts can do that on their own

32
01:11.040 --> 01:13.200
and that's referred to as a distributed router.

33
01:13.200 --> 01:15.780
So if we're implementing this logical distributed router,

34
01:15.780 --> 01:18.390
and it lives here on ESXi-A

35
01:18.390 --> 01:20.820
and that distributed router lives here on ESXi-B,

36
01:20.820 --> 01:23.100
it also lives up on edge-1,

37
01:23.100 --> 01:25.020
so it has all the information for all the ports

38
01:25.020 --> 01:27.660
and interfaces and IP addresses and layer two addresses

39
01:27.660 --> 01:31.050
associated with that distributed router, and so does edge-2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:27.660 --> 01:31.050
associated with that distributed router, and so does edge-2.

40
01:31.050 --> 01:33.090
If we're just forwarding traffic for these two hosts,

41
01:33.090 --> 01:35.970
between these various VMs on those different segments,

42
01:35.970 --> 01:38.730
that can all be done by the ESXi host themselves

43
01:38.730 --> 01:42.960
and we do not at that moment need a edge transport node.

44
01:42.960 --> 01:43.980
Even though they could do it,

45
01:43.980 --> 01:46.530
there's no need to forward the traffic to a little VM

46
01:46.530 --> 01:49.110
that's running as one of our edge nodes to do the routing

47
01:49.110 --> 01:50.880
and then forward it back down to destination

48
01:50.880 --> 01:52.230
or back down to the same host

49
01:52.230 --> 01:55.800
because the ESXi host here can do the routing logically

50
01:55.800 --> 01:58.860
and it can send it over to ESXi-B if it needs to.

51
01:58.860 --> 02:01.170
So the next logical question from the customer might be,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:58.860 --> 02:01.170
So the next logical question from the customer might be,

52
02:01.170 --> 02:03.750
well, why exactly then do we even need

53
02:03.750 --> 02:05.520
these edge transport nodes

54
02:05.520 --> 02:08.340
if the ESXi host transport nodes

55
02:08.340 --> 02:09.900
can do all the logical routing

56
02:09.900 --> 02:11.100
and the forwarding between them?

57
02:11.100 --> 02:12.360
And the answer is,

58
02:12.360 --> 02:15.780
any time that we need some type of service

59
02:15.780 --> 02:19.980
or function that an ESXI host cannot provide on its own.

60
02:19.980 --> 02:22.200
So we can kinda think of the edge transport nodes

61
02:22.200 --> 02:26.280
as a resource to go to when the ESXi host needs some help

62
02:26.280 --> 02:28.080
and can't do the work on its own.

63
02:28.080 --> 02:30.130
And some of those functions where an ESXi host
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:28.080 --> 02:30.130
And some of those functions where an ESXi host

64
02:30.130 --> 02:32.250
can't do the job on its own would be

65
02:32.250 --> 02:33.840
high availability solutions.

66
02:33.840 --> 02:34.920
As we did in the demo,

67
02:34.920 --> 02:37.590
we took a look at setting up this gateway function

68
02:37.590 --> 02:39.960
as active standby, and as a result,

69
02:39.960 --> 02:41.790
that's gonna require the use

70
02:41.790 --> 02:43.620
of our edge transport node cluster

71
02:43.620 --> 02:45.960
with two transport nodes in it

72
02:45.960 --> 02:47.790
that can provide that fault tolerance.

73
02:47.790 --> 02:50.550
So in the case of active standby, that'd be a function

74
02:50.550 --> 02:52.710
that our edge transport node cluster

75
02:52.710 --> 02:54.270
could provide the fault tolerance for.

76
02:54.270 --> 02:55.740
So that'd be one example

77
02:55.740 --> 02:58.170
of where the ESXi host needs some help.

78
02:58.170 --> 03:00.750
Another example would if we need to forward traffic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:58.170 --> 03:00.750
Another example would if we need to forward traffic

79
03:00.750 --> 03:04.020
out of our local NSX virtualized router environment

80
03:04.020 --> 03:05.310
to the external world.

81
03:05.310 --> 03:07.290
So if we need to send traffic out, for example,

82
03:07.290 --> 03:09.690
to the internet or to another data center

83
03:09.690 --> 03:11.820
outside of our NSX router environment,

84
03:11.820 --> 03:14.250
that'd be another example when the edge transport node

85
03:14.250 --> 03:17.070
would be called upon, so we'll call it external routing.

86
03:17.070 --> 03:19.620
And also, as we're adding those additional services

87
03:19.620 --> 03:22.590
and adding those functions at the edge transport nodes,

88
03:22.590 --> 03:26.040
we're also implementing another logical services router

89
03:26.040 --> 03:29.400
on those transport nodes so they can provide those services.

90
03:29.400 --> 03:30.840
Some other services that we mentioned
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:29.400 --> 03:30.840
Some other services that we mentioned

91
03:30.840 --> 03:35.100
would be VPNs and centralized DHCP services

92
03:35.100 --> 03:37.290
and things like network address translation,

93
03:37.290 --> 03:38.430
and there's several others.

94
03:38.430 --> 03:39.990
And most of the time we're gonna be implementing

95
03:39.990 --> 03:42.570
the edge transport nodes as VMs.

96
03:42.570 --> 03:44.250
Now the exception to that would be

97
03:44.250 --> 03:45.720
if the customer, for example,

98
03:45.720 --> 03:48.270
is doing external routing out to the internet

99
03:48.270 --> 03:49.830
or to some other external network,

100
03:49.830 --> 03:51.180
and let's just say we have like

101
03:51.180 --> 03:53.850
40 gigabits per second of traffic

102
03:53.850 --> 03:55.440
that we need to forward through there,

103
03:55.440 --> 03:58.440
the actual implementation of the edge transport nodes,

104
03:58.440 --> 03:59.790
if they're setup as VMs,

105
03:59.790 --> 04:02.640
may not be able to handle that quantity of data.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
03:59.790 --> 04:02.640
may not be able to handle that quantity of data.

106
04:02.640 --> 04:04.260
So as a result, at that point,

107
04:04.260 --> 04:06.600
instead of using VMs for our edge transport nodes,

108
04:06.600 --> 04:08.490
we may choose a bare metal option

109
04:08.490 --> 04:09.990
and have some physical hardware

110
04:09.990 --> 04:11.760
acting as edge transport nodes

111
04:11.760 --> 04:13.020
to do that forwarding of traffic

112
04:13.020 --> 04:14.220
out to the external network.

113
04:14.220 --> 04:17.370
But whether we're using the VMs as edge transport nodes,

114
04:17.370 --> 04:18.840
using their respective uplinks,

115
04:18.840 --> 04:20.940
or we have some dedicated hardware

116
04:20.940 --> 04:24.090
doing that functional forwarding, the logic is the same.

117
04:24.090 --> 04:25.740
And that is that the edge transport node

118
04:25.740 --> 04:28.050
is providing services and functionality

119
04:28.050 --> 04:30.540
that a host transport node on its own
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
04:28.050 --> 04:30.540
that a host transport node on its own

120
04:30.540 --> 04:32.100
doesn't have the ability to do,

121
04:32.100 --> 04:34.320
and that's why we're implementing

122
04:34.320 --> 04:36.090
this additional type of transport node,

123
04:36.090 --> 04:38.010
the edge transport node.

124
04:38.010 --> 04:40.860
So thanks for joining me in these videos in this skill,

125
04:40.860 --> 04:42.870
and also for this validation section.

126
04:42.870 --> 04:45.150
And when you're ready, I'll see you, my friend,

127
04:45.150 --> 04:46.920
in the very next skill.

128
04:46.920 --> 04:49.500
Until then, I hope this has been informative

129
04:49.500 --> 04:51.933
and I'd like to thank you for viewing.