 rate 81000 bps, drop rate 0 bps Match: ip precedence 5 19211963 packets, 3918472220 bytes 5 minute rate 81000 bps Queueing Strict Priority Output Queue: Conversation 264 Bandwidth 128 (kbps) Burst 3200 (Bytes) (pkts matched/bytes matched) 19211963/3918472220 (total drops/bytes drops) 0/0 Class-map: Voice-Control (match-all) 793462 packets, 161097064 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: ip precedence 3 Queueing Output Queue: Conversation 265 Bandwidth 5 (%) Max Threshold 64 (packets) (pkts matched/bytes matched) 793462/161097064 (depth/total drops/no-buffer drops) 0/0/0 Class-map: HTTP (match-any) 717928 packets, 42537234 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: access-group 101 717928 packets, 42537234 bytes 5 minute rate 0 bps Queueing Output Queue: Conversation 266 Bandwidth 10 (%) Max Threshold 64 (packets) (pkts matched/bytes matched) 717934/42537620 (depth/total drops/no-buffer drops) 0/0/0 Class-map: class-default (match-any) 2243454 packets, 2851898036 bytes 5 minute offered rate 52000 bps, drop rate 0 bps Match: any Queueing Flow Based Fair Queueing Maximum Number of Hashed Queues 256 (total queued/total drops/no-buffer drops) 0/0/0 Each queue is shown in detail with slightly different information reported. The strict priority queue is used in the class map Voice-RTP. Here is the output for that queue: Chapter 34: The Converged Network Class-map: Voice-RTP (match-any) 19211963 packets, 3918472220 bytes 5 minute offered rate 81000 bps, drop rate 0 bps Match: ip precedence 5 19211963 packets, 3918472220 bytes 5 minute rate 81000 bps Queueing Strict Priority Output Queue: Conversation 264 Bandwidth 128 (kbps) Burst 3200 (Bytes) (pkts matched/bytes matched) 19211963/3918472220 (total drops/bytes drops) 0/0 The interesting tidbits are in bold. The first bold line shows the 5 minute offered rate followed by the drop rate. The drop rate should always be zero, especially in the priority queue. If you're dropping packets, your queue is too small. The five-minute offered rate 