sm_server proccess and CDP discovery

Unanswered Question
Apr 20th, 2007
User Badges:


i have two problems with my CiscoWorks LMS 2.6

First, when i make a discovery with a seed device in Campus Manager, some devices are not discovered. If i look for seed device neighbors, i can see more devices that ones that are put into inventory, i mean, not all neighbors are discovered. The devices are reachable by ping. Why are not all devices discovered although ciscoworks detect them as neighbors???? There is no filter applied.

Second, my ciscoworks is very slow. The sm_server is using 80% of CPU load. What can i do??? i have read about it, but i cannot find a workaround.

Thank you in advanced.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 04/20/2007 - 05:06
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The Device Discovery process will only move SNMP reachable devices into DCR for management by other applications. So, click on the number next to Device Discovery on the Campus Manager Homepage, and see what the status of the missing devices is. If the devices don't even show up there, check your discovery filters under Campus Manager > Admin > Device Discovery > Discovery Filters, and make sure hey are not being filtered out.

As for sm_server, this process is part of DFM. If it's taking 80% of the CPU it could be doing real work (i.e. polling devices for events, rediscovering devices, etc.) or there may be a problem. The first thing you should do is find out how many managed ports and interfaces are in DFM. To do that, run:

NMSROOT/objects/smarts/bin/sm_tpmgr -s DFM --sizes

The total number of ports+interfaces cannot exceed 45,000. The total number of ports+interfaces instrumented for connectivity or performance cannot exceed 6,750. If you find that you have more objects in DFM than is supported, you will need to disable auto-manage mode under DFM > Device Management > Device Selector, then remove some devices from DFM.


This Discussion