Frequently Used QoS Terms
Quality of Service Guide 891
Offered Load
Offered load is evaluated per child in the scheduler hierarchy. The offered load is the amount
of bandwidth a child queue or scheduler can use to accommodate the data passing through the
child. It is separated into two portions; within CIR and above CIR. Within CIR offered load
is the portion of bandwidth required to meet the child’s CIR value. It can be less than the CIR
value but never greater. If the forwarding requirement for the child is greater than the CIR
value, the remaining is considered to be the above CIR offered load. The sum of the within
CIR and above CIR offered load cannot be greater than the maximum rate defined for the
child.
Orphan
When a child queue is configured with a parent scheduler specified but the parent scheduler
does not exist on the object the queue is created on, the state is considered orphaned.
An orphaned state is not the same condition as when a queue is not defined with a parent
association. Orphan states are cleared when the parent scheduler becomes available on the
object. This can occur when a scheduler policy containing the parent scheduler name is
applied to the object that the queue exists on or when the scheduler name is added to the
scheduler policy already applied to the object that the queue exists on.
Parent
A scheduler becomes a parent when a queue or scheduler defines it as its parent. A queue or
scheduler can be a child of only one scheduler. When defining a parent association on a child
scheduler, the parent scheduler must already exist in the same scheduler policy and on a
scheduler tier higher (numerically lower) then the child scheduler. Parent associations for
queues are only checked once, when an instance of the queue is created on a SAP.
To Next Page
Loading...
