QoS Scheduler Policy Command Reference
572 Quality of Service Guide
Changing the parent context on a SAP egress policy queue may cause a SAP or subscriber context of
the queue (policy associated with a SAP or subscriber profile) to enter an orphaned state. If an instance
of a queue is created on a port or channel that does not have a port scheduler enabled and the sap-egress
policy creating the queue has a port-parent association, the queue will be allowed to run according to
its own rate parameters and will not be controlled by a virtual scheduling context. If an instance of a
queue is on a port or channel that has a port scheduler configured and the sap-egress policy defines the
queue as having a non-existent intermediate scheduler parent, the queue will be treated as an orphan
and will be handled according to the current orphan behavior on the port scheduler.
The no form of this command removes a port scheduler parent association for the queue or scheduler.
If a port scheduler is defined on the port which the queue or scheduler instance exists, the queue or
scheduler will become orphaned if an port scheduler is configured on the egress port of the queue or
scheduler.
Default no port-parent
Parameters weight weight — Defines the weight the queue or scheduler will use at the above-cir port priority
level (defined by the level parameter).
Values 0 to 100
Default 1
level level — Defines the port priority the queue or scheduler will use to receive bandwidth for its
above-cir offered-load.
Values 1 to 8 (8 is the highest priority)
Default 1
cir-weight cir-weight — Defines the weight the queue or scheduler will use at the within-cir port
priority level (defined by the cir-level parameter). The weight is specified as an integer value
from 0 to 100 with 100 being the highest weight. When the cir-weight parameter is set to a
value of 0, the queue or scheduler does not receive bandwidth during the port scheduler’s
within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or
greater, the cir-level parameter comes into play.
Values 0 to 100
Default 1
cir-level cir-level — Defines the port priority the queue or scheduler will use to receive
bandwidth for its within-cir offered-load. If the cir-weight parameter is set to a value of 0 (the
default value), the queue or scheduler does not receive bandwidth during the port scheduler’s
within-cir pass and the cir-level parameter is ignored. If the cir-weight parameter is 1 or
greater, the cir-level parameter comes into play.
Values 0 to 8 (8 is the highest priority)
Default 0
rate
Syntax rate [pir-rate] [cir cir-rate]
To Next Page
Loading...
