11-14-2019 01:09 PM - edited 11-14-2019 01:11 PM
Hello,
My default class-default is not using the traffic shaping and queue length that i have configured. I configured a parent policy map (Out) and a child policy map called (MPLS_Out). The parent policy map provides traffic shaping for my MPLS cicuit. I have purchased 20MB Bandwidth delivered on a 100MB circuit. The child policy prioritizes VoIP (EF traffic) and gives approximately 1M of bandwidth.
My issue is the default class is not using the parent traffic shaping policy. I need a configuration that allows both 1)Traffic shaping of the circuit to about 15M bandwidth with 2M queue depth, and allocated to 1M of bandwidth to EF traffic.
class-map match-any Critical
match access-group 107
class-map match-any REAL_TIME
match access-group 105
!
policy-map MPLS_OUT
class REAL_TIME
priority 1048
class Critical
priority 1048
class class-default
fair-queue
policy-map OUT
class class-default
shape average 17000000
queue-limit 2500 packets
service-policy MPLS_OUT
interface GigabitEthernet0/1
service-policy output OUT
!
_________________________________________
#show policy-map int gi0/1
GigabitEthernet0/1
Service-policy output: OUT
Class-map: class-default (match-any)
204834 packets, 95613028 bytes
5 minute offered rate 1509000 bps, drop rate 8000 bps
Match: any
Queueing
queue limit 2500 packets
(queue depth/total drops/no-buffer drops) 0/640/0
(pkts output/bytes output) 205234/96132004
shape (average) cir 17000000, bc 68000, be 68000
target shape rate 17000000
Service-policy : MPLS_OUT
queue stats for all priority classes:
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 26779/5724002
Class-map: REAL_TIME (match-any)
26742 packets, 5720776 bytes
5 minute offered rate 82000 bps, drop rate 0000 bps
Match: access-group 105
26742 packets, 5720776 bytes
5 minute rate 82000 bps
Priority: 1048 kbps, burst bytes 26200, b/w exceed drops: 0
Class-map: Critical (match-any)
37 packets, 3226 bytes
5 minute offered rate 0000 bps, drop rate 0000 bps
Match: access-group 107
37 packets, 3226 bytes
5 minute rate 0 bps
Priority: 1048 kbps, burst bytes 26200, b/w exceed drops: 0
Class-map: class-default (match-any)
178055 packets, 89889026 bytes
5 minute offered rate 1425000 bps, drop rate 7000 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops/flowdrops) 0/640/0/640
(pkts output/bytes output) 178455/90408002
Fair-queue: per-flow queue limit 16 packets
11-15-2019 10:59 AM
11-15-2019 11:45 AM
When I do a shop policy-map int gi0/1. The default queue is not correct. My queue length is incorrect.
Class-map: class-default (match-any)
178055 packets, 89889026 bytes
5 minute offered rate 1425000 bps, drop rate 7000 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops/flowdrops) 0/640/0/640
(pkts output/bytes output) 178455/90408002
Fair-queue: per-flow queue limit 16 packets
11-15-2019 12:18 PM
Again, how do you know?
You configure queue length on:
policy-map OUT
class class-default
shape average 17000000
queue-limit 2500 packets
service-policy MPLS_OUT
but NOT on:
policy-map MPLS_OUT
class REAL_TIME
priority 1048
class Critical
priority 1048
class class-default
fair-queue
So the queue-length of 64, for the latter, is a default. If you want to override it, try to configure queue-length on the latter's policy-map's class-default.
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