Professional Documents
Culture Documents
03-MQC AutoQoS PDF
03-MQC AutoQoS PDF
QoS CLI
AutoQoS
Modular
QoS
CLI
• The
MQC
provides
a
modular
approach
to
configuraEon
of
QoS
mechanisms.
• First,
build
modules
defining
classes
of
traffic.
• Then,
build
modules
defining
QoS
policies
and
assign
classes
to
policies.
• Finally,
assign
the
policy
modules
to
interfaces.
Modular
QoS
CLI
Components
Define
Classes
of
Define
QoS
Policies
for
Apply
a
Service
Policy
Traffic
Classes
“What
will
be
done
to
“Where
will
this
policy
“What
traffic
do
we
this
traffic?”
be
implemented?”
care
about?”
Defines
a
policy
map,
which
configures
the
ATaches
a
service
Each
class
of
traffic
is
QoS
features
associated
policy
configured
with
a
defined
using
a
class
with
a
traffic
class
policy
map
to
an
map.
previously
idenEfied
interface.
using
a
class
map.
Class
Maps
• “What
traffic
do
we
care
about?”
• Each
class
is
idenEfied
using
a
class
map.
• A
traffic
class
contains
three
major
elements:
– A
case-‐sensiEve
name
– A
series
of
match
commands
– If
more
than
one
match
command
exists
in
the
traffic
class,
an
instrucEon
on
how
to
evaluate
these
match
commands
• Class
maps
can
operate
in
two
modes:
– Match
all:
all
condiEons
have
to
succeed
– Match
any:
at
least
one
condiEon
must
succeed
• The
default
mode
is
match
all.
• MulEple
traffic
classes
can
be
configured
as
a
single
traffic
class
(nested).
ClassificaEon
Using
Class
Maps
• Example
policy:
– Shape
all
traffic
on
FastEthernet
to
2
Mbps.
– Out
of
the
2
Mbps,
guarantee
1
Mbps
to
HTTP
traffic.
Service
Policy
• “Where
will
this
policy
be
implemented?”
• ATaches
a
traffic
policy
configured
with
a
policy
map
to
an
interface.
• Service
policies
can
be
applied
to
an
interface
for
inbound
or
outbound
packets.
Summary
• MQC
is
a
modular
approach
to
designing
and
implemenEng
an
overall
QoS
policy.
• Applying
an
overall
QoS
policy
involves
three
steps:
defining
class
maps
to
idenEfy
classes
of
traffic,
defining
QoS
policy
maps,
and
assigning
the
policy
maps
to
interfaces.
• Each
class
of
traffic
is
defined
in
a
class
map
module.
• The
class-‐map
global
configuraEon
command
is
used
to
create
a
class
map
and
enter
the
class-‐map
configuraEon
mode.
The
show
class-‐map
command
lists
all
class
maps
with
their
match
statements.
Summary
(Cont.)
• A
policy
map
module
defines
a
traffic
policy,
which
configures
the
QoS
features
associated
with
a
traffic
class
previously
idenEfied
using
a
class
map.
• The
service-‐policy
command
assigns
a
single
policy
map
to
mulEple
interfaces
or
assigns
mulEple
policy
maps
to
a
single
interface
(a
maximum
of
one
in
each
direcEon,
inbound
and
outbound).
• A
service
policy
aTaches
a
traffic
policy
configured
with
a
policy
map
to
an
interface.
Example:
Complete
MQC
ConfiguraEon
• two
traffic
classes
are
created
and
their
match
criteria
are
defined.
• For
the
first
traffic
class,
called
class1,
access
control
list
(ACL)
101
is
used
as
the
match
criterion.
• For
the
second
traffic
class,
called
class2,
ACL
102
is
used
as
the
match
criterion.
• Packets
are
checked
against
the
contents
of
these
ACLs
to
determine
if
they
belong
to
the
class.
Traffic
Classes
Defined
• Router(config)#
class-‐map
class1
• Router(config-‐cmap)#
match
access-‐group
101
• Router(config-‐cmap)#
exit
• Router(config)#
class-‐map
class2
• Router(config-‐cmap)#
match
access-‐group
102
• Router(config-‐cmap)#
exit
Traffic
Policy
Created
• a
traffic
policy
called
policy1
is
defined
to
contain
policy
specificaEons
for
the
two
classes:
class1
and
class2.
The
match
criteria
for
these
classes
was
defined
in
the
traffic
classes.
• For
class1,
the
policy
includes
a
bandwidth
allocaEon
request
and
a
maximum
packet
count
limit
for
the
queue
reserved
for
the
class.
• For
class2,
the
policy
specifies
only
a
bandwidth
allocaEon
request.
• Router(config)#
policy-‐map
policy1
• Router(config-‐pmap)#
class
class1
• Router(config-‐pmap-‐c)#
bandwidth
3000
• Router(config-‐pmap-‐c)#
queue-‐limit
30
• Router(config-‐pmap-‐c)#
exit
• Router(config-‐pmap)#
class
class2
• Router(config-‐pmap-‐c)#
bandwidth
2000
• Router(config-‐pmap-‐c)#
exit
Traffic
Policy
ATached
to
an
Interface
• Aoer
a
traffic
policy
is
defined
with
the
policy-‐
map
command,
the
traffic
policy
can
be
aTached
to
one
or
more
interfaces
to
specify
the
traffic
policy
for
those
interfaces
by
using
the
service-‐
policy
command
in
interface
configuraEon
mode.
• Although
the
same
traffic
policy
can
be
assigned
to
mulEple
interfaces,
each
interface
can
have
only
one
traffic
policy
aTached
at
the
input
and
a
single
traffic
policy
aTached
at
the
output.
• Router(config)#
interface
e1/1
• Router(config-‐if)#
service-‐policy
output
policy1
• Router(config-‐if)#
exit
• Router(config)#
interface
fa1/0/0
• Router(config-‐if)#
service-‐policy
output
policy1
• Router(config-‐if)#
exit
CISCO
AUTO
QOS
VOIP
AutoQoS
• ability
to
deploy
QoS
features
for
converged
IP
telephony
and
data
networks
– simplifies
and
automates
the
MQC,
definiEon
of
traffic
classes,
and
the
creaEon
and
configuraEon
of
traffic
policies.
• generates
traffic
classes
and
policy
map
CLI
templates.
• When
it
is
configured
at
the
interface,
the
traffic
receives
the
required
QoS
treatment
automaEcally.
When
to
use
AutoQoS
• Small-‐
to
medium-‐sized
businesses
that
must
deploy
IP
telephony
quickly,
but
lack
the
experience
and
staffing
to
plan
and
deploy
IP
QoS
services.
• Large
enterprises
that
need
to
deploy
Cisco
telephony
soluEons
on
a
large
scale
while
reducing
the
costs,
complexity,
and
Eme
frame
for
deployment,
and
ensuring
that
the
appropriate
QoS
for
voice
applicaEons
is
being
set
in
a
consistent
fashion.
• InternaEonal
enterprises
or
service
providers
requiring
QoS
for
VoIP
in
different
regions
of
the
world
where
liTle
experEse
exists
and
where
provisioning
QoS
remotely
and
across
different
Eme
zones
is
difficult.
• Service
providers
requiring
a
template-‐driven
approach
for
delivering
managed
services
and
QoS
for
voice
traffic
to
many
customer
premise
devices.
AutoQoS
(Cont.)
• ApplicaEon
ClassificaEon
-‐
NBAR
– AutomaEcally
discovers
applicaEons
and
provides
appropriate
QoS
treatment
• Policy
GeneraEon
– AutomaEcally
generates
iniEal
and
ongoing
QoS
policies
• ConfiguraEon
– Provides
high-‐level
business
knobs,
and
mulE-‐device/domain
automaEon
for
QoS
• Monitoring
&
ReporEng
– Generates
intelligent,
automaEc
alerts
and
summary
reports
• Consistency
– Enables
automaEc,
seamless
interoperability
among
all
QoS
features
and
parameters
across
a
network
topology
–
LAN,
MAN,
and
WAN
AutoQoS
VoIP:
Switch
Playorms
• You
can
meet
the
voice
QoS
requirements
without
extensive
knowledge
about:
– Trust
boundary
– CoS-‐to-‐DSCP
mappings
– WRR
&
PQ
scheduling
parameters
• Generated
parameters
and
configuraEons
are
user-‐tunable
AutoQoS
VoIP:
Switch
Playorms
(Cont.)
• Single
command
at
the
interface
level
configures
interface
and
global
QoS
– Support
for
Cisco
IP
Phone
&
Cisco
SooPhone
– Trust
boundary
is
disabled
when
IP
Phone
is
moved
– Buffer
allocaEon
and
egress
queuing
dependent
on
interface
type
(Gigabit
Ethernet/Fast
Ethernet)
• Supported
on
staEc,
dynamic-‐access,
voice
VLAN
access,
and
trunk
ports
• CDP
must
be
enabled
for
AutoQoS
to
funcEon
properly
Configuring
AutoQoS
VoIP:
Prerequisites
for
Using
AutoQoS
VoIP
• CEF
must
be
enabled
at
the
interface
or
ATM
PVC.
• This
feature
cannot
be
configured
if
a
QoS
policy
(service
policy)
is
aTached
to
the
interface.
• An
interface
is
classified
as
low-‐speed
if
its
bandwidth
is
less
than
or
equal
to
768
kbps.
It
is
classified
as
high-‐speed
if
its
bandwidth
is
greater
than
768
kbps.
– The
correct
bandwidth
should
be
configured
on
all
interfaces
or
subinterfaces
using
the
bandwidth
command.
– If
the
interface
or
subinterface
has
a
link
speed
of
768
kbps
or
lower,
an
ip
address
must
be
configured
using
the
ip
address
command.
Configuring
AutoQoS
VoIP:
Routers