[nsp] Rate limit on Native 6500

[Jared Mauch]

	you need to use policy-maps and police using that.

	what you can do is create a policy map for your upstream
interfaces and police inbound on that.  that will solve your bidrectional issues.

	- jared

On Tue, Jan 28, 2003 at 05:18:04PM +0100, Iva Cabric wrote:
> Can someone clear this out for me,... I have following situation:
> on Catalyst 6500 (Sup1/MSFC1), running Native IOS, rate-limit is
> used on Layer 3 interface:
> 
> interface FastEthernet3/48
>  ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
>  rate-limit input access-group 170 4096000 128000 128000 conform-action transmit exceed-action drop
>  rate-limit output access-group 171 4096000 128000 128000 conform-action transmit exceed-action drop
> end
> 
> In this case who is responsible for policing, MSFC or PFC?
> 
> >From "show interfaces FastEthernet 3/48 switching" it looks like
> MSFC is doing all work (or maybe just in output direction).
> 
> What is situation on Sup2/MSFC2/PFC2?
> 
> Also in case of using PFC QoS (Policy Maps), on Sup1/MSFC1 it is
> not allowed to use Policy Map on output direction. Is this same
> on Sup2/MSFC2?
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.