DX NetOps Performance Management Data Collector is sending out packets to port 162 for all devices managed by the Data Collector.
Why are requests from the Data Collector for SNMP data using the wrong port, port 162, the port normally used to send and receive traps?
A Discovery Profile is configured to attempt communication using all available SNMP Profiles. One of the SNMP Profiles it's trying to utilize is the one configured for Notification Rules sending Traps which is set to use port 162.
All supported DX NetOps Performance Management releases
Configure Discovery Profiles to utilize only the necessary SNMP Profiles configured for SNMP request access.
It can be configured to use all SNMP Profiles but should not have the Trap based SNMP Profile configured to use port 162.
The only SNMP Profiles that would be ignored by a Discovery Profile configured to use all available ones are those enabled for SNMP SET operations.
Support and Engineering agree that a new feature to ignore SNMP Profiles configured for Notification Rules that send traps using port 162 should be ignored in the same manner as those enabled for SNMP SET operations. While a great idea its not a current feature of the product making it an Enhancement Request. To submit an Enhancement Request submit an Idea via the Ideation page for submitting Enhancement Requests.
How does an SNMP Profile set to “Use by Default” impact this scenario?
The SNMP Profile "Use by Default" option per documentation is defined as:
Use by default for new devices: Specifies whether CA Application Delivery Analysis, Network Flow Analysis, and CA Unified Communications Monitor use this profile to contact any new items. To stop these data sources from using this SNMP profile for discovery, disable this parameter.
That option is used for other Data Sources and is never utilized by the Data Aggregator and it's Discovery Profiles.