WEBVTT

1
00:00.000 --> 00:03.360
Alright, let's jump into this topology challenge.

2
00:03.360 --> 00:07.210
So what we have here is a topology with a couple of plain circuits, just a

3
00:07.210 --> 00:07.560
couple of

4
00:07.560 --> 00:10.200
routers to keep things simple here.

5
00:10.200 --> 00:13.160
And the first question is how many tunnels will be formed?

6
00:13.160 --> 00:17.320
Well, when we're thinking about tunnels, we have to think about things from

7
00:17.320 --> 00:18.080
both a control

8
00:18.080 --> 00:20.600
plane and a data plane perspective.

9
00:20.600 --> 00:26.130
From a data plane perspective, we're going to form a tunnel this way through

10
00:26.130 --> 00:27.120
the MPLS

11
00:27.120 --> 00:31.000
provider and a tunnel this way through the internet provider.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.120 --> 00:31.000
provider and a tunnel this way through the internet provider.

12
00:31.000 --> 00:35.560
And so that would be two IPsec tunnels.

13
00:35.560 --> 00:37.440
Hopefully we're using IPsec.

14
00:37.440 --> 00:40.840
But we're not done there because we have to consider the control plane tunnels.

15
00:40.840 --> 00:46.550
I am actually building tunnels out to not just the V-Smart, so there's another

16
00:46.550 --> 00:47.160
two to

17
00:47.160 --> 00:51.930
the V-Smart, but I'm also building tunnels out to the V-Manage, which wasn't

18
00:51.930 --> 00:52.480
listed

19
00:52.480 --> 00:53.480
here.

20
00:53.480 --> 00:57.960
So keep that in mind that we're going to need to form tunnels this way to

21
00:57.960 --> 00:58.560
secure the

22
00:58.560 --> 01:02.320
communication between the V-Manage and the WAN edge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:58.560 --> 01:02.320
communication between the V-Manage and the WAN edge.

23
01:02.320 --> 01:06.390
So if we count up all of these tunnels, then we actually have a total of six

24
01:06.390 --> 01:06.960
tunnels

25
01:06.960 --> 01:11.360
because we have also two tunnels going to the V-Smart.

26
01:11.360 --> 01:19.170
And so these would be TLS or DTLS and two going to the V-Manage, again TLS or D

27
01:19.170 --> 01:20.040
TLS.

28
01:20.040 --> 01:21.440
Now what about the V-Bond?

29
01:21.440 --> 01:26.260
Well remember the V-Bond, we do form DTLS tunnels, but they actually end up

30
01:26.260 --> 01:27.800
breaking down

31
01:27.800 --> 01:33.600
to the SD-WAN edge devices after they've been torn down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:27.800 --> 01:33.600
to the SD-WAN edge devices after they've been torn down.

32
01:33.600 --> 01:37.400
But we do form tunnels to the V-Manage.

33
01:37.400 --> 01:42.160
So we're still not done because we have two to the V-Manage from the SD-WAN

34
01:42.160 --> 01:42.840
devices, but

35
01:42.840 --> 01:45.880
we also have two that the V-Bond is running.

36
01:45.880 --> 01:48.560
And remember the V-Bond always runs DTLS.

37
01:48.560 --> 01:53.430
Oh, and let's not forget that we do have a tunnel forming between the V-Manage

38
01:53.430 --> 01:53.880
and the

39
01:53.880 --> 01:54.880
V-Smart.

40
01:54.880 --> 01:57.840
So we'll actually add one more onto this.

41
01:57.840 --> 02:02.320
And so that gives us a total of nine tunnels.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:57.840 --> 02:02.320
And so that gives us a total of nine tunnels.

42
02:02.320 --> 02:05.820
So again, it's important for us to recognize it's not just about the data plane

43
02:05.820 --> 02:06.440
tunnels,

44
02:06.440 --> 02:10.130
but we also have tunnels on the control plane side of things, which includes

45
02:10.130 --> 02:11.000
the management

46
02:11.000 --> 02:14.560
and orchestration planes and devices as well.

47
02:14.560 --> 02:19.280
Now next, given the multi-tenant environment, how many VPNs will be used in

48
02:19.280 --> 02:20.000
total?

49
02:20.000 --> 02:25.520
So we know that we're going to need VPNs for each of the customers.

50
02:25.520 --> 02:30.500
Let's say again, VPN 10 for customer A and VPN 20 for customer B. Just remember
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:25.520 --> 02:30.500
Let's say again, VPN 10 for customer A and VPN 20 for customer B. Just remember

51
02:30.500 --> 02:30.760
that we're

52
02:30.760 --> 02:35.680
also using VPN 0 for the underlay.

53
02:35.680 --> 02:41.720
And we're using VPN 512 for the sake of management information.

54
02:41.720 --> 02:46.640
So we're actually using four total VPNs in this environment.

55
02:46.640 --> 02:50.000
Now next map out the OMP adjacencies that exist.

56
02:50.000 --> 02:58.520
Well, OMP is going to only exist between an edge device and V-Smart.

57
02:58.520 --> 03:02.240
And if we have multiple V-Smarts, then we'll have multiple connections per one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:58.520 --> 03:02.240
And if we have multiple V-Smarts, then we'll have multiple connections per one

58
03:02.240 --> 03:03.760
edge device.

59
03:03.760 --> 03:07.210
But when we're talking about just a single V-Smart as we have in the diagram

60
03:07.210 --> 03:08.520
here, my OMP

61
03:08.520 --> 03:11.160
connections are going to be here.

62
03:11.160 --> 03:20.000
For OMP and here as well, which means that we have a total of two adjacencies.

63
03:20.000 --> 03:26.240
The key point here, we do not form OMP adjacencies from when edge to when edge.

64
03:26.240 --> 03:30.370
The benefit of OMP and using the V-Smart is essentially a route reflector is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:26.240 --> 03:30.370
The benefit of OMP and using the V-Smart is essentially a route reflector is

65
03:30.370 --> 03:30.960
that we don't

66
03:30.960 --> 03:32.640
have to have a full mesh.

67
03:32.640 --> 03:38.940
All of my subnets that I'm learning will be advertised via OMP to the V-Smart

68
03:38.940 --> 03:39.360
and then

69
03:39.360 --> 03:42.440
pushed down to the other when edge devices.

70
03:42.440 --> 03:48.080
Now lastly, we're forming all of these tunnels, especially the data plane

71
03:48.080 --> 03:49.040
tunnels via these

72
03:49.040 --> 03:52.800
pseudo interfaces that we're calling T-Locks.

73
03:52.800 --> 03:55.320
But the T-Locks don't have an IP address associated.

74
03:55.320 --> 03:57.640
So how do I know how to connect?

75
03:57.640 --> 03:59.320
Well that is the job of OMP.

76
03:59.320 --> 04:02.000
OMP has those T-Lock routes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:59.320 --> 04:02.000
OMP has those T-Lock routes.

77
04:02.000 --> 04:04.520
Remember there are three different route types.

78
04:04.520 --> 04:09.930
The T-Lock route is going to say, hey, if you want to connect to T-Lock A, use

79
04:09.930 --> 04:10.840
this IP

80
04:10.840 --> 04:12.040
address.

81
04:12.040 --> 04:15.550
Because the T-Locks have the color information, I also know which WAN circuit

82
04:15.550 --> 04:17.280
provider to use.

83
04:17.280 --> 04:20.380
So this challenge was just intended to bring together a bunch of the different

84
04:20.380 --> 04:20.880
concepts

85
04:20.880 --> 04:23.120
that we talked about throughout the skill.

86
04:23.120 --> 04:27.440
There's a lot of information in here, but we just have a few key takeaways here

87
04:27.440 --> 04:27.720
.

88
04:27.720 --> 04:31.220
Namely, how many tunnels are formed, where tunnels are formed, what type of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
04:27.720 --> 04:31.220
Namely, how many tunnels are formed, where tunnels are formed, what type of

89
04:31.220 --> 04:31.720
tunnels

90
04:31.720 --> 04:34.440
are formed, and then also how T-Locks come together.

91
04:34.440 --> 04:37.990
We're going to want to remember those three pieces of information that make up

92
04:37.990 --> 04:38.600
a T-Lock.

93
04:38.600 --> 04:41.520
The fact that a T-Lock doesn't include its own IP address.

94
04:41.520 --> 04:44.800
And so we need to know how to connect to that and OMP is sort of the glue that

95
04:44.800 --> 04:45.240
brings

96
04:45.240 --> 04:46.480
everything together.

97
04:46.480 --> 04:49.120
I hope there's been informative for you and I'd like to thank you for viewing.
