Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

SM_server error in LMS2.6


I am using LMS 2.6

SM_server process is taking high cpu utilization. I am not able to configure, polling parameter or Managing Threshold as I am getting the error " PTMServer" process is down.

But the process status is "Running Normally" . I have also restarted the "PTMServer" process but no result.

Attached the DFM.log.

Cisco Employee

Re: SM_server error in LMS2.6

It appears sm_server is crashing due to bad trap data. Post a screenshot of DFM > Configuration > Other Configurations > SNMP Trap Forwarding.

Re: SM_server error in LMS2.6


I havce stoped syslog service and DfmServer process after that also DBsrv9.exe process had shown high CPU utilization. I have above 3000 device monitored in my cisco works. Out of these devices 586 devices showing under confilcting device in DFM.

is the problem because of these confilcting devices?

I have attached the CPU utilization screen shoot of CPu utilization screen shoot when both syslog and DFM are running (cpuutil.jpg), snmp trap forwarding(trapforwarding.JPG) and DFM device summury (dupdev.JPG).

Please help me if this error is not because of DFM device conflict.


Cisco Employee

Re: SM_server error in LMS2.6

The problem is being caused by too much or bad trap data. However, you are managing too many devices in DFM. DFM 2.x could only handle up to 1500 devices in ideal conditions, and you are trying to manage twice that.

First, to prevent the crashing, temporarily disable trap reception under DFM > Configuration > Other Configurations > SNMP Trap Receiving. Then, reduce the number of managed devices to a supported value. While 1500 is a rule of thumb, the real number depends on the number of managed ports and interfaces. The real rule is:

DFM supports configurations of up to 45,000 ports/interfaces, of which 6,750 (or 15%) are managed. This support was tested with an average of 30 ports/interfaces per device.

You can use the NMSROOT/objects/smarts/bin/sm_tpmgr --sizes command to see the current number of managed ports and interfaces.

Once you have the managed device count under control, you should stop sending traps from devices no longer managed by DFM. Once you do that, you can try re-enabling trap reception in DFM, and see if the crashing goes away.