How to complete ACI SNMP trap destination configuration?
An engineer configures SNMP for an ACI fabric and created an SNMP Monitoring Destination Group called snmp_dgroup1. Snmp_dgroup1 is configured with the server hostname and community password. An SNMP policy called snmp_podpolicy1 is configured to enable SNMP and add an SNMP Client Group Profile called snmp_clgroup1. Snmp_podpolicy1 is associated the default pod profile via a pod policy group named pod1. Which configuration set must the engineer enable to complete the SNMP configuration?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tested: distinguishing SNMP trap traffic (UDP 162) from polling (UDP 161) and placing the filter on the mgmt tenant OOB contract; the trap is that an 'SNMP management contract' does not exist in ACI.
This 300-620 ACI question tests SNMP trap destination configuration and the OOB management contract filter needed to permit UDP 162. The correct completion is to configure the OOB management contract to permit UDP 162.
A common wrong pick is C, assuming a service-specific 'SNMP management contract' must permit UDP 162; ACI uses the mgmt tenant OOB contract instead.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The SNMP Monitoring Destination Group (snmp_dgroup1) defines where ACI sends SNMP traps, and traps traditionally use UDP port 162. To let those traps reach the external server, the mgmt tenant out-of-band (OOB) EPG needs a contract that permits UDP 162. The engineer already created the destination group, SNMP policy, client group profile, and pod policy group, so the remaining piece is the OOB management contract filter. Option A correctly scopes the contract to UDP 162 rather than allowing all traffic, which matches ACI SNMP trap best practice. As samfab noted, the destination group should be associated with the OOB management EPG.Why the Other Options Are Wrong
Option B suggests an 'SNMP management contract' permitting all traffic, but ACI does not provide a special SNMP contract type; the contract belongs under the mgmt tenant and is applied to the OOB EPG. Option C repeats the same invalid 'SNMP management contract' construct while fixing only the port, so it still places the filter in the wrong object. Option D chooses the correct OOB contract but permits all traffic, which is unnecessarily permissive and not the required configuration. Only A combines the correct contract object with the correct UDP port for SNMP traps. As prospio971 outlined, the OOB contract filter should permit UDP ports 161 and 162 for SNMP traffic.Community Comment Notes
Community consensus strongly supports A, with all visible votes agreeing on the OOB management contract answer. samfab framed the issue as associating the destination group with the OOB management EPG, which aligns with the trap path. prospio971 gave detailed steps to create an OOB contract in the mgmt tenant and add filters for UDP 161 and 162. crosillo30 shared a Cisco community reference and quoted 'Step 1 - Management Contracts (Out-of-band and inband)' to reinforce that existing OOB contracts need SNMP filters.Official Reference
Exam Strategy
Identify whether the question is about SNMP polling or SNMP traps before selecting a port, because polling uses UDP 161 and traps use UDP 162. Then place the filter on the mgmt tenant OOB contract associated with the OOB EPG, not on an invented SNMP-specific contract.
Frequently Asked Questions
Why is UDP 162 required instead of UDP 161 for this ACI SNMP setup?
The SNMP Monitoring Destination Group defines trap receivers, and SNMP traps are sent to UDP 162. UDP 161 is for polling, which is handled by the SNMP Client Group Profile.
Why is an SNMP management contract not the right option?
ACI does not have an 'SNMP management contract'; the mgmt tenant out-of-band contract on the OOB EPG is where you add the UDP 162 filter for SNMP traps.