Service Egress and Ingress QoS Policies
Quality of Service Guide 329
The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where
the policy 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.
bytes — When byte is defined, the value given for size is interpreted as the queue’s MBS value
given in bytes.
kilobytes — When kilobytes is defined, the value is interpreted as the queue’s MBS value given
in kilobytes.
Values 0 – 16777216 or default
Default kilobytes
packet-byte-offset
Syntax packet-byte-offset {add bytes | subtract bytes}
no packet-byte-offset
Context config>qos>sap-egress>policer
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.
To Next Page
Loading...
