Methods for Implementing QoS Policy

This topic describes four different methods for implementing and managing a QoS policy.

Just a few years ago, the only way to implement QoS in a network was by using the command-line interface (CLI) to individually configure QoS policies at each interface. This was a time-consuming, tiresome, and error-prone task that involved cutting and pasting configurations from one interface to another.

Cisco introduced the MQC in order to simplify QoS configuration by making configurations modular. Using MQC, you can configure QoS in a building-block approach using a single module repeatedly to apply policy to multiple interfaces.

Cisco AutoQoS represents innovative technology that simplifies the challenges of network administration by reducing QoS complexity, deployment time, and cost to enterprise networks. Cisco AutoQoS incorporates value-added intelligence in Cisco IOS software and Cisco Catalyst software to provision and assist in the management of large-scale QoS deployments. AutoQoS is an intelligent macro that enables you to enter one or two simple AutoQoS commands to enable all the appropriate features for the recommended QoS setting for an application on a specific interface.

There are these two versions of AutoQoS:

■ AutoQoS VoIP: In its initial release, AutoQoS VoIP provided best-practice QoS configuration for VoIP on both Cisco switches and routers. This was accomplished by entering one global or interface command. Depending on the platform, the AutoQoS macro would then generate commands into the recommended VoIP QoS configurations, along with class maps and policy maps, and apply those to a router interface or switch port. AutoQoS is available on both LAN and WAN Cisco Catalyst switches and Cisco IOS routers. In its initial version, AutoQoS applied to VoIP deployments; until the release of a new feature in AutoQoS which is only applicable to the router platform and includes a traffic discovery mechanism which detects not only VoIP traffic but video and data traffic as well.

■ AutoQoS Enterprise: AutoQoS Enterprise relies on network-based application recognition (NBAR) to gather statistics and detect ten traffic types, resulting in the provisioning of class maps and policy maps for these traffic types. This feature deploys best-practice QoS policies for voice, video, and data traffic, and is introduced in Cisco IOS Release 12.3(7)T. These ten traffic types are detected as traffic crosses the WAN interfaces.

AutoQoS Enterprise combined with the AutoQoS VoIP command allows a novice network administrator to administer complex detailed QoS policies throughout the enterprise network. AutoQoS Enterprise is only for Cisco IOS router platforms. The VoIP feature for Cisco Catalyst switches does not change.

There are some major differences between AutoQoS VoIP and AutoQoS Enterprise. AutoQoS VoIP does not detect traffic types nor does it use NBAR. AutoQoS VoIP only creates QoS policy to provide priority of voice traffic. AutoQoS Enterprise, on the other hand, uses a discovery mechanism or traffic data collection process which uses NBAR. The AutoQoS VoIP macros use the NBAR statistics to create QoS polices. AutoQoS Enterprise is only supported on routers at this time.

You can more easily provision and manage successful QoS deployments by using Cisco AutoQoS together with CiscoWorks QPM. Cisco AutoQoS provides QoS provisioning for individual routers and switches, simplifying deployment and reducing human error. CiscoWorks QPM provides centralized QoS design, administration, and traffic monitoring that scales to large QoS deployments.

Was this article helpful?

0 0

Post a comment