Refer to the exhibit. An engineer implemented CoPP to limit Telnet traffic to protect the router CPU. It was noticed that the Telnet traffic did not pass through
CoPP. Which configuration resolves the issue?
Refer to the exhibit. An engineer implemented CoPP to limit Telnet traffic to protect the router CPU. It was noticed that the Telnet traffic did not pass through
CoPP. Which configuration resolves the issue?
The configuration issue lies within the access-list entries, where source and destination IP addresses appear to be swapped. The correct configuration should specify the correct source and destination IPs for Telnet traffic to match the intended control plane policing (CoPP) policy. Hence, the correct configuration is to permit TCP traffic from the actual source IP to the destination IP on the Telnet port, which is correctly reflected in option C.
C is correct. matching IP address source and destination.
"exceed-action drop" achieves the goal, however, the source IPs in the access-list are wrong and need to be corrected for sure. So it is "C" for me.
police bps [burst-normal] [burst-max] conform-action action exceed-action action [violate-action action] Syntax Description bps Average rate, in bits per second. Valid values are 8000 to 200000000. burst-normal (Optional) Normal burst size in bytes. Valid values are 1000 to 51200000. Default normal burst size is 1500. burst-max (Optional) Maximum burst size, in bytes. Valid values are 1000 to 51200000. Default varies by platform. conform-action Specifies action to take on packets that conform to the rate limit. exceed-action Specifies action to take on packets that exceed the rate limit. violate-action (Optional) Specifies action to take on packets that violate the normal and maximum burst sizes. action Action to take on packets. Specify one of the following keywords: •drop—Drops the packet.
C is correct
C is the answer
I meant the destination IPs in the access-list. Destination IPs need to be corrected.
limit Telnet traffic to protect the router CPU