Way too many drops in 3hrs uptime , Looks like you running qos and your running priority queuing which means everything in priority queue will be serviced first in qos but you have bound the qos to the queue set 2 instead of default queue 1 in the module and then given a custom queue set in srr , im guessing you did not originally set this up as this looks like it was done for a reason if they applied queue set 2 to the interface and given specific custom weightings
These drops could be from the way that's setup , your telling interface only care about priority queue first so drops will occur due to this
: Priority queue is serviced until empty before the other queues are serviced in qos
Qos can be responsible for drops depending on the way its configured , sometimes interfaces experience a lot less drops without qos at layer 2
srr-queue bandwidth share 12 8 30 50
queue-set 2
priority-queue out
You need to check are these drops been seen in qos in the interface , is MLS qos enabled globally post the below off that interface if it is and we can check is qos seeing drops
sh mls qos interface gigabitEthernet x/x statistics
There are a couple of things you can try to fix this
1 Manipulate the srr queues so that any queue that's seeing major drops is given more available percentage. the ssr adds up top 100% and is divided between the queues in the interface 12 8 30 50 = 100 , and it must always equal 100 but you can alter them say if all the drops were in queueu 4 but none in queue 3 as an example you could change it too 12 8 20 60 = 100
2 Remove qos and just use the mls qos trust so there is no queue prioritisation and the voice is still trusted as phone will mark at the source
3 Remove just the priority statement to stop the queue starvation
Its all about getting the right fit for your traffic and environment when using layer 2 qos
These are options only don't change everything at once take a test interface make a few changes and when you get it right with 1 roll it out to the rest
As well if your using different modules in the switch each have different queuing capabilities like below example this can also guide in what the module hardware is capable of
#sh int g1/4/1 capabilities
GigabitEthernet1/4/1
Model: NO IDPROM
Type: unknown (4)
Speed: 1000
Duplex: full
Trunk encap. type: 802.1Q
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100)
Flowcontrol: rx-(off,on,desired),tx-(off,on,desired)
Membership: static
Fast Start: yes
QOS scheduling: rx-(1q8t), tx-(1p3q8t)
QOS queueing mode: rx-(cos), tx-(cos)
CoS rewrite: yes
ToS rewrite: yes
Inline power: no
Inline power policing: no
SPAN: source/destination
UDLD yes
Link Debounce: yes
Link Debounce Time: yes
Ports-in-ASIC (Sub-port ASIC) : UNAVAILABLEnum_bus = 0, num_ports = 0
Remote switch uplink: no
Port-Security: yes
Dot1x: yes
