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?
On AOS-CX switches, egress queue shaping allows the definition of a maximum traffic rate and burst size for a queue. This means you can control the rate at which queued traffic is sent out, smoothing out bursts and controlling bandwidth allocation to prevent high-priority traffic from overwhelming other queues. This corresponds with option A, which states that only a traffic rate and burst size can be defined for a queue.
The answer is A, page 896
hi, where you download the ebook ? or you purchased.
A page 258
I also went with A
b is incorrect because rate-limiting can also be applied to unknown unicasts.
answer A
I think that D 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: traffic rate and burst size can be defined for only strict priority queue -> Egress queue shaping allows you to apply a maximum bandwidth to a priority queue, as well as a burst size. The port buffers excess traffic up to the burst size and sends the buffered traffic at the max rate, smoothing out bursts while also preventing the high priority queue from exceeding its maximum rate and starving out lower priority queues. Only process queues under the 7 queue if not have traffic in the 7 queue To process all queues Aruba-CX uses DWRR or WFQ -> In both algorithms, each queue receives a predictable share of the bandwidth based on the queue's relative priority, or weigh B is not correct: restrict unknow unicast C is not correct: egress queue shaping can be used to restrict outbound traffic
Answer A
A you could apply egress queue shaping to the high priority queues to prevent starvation of low priority queues. Egress queue shaping allows you to apply a maximum bandwidth to a priority queue, as well as a burst size. The port buffers excess traffic up to the burst size and sends the buffered traffic at the max rate, smoothing out bursts while also preventing the high priority queue from exceeding its maximum rate and starving out lower priority queues.
See also Question 71 Only answer, common to both questions is C: Rate limiting and egress queue shaping can be used to restrict inbound traffic
damn - no edit function should read D: Rate limiting and egress queue shaping can be applied globally
you cannot control inbound traffic using QoS features, only outbound or egress traffic, so C is certainly wrong
i think should be D, tested with 8325 and the qos queue and schedule profile could be apply globally and not must with int
Sorry i have tested again, answer should be A, in schedule profile, only bandwidth and burst can be defined. and the profile cannot be applied globally.
Correct answer is A
Same question as the other one in the database. It should be A
A is correct answer.
D: On Aruba AOS-CX, rate limiting and egress queue shaping can be applied globally on the switch or on specific interfaces
Should be A Click Quality of Service > General > Egress Shaping per Queue. The Egress Shaping Per Queue page displays the rate limit and burst size for each queue.
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]
Hi SeidorBruno, please could you supply me with your eamil address I wuold like to email you regarding a certain question I have please. Thank you, my email william.waller86.co.za
Hi SeidorBruno, please could you supply me with your eamil address I wuold like to email you regarding a certain question I have please. Thank you, my email william.waller86.co.za
In the official HPE Study Guide, in the section "Egress Queue Shaping/Rate Limiting" it states, "1. Create a schedule profile" and "2. Apply profile to an interface."