Interfaces
Page 578 7750 SR Interface Configuration Guide
beyond the metering rate, the amount of data allowed above the rate is capped by the threshold. The low pri-
ority violate threshold provides a smaller burst size for the lower priority traffic associated with the policer.
Since all lower priority traffic is discarded at the lower burst tolerance size, the remaining burst tolerance
defined by high-prio-only is available for the higher priority traffic.
The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the pol-
icy is applied.
The no form of this command returns the policer to its default MBS size.
Default None
Parameters size [bytes | kilobytes] — The size parameter is required when specifying mbs and is expressed as an
integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional
byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size
represents bytes or kilobytes.
byte — When byte is defined, the value given for size is interpreted as the queue’s MBS value given in
bytes.
kilobyte — When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes.
Values 0 — 16777216
Default kilobyte
packet-byte-offset
Syntax packet-byte-offset {add bytes | subtract bytes}
no packet-byte-offset
Context config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description This command is used to modify the size of each packet handled by the policer by adding or subtracting a
number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth
impact is changed. The packet-byte-offset command is meant to be an arbitrary mechanism the can be used
to either add downstream frame encapsulation or remove portions of packet headers. Both the policing
metering and profiling throughput is affected by the offset as well as the stats associated with the policer.
When child policers are adding to or subtracting from the size of each packet, the parent policer’s min-
thresh-separation value should also need to be modified by the same amount.
The policer’s packet-byte-offset defined in the QoS policy may be overridden on an sla-profile or SAP
where the policy is applied.
The no version of this command is used to remove per packet size modifications from the policer.
Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must
be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that
is added to the size each packet associated with the policer for rate metering, profiling and accounting
To Next Page
Loading...
