Cisco Blogs

Get Your Network Fit for Video – the easy way! AutoQos

February 16, 2012 - 2 Comments

The month of January always seems to be a very busy time at gyms; everyone starts the New Year off with good intentions. Now that February is here I can definitely see the trail off of in attendance at the local gym. Have you resolved to deploy video this year, or maybe your users have resolved for you J ? You’ll need to ensure your network is fit for the job. It won’t be difficult at all. There are features to make it easy to stay on track.

The first  of those features is AutoQos.

The concept of Auto Qos is that the hard work of defining a QOS strategy and implementing it on the network is already done for you. Two main things compromise that strategy, what are the DSCP settings that should be used and how to interpret those setting into a configuration that implements classification, policing and queuing mechanisms within the network.

The actual DSCP values are not as important as the fact that you need to define a network standard in your organization so that applications, endpoints and the network all agree what those values mean, and what service levels will be defined by those values.  The “Informational RFC” 4594, provides a suggested classification scheme that incorporates SLA for video applications.  Cisco collaboration and communication devices are designed with default configurations that match the recommendations of that RFC. Two obstacles are already overcome, defining that DSCP hierarchy, and configuration of the endpoints to conform.

AutoQos helps with the third obstacle, setting up the switching infrastructure to make use of those DSCP values and implementing SLA on the devices. When AutoQos is enabled with a single global command,  it performs bulk configuration of the queuing mechanisms. It sets up input and output queues based on RFC 4594 recommendations.

See the Qos Configuration Guide , as an example on the 3750 series switches on how to utilize AutoQos.

Once autoqos is enabled  globally then individual ports may be configured to use specific prebuilt groups of commands for specific applications. Profiles exists for  voice hard phones, voice softphones, telepresence, and video surveillance. These profiles define DSCP remarking, policing and cause priority queuing to be configured as needed.

Prebuilt profiles also exist for queuing based on trust of COS or DSCP values that endpoints use.

With very few commands you can make use of the most sophisticated queuing in the industry and leverage the prebuilt multimedia  SLA strategy that has already been defined by the RFC’s and forged into the products. Now get back to working on those resolutions.

Learn more:

–          Medianet

–          Questions about medianet? Visit the: medianet support forum

–          Medianet Knowledge Base

–          Medianet Media Monitoring

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.


  1. Hello Michael,

    I’d like to suggest a 4th step to your AutoQos recommendation.

    1) Define the DSCP Hierarchy
    2) Configure the end points to conform
    3) Use AutoQos to setup the switch infrastructure to make use of DSCP values
    4) Monitor with Flexible NetFlow Performance Routing and Medianet Performance Monitoring

    IMO: The fourth step allows admins to confirm that the infrastructure is labeling as expected.

    Nice post.

    Michael Patterson

  2. haha! correct Januarary is very busy month. All are busy in implementing their ideas