XR policing, exceed vs violate?

[Seth Beauchamp]

With XR, if you have a policy-map configured with a class like below... at what point is traffic considered "exceed" vs "violate"? without PIR specifically configured, does it assume a default PIR?

class EF
priority level 1
police rate percent 80
conform-action transmit
exceed-action transmit
violate-action drop

[tkarnani · Accepted solution]

I have configured your policy on a lab node, you can verify values with below command

RP/0/RSP0/CPU0:ASR9006-M#show qos interface tenGigE 0/2/1/3 input
Thu May 10 05:03:02.168 EDT
Interface: TenGigE0_2_1_3 input
Bandwidth configured: 10000000 kbps Bandwidth programed: 10000000 kbps
ANCP user configured: 0 kbps ANCP programed in HW: 0 kbps
Port Shaper programed in HW: 0 kbps
Policy: EFFF Total number of classes: 2
----------------------------------------------------------------------
Level: 0 Policy: EFFF Class: EF
QueueID: 196640 (Port Priority 1)
Policer Profile: 64 (SrTCM)
Conform: 8000000 kbps (80 percent) Burst: 100000000 bytes (0 Default)
Peak Burst: 100000000 bytes (0 Default)
Child Policer Conform: TX
Child Policer Exceed: TX
Child Policer Violate: DROP
----------------------------------------------------------------------
Level: 0 Policy: EFFF Class: class-default
QueueID: 196642 (Port Default)
----------------------------------------------------------------------
RP/0/RSP0/CPU0:ASR9006-M#

policy-map EFFF
 class EF
  priority level 1
  police rate percent 80
   conform-action transmit
   exceed-action transmit
   violate-action drop
  !
 !
 class class-default
 !
 end-policy-map
!

[Seth Beauchamp]

Ah i see. Thanks.

If you use it as an output policy, does yours show the Burst as well? Mine doesn't show the same when i run the command with "output" instead.

EDIT: oops sorry, it does indeed show it. i was using the wrong command.

[tkarnani]

Hi Seth,

here is what i see

RP/0/RSP0/CPU0:ASR9006-M#show qos interface tenGigE 0/2/1/3 output
Thu May 10 05:37:40.385 EDT
Interface: TenGigE0_2_1_3 output
Bandwidth configured: 10000000 kbps Bandwidth programed: 10000000 kbps
ANCP user configured: 0 kbps ANCP programed in HW: 0 kbps
Port Shaper programed in HW: 0 kbps
Policy: EFFF Total number of classes: 2
----------------------------------------------------------------------
Level: 0 Policy: EFFF Class: EF
QueueID: 201800 (Priority 1)
Queue Limit: 98304 kbytes Abs-Index: 173 Template: 0 Curve: 6
Shape CIR Profile: INVALID
Policer Profile: 64 (SrTCM)
Conform: 8000000 kbps (80 percent) Burst: 100000000 bytes (0 Default)
Peak Burst: 100000000 bytes (0 Default)
Child Policer Conform: TX
Child Policer Exceed: TX
Child Policer Violate: DROP
----------------------------------------------------------------------
Level: 0 Policy: EFFF Class: class-default
QueueID: 201802 (Priority Normal)
Queue Limit: 24512 kbytes Abs-Index: 142 Template: 0 Curve: 0
Shape CIR Profile: INVALID
WFQ Profile: 3/9 Committed Weight: 10 Excess Weight: 10
Bandwidth: 0 kbps, BW sum for Level 0: 0 kbps, Excess Ratio: 1
----------------------------------------------------------------------
RP/0/RSP0/CPU0:ASR9006-M#