JN0-663 · Question #10
You have a strict-high queue configured. You notice that under bursty traffic conditions, there are tail drops on the strict-high queue. Which action would solve this problem?
The correct answer is D. Increase the buffer size of the strict-high queue. A queue with strict-high priority is assured unlimited transmission bandwidth but is not actually assigned a large delay buffer. Not configuring a transmit-rate or an explicit buffer-size on a strict- high priority queue only ensures that the queue gets assigned a default…
Question
You have a strict-high queue configured. You notice that under bursty traffic conditions, there are tail drops on the strict-high queue. Which action would solve this problem?
Options
- AAssign a policer on ingress to assign a low packet loss priority to the strict-high queue.
- BDecrease the buffer size of the strict-high queue.
- CAssign a policer on egress to assign a low packet loss priority to the strict-high queue.
- DIncrease the buffer size of the strict-high queue.
How the community answered
(45 responses)- A7% (3)
- B16% (7)
- C2% (1)
- D76% (34)
Explanation
A queue with strict-high priority is assured unlimited transmission bandwidth but is not actually assigned a large delay buffer. Not configuring a transmit-rate or an explicit buffer-size on a strict- high priority queue only ensures that the queue gets assigned a default minimum delay buffer, making it possible, under bursty conditions, to see tail-drops on strict-high priority queues. Assigning a small transmit-rate or an explicit temporal or percentage buffer-size to the queue ensures that the queue has a large enough buffer to hold bursts and protect against tail-drops. schedulers-for-priority-scheduling.html
Topics
Community Discussion
No community discussion yet for this question.