15 messages in net.nether.puck.cisco-nsp[c-nsp] 3550 QoS not working as expected
FromSent OnAttachments
Tim DevriesJan 6, 2005 12:14 pm 
Nick ShahJan 6, 2005 5:39 pm 
Tim DevriesJan 6, 2005 6:21 pm 
Nick ShahJan 6, 2005 6:58 pm 
Tim DevriesJan 6, 2005 7:27 pm 
Nick ShahJan 6, 2005 7:51 pm 
Tim DevriesJan 6, 2005 8:24 pm 
Sam SticklandJan 6, 2005 8:49 pm 
Tim DevriesJan 6, 2005 9:28 pm 
McCallum, RobertJan 7, 2005 3:49 am 
Dmitry ValdovJan 7, 2005 4:03 am 
McCallum, RobertJan 7, 2005 4:05 am 
WILDE, DavidJan 7, 2005 4:25 am 
Nick ShahJan 9, 2005 4:10 am 
Tim DevriesJan 10, 2005 11:02 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] 3550 QoS not working as expectedActions...
From:Sam Stickland (sam@spacething.org)
Date:Jan 6, 2005 8:49:45 pm
List:net.nether.puck.cisco-nsp

On Thu, 6 Jan 2005, Tim Devries wrote:

When I do a

Colo-3550#sh mls qos int fa0/1 stat FastEthernet0/1 Ingress dscp: incoming no_change classified policed dropped (in pkts) Others: 38469779 38379716 90063 0 190138 Egress dscp: incoming no_change classified policed dropped (in pkts) Others: 33285081 n/a n/a 0 0

Colo-3550#

I see packets being dropped, but in my monitoring software I still see it spiking up to 5-6Mb.

I believe the interface counters on the 3550 increment before the traffic policing is applied - ie. they count prepoliced traffic.

It's something that makes checking whether configurations like this are working an order of magnitude more difficult :/

S