[c-nsp] ME 6524 rate-limit
Rodney Dunn
rodunn at cisco.com
Thu Aug 30 09:19:38 EDT 2007
On Thu, Aug 30, 2007 at 09:09:05AM -0400, Jay Young wrote:
> I have put an ME6524 (s6523-advipservicesk9-mz.122-18.ZU2.bin) in to
> replace a 7200 and one of the interfaces has a rate-limit. When I do a "show
> int rate-limit" I see:
>
> GigabitEthernet1/1.460
> Input
> matches: access-group 100
> params: 144696000 bps, 1048576 limit, 1048576 extended limit
> conformed 0 packets, 0 bytes; action: transmit
> exceeded 0 packets, 0 bytes; action: drop
> last packet: 1573927164ms ago, current burst: 0 bytes
> last cleared 00:51:24 ago, conformed 0 bps, exceeded 0 bps
> Output
> matches: access-group 101
> params: 144696000 bps, 1048576 limit, 1048576 extended limit
> conformed 0 packets, 0 bytes; action: transmit
> exceeded 0 packets, 0 bytes; action: drop
> last packet: 1573927164ms ago, current burst: 0 bytes
> last cleared 00:51:24 ago, conformed 0 bps, exceeded 0 bps
>
>
> I know there is traffic that is matched by the acl, is this config
> supported?
Not sure but I wouldn't advise it.
All new implementations are based on MQC policers. You should use that.
Rodney
Should I convert this to a policy map?
>
> Thanks,
> Jay
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list