[cisco-voip] LLQ Qn on policing

[Ki Wi]

Thanks guys.

The part I'm concern on this if I put in violation as remark, the policing
have "no upper limit", will this starve other class ? or

each class are guarantee to receive their "minimum" share when bandwidth is
configured?

On Fri, Jun 2, 2017 at 6:55 AM, Terry Cheema <terry.cheema at gmail.com> wrote:

> Yes Brian is right.
>
>
>
> However, to be more clear:
>
>
>
> 1)    Explicitly configured Policer is active all the time, you will
> never be allowed to go above the configured limit i.e. interface congested
> or not
>
> 2)    But if you use LLQ – *priority* command, it has an implicit
> Policer, that *does not* kick in unless the TX ring is filled or in other
> words interface is congested.
>
> So the priority queue can go above the configured limit unless there is
> congestion on the interface, in which case it will start policing the
> traffic.
>
> On Fri, Jun 2, 2017 at 12:22 AM, Brian Meade <bmeade90 at vt.edu> wrote:
>
>> Policing always applies even if no congestion.
>>
>> You can set the exceed-action to remark DSCP and transmit.  There's also
>> a conform-action which just applies to burst traffic you can configure.
>> There's no upper limit if you configure the exceed-action to remark and
>> transmit.
>>
>> On Thu, Jun 1, 2017 at 2:29 AM, Ki Wi <kiwi.voice at gmail.com> wrote:
>>
>>> Hi Group,
>>> I have a question on policing.
>>>
>>> Under CBWFQ (or LLQ), each policy map class can be configured
>>> with bandwidth command which acts as the minimum bandwidth commitment for
>>> each traffic class.
>>>
>>> For policing, I understand that it sets the upper limit for each traffic
>>> class.
>>>
>>> Now my question is
>>> 1) policing only kicks in when there's congestion?
>>>
>>> 2) if the policing command is configured to remark traffic only (no
>>> drop) for violate action. What will happen? Traffic will still flow, no
>>> upper limit?
>>>
>>> Will it starve other policy map?
>>>
>>> --
>>> Regards,
>>> Ki Wi
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>


-- 
Regards,
Ki Wi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170602/feb408b5/attachment.html>