What would explain why the policer is allowing 100 Mbps of traffic into the router?

Refer to the exhibit.

What would explain why the policer is allowing 100 Mbps of traffic into the router?

Refer to the exhibit.

What would explain why the policer is allowing 100 Mbps of traffic into the router?

A.
The burst-size-limit is inappropriate for the bandwidth-limit and for the default MTU of the ge-*/3# interfaces.

B.
The policer is not using shared-bandwidth-policer, which it must to achieve a rate of 50 Mbps of
traffic.

C.
The policer is applied in the wrong direction.

D.
The policer is not using logical-interface-policer, which it must to achieve a rate of 50 Mbps of
traffic.

Explanation:

Show Hint

Leave a Reply 2

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

testokhan

testokhan

By default, policer bandwidth and burst-size applied on aggregated bundles is not matched to the user-configured bandwidth and burst-size.

You can configure interface-specific policers applied on an aggregated Ethernet bundle or an aggregated SONET bundle to match the effective bandwidth and burst-size to user-configured values. The shared-bandwidth-policer statement is required to achieve this match behavior.

Reply