Question 170
At a branch router serving several application classes, a Junos specialist investigates this scenario: A busy output queue suffers severe tail drop and interactive applications need controlled early loss behavior. The team must validate packet drops by actual queue statistics. What is the most appropriate correction to implement?
Explanation
Correct Answer
For a branch router serving several application classes, the direct corrective action is: Apply a suitable RED or weighted drop profile through the appropriate scheduler. This addresses the mechanism: A Junos drop profile can define queue occupancy thresholds and drop probabilities before absolute congestion. Confirm by checking: Congestion tests show the intended early-drop curve without unbounded queue growth. During rollout, avoid aggressive early drops that harm short or sensitive application flows.
Incorrect Answers
A scheduler map must be associated with the appropriate interface for selected class-to-scheduler behavior. The appropriate correction for the reported case is: Apply a suitable RED or weighted drop profile through the appropriate scheduler.
A scheduler can prioritize selected latency-sensitive queues over other queues when the interface is congested. Fixing that different mechanism would not address the current root cause: a Junos drop profile can define queue occupancy thresholds and drop probabilities before absolute congestion.
Junos rewrite rules map internal forwarding class and loss-priority information to outgoing packet codepoints. Its verification is distinct from the reported condition: A busy output queue suffers severe tail drop and interactive applications need controlled early loss behavior. The team must validate packet drops by actual queue statistics.