Re: [c-nsp] policer on ASR1001X

james list <[email protected]>
Newsgroups gmane.network.nsp.cisco
Message-ID <CAEcMOL6pazXSBDfjQ63d7k-yoHmjCwxCGTbMtYCbNs+5--LuTg@mail.gmail.com>
Thanks
I would try to apply both Bps OR pps if possible

Cheers

Il Mer 8 Set 2021, 15:51 Lukasz Bromirski <[email protected]> ha scritto:

> Saku is always on point ;)
>
> > On 8 Sep 2021, at 15:31, Saku Ytti <[email protected]> wrote:
> >
> > On Wed, 8 Sept 2021 at 16:30, Lukasz Bromirski <[email protected]>
> wrote:
> >
> >>> 3) is there any mode to limit pps and not only bandwidth
> >>
> >> I no longer remember this from top of my mind, but there’s bunch of
> good QoS/HQoS presentations about ASR 1000 in particular on ciscolive.com
> that you can use as reference.
> >
> > police rate x pps
>
> Just checked this on 17.x based release (3k = 3000 for this example):
>
> rtr-edge(config-pmap-c)#police rate 3k ?
>   account         Overhead Accounting
>   bps             Treat 'rate' value in bits-per-second
>   burst           Specify 'burst' parameter
>   conform-action  action when rate is less than conform burst
>   cps             Treat 'rate' value in cells-per-second
>   peak-rate       Specify peak rate or PCR for single-level ATM 4.0
> policer policies
>   pps             Treat 'rate' value in packets-per-second
>   <cr>            <cr>
>
> --
> ./
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.