Alcatel-Lucent 7750 SR OS Service Manual page 89

The no form of this command removes the configured ingress or egress scheduler policy from the
multi-service customer site. When the policy is removed, the schedulers created due to the policy are
removed also making them unavailable for the ingress SAP queues associated with the customer site.
Queues that lose their parent scheduler association are deemed to be orphaned and are no longer
subject to a virtual scheduler. The SAPs that have ingress queues reliant on the removed schedulers
enter into an operational state depicting the orphaned status of one or more queues. When the no
scheduler-policy command is executed, the customer site ingress or egress node will not contain an
applied scheduler policy.
scheduler-policy-name: — The scheduler-policy-name parameter applies an existing scheduler policy
tod-suite
Syntax tod-suite tod-suite-name
no tod-suite
Context config>service>cust>multi-service-site
Description
This command applies a time-based policy (filter or QoS policy) to the multiservice site. The suite
name must already exist in the config>cron context.
Default
no tod-suite
Parameters
tod-suite-name — Specifies collection of policies (ACLs, QoS) including time-ranges. Only the
7750 SR OS Services Guide
that was created in the config>qos>scheduler-policy scheduler-policy-name context to create
the hierarchy of ingress or egress virtual schedulers. The scheduler names defined within the
policy are created and made available to any ingress or egress queues created on associated
SAPs.
Values
Any existing valid scheduler policy name.
scheduler-policy part of the tod-suite is taken into account. The suite can be applied to more than
one multi-service-site.
Subscriber Services
Page 89