Interface Configuration
7750 SR Interface Configuration Guide Page 577
cbs
Syntax cbs {size [bytes | kilobytes] | default}
no cbs
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 configure the policer’s CIR leaky bucket’s exceed threshold. The CIR bucket’s
exceed threshold represents the committed burst tolerance allowed by the policer. If the policer’s forwarding
rate is equal to or less than the policer's defined CIR, the CIR bucket depth hovers around the 0 depth with
spikes up to the maximum packet size in the offered load. If the forwarding rate increases beyond the profil-
ing rate, the amount of data allowed to be in-profile above the rate is capped by the threshold.
The policer’s cbs 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 CBS size.
Default none
Parameters size [bytes | kilobytes] — The size parameter is required when specifying cbs 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
mbs
Syntax mbs {size [bytes | kilobytes] | default}
no mbs
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 configure the policer’s PIR leaky bucket’s high priority violate threshold. The
high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold.
For ingress, trusted in-profile packets and un-trusted high priority packets use the policer’s high priority vio-
late threshold while trusted out-of-profile and un-trusted low priority packets use the policer's low priority
violate threshold. At egress, in-profile packets use the policer’s high priority violate threshold and out-of-
profile packets use the policer's low priority violate threshold.
The PIR bucket’s violate threshold represent the maximum burst tolerance allowed by the policer. If the
policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around
the 0 depth with spikes up to the maximum packet size in the offered load. If the offered rate increases
To Next Page
Loading...
