- play_arrow Overview
- play_arrow Introduction to Class of Service
-
- play_arrow Configuring Class of Service Components
- play_arrow Assigning Service Levels with Classifiers
- play_arrow Controlling Network Access with Traffic Policing
- Simple Filters and Policers Overview
- Two-Rate Three-Color Policer Overview
- Example: Configuring a Two-Rate Three-Color Policer
- Logical Interface (Aggregate) Policer Overview
- Two-Color Policer Configuration Overview
- Example: Configuring a Two-Color Logical Interface (Aggregate) Policer
- Guidelines for Configuring Simple Filters
- Example: Configuring and Applying a Firewall Filter for a Multifield Classifier
- play_arrow Controlling Output Queues with Forwarding Classes
- Forwarding Classes Overview
- Example: Configuring Forwarding Classes
- Example: Assigning Forwarding Classes to Output Queues
- Example: Classifying All Traffic from a Remote Device by Configuring Fixed Interface-Based Classification
- Understanding the SPC High-Priority Queue
- Example: Configuring the SPC High-Priority Queue
- Understanding Queuing and Marking of Host Outbound Traffic
- Default Routing Engine Protocol Queue Assignments
- play_arrow Altering Outgoing Packets Headers with Rewrite Rules
- play_arrow Defining Output Queue Properties with Schedulers
- Schedulers Overview
- Default Scheduler Settings
- Transmission Scheduling Overview
- Excess Bandwidth Sharing and Minimum Logical Interface Shaping
- Excess Bandwidth Sharing Proportional Rates
- Calculated Weights Mapped to Hardware Weights
- Weight Allocation with Only Shaping Rates or Unshaped Logical Interfaces
- Shared Bandwidth Among Logical Interfaces
- Example: Configuring Class-of-Service Schedulers on a Security Device
- Scheduler Buffer Size Overview
- Example: Configuring a Large Delay Buffer on a Channelized T1 Interface
- Configuring Large Delay Buffers in CoS
- Example: Configuring and Applying Scheduler Maps
- Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs
- Example: Applying Scheduling and Shaping to VLANs
- play_arrow Removing Delays with Strict-Priority Queues
- play_arrow Controlling Congestion with Drop Profiles
- play_arrow Controlling Congestion with Explicit Congestion Notification
- play_arrow Controlling Congestion with Adaptive Shapers
- play_arrow Limiting Traffic Using Virtual Channels
- play_arrow Enabling Queuing for Tunnel Interfaces
- play_arrow Naming Components with Code-Point Aliases
-
- play_arrow Configuring Class of Service for IPv6
- play_arrow Configuring Class of Service for IPv6 Traffic
-
- play_arrow Configuring Class of Service for I/O Cards
- play_arrow Configuring Class of Service for I/O Cards
- PIR-Only and CIR Mode Overview
- Understanding Priority Propagation
- Understanding IOC Hardware Properties
- Understanding IOC Map Queues
- WRED on the IOC Overview
- MDRR on the IOC Overview
- CoS Support on the SRX5000 Module Port Concentrator Overview
- Example: Configuring CoS on SRX5000 Firewalls with an MPC
-
- play_arrow Configuration Statements and Operational Commands
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.
