Search this Blog

Thursday, December 10, 2009

CSDiscovery does not work


Issues with the CSDiscovery process in Common Services 3.3 running on Windows Server 2003. Somehow the process ignores what we have configured as discovery settings.
All that we have configured can been seen stored in the CSDiscovery-config.xml file. But discovery starts and stops immediately and does not discover a single device. Also the information on the summary page does not correspond to the one in the CSDiscovery-config.xml file.

Debugging options

  1. Discovery maintains multiple copies of this file. The file under NMSROOT/conf/csdiscovery is the one used for ad hoc discoveries.
  2. When you schedule a Discovery job, the current settings are copied to the job. However, when you modify the Discovery settings later on, the job config is not changed. Therefore, adjust the Discovery settings to your liking in the GUI, then delete all currently scheduled Discovery jobs. Then start a new Discovery, and see if it does what you want.
  3. The screens might reflect some old LMS 3.1 information. Try doing the following -
* Shutdown Daemon Manager
* Delete all files and directories under NMSROOT/MDC/tomcat/work/Standalone/localhost
* Restart Daemon Manager

4. To rule out any browser-cache related issues try viewing the discovery settings from a new client.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

No comments :

Post a Comment

 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */