10-29-2010 01:36 PM - edited 03-16-2019 01:38 AM
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
11-08-2010 11:30 AM
Bump!
I would like to know the answer to this as well.
03-11-2016 04:32 PM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide