All right, let's take a moment, answer these questions together and just make
sure that
we've got all of this down as far as the major topics that we've discussed.
We are laying the groundwork for why QOS is so important as well as how we can
kind of
measure the success of whether our QOS is working.
And from here, we're going to launch ourselves into all the mechanisms we have
to deploy
in order to make QOS work.
So to start off with, match the traffic type to their classifications.
So we need a mission critical time-sensitive application. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we need a mission critical time-sensitive application.
That would be voiceover IP and video.
Time-sensitive is the key word there.
A non-critical example would probably be internet streaming and then the
mission critical, but
not time-sensitive.
Remember, we gave an example of those data center live migrations.
That would be a great concept here.
We don't need to prioritize that traffic over voiceover IP, for example.
But we do want it to happen in a timely fashion and so we'd give some
reservations around
it, but we don't need to worry about whether or not it's going to make it an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it, but we don't need to worry about whether or not it's going to make it an
extra 500
milliseconds or not.
Now match the concepts to the QOS model.
Remember, diff-serve and int-serve are two different models.
We have an upside for diff-serve and we're looking at the upside for diff-serve
.
This is the model that we use in our modern networks.
The biggest advantage is the fact that bandwidth is efficiently used.
The mechanism we use for this is not reserving bandwidth, but it's actually
tagging our packets
and doing those per-hot behaviors. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and doing those per-hot behaviors.
Int-serve, meanwhile, only wants to emulate those old circuit-style networks
and so we
are going to perform the mechanism here is the resource reservations using RSVP
and the
upside is that bandwidth is fully reserved.
Next what is the Cisco recommended voiceover IP threshold?
So now we're going to vault into these three different metrics.
Want to make sure that we know what the recommended thresholds are for each one
of these.
The one-way latency, don't be fooled here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The one-way latency, don't be fooled here.
Remember, the one-way latency is 150 milliseconds, not 300.
Recall that if we're going to test round trip time or RTT, it might go in 150
milliseconds
this way and 150 milliseconds that way and we might say okay, well that's 300
milliseconds,
but even if we have an RTT of 250 milliseconds, that might be problematic.
What if it was 50 milliseconds one way and 200 coming back?
Well that would exceed the one-way latency requirements and so that's why we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well that would exceed the one-way latency requirements and so that's why we
always have
to test one-way as best we can.
What is the Cisco recommended voiceover IP threshold for the average jitter?
It's also measured in milliseconds and again it's comparing the differences in
our latency.
So 30 milliseconds is the threshold for jitter, it's just something we're going
to have to
remember.
And lastly what is the Cisco recommended voiceover IP threshold for packet loss
?
Well it doesn't sound like much, it's 1% and yeah, I mean when we're talking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well it doesn't sound like much, it's 1% and yeah, I mean when we're talking
about voiceover
IP, we need to make sure that we keep as many of those packets alive as
possible, even dropping
1% of our voiceover IP packets can result in a noticeable slip of that mean
opinion
score MOS.
So let's make sure that we've got those different measurements down as far as
how we measure
them and what those thresholds are as well as understanding that we're going to
be vaulting
into the diff serve model and learning how exactly that all comes together. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
into the diff serve model and learning how exactly that all comes together.
I hope this has been informative for you and I'd like to thank you for viewing.