I have two IPs configured in the DMA VM. I want the SNMP manager only to use one of those IPs to send out traps. SNMP Manager was using the first configured IP until restart, after which it started to use the second IP. Is there any way to force the manager to use specific IP to send out traps?
Hi Martin,
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer that has been most helpful for you (using the ✓ icon)?
As this question has now been inactive for a long time, I will close it. If you still want more information about this, could you post a new question?
This is a more advanced setting, and making a mistake could result in serious communication issues, but there is a 'SkipAsSource' flag in Windows on the NICs and IPs. This basically configures that an IP can be used a source IP or not. So, maybe you can skip this IP as source, BUT this means that nothing will be able to use it as source anymore, not only SNMP.
Be very careful when configuring such a flag in Windows!
We have a tool available to visualize and configure this: SLSkipAsSourceTool | DataMiner Docs
To the best of my knowledge, this is not configurable. It currently supports following the virtual IP of the failover configuration, but not a user configured address. Otherwise it just relies on the default handling of the operating system by specifying "0.0.0.0" / "::" as source.
I'm not familiar with any way to force the behaviour you want through manipulation of the network adapters either.
Just a test…
You mention a VM with two IPs – so I believe it’s a single DMA server (no VIP/failover): if that’s the case, I’d check what’s the behaviour of the SNMP manager traps if you define a NIC team over the interfaces in the VM and just associate a single IP to the NIC-team. This might not be possible within the VM,
I’m assuming you might define a Nic-Team as SNMP Manager is moving from one interface to the other (no Corporate/Acquisition separation) – so possibly no need to keep 2 different IPs at OS layer.