According to the guidelines, you can enable auto-QoS on static, dynamic-access, voice VLAN access, and trunk ports. Add either 'switchport mode access' or 'switchport voice vlan' to the port. What is the port used for anyway ?

Re: Why service-policy is not generated after using auto qos voip?

I could be wrong here but on the 3560s from memory its IOS so it doesn't actually add the service policy to the interface on a layer 2 interfaces it just applys the qos , it does on IOS-XE with auto qos on a 3650 it creates full maps then applies it to each individual interface that has auto enabled

You can check your qos is working with show mls qos interface gx/x statistics

also in your post your best off using DSCP if available rather than COS and set the uplink to trust DSCP too , most new phones etc send in DSCP now

Re: Why service-policy is not generated after using auto qos voip?

I recall (?) on that series, once auto QoS commands have been triggered, they are not regenerated unless you completely remove all of them from the device. This, I believe, was allow you to "customize" the auto QoS generated commands after they are installed the first time.

Re: Why service-policy is not generated after using auto qos voip?

How did you remove all the config? Reason I ask, I don't recall exactly what I've done in the past to reset the auto QoS regeneration trigger, but if you're in a position to try it, erase the startup config (you can save a copy under a different file name) and reboot. See if that then allows for a reset of auto QoS. (You can then [later] either copy it to startup or merge it with running and re-save.)

Re: Why service-policy is not generated after using auto qos voip?

my 3560s dont contain policy's either running qos interface or global as i was saying in earlier post i dont think they do in general I just tested it on a fresh non qos 3560 to be sure same results no policies ingterface or global but qos is working fine

NOTE: This lab utilizes the dCloud platform for delivery. Be sure to schedule your session ahead of time!
Digitization is placing unprecedented demands on IT to increase the speed of services and applications delivered to customers, partners, and employe...
view more

Step 1: Building a Cloud onRamp Colocation ClusterStep 2: Building a Service Chain and Adjusting PolicyStep 3: Monitoring
Preamble
This was created for and used with FreeZTP, but can likely be used with any Jinja2 templating system.
When this snippet (l...
view more

Note: This lab utilizes the dCloud SD-WAN platform. You must schedule this ahead of time before proceeding below!
Cloud onRamp for IaaS extends the fabric of the Cisco SDWAN overlay network into public cloud instances, allowing branches with cEdge/vEdge ...
view more

Note: This lab utilizes the dCloud SD-WAN platform. You must schedule this ahead of time before proceeding below!
Cloud onRamp is one of the most popular features to enable within Cisco SDWAN. As many organizations start to make their shift to the cloud,...
view more