06-08-2011 05:01 AM - edited 03-04-2019 12:38 PM
Hi have a question about QOS on ATM PVC
pre 12.4.20T we did it like following, as I understood we do not need a shaper in the service-policy, shaping/policing should be configured with atm vc-class, correct.
---------------------------------------------------------
vc-class atm 32000Kbps-PVC
vbr-nrt 32000 32000 1 32000 32000 1
tx-ring-limit 3
oam-pvc manage
encapsulation aal5snap
policy-map xQOS-QUEUE-POLICY
class xQOS-CLASS-EF_Realtime_Voice
priority percent 20
class xQOS-CLASS-CS5
class xQOS-CLASS-AF41
bandwidth remaining percent 10
class xQOS-CLASS-CS4_Realtime_Video
bandwidth remaining percent 40
class xQOS-CLASS-AF31_Video_Streaming
bandwidth remaining percent 8
class xQOS-CLASS-CS3_Realtime_Signalling
bandwidth remaining percent 3
class xQOS-CLASS-AF21_Transactional_Data
bandwidth remaining percent 10
class xQOS-CLASS-CS2_Management_OAM
bandwidth remaining percent 3
class xQOS-CLASS-AF11_Bulk_Data
bandwidth remaining percent 5
class xQOS-CLASS-CS1_Scavanger_Data
bandwidth remaining percent 1
class xQOS-CLASS-BE_Best_Effort
bandwidth remaining percent 19
!
interface ATM1/0
description ATM-OC3
no ip address
ip flow ingress
logging event subif-link-status
load-interval 30
no atm ilmi-keepalive
no atm enable-ilmi-trap
!
max-reserved-bandwidth 100
hold-queue 200 in
!
interface ATM1/0.12 point-to-point
description 32Mbit/s-ATM-PVC
mtu 1578
bandwidth 32000
ip address 22.161.198.102 255.255.255.252
ip accounting output-packets
ip flow ingress
ip pim sparse-mode
delay 200
no atm enable-ilmi-trap
pvc PVC 12/161
class-vc 32000Kbps-PVC
service-policy output xQOS-QUEUE-POLICY
---------------------------------------------------------
upgrading to 15.0 we had a lot of drops though there was less traffic,
Service-policy output: xQOS-QUEUE-POLICY
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: xQOS-CLASS-EF_Realtime_Voice (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
30 second rate 0 bps
Priority: 20% (6400 kbps), burst bytes 160000, b/w exceed drops: 0
Class-map: xQOS-CLASS-CS5 (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
30 second rate 0 bps
Class-map: xQOS-CLASS-AF41 (match-any)
30 packets, 1863 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp af41 (34) af42 (36) af43 (38)
30 packets, 1863 bytes
30 second rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 30/1863
bandwidth remaining 10% (2560 kbps)
Class-map: xQOS-CLASS-CS4_Realtime_Video (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
30 second rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining 40% (10240 kbps)
Class-map: xQOS-CLASS-AF31_Video_Streaming (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp af31 (26) af32 (28) af33 (30)
0 packets, 0 bytes
30 second rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining 8% (2048 kbps)
Class-map: xQOS-CLASS-CS3_Realtime_Signalling (match-any)
42239 packets, 3828404 bytes
30 second offered rate 458000 bps, drop rate 288000 bps
Match: ip dscp cs3 (24)
42239 packets, 3828404 bytes
30 second rate 458000 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 64/23698/0
(pkts output/bytes output) 18541/1473065
bandwidth remaining 3% (768 kbps)
Class-map: xQOS-CLASS-AF21_Transactional_Data (match-any)
2618 packets, 479056 bytes
30 second offered rate 51000 bps, drop rate 0 bps
Match: ip dscp af21 (18) af22 (20) af23 (22)
2618 packets, 479056 bytes
30 second rate 51000 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 15/0/0
(pkts output/bytes output) 2618/479056
bandwidth remaining 10% (2560 kbps)
Class-map: xQOS-CLASS-CS2_Management_OAM (match-any)
12008 packets, 12324882 bytes
30 second offered rate 1188000 bps, drop rate 662000 bps
Match: ip dscp cs2 (16)
12008 packets, 12324882 bytes
30 second rate 1188000 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 22/5047/0
(pkts output/bytes output) 6961/6358429
bandwidth remaining 3% (768 kbps)
Class-map: xQOS-CLASS-AF11_Bulk_Data (match-any)
23469 packets, 4343590 bytes
30 second offered rate 342000 bps, drop rate 69000 bps
Match: ip dscp af11 (10) af12 (12) af13 (14)
23469 packets, 4343590 bytes
30 second rate 342000 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 62/5585/0
(pkts output/bytes output) 17884/3687620
bandwidth remaining 5% (1280 kbps)
Class-map: xQOS-CLASS-CS1_Scavanger_Data (match-any)
33 packets, 2124 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp cs1 (8)
33 packets, 2124 bytes
30 second rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 33/2124
bandwidth remaining 1% (256 kbps)
Class-map: xQOS-CLASS-BE_Best_Effort (match-any)
45222 packets, 6439836 bytes
30 second offered rate 614000 bps, drop rate 251000 bps
Match: ip dscp default (0)
45222 packets, 6439836 bytes
30 second rate 614000 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 64/17640/0
(pkts output/bytes output) 27582/3986130
bandwidth remaining 19% (4864 kbps)
Class-map: class-default (match-any)
156 packets, 45864 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 180/47732
seems the queue-depht MUST be increased.
Is that all what has changed or do I need a shaper also under the service-policy like following , I am really not sure?
vc-class atm 32000Kbps-PVC
vbr-nrt 32000 32000 1 32000 32000 1
tx-ring-limit 3
oam-pvc manage
encapsulation aal5snap
policy-map xQOS-QUEUE-POLICY
class xQOS-CLASS-EF_Realtime_Voice
priority percent 20
class xQOS-CLASS-CS5
class xQOS-CLASS-AF41
bandwidth remaining percent 10
class xQOS-CLASS-CS4_Realtime_Video
bandwidth remaining percent 40
class xQOS-CLASS-AF31_Video_Streaming
bandwidth remaining percent 8
class xQOS-CLASS-CS3_Realtime_Signalling
bandwidth remaining percent 3
class xQOS-CLASS-AF21_Transactional_Data
bandwidth remaining percent 10
class xQOS-CLASS-CS2_Management_OAM
bandwidth remaining percent 3
queue-limit 256 packets
class xQOS-CLASS-AF11_Bulk_Data
bandwidth remaining percent 5
queue-limit 256 packets
class xQOS-CLASS-CS1_Scavanger_Data
bandwidth remaining percent 1
class xQOS-CLASS-BE_Best_Effort
bandwidth remaining percent 19
queue-limit 256 packets
!
policy-map xQOS-SHAPED-QUEUE-POLICY
class class-default
shape average 32000000 32000 0
service-policy xQOS-QUEUE-POLICY
!
interface ATM1/0
description ATM-OC3
no ip address
ip flow ingress
logging event subif-link-status
load-interval 30
no atm ilmi-keepalive
no atm enable-ilmi-trap
!
max-reserved-bandwidth 100
hold-queue 200 in
!
interface ATM1/0.12 point-to-point
description 32Mbit/s-ATM-PVC
mtu 1578
bandwidth 32000
ip address 22.161.198.102 255.255.255.252
ip accounting output-packets
ip flow ingress
ip pim sparse-mode
delay 200
no atm enable-ilmi-trap
pvc PVC 12/161
class-vc 32000Kbps-PVC
service-policy output xQOS-SHAPED-QUEUE-POLICY
Thx in advance
Hubert
06-08-2011 05:06 AM
You should not need a shaper.
But if you find that the ATM native shaping is not working, you may need that as a workaround while waiting for cisco to recognise and fix the bug (may take a long time however you are helped by having it working with an older IOS version).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide