7950 XRS Quality of Service Guide
Page 493
Scheduler Policy Commands
scheduler-policy
Syntax
scheduler-policy
scheduler-policy-name
no scheduler-policy
scheduler-policy-name
Context
config>qos
Description
Each scheduler policy is divided up into groups of schedulers based on the tier each scheduler is created
under. A tier is used to give structure to the schedulers within a policy and define rules for parent scheduler
associations.
The
scheduler-policy
command creates a scheduler policy or allows you to edit an existing policy.The
policy defines the hierarchy and operating parameters for virtual schedulers. Merely creating a policy does
not create the schedulers; it only provides a template for the schedulers to be created when the policy is
associated with a SAP or multi-service site.
Each scheduler policy must have a unique name within the context of the system. Modifications made to an
existing policy are executed on all schedulers that use the policy. This can cause queues or schedulers to
become orphaned (invalid parent association) and adversely affect the ability of the system to enforce
service level agreements (SLAs).
If a
scheduler-policy-name
does not exist, it is assumed that an attempt is being made to create a new
policy. The success of the command execution is dependent on the following:
1.
The maximum number of scheduler policies has not been configured.
2.
The provided scheduler-policy-name is valid.
3.
The
create
keyword is entered with the command if the system is configured to require it (enabled
in the
environment create
command).
When the maximum number of scheduler policies has been exceeded a configuration error occurs, the
command will not execute, and the CLI context will not change.
If the provided scheduler-policy-name is invalid according to the criteria below, a name syntax error occurs,
the command will not execute, and the CLI context will not change.
Default
none
— Each scheduler policy must be explicitly created.
Parameters
scheduler-policy-name —
The name of the scheduler policy.
Values
Valid names consist of any string up to 32 characters long composed of printable, 7-bit
ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire
string must be enclosed within double quotes.
Summary of Contents for 7950
Page 12: ...Page 12 7950 XRS Quality of Service Guide List of Figures ...
Page 16: ...Preface Page 16 7950 XRS Quality of Service Guide ...
Page 82: ...Editing QoS Policies Page 82 7950 XRS Quality of Service Guide ...
Page 90: ...Applying Network Queue Policies Page 90 7950 XRS Quality of Service Guide ...
Page 96: ...Editing QoS Policies Page 96 7950 XRS Quality of Service Guide ...
Page 98: ...Command Hierarchies Page 98 7950 XRS Quality of Service Guide ...
Page 108: ...Command Hierarchies Page 108 7950 XRS Quality of Service Guide ...
Page 156: ...Basic Configurations Page 156 7950 XRS Quality of Service Guide exit exit ...
Page 164: ...Queue Depth Monitoring Page 164 7950 XRS Quality of Service Guide ...
Page 304: ...Service Queue QoS Policy Commands Page 304 7950 XRS Quality of Service Guide ...
Page 368: ...Command Hierarchies Page 368 7950 XRS Quality of Service Guide ...
Page 430: ...Configuration Commands Page 430 7950 XRS Quality of Service Guide ...
Page 532: ...Editing QoS Policies Page 532 7950 XRS Quality of Service Guide ...
Page 552: ...Editing Advanced Policies Page 552 7950 XRS Quality of Service Guide ...
Page 600: ...Command Hierarchies Page 600 7950 XRS Quality of Service Guide ...
Page 602: ...QoS Commands Page 602 7950 XRS Quality of Service Guide ...
Page 610: ...Standards and Protocols Page 610 7950 XRS Quality of Service Guide ...
Page 612: ... 2015 Alcatel Lucent All rights reserved 3HE 09868 AAAA TQZZA 01 ...