- play_arrow Overview
- play_arrow Use Juniper BNG CUPS
- Use Juniper BNG CUPS with Multiple Geographical Redundancy
- Use Dynamic Address Pools in Juniper BNG CUPS
- Juniper BNG CUPS High Availability
- Use Juniper BNG CUPS Subscriber Groups
- Use BNG User Plane Maintenance
- Use Juniper BNG CUPS Smart Session Load Balancing
- Use Juniper BNG CUPS for Subscriber Steering
- Use Juniper BNG CUPS Multicast
- Use Juniper BNG CUPS Lawful Intercept
- Use Juniper BNG CUPS Captive Portal and Content Delivery Services
- Configure Agent Circuit Identifier and IFL Sets in Juniper BNG CUPS
- Understanding DVLAN (Single/Dual tag) for Subscriber Services Scaling (Junos Evolved for ACX7100-48L, ACX7332, and ACX7348 Devices)
- How to Use the Juniper BNG CUPS Controller Utility Commands
- Troubleshooting and Monitoring Juniper BNG CUPS
- play_arrow Juniper BNG CUPS Controller CLI Configuration Statements
- play_arrow Juniper BNG CUPS Controller CLI Operational Statements
- play_arrow Juniper BNG User Plane CLI Operational Commands
hierarchical-scheduler
Syntax
hierarchical-scheduler {
implicit-hierarchy;
maximum-hierarchy-levels number;
}
Hierarchy Level
[edit interfaces] [edit dynamic-profiles name interfaces], [edit dynamic-profiles name logical-systems name interfaces]
Description
Enable the use of hierarchical schedulers. If you do not include this statement, the interfaces on the router cannot use hierarchical interfaces.
When configuring hierarchical scheduling for network slices on an interface, you do not need to enable vlan-tagging on that interface.
To enable hierarchical scheduling on MX80 and MX104 routers, configure the
hierarchical-scheduler statement at each member physical interface level of a
particular aggregated Ethernet interface as well as at that aggregated Ethernet interface
level. On other routing platforms, it is enough if you include this statement at the
aggregated Ethernet interface level.
Options
| implicit-hierarchy | For MPC/MIC subscriber interfaces and interface sets running over aggregated Ethernet on MX Series routers, form a hierarchical relationship between the CoS scheduler nodes at level 1, level 2, and level 3. |
| maximum-hierarchy-levels number | Set the maximum number of hierarchy levels.
|
