Scheduler Policies - Alcatel-Lucent 7450 Quality Of Service Manual

Ethernet service switch; service router; extensible routing system

Hide thumbs Also See for 7450:

Table of Contents

Exceed (RED)

Scheduler Policies

A scheduler policy defines the hierarchy and all operating parameters for the member

schedulers. A scheduler policy must be defined in the QoS context before a group of virtual

schedulers can be used. Although configured in a scheduler policy, the individual schedulers

are actually created when the policy is applied to a site, such as a SAP or interface.

Scheduler objects define bandwidth controls that limit each child (other schedulers and

queues) associated with the scheduler. The scheduler object can also define a child

association with a parent scheduler of its own.

A scheduler is used to define a bandwidth aggregation point within the hierarchy of virtual

schedulers. The scheduler's rate defines the maximum bandwidth that the scheduler can

consume. It is assumed that each scheduler created will have queues or other schedulers

defined as child associations. The scheduler can also be a child (take bandwidth from) a

scheduler in a higher tier, except for schedulers created in Tier 1.

A parent parameter can be defined to specify a scheduler further up in the scheduler policy

hierarchy. Only schedulers in Tiers 2 and 3 can have parental association. Tier 1 schedulers

cannot have a parental association. When multiple schedulers and/or queues share a child

status with the scheduler on the parent, the weight or strict parameters define how this

scheduler contends with the other children for the parent's bandwidth. The parent scheduler

can be removed or changed at anytime and is immediately reflected on the schedulers actually

created by association of this scheduler policy.

When a parent scheduler is defined without specifying level, weight, or CIR parameters, the

default bandwidth access method is weight with a value of 1.

If any orphaned queues (queues specifying a scheduler name that does not exist) exist on the

ingress SAP and the policy application creates the required scheduler, the status on the queue

becomes non-orphaned at this time.

Quality of Service Guide

Table 15: Default Slope Policy Definition (Continued)

Administrative state

Time average factor

30% utilization

55% utilization

80% probability

QoS Policies