So recall, we have two different ways we can do this,
and we're going to start with the centralized version.
So let's go ahead and go to Configuration and Policies,
and I'm gonna add a centralized policy here.
And we're gonna skip groups of interest.
We already have those,
and we're not changing the topology or VPN membership,
but right here where we have traffic rules.
We used this tab earlier
to configure application-aware routing.
We also have the Traffic Data tab,
which is going to allow me to add a new traffic data policy
that has lots of different options in here.
So there've been a few times where we've seen this concept.
We see a lot of different data traffic policies,
like traffic engineering and service chain,
but right there is quality of service as well.
So let's go ahead and just quickly give this a name.
We'll call this QoS underscore centralized policy.
I'm not sure why I used all caps, but I did.
All right, and so this is QoS centralized policy.
And from here, I already added the QoS sequence type.
So now I'm gonna add a sequence rule,
and this is going to be match action.
As we mentioned, whether it's centralized or localized,
we're doing it match action.
So I can match against an application family list.
I could do, for example, real-time apps here.
And then under actions, make sure it's set to accept,
which it is by default.
With QoS, we're not usually dropping traffic.
We're usually sorting it into different queues.
And so now I can select forwarding class,
and I can specify the forwarding class here.
Now notice again, it's not a dropdown
because it doesn't know where this policy
is going to get applied
and which forwarding classes are available.
So I have to type it in manually,
and I have to remember what that forwarding class name was.
That's why I mentioned earlier,
very important to remember that.
So now I have to click this save match and actions.
Again, it always looks like
I want to click the big blue button,
but save match and actions here.
And usually I want to add another one.
And for best effort, I might just match against
some kind of source prefix list or destination.
Either way, it just says,
hey, we're matching all of the traffic.
I can also still match by DSCP, for example.
So I can say for DSCP zero, we're going to match this,
and we're going to put this
into our best effort forwarding class.
So again, scroll down, save match and actions.
And so now we've got our QoS sequence rules in place.
I'm going to go ahead and click save policy.
So now I've created this policy.
I can click next.
And now we're still not quite done
because we have to name this centralized policy.
So we're going to call this QoS.
I probably actually named that poorly before.
I think I didn't mean to call it a centralized policy.
We'll call this the QoS centralized policy.
Either way, just make sure your names have good application.
So those are QoS policy.
And now, just like with topology,
I had to do more stuff here.
With traffic data, I'm going to have to do it here.
I'm going to have to apply it to a site list.
Let's just say site 11.
Actually, let's just say both sites.
There we go, sites 11 and 12.
And then also for VPN 10, something like that.
And then I click the add button.
And now I can save my policy.
So at this point, I've saved it.
But again, it's a centralized policy.
So I come over here and I click activate.
It's going to push it to our controller,
the one controller we have in our lab environment.
And now I can click on this, do a config diff,
and scroll down to see what's getting pushed.
So it's an SD-WAN policy.
It's a data policy specifically.
And then here's all the information in here.
We see what we're matching,
specifically against an app list.
And then we are setting a forwarding class
to voice over IP.
Here we're matching DSCP zero, forwarding class best effort.
And then down here is where we actually apply
the data policy.
So let's go ahead and activate this
and push this out to our vSmart, our SD-WAN controllers.
So remember, we do have two ways of doing this.
The way we just demonstrated,
which is usually in all likelihood what we're going to do.
Because if it's a centralized policy,
it's getting pushed down everywhere.
And if it's getting pushed down everywhere,
then we have the same policy everywhere,
which is usually what we want.
QoS maps can vary.
They can go to different edges
and give us different bandwidths, potentially.
One site, we might have a 20 meg circuit.
Another site, we might have a 50 meg circuit.
But if we're assigning by percentages,
first of all, it might not matter.
Second of all, even in those cases,
usually the queues and the traffic assignment is the same,
which is why we can push this out centrally.
But what if we did want to do
the traffic assignment locally?
Well, again, we can do that via access control list.
So we're not going to do the full configuration,
but let's just demonstrate really quickly
what this looks like.
We're going to go to configuration policies,
go to the localized policies
and the access control list section.
And we're going to add a control list policy here,
give it a name and description,
add a sequence, sequence rule.
And essentially what we're getting here
is another method for matching actions.
So I can match on DSCP.
I could match on DSCP of 38 or whatever the situation is.
And then under actions, I, as we see,
I can apply a class to my actions
and I could type in a voice over IP
or whatever the situation is.
In fact, here, it actually gives us the dropdown,
which is kind of nice.
So we can select best effort or voice over IP here,
save matching actions and apply the access control list
to the whatever device that we're trying to push it out to.
So this is how we would do it
via localized traffic assignment.
Centralized traffic assignment is pretty common.
We're probably going to look at that,
but we should be comfortable with both methods.
In the end, what we're really doing
is we're creating that traffic assignment policy,
which pushes traffic into specific queues,
which is now enforced thanks to our QLS map,
which we pushed down via a localized data policy
to our edge devices.