Device Discovery always "running"

riko.arizona · ‎01-13-2009

My LMS version is 3.01, running on windows system. I run Device Discovery, but the status always running. I have try pdterm CSDiscovery, restart LMS service. File ngdiscovery.log and discover.log shows 0 kb.

Jeroen Tebbens · ‎01-13-2009

We experience the same issue with CWLMS 3.1

Although we see this in CSDiscovery.log:

log4j:WARN No appenders could be found for logger (com.cisco.nm.csdiscovery.CSDiscoveryManager).

log4j:WARN Please initialize the log4j system properly.

[ di jan 13 12:23:57 CET 2009 ] FATAL [CSDiscoveryManager : stopDiscovery] : Exception occured during stop discovery in CS.

Reason : Discovery is not running

com.cisco.nm.csdiscovery.CSDiscoveryException: Exception occured during stop discovery in CS.

Reason : Discovery is not running

dany.datacraft · ‎01-14-2009

I had similar problem before. You may want to check the snmp timeout and retry settings.

Jeroen Tebbens · ‎01-15-2009

Fixed it by moving the seed devices from the global options to the CDP module in the discovery settings. CDP module was empty (no seed devices) but the checkbox for using the DCR as seed list doesn't seem to work.

So it hadn't anything to do with the snmp settings and timeouts. I recon this is a bug because these settings worked in 3.0.1.