Refer to the exhibit. When applying this policy map on the tunnel1 interface, you see packet loss for the TCP class starting at around 100000 b/s, instead of the configured 150000 b/s. What is the…

The correct answer is C. The burst size is too low. Configuration Tasks See the following sections for configuration tasks for the Configuring Burst Size in Low Latency Queueing feature. Each task in the list is identified as optional or required. Configuring the LLQ Bandwidth (Required) Configuring the LLQ Burst Size (Required)…

QoS

Question

Refer to the exhibit. When applying this policy map on the tunnel1 interface, you see packet loss for the TCP class starting at around 100000 b/s, instead of the configured 150000 b/s. What is the most likely cause of the discrepancy?

Exhibit

Options

AThe violate-action command should not be configured.
BThe current configuration of the load-interval command on the tunnel interface is preventing
CThe burst size is too low.
DPolicing on tunnel interfaces is not supported.
EThe CIR keyword is missing in the policer.

How the community answered

(54 responses)

A
6% (3)
B
4% (2)
C
57% (31)
D
11% (6)
E
22% (12)

Explanation

Configuration Tasks See the following sections for configuration tasks for the Configuring Burst Size in Low Latency Queueing feature. Each task in the list is identified as optional or required. Configuring the LLQ Bandwidth (Required) Configuring the LLQ Burst Size (Required) Verifying the LLQ Burst Size (Optional) Configuring the LLQ Bandwidth To configure the LLQ bandwidth, use the following command in policy-map class configuration Configuring the LLQ Burst Size To configure the LLQ burst size, use the following command in policy-map class configuration Verifying the LLQ Burst Size To verify the LLQ burst size, use one of the following commands in EXEC mode:

Topics

#policing#burst size#packet loss#CIR

Community Discussion

No community discussion yet for this question.

Full 350-001 Practice