Hi all, this question is in relation customizing the trap reception port of a DMA.
Dataminer Docs does cover one scenario whereby we customize the SNMPv3 trap reception port (link).
However, what if the intended outcome is to keep SNMPv3 trap reception port at default value of 162 and to have SNMPv2 trap reception at a customized port (e.g.: 16261)?
It is observed that if we specify the following in DataMiner.xml (i.e.: keep SNMPv3 trap reception port at 162):
and if we specify the following in C:\Windows\System32\drivers\etc\services (i.e.: set SNMPv2 trap reception port to 16261):
snmptrap 16261/udp snmp-trap #SNMP trap
Upon a DMA restart, the Windows SNMPTRAP process is 'Stopped' and therefore any custom port set for snmptrap in C:\Windows\System32\drivers\etc\services does not matter.
So is the correct way to configure the above to:
(1) Specify the following in DataMiner.xml:
(2) Comment out 'snmptrap' line in C:\Windows\System32\drivers\etc\services
# snmptrap 162/udp snmp-trap #SNMP trap
Please help clarify:
- If 'SNMPv2 trapPort' is a valid tag in DataMiner.xml
- If we should comment out the snmptrap line or set it to 16261 to align with what is in DataMiner.xml file
DataMiner has two ways of taking in traps, either through WinSNMP or either through snmp++. The latter is the only one that is able to process SNMPv3 traps which is why that one always needs to come in play.
Then then are two scenarios:
- The SNMPv1 and SNMPv2 ports are configured on the same port as SNMPv3.
DataMiner will only use snmp++ to take in the traps and will even completely kill the snmptrap service so it doesn’t interfere with what it is trying to setup.
- The SNMPv1 or SNMPv2 ports are configured on a different port than SNMPv3 (your scenario)
WinSNMP and snmp++ need to run side by side (remember, SNMPv3 traps can only be processed by snmp++) and the SNMPv2 traps will be processed by WinSNMP for performance reasons (in the past we noticed a significant higher throughput of UDP datagrams with WinSNMP compared to snmp++)
<SNMPv2 trapPort="16261"> is definitely a valid configuration. There is however a limitation that the trap port used by the snmptrap service can not be changed by the API. That is why it is important that you change the service configuration to align it with the desired port as well. The one that is configured in the DataMiner.xml configuration file is only to make the SLSNMPManager module know that it differs from the SNMPv3 trap port and for logging purposes.