Virtual Private LAN Services
7750 SR OS Services Guide Page 515
scheduler-override
Syntax [no] scheduler-override
Context config>service>vpls>sap>egress
config>service>vpls>sap>ingress
Description This command specifies the set of attributes whose values have been overridden via management on
this virtual scheduler. Clearing a given flag will return the corresponding overridden attribute to the
value defined on the SAP's ingress scheduler policy.
scheduler
Syntax scheduler scheduler-name
no scheduler scheduler-name
Context config>service>vpls>sap>egress>sched-override
Description This command can be used to override specific attributes of the specified scheduler name.
A scheduler defines a bandwidth controls that limit each child (other schedulers and queues)
associated with the 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 scheduler-name already exists within the
policy tier level (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 exists within the policy on a different tier (regardless of the inclusion of the
keyword create), an error occurs and the current CLI context will not change.
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.
To Next Page
Loading...
