QoS Scheduler Policies
Quality of Service Guide 567
Description This command determines the expected location of the parent schedulers for the tier 1 schedulers
configured with a parent command within the scheduler-policy. The parent schedulers must be
configured within a scheduler-policy applied at the location corresponding to the parent-location
parameter.
If a parent scheduler name does not exist at the specified location, the schedulers will not be parented
and will be orphaned.
The configuration of parent-location and frame-based-accounting in a scheduler policy is mutually
exclusive in order to ensure consistency between the different scheduling levels.
The no form of the command reverts to the default.
Default none
Parameters none — This parameter indicates that the tier 1 schedulers do not have a parent scheduler and the
configuration of the parent under a tier 1 scheduler is blocked. Conversely, this parameter is
blocked when any tier 1 scheduler has a parent configured.
sub — When the scheduler-policy is applied to an sla-profile for a subscriber, the parent
schedulers of the tier 1 schedulers need to be configured in the scheduler-policy applied to the
subscriber’s sub-profile.
If this parameter is configured within a scheduler-policy that is applied to any object except
for the egress of an sla-profile, the configured parent schedulers will not be found and so the
tier 1 schedulers will not be parented and will be orphaned.
vport — When the scheduler-policy is applied to an sla-profile, a sub-profile for a subscriber or
to the egress of a pseudowire SAP, the parent schedulers of the tier 1 schedulers need to be
configured in the scheduler-policy applied to the vport to which the subscriber will be
assigned.
If this parameter is configured within a scheduler-policy that is applied to to any object except
for the egress of an sla-profile or sub-profile, or to the egress of a PW SAP, the configured
parent schedulers will not be found and so the tier 1 schedulers will not be parented and will
be orphaned.
tier
Syntax tier tier
Context config>qos>scheduler-policy
Description This command identifies the level of hierarchy that a group of schedulers are associated with. Within
a tier level, a scheduler can be created or edited. Schedulers created within a tier can only be a child
(take bandwidth from a scheduler in a higher tier). Tier levels increase sequentially with 1 being the
highest tier. All tier 1 schedulers are considered to be root and cannot be a child of another scheduler.
Schedulers defined in tiers other than 1 can also be root (parentless).
3 tiers (levels 1, 2 and 3) are supported.
To Next Page
Loading...
