What is the most likely cause of the discrepancy?

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?

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?

A.
The violate-action command should not be configured.

B.
The current configuration of the load-interval command on the tunnel interface is preventing
proper policing calculations.

C.
The burst size is too low.

D.
Policing on tunnel interfaces is not supported.

E.
The CIR keyword is missing in the policer.

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
mode:

Configuring the LLQ Burst Size
To configure the LLQ burst size, use the following command in policy-map class configuration
mode:

Verifying the LLQ Burst Size
To verify the LLQ burst size, use one of the following commands in EXEC mode:

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t3/feature/guide/dtcfgbst.html#wp1015329



Leave a Reply 0

Your email address will not be published. Required fields are marked *