Aww. For competitive analysis this is supported in MX Trio (actually my RLI) and PTX Triton (but not Paradise, hw limit, unsure if SW for Triton exists yet, haven't tested.).
Definitely no reason why ASR1k could not support it if you have leverage towards vendor. On Thu, 9 Sept 2021 at 20:02, james list <jameslis...@gmail.com> wrote: > > Hi > just tested and police rate x pps is only applicable to control plane > > Cheers > > Il giorno mer 8 set 2021 alle ore 15:51 Lukasz Bromirski > <luk...@bromirski.net> ha scritto: >> >> Saku is always on point ;) >> >> > On 8 Sep 2021, at 15:31, Saku Ytti <s...@ytti.fi> wrote: >> > >> > On Wed, 8 Sept 2021 at 16:30, Lukasz Bromirski <luk...@bromirski.net> >> > 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> >> >> -- >> ./ -- ++ytti _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
