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:Nick Shah (Nick@aapt.com.au)
Date:Jan 6, 2005 5:39:55 pm
List:net.nether.puck.cisco-nsp

Tim

There are a couple of things wrong with the config. Here's what 3550 can & cant do in terms of QOS:

- Only ingress & egress policing is supported, SHAPING is NOT supported - It supports 2 types of policers Aggregate & individual - An aggregate policer acts, in a combined manner, on all classes within the policy map, essentially policing it to the rate prescribed in the aggregate policer - Individual policer polices each class to the rate - 1 x match statement per class map is supported - Ingress matching can only be done on match access-group, match ip dscp & match ip precedence - Egress matching can only be done on match ip dscp

In your case you can only match on ip dscp (on egress), and you can use an individual policer. If you want the inbound rate to also be 3MB than you may need to match on access list, dscp & precedence and then use an aggregate policer.

Check : http://www.cisco.com/warp/public/473/153.html

That url explains what you can & cant do & how to do it.

Rgds

Nick

-----Original Message----- From: cisc@puck.nether.net [mailto:cisc@puck.nether.net] On Behalf Of Tim Devries Sent: Friday, 7 January 2005 4:14 AM To: cisc@puck.nether.net Subject: [c-nsp] 3550 QoS not working as expected

Hello,

We are currently attempting to do QoS with our 3550 for customers in our collocation. However, when monitoring the real-time usage of the interface using our monitoring software, it does not appear to work. For example we have a customer limited to 3Mb, but they frequently jump as high as 6Mb.

We are running Version 12.1(22)EA1a. Relevant portions of the config follow:

! Mls qos ! class-map match-all customerA match any match input-interface FastEthernet0/1 match access-group 101 match access-group 102 ! policy-map customerA class customerA bandwidth 3000 police 3000000 8000 exceed-action drop ! interface FastEthernet0/1 description CustomerA - 3MB/s switchport access vlan 4 switchport mode access switchport protected mls qos monitor packets flowcontrol send off service-policy history service-policy output customerA no cdp enable spanning-tree portfast ! access-list 101 permit ip host X.X.X.X any access-list 101 permit ip host X.X.X.X any access-list 102 permit ip any host X.X.X.X access-list 102 permit ip any host X.X.X.X

As an aside, Cisco literature mentions 3550's can do rate-limiting, but I have been unable to find any literature on how, as the usual commands don't seem to work. Is there a better way to do what I am trying to do?

Thanks for any help,

Tim

_______________________________________________ cisco-nsp mailing list cisc@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/

------------------------------------------------------------------------------ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it.

------------------------------------------------------------------------------