Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Internal Scheduler Nodes

A node in the hierarchy is considered internal if either of the following conditions apply:

  • Any one of its children nodes has a traffic control profile configured and applied.

  • You include the internal-node statement at the [edit class-of-service interfaces interface-set set-name] hierarchy level.

Why would it be important to make a certain node internal? Generally, there are more resources available at the logical interface (unit) level than at the interface set level. Also, it might be desirable to configure all resources at a single level, rather than spread over several levels. The internal-node statement provides this flexibility. This can be a helpful configuration device when interface-set queuing without logical interfaces is used exclusively on the interface.

The internal-node statement can be used to raise the interface set without children to the same level as the other configured interface sets with children, allowing them to compete for the same set of resources.

In summary, using the internal-node statement allows statements to all be scheduled at the same level with or without children.

The following example makes the interfaces sets if-set-1 and if-set-2 internal:

If an interface set has logical interfaces configured with a traffic control profile, then the use of the internal-node statement has no effect.

Internal nodes can specify a traffic-control-profile-remaining statement.