Router(config)#class-map
AutoQoS-Bulk-Se0/1/0
Router(config-cmap)#match
protocol sqlnet
Router(config-cmap)#exit
Step 4 Classify all SNMP traffic coming from the IP subnet
193.87.95.0 as Management class.
Router
(config)#access-list 101 permit udp 193.87.95.0 0.0.0.255
any eq snmp
Router(config)#class-map
AutoQoS-Management-Se0/1/0
Router(config-cmap)#match
access-group 101
Router(config-cmap)#end
- Review the new classification policy (only the
classification portion is shown).
Router#show auto
qos
<output omitted>
!
Suggested AutoQoS
Policy for the current uptime:
class-map match-any
AutoQoS-Voice-Se0/1/0
match protocol rtp audio
!
class-map match-any AutoQoS-Signaling-Se0/1/0
match
protocol h323
match protocol sip
match protocol
mgcp
!
class-map match-any
AutoQoS-Transactional-Se0/1/0
match protocol telnet
match protocol citrix
!
class-map match-any
AutoQoS-Bulk-Se0/1/0
match protocol exchange
match
protocol ftp
match protocol sqlnet
!
class-map
match-any AutoQoS-Scavenger-Se0/1/0
match protocol
kazaa2
!
class-map match-any
AutoQoS-Management-Se0/1/0
match protocol ldap
match
access-group 101
!
access-list 101 permit udp
193.87.95.0 0.0.0.255 any eq snmp
Content
5.2 Mitigating Common Cisco AutoQoS
Issues 5.2.7 Modifying AutoQoS Generated
Policy with MQC When you are generating QoS policy
templates, Cisco AutoQoS enables several Cisco IOS QoS
mechanisms. The Cisco IOS QoS mechanisms that Cisco AutoQoS
enables include: - Traffic scheduling and congestion
management using LLQ, CBWFQ, or WRR
- Traffic marking
using class-based marking
- Traffic shaping using
class-based shaping or FRTS
- Link efficiency using
cRTP and LFI (MLP or FRF.12)
- Congestion avoidance
using WRED
Besides these policies selected by Cisco
AutoQoS, the resulting policy configuration generated can be
tuned with any available Cisco IOS MQC policy option. Cisco IOS
software supports a broad range of options to implement
DiffServ per-hop behaviors (PHBs) and adapt to any enterprise
policy. The procedure for modifying an existing, active policy
generated by Cisco AutoQoS is similar to the procedure for
classification. The following is an example of policy
modification: - Review the existing QoS policy,
identify the new requirements, and outline the configuration
modifications necessary (the example only shows the policy
section).
Router#show auto discovery qos
<output omitted>
!
Suggested AutoQoS Policy for
the current uptime:
policy-map AutoQoS-Policy-Se0/1/0
class AutoQoS-Voice-Se0/1/0
priority percent 10
compress header ip
set dscp ef
class
AutoQoS-Signaling-Se0/1/0
bandwidth remaining percent
4
set dscp cs3
class AutoQoS-Transactional-Se0/1/0
bandwidth remaining percent 40
random-detect
dscp-based
set dscp af21
class
AutoQoS-Bulk-Se0/1/0
bandwidth remaining percent 19
random-detect dscp-based
set dscp af11
class
AutoQoS-Scavenger-Se0/1/0
bandwidth remaining percent
1
set dscp cs1
class AutoQoS-Management-Se0/1/0
bandwidth remaining percent 6
set dscp cs2
class
class-default
fair-queue Necessary policy changes include:
Step 1 Mark the voice signaling traffic with DSCP AF31,
instead of the current CS3. Step 2 Rate-limit the
scavenger traffic to a maximum of 64 kbps. Step 3
Guarantee minimally 10 percent of the available interface
bandwidth to the best-effort traffic. Step 4 Mark the
management traffic with DSCP AF21, instead of the current CS2.
- Modify the policy generated by Cisco
AutoQoS according to the new requirements.
Step 1
Mark the voice signaling traffic with DSCP AF31, instead of the
current CS3. Router#configure terminal
Router(config)#policy-map AutoQoS-Policy-Se0/1/0
Router(config-pmap)#class AutoQoS-Signaling-Se0/1/0
Router(config-pmap-c)#no set dscp cs3
Router(config-pmap-c)#set dscp af31
Router(config-pmap-c)#exit Step 2 Rate-limit the
scavenger traffic to a maximum of 64 kbps.
Router(config-pmap)#class AutoQoS-Scavenger-Se0/1/0
Router(config-pmap-c)#police 64000 conform-action transmit
exceed-action drop
Router(config-pmap-c)#exit
Step 3 Guarantee minimally 10 percent of the available
interface bandwidth to the best-effort traffic.
Router(config-pmap)#class class-default
Router(config-pmap-c)#bandwidth remaining percent
10
Router(config-pmap-c)#exit Step 4
Mark the management traffic with DSCP AF21, instead of the
current CS2. Router(config-pmap)#class
AutoQoS-Management-Se0/1/0
Router(config-pmap-c)#no
set dscp cs2
Router(config-pmap-c)#set dscp
af21
Router(config-pmap-c)#end
-
Review the new service policy (the example only shows the
policy portion).
Router#show auto qos
<output omitted>
!
Suggested AutoQoS Policy for
the current uptime:
policy-map AutoQoS-Policy-Se0/1/0
class AutoQoS-Voice-Se0/1/0
priority percent 10
compress header ip
set dscp ef
class
AutoQoS-Signaling-Se0/1/0
bandwidth remaining percent
4
set dscp af31
class AutoQoS-Transactional-Se0/1/0
bandwidth remaining percent 40
random-detect
dscp-based
set dscp af21
class
AutoQoS-Bulk-Se0/1/0
bandwidth remaining percent 19
random-detect dscp-based
set dscp af11
class
AutoQoS-Scavenger-Se0/1/0
bandwidth remaining percent
1
set dscp cs1
police 64000 conform-action transmit
exceed-action drop
class AutoQoS-Management-Se0/1/0
bandwidth remaining percent 6
set dscp af21
class
class-default
bandwidth remaining percent 10
Content 5.3 Cisco AutoQoS Lab Exercise
5.3.1 Lab 5.1 AutoQoS Lab Activity Lab
Exercise: Lab 5.1 AutoQoS In this lab, you will configure
AutoQoS, a Cisco QoS solution for simple, scalable QoS
deployments. For this lab you are required to use a Pagent IOS
image on TrafGen to generate lab traffic.
Content
Summary The Cisco AutoQoS option simplifies configuration
of QoS. Most Cisco routers and Cisco Catalyst switches support
Cisco AutoQoS. QoS configuration requires a deep understanding
of various QoS features including queuing, dropping, traffic
conditioning, queue-depth, drop thresholds, burst parameters,
LFI, and cRTP, as well as the complexities of configuring many
parameters associated with these features. Cisco AutoQoS helps
overcome these difficulties by automatically configuring the
device for Cisco QoS features and variables with the correct
parameters. The mechanism takes into account interface
bandwidth, traffic pattern discovery and Cisco best practices
when configuring QoS. Typically, QoS network design and
implementation over multiple LAN and WAN sites is fairly
complex and labor intensive. Customers want to reduce
deployment time, provisioning errors, and operating expenses to
optimize their network for the applications, while retaining
the flexibility to subsequently fine-tune QoS. To expedite QoS
deployment, the user interface must be simplified. Cisco