
This document requires an understanding of IP to ATM CoS. The following resources provide information on these features.
| Platform | 12.0S | 12.1T | 12.1E |
| 7200 Series | Not supported | 12.0(7)XE, 12.1(5)T | Not supported |
| 7500 Series | 12.0(14)S | Not supported | 12.1(12c)E (CSCdu89722) |
As of Cisco IOS Software Releases 12.1(5)T, 12.1(5)E, and 12.0(14)S, only VIP-based or distributed per-VC queueing is supported on the 7500 Series. RSP-based QoS is no longer supported. Configuring a service policy with distributed LLQ (dLLQ) in a Cisco IOS image without dLLQ support leads to VIP crashes (CSCdt78618).
Our traffic generator sent two types of traffic, one emulating voice and the other "disturbing" data to congest the VC's hardware or driver-level first-in-first-out (FIFO) queue. By virtue of LLQ, the voice traffic received the expected priority.
When configuring LLQ for voice traffic, ensure that you decrease the size
of the hardware FIFO queue, known as the transmit ring, with the tx-ring-limit
command. Otherwise, the voice traffic may experience excessive latency.
Normally, a TX-ring-limit value of three or four is fine. Using this sample
configuration, voice latency averaged 7ms, compared to 3ms in the absence of
competing traffic.
|
|
class-map match-all rtp match ip rtp 5000 10000 ! policy-map llq class rtp priority 1000 ! interface ATM3/0 no ip address ima-group 0 ! interface ATM3/ima0 no ip address no atm ilmi-keepalive ! interface ATM3/ima0.34 point-to-point ip address 5.0.34.3 255.255.255.0 pvc 0/34 tx-ring-limit 3 vbr-nrt 4000 4000 service-policy output llq ! interface ATM3/1 no ip address ima-group 0 ! interface ATM3/2 no ip address ima-group 0 |
Note: All commands entered in VC configuration mode take effect only when you exit for this mode. Exiting causes the VC to be removed and recreated with the new configuration parameters, which may include QoS policies, shaping rates, etc. If you wish to remove a QoS service policy, you must type exit or CTRL-Z to ensure that the no form of the command actually takes effect.
r3#show policy-map interface atm3/ima0.34
ATM3/ima0.34: VC 0/34 -
Service-policy output: llq (1089)
Class-map: rtp (match-all) (1091/2)
2242843 packets, 435111542 bytes
! -- Number of packets matching the criteria of the class.
30 second offered rate 775000 bps, drop rate 0 bps
Match: ip rtp 5000 10000 (1095)
Weighted Fair Queueing
Strict Priority
Output Queue: Conversation 136
Bandwidth 1000 (kbps) Burst 25000 (Bytes)
(pkts matched/bytes matched) 2016845/391267930
! -- Number of packets matching the class during periods
! -- of congestion, when the interface's transmit ring was full.
(total drops/bytes drops) 0/0
Class-map: class-default (match-any) (1099/0)
3987455 packets, 6028018316 bytes
30 second offered rate 8051000 bps, drop rate 0 bps
Match: any (1103)
All contents are Copyright © 1992--2003 Cisco Systems Inc. All rights reserved. Important Notices and Privacy Statement.
| Updated: Jun 05, 2005 | Document ID: 10484 |