What is correct regarding rate limiting and egress queue shaping on AOS-CX switches?
What is correct regarding rate limiting and egress queue shaping on AOS-CX switches?
Traffic rate limiting and egress queue shaping on AOS-CX switches are configured at the queue level. This means you can define specific rate limits for different traffic queues, enabling fine-grained control over the bandwidth allocation for various types of traffic. This approach helps in managing network congestion and ensuring important traffic gets prioritized appropriately.
Correct Answer: D
I think that C is correct because rate limiting can be applied globally by a policy and for egress queue shapping apply the global schedule profile when apply the queue profile. Based on the schedule profile, DWRR is being used and the queue and schedule profile are applied globally. A is not correct: queue shaping restrict outbound traffic B is not correct: restrict unknow unicast D is not correct: traffic rate limit is configured on interface level
D. the traffic rate limit is configured on an interface level. You maybe defined max-bandwidth in strict queue, but you applied to an interface.
D is correct。 for example: switch(config)# qos schedule-profile EQSExample switch(config-schedule)# strict queue 0 switch(config-schedule)# strict queue 1 max-bandwidth 10000000 burst 120 switch(config-schedule)# strict queue 2 switch(config-schedule)# strict queue 3 switch(config-schedule)# strict queue 4 max-bandwidth 20000000 switch(config-schedule)# strict queue 5 switch(config-schedule)# strict queue 6 switch(config-schedule)# strict queue 7 max-bandwidth 30000000 burst 120 switch(config-schedule)# exit switch(config)# interface 1/1/1 switch(config-if)# apply qos schedule-profile EQSExample
https://www.arubanetworks.com/techdocs/AOS-CX/10.08/PDF/qos_832x.pdf Page 851 Study Guide: Egress queue shaping allows you to apply a maximum bandwidth to a priority queue, as well as a burst size. [Aruba Networks]
Page 258 vol2 says Egress queue shaping limits the amount of traffic transmitted per output queue.
I think it should be D. EQS can be configured with a schedule profile and be applied on an ETH port or LAG, cannot be applied in globally (Test with 8400 and 8325).
C: Rate limiting, you configure it per physical or lag interface. P:825 Study Guide
From ACSP Learning book QoS Egress Queue Shaping/Rate Limiting: - A is wrong because "EQS limits the amount of traffic transmitted per output queue" - B is wrong because Interface Rate Limiting can be applied for broadcast, multicast and unknown unicast and Interface Rate Limiting is not same than EQS - C is wrong because "EQS can be configured on an Ethernet port or on link aggregation group (LAC)" - D is correct