It is expected that by default, a DMS should have trap distribution enabled (i.e.: if tag not specified in dataminer.xml).
- This understanding is supported by our DataMiner Docs: (DataMiner.xml | DataMiner Docs)
- RN21389 also supports this understanding.
Testing in in user's set up shows that:
- Trap distribution is disabled by default. When a device sends a trap to the DMA that does not host the element that polls that device, the trap is not registered by that element. When the device config is updated to send trap to the DMA that hosts the element polling the device, the trap is then registering by the element.
Please help to confirm if trap distribution is disabled by default in 10.3.0.0 CU9 or is this a bug?
Trap distribution is by default enabled on a DataMiner system. If you want to verify if that is the case on your system, you can check its state in the SNMP Managers logging.
|CSNMPManager::Init_Wrapper|CRU|-1|DMS Trap Distribution Enabled
For further troubleshooting, you can set Debug logging level on SNMP Managers to Log everything (5)
Then you should see the trap being forwarded to SLDMS.
|CSNMPManager::TryDistributeTrap|DBG|5|Distributed trap to SLDMS. Trap source IP: [source IP], trap destination IP: [destination IP]
If there's an element configured on a different agent in the cluster that has an SNMP interface with the trap source IP configured, the trap will end up being forwarded to the SLSNMPManager process of the other agent and will be further processed there.