All right, remember what adaptive QoS is.
The concept here is we want to apply adaptivity to our network shapers,
shapers being the concept of us preemptively dropping traffic
before sending it to our service provider
because we don't want our service provider to say,
eh, voice over IP packet, I don't know what it is,
I'm just going to drop it, whatever.
We want to make sure we're dropping non-critical traffic
so we always abide by our SLA.
Basically, we want to prevent our service provider
And so that's what traffic shaping does,
but adaptive QoS says that's great and all
for stable links like MPLS,
but the internet could probably use some dynamic adjustment
and fortunately we have the resources to do that
thanks to BFD, our tunnels,
and our ability to now dynamically move up and down
as far as our shapers are concerned.
So we need to be able to configure that range.
So how do we do that?
Well, we do a config-t
because this is an SD-WAN concept.
I'm going to get onto an interface directly
so I don't have to worry about class maps
or policy maps or anything like that.
Just get onto an interface.
Let's say gigabit ethernet one.
Typically, these are going to be our interfaces
that are facing service providers
because shaping is an outbound concept.
I'm always shaping things outbound
as I'm about to send them.
So from here, I simply use the QoS adaptive config.
So I'm going to say QoS-adaptive, hit enter,
and now we're going to see all kinds of options.
Well, really, we have three options,
period, downstream, and upstream.
So period is the first thing we might want to do.
This is the period over time,
basically the amount of time over which we want to evaluate
what a bandwidth average looks like.
So the shorter the period,
the more reactive it's going to be to spikes
and the longer the period, the less reactive it will be.
So the default is 15 minutes.
Let's just say I want to schedule it for 60 minutes.
Keep in mind that these are minutes,
not seconds, not hours, or anything like that.
It's truly saying 60 minutes.
And then I have to decide between downstream
and upstream connectivity.
So since I'm going outbound towards my service provider,
I'm going to say upstream here,
and then we'll find that I can do one of two things.
I can specify a shaping value,
which is what I want to do first.
Let's say I want to do 12,000 kilobits per second.
That would be 12 megabits per second.
So again, we see right here it's in kilobits per second.
So upstream 12,000, but now I want to specify a range.
So I'm going to say upstream again.
Now I'm going to use the range option here,
and I could say something like between 8,000 and 16,000.
And then I can commit this.
So that's it. That's all there is to it.
It's a pretty straightforward configuration.
Again, just to quickly review,
we're going to get onto the SD-WAN side,
get onto our outbound interface,
use this QoS adaptive command,
which enters into a new mode of operation,
at which point I can adjust the default period if I want to,
and I can specify upstream or downstream shaping.
And so I'm going to want to start
by specifying the shaping rate itself,
which is more or less what I'm aiming for,
but then give it a range that says,
hey, we're allowed to adapt down to this number
and up to this number depending on network conditions.
so let's go ahead and do that,
and we're going to find that it abides
exactly by this same process.
It's just at the graphical user interface.
So we're on the interface.
At this point, we should be pretty comfortable
with how we push interface level configurations down.
We're talking about a data policy
that's going to exist on an SD-WAN device,
and so that is going to require us
to change the feature templates.
So let's go ahead and do that.
Remember, policies are usually pushed out globally,
but in our case, we're just going to come down to,
oops, what are we doing here?
Configuration and templates, there we go,
and we want to get onto a template
that allows us to change interface commands,
and that would be right here.
I already put the mouse cursor over it,
but it's the feature template side of things.
So I'm going to go to feature templates.
I'm going to edit my interface.
Let's say it's my, well, let's just do the internet
because that's what it's supposed to be
is us using this on internet circuits.
So I'm going to edit my interface feature template,
this is how we want to configure our interface.
So I'm going to scroll up here a little bit
because it always puts me at the bottom
to ACL and QoS.
We actually, whoops, I actually collapsed it.
We pointed this out earlier,
but here's where adaptive QoS is.
So I'm just going to change this over to a global setting
and enable it.
And now that it's enabled,
we see I can change the adapt period.
It's defaulting to 15 minutes,
and I can say let's go ahead
and change the shaping rate upstream.
So I'm going to change this as well to global,
and then I'm going to set my minimum and default.
So what did we do before?
We said 12,000 kilobits per second,
and then the minimum was 8,000,
and the max upstream was 16,000.
So we'd update and push this out to our device,
and so that is how we go about configuring adaptive QoS
at both the CLI and the graphical user interface.