 from the least important queue first. The least important queue is the class- default queue, where all nonprioritized packets are queued. Here, I have routed excessive traffic across our sample network's T1 link. While most of the queues are busy, only the class-default queue is showing dropped packets: R1# sho policy-map interface s0/1 Serial0/1 Service-policy output: WAN Class-map: Voice-RTP (match-any) 11091627 packets, 2262021588 bytes 5 minute offered rate 324000 bps, drop rate 0 bps Match: ip precedence 5 11091627 packets, 2262021588 bytes 5 minute rate 324000 bps Chapter 32: The Converged Network Queueing Strict Priority Output Queue: Conversation 264 Bandwidth 500 (kbps) Burst 12500 (Bytes) (pkts matched/bytes matched) 11091627/2262021588 (total drops/bytes drops) 0/0 Class-map: Voice-Control (match-all) 7312459 packets, 1477128588 bytes 5 minute offered rate 255000 bps, drop rate 0 bps Match: ip precedence 3 Queueing Output Queue: Conversation 265 Bandwidth 5 (%) Max Threshold 64 (packets) (pkts matched/bytes matched) 7312784/1477194238 (depth/total drops/no-buffer drops) 0/0/0 Class-map: HTTP (match-any) 79255 packets, 4690398 bytes 5 minute offered rate 1000 bps, drop rate 0 bps Match: access-group 101 79255 packets, 4690398 bytes 5 minute rate 1000 bps Queueing Output Queue: Conversation 266 Bandwidth 10 (%) Max Threshold 64 (packets) (pkts matched/bytes matched) 78903/4669112 (depth/total drops/no-buffer drops) 0/0/0 Class-map: class-default (match-any) 23750755 packets, 2030244008 bytes 5 minute offered rate 887000 bps, drop rate 4000 bps Match: any Queueing Flow Based Fair Queueing Maximum Number of Hashed Queues 256 (total queued/total drops/no-buffer drops) 12/16501/0 If users are complaining at this point, there are a few things to consider: The link may be saturated, in which case it should be replaced with a larger link. Some traffic in the class-default queue may need to be prioritized above this queue. One or more of the queues may not be configured appropriately. Look at the HTTP queue. Wh