Class Fair Hierarchical Policing (CFHP) Policy Command Reference
886 Quality of Service Guide
Description This command is used to define from where the tiered arbiter receives bandwidth. Both tier 1 and tier 2
arbiters default to parenting to the root arbiter. Tier 2 arbiters may be modified to parent to a tier 1
arbiter. The tier 1 arbiter parent cannot be changed. If the no parent command is executed, the arbiter
reverts to its root parenting default parameters.
The parent command is also used to define the parenting parameters. Each child arbiter attaches to its
parent on one of the parents eight strict levels. Level 1 is the lowest and 8 is the highest. The level
attribute is used to define which level the child arbiter uses on its parent. The parent distributes its
available bandwidth based on strict priority starting with priority level 8 and proceeding towards
level 1.
The weight attribute is used to define how multiple children at the same parent strict level compete
when insufficient bandwidth exist on the parent for that level. Each child's weight is divided by the
sum of the active children's weights and the result is multiplied by the available bandwidth. If a child
cannot receive its entire weighted fair share of bandwidth due to a defined child rate limit, the
remainder of its bandwidth is distributed between the other children based on their weights.
The no version of this command is used to return the tiered arbiter to the default parenting behavior.
The arbiter will be attached to the root arbiter at priority level 1 with a weight of 1.
Default none
Parameters root — The root keyword is mutually exclusive with the arbiter-name parameter. In tier 1,
arbiter-name is not allowed and only root is accepted. When root is specified, the arbiter will
receive all bandwidth directly from the root arbiter. This is the default parent for tiered
arbiters.
arbiter-name — The arbiter-name parameter is mutually exclusive with the root keyword. In tier
1, arbiter-name is not allowed and only root is accepted. The specified arbiter-name must
exist within the policer-control-policy at tier 1 or the parent command will fail. Once a tiered
arbiter is acting as a parent for another tiered arbiter, the parent arbiter cannot be removed
from the policy. The child arbiter will receive all bandwidth directly from its parent arbiter
(which receives bandwidth from the root arbiter).
level priority-level — The level priority-level keyword and parameter are optional when
executing the parent command. When level is not specified, a default level of 1 is used in the
parent arbiter. When level is specified, the priority-level parameter must be specified as an
integer value from 1 through 8.
weight weight-within-level — The weight weight-within-level keyword and parameter are
optional when executing the parent command. When weight is not specified, a default level
of 1 is used in the parent arbiters priority level. When weight is specified, the weight-within-
level parameter must be specified as an integer value from 1 through 100.
To Next Page
Loading...
