Alcatel-Lucent 7450 Quality Of Service Manual page 331

enters the orphan state, it is flagged as operationally degraded due to the fact that it is not operating as
intended and a trap is generated. Whenever a policer-control-policy is added to the SAP or the
existing policy is modified, the SAP's policer's parenting configurations must be reevaluated. If an
orphan policer becomes parented, the degraded flag should be cleared and a resulting trap should be
generated.
On the 7450 ESS and 7750 SR, for subscribers, the policer control hierarchy is created through the
policer-control-policy applied to the sub-profile used by the subscriber. A unique policer control
hierarchy is created for each subscriber associated with the sub-profile. The QoS policy containing the
policer with the parenting command comes into play through the subscriber sla-profile which
references the QoS policy. The combining of the sub-profile and the sla-profile at the subscriber level
provides the system with the proper information to create the policer control hierarchy instance for the
subscriber.
Executing the parent command will fail if:
A policer with a parent command applied cannot be configured with stat-mode no-stats in either the
QoS policy or as an override on an instance of the policer
Once a policer is successfully parented to an arbiter, the parent commands level and weight
parameters are used to determine at what priority level and at which weight in the priority level that
the child policer competes with other children (policers or other arbiters) for bandwidth.
The no form of this command is used to remove the parent association from all instances of the policer.
Parameters
{root | arbiter-name} — When the parent command is executed, either the keyword root or an
root — The root keyword specifies that the policer is intended to become a child to the root
arbiter-name — The arbiter-name parameter specifies that the policer is intended to become a
weight weight-within-level — The weight weight-within-level keyword and parameter are
Quality of Service Guide
• The policer's stat-mode in the QoS policy is set to no-stats
• A stat-mode no-stats override exists on an instance of the policer on a SAP or subscribers or
multi-service site context
arbiter-name must be specified.
arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer
will be placed in the orphan state.
child to one of the tiered arbiters with the given arbiter-name where an instance of the policer
is created. If the specified arbiter-name does not exist, the policer will be placed in the orphan
state.
Default None
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.
Default 1
Service Egress and Ingress QoS Policies
331