Virtual Private LAN Services
7750 SR OS Services Guide Page 517
The PIR parameter for SAP ingress queues do not have a negate (no) function. To return the
queues PIR rate to the default value, that value must be specified as the PIR value.
Values 1 — 100000000, max
Default max
cir cir-rate — The cir parameter accepts a step-multiplier value that specifies the multiplier used to
determine the CIR rate at which the queue will operate. A value of 0 to 250 or the keyword max
is accepted. Any other value will result in an error without modifying the current CIR rate.
To calculate the actual CIR rate, the rate described by the rate pir pir-rate is multiplied by the cir
cir-rate. If the cir is set to max, then the CIR rate is set to infinity.
The SAP ingress context for CIR is dependent on the defined forwarding class (fc) for the queue.
The default CIR and definable range is different for each class. The CIR in effect for a queue
defines both its profile (in or out) marking level as well as the relative importance compared to
other queues for scheduling purposes during congestion periods.
Values 0 — 10000000, max, sum
Default sum
scheduler-policy
Syntax scheduler-policy scheduler-policy-name
no scheduler-policy
Context config>service>vpls>sap>ingress
config>service>vpls>sap>egress
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.
scheduler-policy-name: — The scheduler-policy-name parameter applies an existing scheduler policy
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.
To Next Page
Loading...
