WEBVTT

1
00:00.000 --> 00:07.280
So now it's time to jump into the SD-WAN Manager interface and take a look at

2
00:07.280 --> 00:07.480
how to

3
00:07.480 --> 00:09.600
actually configure these policies.

4
00:09.600 --> 00:14.000
We'll start by looking at the interface for the localized policies.

5
00:14.000 --> 00:17.120
We'll go through the interface, although we're not going to actually configure

6
00:17.120 --> 00:17.360
one.

7
00:17.360 --> 00:20.600
And then we'll take a look at our centralized policies.

8
00:20.600 --> 00:26.360
And then we'll actually create an AAR policy and attempt to activate it.

9
00:26.360 --> 00:28.120
You'll see what I mean by attempt.

10
00:28.120 --> 00:31.420
It's not exactly going to work, but we'll take a look at why.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.120 --> 00:31.420
It's not exactly going to work, but we'll take a look at why.

11
00:31.420 --> 00:34.600
And then we'll be fixing it in an upcoming video.

12
00:34.600 --> 00:38.800
But all of that said, let's jump into the interface and get started configuring

13
00:38.800 --> 00:39.040
our

14
00:39.040 --> 00:42.160
policies.

15
00:42.160 --> 00:47.420
So starting off here on the SD-WAN homepage, let's go ahead and go over here to

16
00:47.420 --> 00:48.760
Configuration.

17
00:48.760 --> 00:51.680
Then we'll go to Policies.

18
00:51.680 --> 00:56.130
And we can see right away that we have tabs up here at the top for our

19
00:56.130 --> 00:57.640
centralized policy

20
00:57.640 --> 01:00.160
versus our localized policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:57.640 --> 01:00.160
versus our localized policy.

21
01:00.160 --> 01:04.060
So like I said, let's start by taking a look at the localized policies and then

22
01:04.060 --> 01:04.600
we'll come

23
01:04.600 --> 01:09.280
back here and do a little more exploring in the centralized policy.

24
01:09.280 --> 01:14.920
So for that we simply click on Localize Policy and we'll say Add a Policy.

25
01:14.920 --> 01:20.440
Notice here the first thing it wants us to do is create groups of interest.

26
01:20.440 --> 01:25.290
We can define these groups of interest by creating these various lists that we

27
01:25.290 --> 01:25.800
see over

28
01:25.800 --> 01:27.560
here on the left.

29
01:27.560 --> 01:31.600
We see here that we could, for example, match on an ASPhath.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:27.560 --> 01:31.600
We see here that we could, for example, match on an ASPhath.

30
01:31.600 --> 01:38.160
We can match on BGP community strings or data prefixes, class maps.

31
01:38.160 --> 01:44.280
We can actually do a police here or we can just match on VPN, for example.

32
01:44.280 --> 01:47.710
Now again, since we're not really configuring this right now, we won't create

33
01:47.710 --> 01:48.360
one of these

34
01:48.360 --> 01:51.800
just yet, but we will go ahead and hit Next.

35
01:51.800 --> 01:56.170
So we can see we have some other choices here where we can do a QOS map, a

36
01:56.170 --> 01:57.520
policy rewrite,

37
01:57.520 --> 02:00.000
or a VPN QOS map.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
02:00.000 --> 02:04.750
We can also add a QOS map here, but again, we don't have to configure anything

39
02:04.750 --> 02:05.240
under

40
02:05.240 --> 02:09.320
forwarding classes or QOS either.

41
02:09.320 --> 02:13.080
So we could simply scroll down, hit Next again.

42
02:13.080 --> 02:16.560
Here's where we can configure our access control lists.

43
02:16.560 --> 02:21.040
And then finally, if we hit Next, this is where we would create the policy

44
02:21.040 --> 02:21.800
itself.

45
02:21.800 --> 02:27.440
So here we could say, for example, add a route policy, we'll say create a new

46
02:27.440 --> 02:27.600
one.

47
02:27.600 --> 02:33.020
And here is where we make that list of sequences that's going to control how
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:27.600 --> 02:33.020
And here is where we make that list of sequences that's going to control how

48
02:33.020 --> 02:34.280
the traffic is

49
02:34.280 --> 02:35.280
handled.

50
02:35.280 --> 02:38.400
So we can simply add new sequence types.

51
02:38.400 --> 02:41.040
So we could add, for example, a route type.

52
02:41.040 --> 02:44.960
We could put in a sequence rule here, matching on certain protocols.

53
02:44.960 --> 02:48.760
We can see here where it is a match action.

54
02:48.760 --> 02:52.210
So we're going to match on the things on the left, and we're going to do the

55
02:52.210 --> 02:52.960
actions of

56
02:52.960 --> 02:55.320
whatever's on the right.

57
02:55.320 --> 03:00.650
If you've ever worked with route maps on a traditional Cisco iOS router, then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:55.320 --> 03:00.650
If you've ever worked with route maps on a traditional Cisco iOS router, then

58
03:00.650 --> 03:01.160
this should

59
03:01.160 --> 03:03.200
be very familiar to you.

60
03:03.200 --> 03:06.360
This is going to be building route maps in the background.

61
03:06.360 --> 03:10.640
Now, like I said, we're not going to be creating a localized policy.

62
03:10.640 --> 03:13.960
So let's just scroll down here and hit Cancel.

63
03:13.960 --> 03:17.200
This will bring us back to our main configuration page.

64
03:17.200 --> 03:19.920
Now let's go to centralized policy.

65
03:19.920 --> 03:24.400
Now there are two things here we can do under the centralized policies.

66
03:24.400 --> 03:30.520
First, we could add a default AAR and QoS policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:24.400 --> 03:30.520
First, we could add a default AAR and QoS policy.

67
03:30.520 --> 03:33.590
Now we're not going to be going through that here, but you can simply go

68
03:33.590 --> 03:34.520
through the wizard

69
03:34.520 --> 03:40.760
and it will let you set up default AAR and QoS policies as the name suggests.

70
03:40.760 --> 03:44.560
Or of course, we can create our own policy, which is what we want to do.

71
03:44.560 --> 03:47.520
We're going to go ahead and hit Add Policy.

72
03:47.520 --> 03:52.800
Now the first thing to note here is it starts off with our application lists

73
03:52.800 --> 03:53.240
here under

74
03:53.240 --> 03:55.280
Create Groups of Interest.

75
03:55.280 --> 03:58.240
That's because this is application-aware routing.

76
03:58.240 --> 04:01.400
So these are the AAR applications.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:58.240 --> 04:01.400
So these are the AAR applications.

77
04:01.400 --> 04:04.280
Notice we can also match on things like color.

78
04:04.280 --> 04:08.200
And again, we have community and data prefix, police-ers.

79
04:08.200 --> 04:13.810
But we can match on far more here, such as prefix lists, site lists, T-locks,

80
04:13.810 --> 04:14.360
VPNs, and

81
04:14.360 --> 04:15.360
so on.

82
04:15.360 --> 04:18.280
So there's a lot of different things here that we can match on.

83
04:18.280 --> 04:24.040
You would of course want to choose what would be appropriate in your case.

84
04:24.040 --> 04:28.600
Just for this example, why don't we go ahead and start with making a site list?

85
04:28.600 --> 04:31.200
We'll make a new site list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:28.600 --> 04:31.200
We'll make a new site list.

86
04:31.200 --> 04:35.160
We'll call it SL for site list, underscore.

87
04:35.160 --> 04:38.160
And let's just make this for site 100.

88
04:38.160 --> 04:42.560
For the site, we'll add site 100 as the name implies.

89
04:42.560 --> 04:44.160
We'll hit Add.

90
04:44.160 --> 04:46.760
And then let's also create a VPN list.

91
04:46.760 --> 04:49.560
We'll call this VL for VPN list.

92
04:49.560 --> 04:54.200
And then we'll simply call this VPN10 for the VPN.

93
04:54.200 --> 04:56.770
Notice by the way, although I'm not doing it and it's very grayed out,

94
04:56.770 --> 04:57.400
hopefully you

95
04:57.400 --> 05:00.920
can read it, where it gives you an example of how you can do this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:57.400 --> 05:00.920
can read it, where it gives you an example of how you can do this.

96
05:00.920 --> 05:05.000
You can put in a single number, such as 10, like we're about to do.

97
05:05.000 --> 05:09.680
You can do a range separated by commas, or you can do a range with a hyphen to

98
05:09.680 --> 05:10.280
include

99
05:10.280 --> 05:14.240
every number between two given endpoints.

100
05:14.240 --> 05:19.520
So for us, we're just going to do VPN 10, and we'll go ahead and hit Add.

101
05:19.520 --> 05:23.640
This is really all we need to create a very simple policy.

102
05:23.640 --> 05:26.200
So let's just go ahead and hit next.

103
05:26.200 --> 05:32.040
Here if we wanted to, we could specify a topology or a VPN membership.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:26.200 --> 05:32.040
Here if we wanted to, we could specify a topology or a VPN membership.

104
05:32.040 --> 05:33.160
This is not necessary.

105
05:33.160 --> 05:34.840
We don't have to do this.

106
05:34.840 --> 05:40.060
We are still going to be applying it to a site and a VPN in our last step up

107
05:40.060 --> 05:40.720
here.

108
05:40.720 --> 05:44.320
So for this step, we can just go ahead and hit next.

109
05:44.320 --> 05:48.630
Then here under the Configure Traffic Rules, under Application Aware Routing,

110
05:48.630 --> 05:49.360
we're going

111
05:49.360 --> 05:50.920
to make a new policy.

112
05:50.920 --> 05:54.320
So we'll say Add Policy, Create New.

113
05:54.320 --> 05:56.800
We of course have to give it a name.

114
05:56.800 --> 05:59.520
We'll simply call this AAR Policy.

115
05:59.520 --> 06:03.400
And of course, you could get very fancy with the description here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:59.520 --> 06:03.400
And of course, you could get very fancy with the description here.

116
06:03.400 --> 06:08.080
But notice regardless of how detailed you choose to get, it's not optional.

117
06:08.080 --> 06:10.520
So we have to put something in here.

118
06:10.520 --> 06:12.840
We'll just say AAR Policy.

119
06:12.840 --> 06:16.360
Next, let's add a sequence type.

120
06:16.360 --> 06:21.040
Notice by the way, before we add one, there is only one sequence, which is the

121
06:21.040 --> 06:21.600
default

122
06:21.600 --> 06:24.400
action here to drop.

123
06:24.400 --> 06:26.200
We can't edit this action.

124
06:26.200 --> 06:29.920
This is the default that comes at the end of every policy.

125
06:29.920 --> 06:33.380
But what we want to do is we want to add our own, so we're going to add a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
06:29.920 --> 06:33.380
But what we want to do is we want to add our own, so we're going to add a

126
06:33.380 --> 06:34.920
sequence type.

127
06:34.920 --> 06:37.640
We'll add a sequence rule.

128
06:37.640 --> 06:41.080
We'll come over here to the Application and Family list.

129
06:41.080 --> 06:46.840
And under the dropdown, let's just go ahead and choose App Bulk Data.

130
06:46.840 --> 06:51.200
So for Application Bulk Data, what do we want to do with it?

131
06:51.200 --> 06:53.880
Well, we'll come over here to Actions.

132
06:53.880 --> 06:59.070
For the Actions, we're going to set the SLA class list, and we'll set this to

133
06:59.070 --> 07:00.840
Bulk Data.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:59.070 --> 07:00.840
Bulk Data.

134
07:00.840 --> 07:05.120
We can also set something, for example, like the color if we wanted to.

135
07:05.120 --> 07:08.960
So let's set this to something like, for example, Bronze.

136
07:08.960 --> 07:14.920
Once this is configured the way we want, we say Save, Match, and Actions.

137
07:14.920 --> 07:17.600
And that's our first sequence.

138
07:17.600 --> 07:22.600
Then we'll add another sequence rule here for the Application type.

139
07:22.600 --> 07:24.840
We'll set this to Voice Apps.

140
07:24.840 --> 07:28.360
For the Actions, let's again set our SLA list.

141
07:28.360 --> 07:31.480
For this, we'll set it to Voice and Video.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
07:28.360 --> 07:31.480
For this, we'll set it to Voice and Video.

142
07:31.480 --> 07:35.400
And for the preferred color, let's go ahead and set this to Gold.

143
07:35.400 --> 07:38.760
Once again, we'll say Save, Match, and Actions.

144
07:38.760 --> 07:44.680
So now we have our two sequences under the app route, Application Route.

145
07:44.680 --> 07:48.340
So let's say Save Application Aware Routing Policy.

146
07:48.340 --> 07:53.340
So we see here we now have our policy called AAR_Policy.

147
07:53.340 --> 07:54.980
Now let's go ahead and scroll down.

148
07:54.980 --> 07:56.500
We'll hit Next.

149
07:56.500 --> 08:00.460
So when we actually apply this to the sites and VPNs, remember what we're doing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
07:56.500 --> 08:00.460
So when we actually apply this to the sites and VPNs, remember what we're doing

150
08:00.460 --> 08:00.900
is we're

151
08:00.900 --> 08:05.940
configuring our traffic rules into the policy and applying it.

152
08:05.940 --> 08:10.250
So this is actually sort of a QoS policy that we're applying here simply

153
08:10.250 --> 08:10.900
because of

154
08:10.900 --> 08:13.380
what we put into the policy.

155
08:13.380 --> 08:16.180
Once again, we have to give it a description.

156
08:16.180 --> 08:20.410
Then what we have to do is go to our Application Aware Routing and we need to

157
08:20.410 --> 08:21.620
add our new site

158
08:21.620 --> 08:24.340
region list and VPN list.

159
08:24.340 --> 08:28.360
So for the site list, we're going to choose the site list that we created

160
08:28.360 --> 08:29.220
earlier.

161
08:29.220 --> 08:31.620
Then we select our VPN list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
08:29.220 --> 08:31.620
Then we select our VPN list.

162
08:31.620 --> 08:35.460
Once both of these are selected, we come over here, we hit Add.

163
08:35.460 --> 08:40.280
And at this point, if everything is correct, we should be able to hit Preview

164
08:40.280 --> 08:40.740
or we'll

165
08:40.740 --> 08:43.660
get an error that something's not correct.

166
08:43.660 --> 08:48.580
As we can see here, it's listing out the entire policy that we just wrote and

167
08:48.580 --> 08:49.100
what it's going

168
08:49.100 --> 08:53.580
to be putting into the policy as it gets deployed.

169
08:53.580 --> 08:59.740
As you can see, particularly the voice apps has a rather long list included.

170
08:59.740 --> 09:03.340
But overall, this is the policy that we're trying to write.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

170
08:59.740 --> 09:03.340
But overall, this is the policy that we're trying to write.

171
09:03.340 --> 09:07.940
And we can see each of the different steps we put in here where we gave it the

172
09:07.940 --> 09:08.580
SLA class

173
09:08.580 --> 09:13.820
for say bulk data and the SLA class for voice and video.

174
09:13.820 --> 09:18.710
We can see those requirements being listed there for the traffic engineering

175
09:18.710 --> 09:19.340
policy.

176
09:19.340 --> 09:25.510
Then we see under the App Route policy how it's matching on our VPN lists, the

177
09:25.510 --> 09:26.020
app list

178
09:26.020 --> 09:29.180
type and then setting the action.

179
09:29.180 --> 09:32.620
We see that for each of our different classes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

179
09:29.180 --> 09:32.620
We see that for each of our different classes.

180
09:32.620 --> 09:37.940
Once everything here looks OK, we'll go ahead and save policy.

181
09:37.940 --> 09:42.140
And we see here that we now have our centralized policy.

182
09:42.140 --> 09:48.260
However, notice that under activated, it says false.

183
09:48.260 --> 09:53.260
So although we have our policy, it's not yet activated.

184
09:53.260 --> 09:56.620
So that's something that we're going to want to change.

185
09:56.620 --> 10:00.300
So what we want to do is click on this little menu over here to the side and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
09:56.620 --> 10:00.300
So what we want to do is click on this little menu over here to the side and we

186
10:00.300 --> 10:02.500
click activate.

187
10:02.500 --> 10:06.580
Notice however, that we're getting an error message here.

188
10:06.580 --> 10:12.480
It's telling us that our vSmart controllers, which of course I only have one of

189
10:12.480 --> 10:12.820
, but it

190
10:12.820 --> 10:17.520
can't activate the policy on that vSmart controller because that vSmart

191
10:17.520 --> 10:19.460
controller is not in the

192
10:19.460 --> 10:20.460
manage mode.

193
10:20.460 --> 10:26.070
Now, of course, if your controllers are already in the manage mode, you wouldn

194
10:26.070 --> 10:28.020
't get this message.

195
10:28.020 --> 10:31.020
But we have so we have to deal with this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
10:28.020 --> 10:31.020
But we have so we have to deal with this.

196
10:31.020 --> 10:34.260
And that's exactly what we're going to do next.

197
10:34.260 --> 10:39.070
So in this video, we mainly wanted to take a look at how to actually create the

198
10:39.070 --> 10:40.100
policies.

199
10:40.100 --> 10:43.780
So we took a look at the localized policies.

200
10:43.780 --> 10:47.020
We didn't really complete one, but we took a look at the interface.

201
10:47.020 --> 10:52.200
And then we went through and we actually created a centralized policy in this

202
10:52.200 --> 10:52.900
case, sort of

203
10:52.900 --> 10:56.340
wrapped around quality of service or QoS.

204
10:56.340 --> 11:00.350
But the important thing is notice that when we went to apply it, the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

204
10:56.340 --> 11:00.350
But the important thing is notice that when we went to apply it, the

205
11:00.350 --> 11:01.740
controllers have to

206
11:01.740 --> 11:05.780
be in vManage mode and currently ours is not.

207
11:05.780 --> 11:09.440
And the reason for that is if you've been following through this course, we

208
11:09.440 --> 11:09.980
haven't had

209
11:09.980 --> 11:13.140
a reason to do this with our controllers yet.

210
11:13.140 --> 11:14.740
But that's what we're going to have to do.

211
11:14.740 --> 11:16.620
And we'll do that in the next video.

212
11:16.620 --> 11:17.460
- Thank you.