Alcatel-Lucent 7750 SR Manual page 1314

VPRN Service Configuration Commands
The no form of this command removes the QoS policy association from the SAP or IP interface, and
the QoS policy reverts to the default.
Parameters
policy-id — The ingress/egress policy ID to associate with SAP or IP interface on ingress/egress. The
shared-queuing — Specify the ingress shared queue policy used by this SAP. When the value of this
multipoint-shared — This keyword specifies that this queue-id is for multipoint forwarded traffic
scheduler-policy
Syntax scheduler-policy scheduler-policy-name
no scheduler-policy
Context config>service>vprn>if>sap>ingress
config>service>vprn>if>sap>egress
config>service>vprn>sub-if>grp-if>sap>egress
config>service>vprn>sub-if>grp-if>sap>ingress
config>service>vprn>ipsec-if>sap>egress
config>service>vprn>ipsec-if>sap>ingress
Description
This command applies an existing scheduler policy to an ingress or egress scheduler used by SAP
queues associated with this multi-service customer site. The schedulers defined in the scheduler
policy can only be created once the customer site has been appropriately assigned to a chassis port,
channel or slot. Scheduler policies are defined in the config>qos>scheduler-policy scheduler-policy-
name context.
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.
Page 1314
policy ID must already exist.
Values
1 — 65535
object is null it means that the SAP will use individual ingress QoS queues instead of the shared
ones.
only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or
unknown unicast ingress traffic. Attempting to map forwarding class unicast traffic to a
multipoint queue generates an error; no changes are made to the current unicast traffic queue
mapping.
A queue must be created as multipoint. The multipoint designator cannot be defined after the
queue is created. If an attempt is made to modify the command to include the multipoint
keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue
to edit queue-id parameters.
Default Present (the queue is created as non-multipoint).
Values
Multipoint or not present.
7750 SR OS Services Guide