On 03/02/11 17:20, Michael Crilly wrote:
After some playing around, I am getting this output from the 'mls qos
int gi0/2 stat' command:
I don't see you using the "service-policy" at interface level, so I'm
not sure if and where your policy-map is matching?
We have QoS on Catalyst 3550s setup; we see things like this:
#sh mls qos interface g0/1 statistics
GigabitEthernet0/1
Ingress
dscp: incoming no_change classified policed dropped (in bytes)
0 : 3987235380 2343274394 2463708897 0 0
8 : 1729277702 0 0 0 0
16: 1531195619 0 0 0 0
26: 300529872 0 0 0 0
32: 1367348968 0 0 0 0
46: 2424106981 1924373538 1490328499 0 0
48: 711185226 0 0 0 0
56: 4172438264 0 0 0 0
Others: 742230244 0 153928336 0 0
Egress
dscp: incoming no_change classified policed dropped (in bytes)
0 : 991756436 n/a n/a 0 0
8 : 0 n/a n/a 0 0
16: 0 n/a n/a 0 0
26: 0 n/a n/a 0 0
32: 0 n/a n/a 0 0
46: 1384502261 n/a n/a 0 0
48: 75988175 n/a n/a 0 0
56: 58312830 n/a n/a 0 0
Others: 79616 n/a n/a 0 0
WRED drop counts:
qid thresh1 thresh2 FreeQ
1 : 0 0 1024
2 : 0 0 1024
3 : 0 0 1024
4 : 0 0 1024
...and our config is something like:
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos
!
class-map match-all hi-priority
match access-group name hi-priority
class-map match-all ALL
match access-group name ALL
!
policy-map CORE-in
class hi-priority
set dscp ef
class ALL
set dscp default
!
interface GigabitEthernet0/1
description core
mls qos monitor dscp 0 8 16 26 32 46 48 56
service-policy input CORE-in
!
interface FastEthernet0/7
description edge - congested link!
mls qos trust dscp
mls qos monitor dscp 0 8 16 26 32 46 48 56
wrr-queue cos-map 1 0 1
wrr-queue cos-map 2 2 4
wrr-queue cos-map 3 3 6 7
wrr-queue cos-map 4 5
priority-queue out
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
