DFM does not receive traps

Answered Question
Jan 13th, 2010

Hi,


I'm running LMS 3.2 with DFM 3.2. It seems that DFM does not receive any traps from devices.

I'm sure that the traps from devices are coming to the LMS server, checked this with a sniffer.

DFM receiving port is default - udp 162
All DFM processes seem to be running, as seen under Common Services

I tried to find some information in the log files, and i found some errors but i don't know what they mean.


Here are the logs attached, and also the netstat and pdshow outputs


Any help?


Regards,

Correct Answer by Joe Clarke about 7 years 1 month ago

Okay, the DFM.log was confusing.  No, DFM does not support SNMPv3 notifications.  What traps are you sending to DFM?  DFM is not a general purpose trap receiver.  Only certain traps will ever appear as-is in AAD.  Others will be processed, and turned into other DFM events.  See http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/TrapFwd.html for more details on what traps DFM supports.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Wed, 01/13/2010 - 10:22

It appears something other than DFM is bound to udp/162.  Post the output of "netstat -a -n -o -b".

Velin Georgiev Thu, 01/14/2010 - 05:08

Here it is the netstat output again.

UDP port 162 is occupied by sm_server.exe



By the way, does DFM supports receiving of SNMPv3 traps?

Anyway i tried with SNMPv2c traps and i cannot seem them in DFM Alerts and Activities

Correct Answer
Joe Clarke Fri, 01/15/2010 - 14:06

Okay, the DFM.log was confusing.  No, DFM does not support SNMPv3 notifications.  What traps are you sending to DFM?  DFM is not a general purpose trap receiver.  Only certain traps will ever appear as-is in AAD.  Others will be processed, and turned into other DFM events.  See http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/TrapFwd.html for more details on what traps DFM supports.

Velin Georgiev Tue, 01/19/2010 - 00:35

OK, I found what caused the problem.

I stopped LMS daemon manager and after some time executed again netstat -o -n -a -b.

Udp port 162 was still occupied by sm_server...Then i looked at the processes in windows task manager - i saw some LMS procesess pending, not sure why. Then i restarted the windows server and now DFM is receiving traps.


I know that DFM is not processing all the traps, i've got it in mind

I didn't know that it does not recognize SNMP v3 traps, but then i found that info in the DFM release notes


Thank you!

Actions

This Discussion