Alcatel-Lucent 7950 Quality Of Service Manual page 496

Generic Commands
scheduler. Scheduler objects are created within the hierarchical tiers of the policy. It is assumed that each
scheduler created will have queues or other schedulers defined as child associations. The scheduler can be a
child (take bandwidth from a scheduler in a higher tier, except for schedulers created in tier 1). A total of 32
schedulers can be created within a single scheduler policy with no restriction on the distribution between the
tiers.
Each scheduler must have a unique name within the context of the scheduler policy; however the same name
can be reused in multiple scheduler policies. If
(regardless of the inclusion of the keyword create), the context changes to that scheduler name for the
purpose of editing the scheduler parameters. Modifications made to an existing scheduler are executed on all
instantiated schedulers created through association with the policy of the edited scheduler. 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 the scheduler-name
create), an error occurs and the current CLI context will not change.
If the scheduler-name
attempt is being made to create a scheduler of that name. The success of the command execution is
dependent on the following:
1.
2.
3.
When the maximum number of schedulers has been exceeded on the policy, a configuration error occurs and
the command will not execute, nor will the CLI context change.
If the provided scheduler-name is invalid according to the criteria below, a name syntax error will occur, the
command will not execute, and the CLI context will not change.
Parameters scheduler-name — The name of the scheduler.
Values
Default
create — This optional keyword explicitly specifies that it is acceptable to create a scheduler with the given
scheduler-name. If the create keyword is omitted, scheduler-name is not created when the system
environment variable create is set to true. This safeguard is meant to avoid accidental creation of system
objects (such as schedulers) while attempting to edit an object with a mistyped name or ID. The
keyword has no effect when the object already exists.
Page 496
exists within the policy on a different tier (regardless of the inclusion of the keyword
does not exist in this or another tier within the scheduler policy, it is assumed that an
The maximum number of schedulers has not been configured.
The provided scheduler-name
The create keyword is entered with the command if the system is configured to require it (enabled
in the environment create command).
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.
None. Each scheduler must be explicitly created.
scheduler-name already exists within the policy tier level
is valid.
7950 XRS Quality of Service Guide