tomz at cisco
Sep 13, 2007, 12:53 PM
Post #2 of 2
(307 views)
Permalink
|
|
Re: Cisco 3550 traffic policing/QoS limitations?
[In reply to]
|
|
The 3550 QoS policer usage is detailed in the configuration guide:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/relea
se/12.2_25_see/configuration/guide/swqos.html#wp1044737
The same policy-map with policer can be attached to each port and in
your case you can use up to 1 policer per FE port so its within limits.
However, Policy-map applies to either ingress (service-policy input) or
egress (service-policy output) are separate.. You can have 5M ingress/5M
egress (or anything that adds to 10M total) by attaching an ingress
policy-map and an egress policy-map. Egress policy-map however, can only
match on DSCP(s) so you have to know the DSCP(s) (if don't care, set
them all to 0 at ingress policy-map first so egress can match on it).
> -----Original Message-----
> From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-
> bounces [at] puck] On Behalf Of TCIS List Acct
> Sent: Thursday, September 13, 2007 9:31 AM
> To: cisco-nsp
> Subject: [c-nsp] Cisco 3550 traffic policing/QoS limitations?
>
> According to:
>
> http://www.cisco.com/warp/public/473/153-2.gif
>
> It appears that there are limitations on the number of policers that
you
> can
> use. What isn't clear is how these apply -- in a nutshell, what we
want
> to be
> able to do is define a policer that limits ingress/egress traffic to
10M
> (we
> will likely use ACLs on Ingress to only apply this limit to traffic
bound
> for
> non-local subnets) on _every_ FE port on our 3550-EMI's. Is this
> possible or no?
>
> TIA.
>
> --Mike
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
|
