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.
See matching posts in thread
- QOS on SRX
Question Is hierarchical QoS per VLAN supported on aggregated Ethernet (AE) interfaces?
Hello - If memory serves me right, H-COS is supported on LAG (egress only) on *MPC* too from JUNOS 12.3 onwards
See matching posts in thread
- QoS on EX2200 Shaping
When there is no traffic generator available, you cannot test quality-of-service (QoS) in terms of bandwidth utilization. You need a tool like the traffic generator to generate the required bandwidth. Consider the following example: 1G interface: Queue 1 - CoS A - 25% bandwidth priority...
Any ideas where I can locate some details on this Spirent product (is it something they are actually releasing)?
To review performance, scalability, and power efficiency validation for the MX Series 3D routers with the Junos Trio chipset, see: EANTC testing validation This article provides answers to the most common questions about the Junos Trio chipset on MX Series routers used with Junos OS Release 10.1 and later
Is hierarchical QoS per VLAN supported on aggregated Ethernet (AE) interfaces? What are the differences between the CoS traffic-manager options on the MX Series? How is the shaping rate calculated on the Enhanced Queuing DPCs (DPCE-R-Qs)? What is the queuing buffer size on MX Series DPCs? Are fine-grained queuing capabilities supported on Enhanced Queuing DPCs (DPCE-R-Q)?
Question What is the default scheduler policy for Junos CoS on routing devices? Answer If you do nothing to configure or assign classifiers on Juniper routing devices, Junos OS automatically assigns an implicit default IP precedence classifier to all logical interfaces that maps IPv4 precedence code points to best-effort and network-control forwarding classes
Question Is it possible to use a common QoS scheduler on a traffic-class group comprised of an aggregate of multiple GRE tunnels? Answer Support for using a common QoS scheduler on an aggregate group of GRE tunnels is accomplished by using a per-unit scheduler for GRE tunnels, which provides fine-grained queuing by using a single scheduler for a set of queues. As of Junos OS Release 10.1 and later, support for per-unit scheduler for GRE tunnels is added for: M Series Multiservice Edge Routers: M320 with SFPC, M120, M7i, and M10i for non-enhanced (ABC-based ) Compact Forwarding Engine Board (CFEB) and enhanced CFEB (I-chip-based) T Series Core Routers, including TX Matrix devices QoS on GRE tunnels is not supported when using the MS-DPC (IP services line card) on an MX Series device
Answer If a certain key-performance indicator (KPI) exists on a device (that is, if you can issue a show command to obtain the KPI), then OpenNTI (an open-source universal collector) can collect the KPI from the device
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. This allows you to support the requirements of different services / applications, and users on the same physical device and infrastructure