cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
603
Views
0
Helpful
2
Replies

Why is Autoqos Classify Marking Voice Traffic to AF41?

rpeasah
Beginner
Beginner

Why is the c3750 "autoqos classify" command introduced in image 12.2(55) SE marking voice traffic to AF41? Shouldn't this traffic be marked EF?

This is the policy map when the auto qos classify command is configured (lifted from the command reference):

policy-map AUTOQOS-SRND4-CLASSIFY-POLICY
class AUTOQOS_MULTIENHANCED_CONF_CLASS
  set dscp af41

class AUTOQOS_BULK_DATA_CLASS
  set dscp af11

class AUTOQOS_TRANSACTION_CLASS
  set dscp af21

class AUTOQOS_SCAVANGER_CLASS
  set dscp cs1

class AUTOQOS_SIGNALING_CLASS
  set dscp cs3

class AUTOQOS_DEFAULT_CLASS
  set dscp default

2 Replies 2

mprescher
Beginner
Beginner

Bump!

I would like to know the answer to this as well.

The "autoqos classify" does not create voip class. The af41 is assigned for the "multienhanced" class, not voip. To auto generate voip class, the command is "auto qos voip ..." , which creates the class autoqos_voip_data_class that is for the voice traffic.

Multienhanced class is for the video traffic of a call. 

Why the separate command for voice? I think the commands were programmed when the 3750 or 3560 and those fixed-ports, high density switches didn't have LLQ configuration in the MQC. Instead, a separate queue was dedicated to voip, making the formula like 1p3q2t .  3750's MQC still does not have LLQ, but the queues are merged making the formula like 4q3t. However, the commands stay.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers