[Contents] [Prev] [Next] [Index] [Report an Error]

Hierarchical Schedulers Terminology

Hierarchical schedulers introduce some new terms into a discussion of CoS capabilities. They also use some familiar terms it different contexts. This section presents a complete overview of the terms used with hierarchical schedulers.

The following terms are important for hierarchical schedulers:

These terms are especially important when applied to a scheduler hierarchy. Scheduler hierarchies are composed of nodes and queues. Queues terminate the CLI hierarchy. Nodes can be either root nodes, leaf nodes, or internal (non-leaf) nodes. Internal nodes are nodes that have other nodes as “children” in the hierarchy. For example, if an interface-set statement is configured with a logical interface (such as unit 0) and queue, then the interface-set is an internal node at Level 2 of the hierarchy. However, if there are no traffic control profiles configured on logical interfaces, then the interface set is at Level 3 of the hierarchy.

Table 49 shows how the configuration of an interface set or logical interface affects the terminology of hierarchical scheduler nodes.

Table 49: Hierarchical Scheduler Nodes

Root Node (Level 1)Level 2Level 3Queue (Level 4)

Physical interface

Interface set

Logical interfaces

One or more queues

Physical interface

 

Interface set

One or more queues

Physical interface

 

Logical interfaces

One or more queues

Scheduler hierarchies consist of levels, starting with Level 1 at the physical port. This chapter establishes a four-level scheduler hierarchy which, when fully configured, consists of the physical interface (Level 1), the interface set (Level 2), the logical interface(s) (Level 3), and the queue(s) (Level 4).


[Contents] [Prev] [Next] [Index] [Report an Error]