Subscriber Services
7750 SR OS Services Guide Page 87
If the scheduler-name does not exist in this or another tier within the scheduler policy, it is assumed
that an attempt is being made to create a scheduler of that name. The success of the command
execution is dependent on the following:
1. The maximum number of schedulers has not been configured.
2. The provided scheduler-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 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 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.
Default None. Each scheduler must be explicitly created.
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.
rate
Syntax rate pir-rate [cir cir-rate]
no rate
Context config>service>customer>multi-service-site>ingress>sched-override>scheduler
config>service>customer>multi-service-site>egress>sched-override>scheduler
Description This command can be used to override specific attributes of the specified scheduler rate. The rate
command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers.
The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent
scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to
the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the
scheduler’s amount of bandwidth to be considered during the parent schedulers ‘within CIR’
distribution phase.
The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum
rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s
needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers
or child queues on the parent based on higher priority. The children of the scheduler may not need the
maximum rate available to the scheduler due to insufficient offered load or limits to their own
maximum rates.
When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a
root scheduler (no parent defined), the default maximum rate must be changed to an explicit value.
To Next Page
Loading...
