Implementing QoS with AutoQoS

AutoQoS VoIP supported both in the LAN and WAN environments

AutoQoS Enterprise supported on WAN interfaces

Routers can deploy Enterprise QoS policy treatment for voice, video, and data traffic

Switches can deploy QoS policy treatments for voice by a single command

[trust] option is used to trust DSCP marking

Depending on the platform, using Cisco AutoQoS VoIP or AutoQoS Enterprise, you can implement the QoS features that support VoIP traffic and data traffic without an in-depth knowledge of these underlying technologies:

■ Service policies

■ Link efficiency mechanisms, such as link fragmentation and interleaving (LFI)

The deployment of AutoQoS simplifies QoS implementation, speeds up the provisioning of QoS technology over a Cisco network, reduces human error, and lowers training costs.

Systems, Inc. All rights reserved

The AutoQoS Enterprise feature, introduced in Cisco IOS Release 12.3(7)T, provides another option for configuring AutoQoS on routers. This new feature allows you to configure AutoQoS to discover data traffic across a router WAN interface before applying AutoQoS VoIP. While previously you could apply AutoQoS VoIP on a WAN interface, this new automated feature allows you to discover data traffic and build the QoS polices based on data gathered during the discovery phase. Configuring switches to support AutoQoS VoIP has not changed. This new feature applies only to router WAN interfaces, and the phases are described as follows:

■ Phase 1 is the Auto-Discovery (data collection) phase and uses NBAR to detect network applications as they arrive at an interface, collect data from the offered traffic, and perform statistical analysis. The data collected is a representative sampling of the volume and type of voice, video, and data on the customer network. The amount of time devoted to data collection varies from network to network.

■ Phase 2 generates templates from the data collected during the Auto-Discovery phase and installs the templates on the interface. These templates are used as the basis for creating the class maps and policy maps for your network. After the class maps and policy maps are created, they are installed on the interface. During this phase, the AutoQoS for the Enterprise also assigns the appropriate bandwidth amounts and sets the appropriate scheduling parameters for the network traffic.

■ You can use CiscoWorks QPM in conjunction with the AutoQoS for the Enterprise feature to provide a centralized, web-based tool to cost-effectively manage and monitor network-wide QoS policies. The AutoQoS VoIP feature, together with CiscoWorks QPM, eases QoS implementation, provisioning, and management.

Note Cisco AutoQoS was introduced in Cisco IOS Release 12.2(15)T. AutoQoS discovery was introduced in Cisco IOS Release 12.3(7)T.

Was this article helpful?

0 0

Post a comment