300-410 · Question #86
Refer the exhibit. Which action resolves intermittent connectivity observed with the SNMP trap packets?
The correct answer is B. Increase the CIR of the mgmt class map. Intermittent connectivity for SNMP trap packets, likely due to CoPP, can be resolved by increasing the allocated bandwidth.
Question
Exhibit
Options
- ADecrease the committed burst Size of the mgmt class map
- BIncrease the CIR of the mgmt class map
- CAdd a new class map to match TCP traffic
- DAdd one new entry in the ACL 120 to permit the UDP port 161
How the community answered
(36 responses)- A3% (1)
- B81% (29)
- C6% (2)
- D11% (4)
Why each option
Intermittent connectivity for SNMP trap packets, likely due to CoPP, can be resolved by increasing the allocated bandwidth.
Decreasing the committed burst size would make the policing even stricter, causing more drops and exacerbating the intermittent connectivity issue.
Intermittent connectivity for SNMP trap packets suggests that the Committed Information Rate (CIR) for the 'mgmt' class map, which likely handles SNMP traffic, is set too low. Increasing the CIR allows the router to process a higher volume of legitimate SNMP trap packets without dropping them due to policing, thus resolving the intermittent connectivity issue.
SNMP traps use UDP, not TCP, so adding a class map for TCP traffic would have no effect on SNMP trap packets.
SNMP traps typically use UDP port 162 for sending traps, not 161 (which is for SNMP queries); even if the port were correct, an ACL blocking would cause consistent, not intermittent, connectivity issues, and this is a CoPP-style question.
Concept tested: Control Plane Policing (CoPP) rate limiting
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_copp/configuration/xe-16/sec-data-copp-xe-16-book/sec-copp-policer-data-plane.html
Topics
Community Discussion
No community discussion yet for this question.
