I have configured snmp trap forwarding from DFM 2.0.7 to another NMS server (HP open view), (DFM > Configuration > Other Configuration > SNMP Trap Forwarding.) And DFM is also listening to traps itself (DFM > Configuration > Other Configuration > SNMP Trap Receiving. Port 162.)
Is there any way I can see that these traps really are getting forwarded to the other NMS server? I have installed Wireshark on my LMS server
and I can only see traps coming into DFM from the network devices. I have tried to find some help/answer about this, but so far no luck.
I can not see any errors in the DFM.log-file and the pdshow shows DfmServer running.
DFM is running on a Windows server 2003. Will there be a conflict if the server itself sends out snmp traps to the NMS? Will it be able to distinguish between DFM forwarding traps and its own "server traps"?
The snmp community RO name is not the same in DFM as it is on the NMS server. Could that be a problem?
I have added a screenshot of the DFM trap forwarding config page if that could be of any help. As for the output of netstat, would it be possible for you to tell me what i should be looking for in the different outputs?
.NET 2.0 SP1 is not installed on the server. Do I need it for this to work?
If the hostname you mention is resolvable from the server it should work.
And the snmp community in the trap message is irrelevant, you could put anything there.
.NET is not required.
I'm not confident when DFM will actually forward a trap. (It may drop traps it doesn't like, e.g. from a host it doesn't manage, that you may wish to receive in HPOV ) I think it is safer to have another application (like net-snmp) receive the traps and let it forward it to DFM and HPOV. Also this will give you a proper file with the received traps.
Yes, you are right. DFM will only process some traps. These processed traps can then be forward to HPOV by using notification services for example. DFM can also receive other traps which it will only forward to a NMS as unidentified (raw) traps.
I will look into other applications such as net-snmp for receiving and forwarding traps to HPOV since DFM is better at generating alerts based on monitoring devices with polling and tresholds.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...