WEBVTT

1
00:00.000 --> 00:07.800
So now it's time to talk about our fourth critical component for our SD-WAN

2
00:07.800 --> 00:09.040
environment,

3
00:09.040 --> 00:11.320
the WAN-edge devices.

4
00:11.320 --> 00:16.860
Now this is going to be sort of a generic discussion about the WAN-edge devices

5
00:16.860 --> 00:17.160
, not

6
00:17.160 --> 00:23.700
anyone in particular because many different Cisco products can be WAN-edge

7
00:23.700 --> 00:24.800
devices.

8
00:24.800 --> 00:29.360
They can operate in either autonomous mode or controller mode.

9
00:29.360 --> 00:33.640
So the catalyst 8000v is an example of that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.360 --> 00:33.640
So the catalyst 8000v is an example of that.

10
00:33.640 --> 00:36.520
We're going to be using that one in this course.

11
00:36.520 --> 00:43.000
Now there are many, many others, both virtual and physical routers and switches

12
00:43.000 --> 00:43.320
that can

13
00:43.320 --> 00:45.560
be WAN-edge devices.

14
00:45.560 --> 00:50.710
I've included a link below this video that will take you to Cisco's page

15
00:50.710 --> 00:51.440
listing the

16
00:51.440 --> 00:53.480
most current items.

17
00:53.480 --> 00:56.040
Hopefully they'll keep that updated.

18
00:56.040 --> 01:01.250
But either way, that is at least the current list of devices that can be WAN-
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:56.040 --> 01:01.250
But either way, that is at least the current list of devices that can be WAN-

19
01:01.250 --> 01:02.560
edge devices.

20
01:02.560 --> 01:10.440
So let's jump in and take a look at what the WAN-edge device actually is.

21
01:10.440 --> 01:16.610
So the WAN-edge devices are what make up the data plane of the SD-WAN

22
01:16.610 --> 01:18.360
architecture.

23
01:18.360 --> 01:23.700
These are the devices actually doing the packet forwarding on our networks

24
01:23.700 --> 01:24.560
between our WAN

25
01:24.560 --> 01:29.140
sites, traffic going from the WAN to the local network and from the local

26
01:29.140 --> 01:29.920
network to

27
01:29.920 --> 01:31.960
the WAN and so on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.920 --> 01:31.960
the WAN and so on.

28
01:31.960 --> 01:35.840
These are the devices actually doing that packet forwarding.

29
01:35.840 --> 01:40.120
Now these devices can be either hardware or software.

30
01:40.120 --> 01:41.960
We support both.

31
01:41.960 --> 01:47.800
Once again, there's a link below this video going to Cisco's compatibility list

32
01:47.800 --> 01:48.600
for WAN-edge

33
01:48.600 --> 01:51.960
devices in SD-WAN.

34
01:51.960 --> 01:55.080
Now that's going to be a continually updating list.

35
01:55.080 --> 01:58.240
So hopefully they maintain that same URL.

36
01:58.240 --> 02:05.300
However, they do maintain a list of the current hardware and software routers
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:58.240 --> 02:05.300
However, they do maintain a list of the current hardware and software routers

37
02:05.300 --> 02:07.080
that can participate

38
02:07.080 --> 02:10.160
as SD-WAN-edge devices.

39
02:10.160 --> 02:12.520
Now what do these things actually do?

40
02:12.520 --> 02:18.120
Well in a large extent, they are very very similar to a traditional router.

41
02:18.120 --> 02:22.320
In that, they're going to have support for standard protocols such as our

42
02:22.320 --> 02:23.560
routing protocols.

43
02:23.560 --> 02:29.960
They support RIP, OSPF, EIGRP, BGP.

44
02:29.960 --> 02:35.350
They support failover mechanisms such as BFD, if you're not familiar with that,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:29.960 --> 02:35.350
They support failover mechanisms such as BFD, if you're not familiar with that,

45
02:35.350 --> 02:35.400
that's

46
02:35.400 --> 02:38.040
bi-directional forwarding detection.

47
02:38.040 --> 02:43.050
We use this to accelerate the detection of a failed link, therefore allowing

48
02:43.050 --> 02:44.640
other features

49
02:44.640 --> 02:50.480
such as our routing protocols and other things to failover quicker.

50
02:50.480 --> 02:55.150
One of those other things could also be VRRP, which is Virtual Router Redund

51
02:55.150 --> 02:56.400
ancy Protocol,

52
02:56.400 --> 02:59.480
which we can use for first-hop redundancy.

53
02:59.480 --> 03:02.560
And we're just going to say much more here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:59.480 --> 03:02.560
And we're just going to say much more here.

54
03:02.560 --> 03:07.260
Basically they support all of the features that a router would need to support

55
03:07.260 --> 03:07.920
on today's

56
03:07.920 --> 03:09.960
modern networks.

57
03:09.960 --> 03:16.450
Other attributes, well it supports a local, rib, and fib that's your routing

58
03:16.450 --> 03:17.600
information

59
03:17.600 --> 03:23.450
base and your forwarding information base to actually perform packet forwarding

60
03:23.450 --> 03:23.480
.

61
03:23.480 --> 03:26.680
Now we're differentiating this because we'll talk about remote routing in a

62
03:26.680 --> 03:27.160
minute.

63
03:27.160 --> 03:31.640
This is simply talking about local that just like any other router, they're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:27.160 --> 03:31.640
This is simply talking about local that just like any other router, they're

64
03:31.640 --> 03:32.800
going to maintain

65
03:32.800 --> 03:37.160
a local routing table for connected interfaces.

66
03:37.160 --> 03:46.320
Also these support NetConf and CLI for both VManage and Local Management.

67
03:46.320 --> 03:52.140
As we mentioned in our previous video, these also maintain a DTLS control plane

68
03:52.140 --> 03:53.280
tunnel for

69
03:53.280 --> 03:56.600
OMP to those VSmart controllers.

70
03:56.600 --> 04:01.840
Again, this is for management, statistic reporting, and various other functions
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:56.600 --> 04:01.840
Again, this is for management, statistic reporting, and various other functions

71
04:01.840 --> 04:03.280
and communication

72
04:03.280 --> 04:08.760
that need to happen between the WAN Edge device and the VSmart controller.

73
04:08.760 --> 04:13.560
However, please note that that is just a control plane tunnel.

74
04:13.560 --> 04:20.200
For the data plane, we also maintain an IPsec tunnel, again for the data plane.

75
04:20.200 --> 04:26.300
This is going to go to other WAN Edge routers and the cool thing here is it's

76
04:26.300 --> 04:27.840
only as needed.

77
04:27.840 --> 04:32.890
We're not simply going to create a full mesh of tunnels between all of your WAN
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
04:27.840 --> 04:32.890
We're not simply going to create a full mesh of tunnels between all of your WAN

78
04:32.890 --> 04:34.480
Edge routers.

79
04:34.480 --> 04:39.720
They're going to be built as needed when traffic needs to go from one remote

80
04:39.720 --> 04:41.800
site to another.

81
04:41.800 --> 04:46.370
And like we said before, these are going to support all of the other data plane

82
04:46.370 --> 04:47.040
features

83
04:47.040 --> 04:50.440
that a traditional modern network would support.

84
04:50.440 --> 04:54.350
So we're going to support all of those fun things like quality of service,

85
04:54.350 --> 04:55.280
access control

86
04:55.280 --> 04:59.400
lists, port mirroring, policy-based routing.

87
04:59.400 --> 05:05.930
And again, much more because the majority of these devices are running iOS XE,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:59.400 --> 05:05.930
And again, much more because the majority of these devices are running iOS XE,

88
05:05.930 --> 05:06.520
which

89
05:06.520 --> 05:13.600
means it's a fully functional router, we're simply controlling it with SD WAN.

90
05:13.600 --> 05:17.890
Now sort of calling back to this first point up here with the support for a

91
05:17.890 --> 05:18.800
local rib and

92
05:18.800 --> 05:25.000
fib, we will say that WAN Edge devices do have local intelligence.

93
05:25.000 --> 05:30.210
Again, if we're just routing within the local site, then we don't need any
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:25.000 --> 05:30.210
Again, if we're just routing within the local site, then we don't need any

94
05:30.210 --> 05:31.560
assistance from

95
05:31.560 --> 05:32.760
VSMART.

96
05:32.760 --> 05:37.720
In other words, it maintains a routing table of your connected interfaces.

97
05:37.720 --> 05:44.730
However, when traffic needs to go between the sites, this is where OMP comes in

98
05:44.730 --> 05:44.880
.

99
05:44.880 --> 05:52.800
As we mentioned in a previous video, OMP is the routing protocol for SD WAN.

100
05:52.800 --> 05:56.720
We maintain sessions with the VSMART controllers.

101
05:56.720 --> 06:01.860
Those VSMART controllers then provide the intelligence for the offsite
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:56.720 --> 06:01.860
Those VSMART controllers then provide the intelligence for the offsite

102
06:01.860 --> 06:02.960
decisions.

103
06:02.960 --> 06:05.840
In other words, it's the routing table.

104
06:05.840 --> 06:12.000
That intelligence is the packet forwarding information that's being collected

105
06:12.000 --> 06:12.960
on VSMART.

106
06:12.960 --> 06:19.090
If you remember a few videos ago, I compared OMP to BGP, and this is where some

107
06:19.090 --> 06:19.760
of that

108
06:19.760 --> 06:21.680
similarity comes in.

109
06:21.680 --> 06:27.680
The VSMART controllers are essentially acting as route reflectors in a BGP

110
06:27.680 --> 06:29.040
environment.

111
06:29.040 --> 06:33.250
They take all of the routes, all of the OMP information from all of the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
06:29.040 --> 06:33.250
They take all of the routes, all of the OMP information from all of the

112
06:33.250 --> 06:34.600
different sites.

113
06:34.600 --> 06:38.640
They coordinate all of that information together into one table and then

114
06:38.640 --> 06:39.800
disseminate that out

115
06:39.800 --> 06:45.480
to all of the other edges so that they can all make the necessary decisions.

116
06:45.480 --> 06:50.750
So in this video, we jumped in and talked in a little bit more detail about the

117
06:50.750 --> 06:51.080
WAN

118
06:51.080 --> 06:52.560
Edge devices.

119
06:52.560 --> 06:57.520
Again, we didn't talk about specific devices that can be WAN Edge devices

120
06:57.520 --> 06:58.480
because that

121
06:58.480 --> 07:04.600
is an ever-growing list that Cisco supports in the SD WAN environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
06:58.480 --> 07:04.600
is an ever-growing list that Cisco supports in the SD WAN environment.

122
07:04.600 --> 07:07.520
But we did want to talk about what it does.

123
07:07.520 --> 07:12.160
And again, it's the data plane for our SD WAN environment.

124
07:12.160 --> 07:17.160
This is the device that actually forwards the traffic based on information from

125
07:17.160 --> 07:17.920
the VSMART

126
07:17.920 --> 07:21.480
controller that it learned over OMP.

127
07:21.480 --> 07:26.880
So that takes care of the four major components that we need in our SD WAN

128
07:26.880 --> 07:28.240
environment.

129
07:28.240 --> 07:32.920
That also means that that's everything we need to cover in this skill except
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
07:28.240 --> 07:32.920
That also means that that's everything we need to cover in this skill except

130
07:32.920 --> 07:33.400
for the

131
07:33.400 --> 07:34.680
challenge.

132
07:34.680 --> 07:39.120
So go ahead and tackle the challenge, and I'll see you in the solution video on

133
07:39.120 --> 07:39.360
the

134
07:39.360 --> 07:40.080
other side.