Upon completing this lesson, you will be able to identify capabilities provided by AutoQoS Enterprise and configure QoS on a network using AutoQoS Enterprise. This ability includes being able to meet these objectives:

■ Explain how AutoQoS Enterprise is used to implement QoS policy

■ Describe the router platforms on which AutoQoS Enterprise is supported

■ Describe the prerequisites for using AutoQoS Enterprise

■ Describe how AutoQoS Enterprise is configured on a router using CLI

■ Describe how to use Cisco IOS commands to examine and monitor a network configuration after AutoQoS Enterprise has been deployed

This topic describes how AutoQoS Enterprise is used to implement QoS policy.

This topic describes how AutoQoS Enterprise is used to implement QoS policy.

The AutoQoS Enterprise feature automates the deployment of QoS policies in a general business environment. The policies deployed by AutoQoS Enterprise are not solely focused on VoIP convergence, but also on convergence of voice, video, and data applications. AutoQoS Enterprise is generally deployed in midsize companies and branch offices of larger companies. It is used to provide best-practice QoS policy generation for voice as well as to provide for classification of up to ten traffic classes. Currently, AutoQoS is supported only on routers.

Existing QoS policies may be present during the first configuration phase of AutoQoS Enterprise; that is, during the auto-discovery (data collection) phase. However, any existing QoS policies must be removed before the AutoQoS-generated policies are applied during the second configuration phase of this feature.

Setting IP Precedence or QoS Group in the IP Routing Table


route-map name permit seq match as-path path-list-number match ip address access-list-number match community community-list set ip precedence precedence set ip qos-group group

• Defines a route map to set IP precedence or QoS-group

• Specifies IP precedence and QoS group values in the routing table/FIB table entry


table-map route-map-name

• Specifies the route map used to set additional routing table attributes

—S- — Q™_J

The figure shows the ten traffic classes that can be classified by AutoQoS Enterprise. The autodiscovery process detects applications and protocol types, and offers a recommended QoS policy, which will be generated and installed by the AutoQoS macros, based on the data gathered by the auto-discovery process. The auto-discovery phase gives the discovery period enough time to gather traffic statistics before applying AutoQoS. The time for gathering traffic statistics before applying AutoQoS depends upon the actual highs and lows of traffic patterns of a network.

• The customer in AS 73 is a Premium customer.

Create an end-to-end QoS solution in a service provider network:

• The customer in AS 73 is a Premium customer.

• All packets to AS 73 shall be sent with IP precedence flash.

• This example illustrates destination-based IP precedence marking using QPPB.

The figure shows the differences between AutoQoS Enterprise and AutoQoS VoIP. The AutoQoS policies came off the same router; AutoQoS VoIP was first configured and then removed, followed by the configuration of AutoQoS Enterprise. Notice how detailed the AutoQoS Enterprise policy is compared to the AutoQoS VoIP policy.

The AutoQoS Enterprise policy is based on the traffic statistics gathered by the AutoQoS discovery process. Conversely, the AutoQoS VoIP policy was not generated by traffic statistics, but from a generic QoS template.

Was this article helpful?

0 0

Post a comment