Understanding Internal Scheduler Nodes
A node in the hierarchy is considered internal if either of the following conditions apply:
One of its children nodes has a traffic control profile configured and applied.
You configure the
internal-nodestatement.
There are more resources available at the logical
interface (unit) level than at the interface set level.
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.
You can use the internal-node statement 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.
Using the internal-node statement allows statements
to all be scheduled at the same level with or without children.
The following example makes the interface sets if-set-1 and if-set-2 internal:
[edit class-of-service interfaces ]
interface-set {
if-set-1 {
internal-node;
output-traffic-control-profile tcp-200m-no-smap;
}
if-set-2 {
internal-node;
output-traffic-control-profile tcp-100m-no-smap;
}
}
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.