Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Question How do schedulers provide different treatment to the different forwarding classes? Answer You use schedulers to define the class-of-service (CoS) properties of forwarding classes and output queues. You configure CoS properties in a scheduler, then map the scheduler to a forwarding class
Question What is the default scheduler policy for Junos CoS on routing devices?
Answer Hierarchical class of service (HCoS) is the ability to provide CoS functionality as a more granular level (for example, per subscriber rather than per port) by applying traffic schedulers and shapers to a hierarchy of scheduler nodes . Each level of the scheduler hierarchy can be used to treat traffic based on different criteria such as per application, user, VLAN, and physical port
Answer Use traffic-manager mode with the following options to configure CoS traffic manager mode of operation: egress-only—Enables CoS queuing and scheduling on the egress side for the PIC that houses the interface
Answer Support for PIR and CIR on MPCs On MX Series devices using MPCs, CIR and PIR are supported at the queue level with class-of-service (CoS) schedulers
How do schedulers provide different treatment to the different forwarding classes?...What is the default scheduler policy for Junos CoS on routing devices?
You map incoming traffic to a forwarding class, define the class-of-service (CoS) properties for the forwarding class through a scheduler, and assign the forwarding class to an output queue
You can configure drop profiles that determine the probability of dropping a queued packet based on the fullness of the queue and then map those drop profiles to PLPs for a particular scheduler
Is it possible to use a common QoS scheduler on a traffic-class group comprised of an aggregate of multiple GRE tunnels?