Class Fair Hierarchical Policing (CFHP)
Quality of Service Guide 883
Parameters size [bytes | kilobytes] — The size parameter is required when executing the mbs-contribution
command. It is expressed as an integer and specifies the priority’s specific portion amount of
accumulative MBS for the priority level in bytes or kilobytes which is selected by the trailing
bytes or kilobytes keywords. If both bytes and kilobytes are missing, kilobytes is assumed.
Setting this value has no effect on parent policer instances where the priority level’s mbs-
contribution value has been overridden.
Values 0 to 4194304 or default (applies to the 7450 ESS)
0 to 16777216 or default (applies to the 7750 SR and 7950 XRS)
Default 8 kilobytes
bytes | kilobytes: — The bytes keyword is optional and is mutually exclusive with the kilobytes
keyword. When specified, size is interpreted as specifying the size of min-thresh-separation
in bytes.
The kilobytes keyword is optional and is mutually exclusive with the bytes keyword. When
specified, size is interpreted as specifying the size of min-thresh-separation in kilobytes.
Default kilobytes
fixed — The optional fixed keyword is used to force the inclusion of the defined mbs-
contribution value in the parent policer’s discard threshold calculations. If the mbs-
contribution command is executed without the fixed keyword, the fixed calculation behavior
for the priority level is removed.
tier
Syntax tier {1 | 2}
Context config>qos>policer-control-policy
Description This command is used to create, configure, and delete tiered arbiters. Two tiers are supported that
always exist specified as tier 1 and tier 2. Tiered arbiters enable you to create a bandwidth control
hierarchy for managing child policers in an arbitrary fashion. Each arbiter enables you to parent child
policers within eight strict levels of priority and a maximum aggregate rate may be defined for the
children that the arbiter will enforce. Arbiters created on tier 1 are automatically parented to the root
arbiter which is always present. Arbiters created on tier 2 default to the root arbiter as parent, but can
also be explicitly parented to a tier 2 arbiter. Child policers associated with an instance of the policer-
control-policy can be parented to any tiered arbiter or to the root arbiter.
Default None.
arbiter
Syntax arbiter arbiter-name [create]
no arbiter arbiter-name
Context config>qos>policer-control-policy>tier
To Next Page
Loading...
