Alcatel-Lucent 7450 Quality Of Service Manual page 330

Service SAP QoS Policy Command Reference
Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either add or
subtract bytes — The subtract keyword is mutually exclusive to the add keyword. Either add or
parent
Syntax parent {root | arbiter-name} [level level] [weight weight-within-level]
no parent
Context config>qos>sap-egress>policer
Description This command is used to create a child to parent mapping between each instance of the policer and
either the root arbiter or a specific tiered arbiter on the object where the policy is applied. Defining a
parent association for the policer causes the policer to compete for the parent policer's available
bandwidth with other child policers mapped to the policer control hierarchy.
Policer control hierarchies may be created on SAPs or on a subscriber or multi-service site context. To
create a policer control hierarchy on an ingress or egress SAP context, a policer-control-policy must
be applied to the SAP. Once applied, the system will create a parent policer that is bandwidth limited
by the policy's max-rate value under the root arbiter. The root arbiter in the policy also provides the
information used to determine the various priority level discard-unfair and discard-all thresholds.
Besides the root arbiter, the policy may also contain user defined tiered arbiters that provide arbitrary
bandwidth control for subsets of child policers that are either directly or indirectly parented by the
arbiter.
When the QoS policy containing the policer with a parent mapping to an arbiter name exists on the
SAP, the system will scan the available arbiters on the SAP. If an arbiter exists with the appropriate
name, the policer to arbiter association is created. If the specified arbiter does not exist either because
a policer-control-policy is not currently applied to the SAP or the arbiter name does not exist within
the applied policy, the policer is placed in an orphan state. Orphan policers operate as if they are not
parented and are not subject to any bandwidth constraints other than their own PIR. When a policer
330
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 purposes. From the policer's perspective, the maximum
packet size is increased by the amount being added to the size of each packet.
Values
0 to 31
Default None
subtract must be specified. When b is defined the corresponding bytes parameter specifies
the number of bytes that is subtracted from the size of each packet associated with the policer
for rate metering, profiling and accounting purposes. From the policer's perspective, the
maximum packet size is reduced by the amount being subtracted from the size of each packet.
The minimum resulting packet size used by the system is 1 byte.
Values 1 to 64
Default None
Quality of Service Guide