device discovery seems to freeze

Unanswered Question
Feb 4th, 2010
User Badges:


Sometimes it's seems that my device discovery freeze...

(the job never ends, always showing running...

sometimes device discovery was started 1 day before and it's still showing ..running...

that is not normal.... i try to stop the discovery with the interface and it doesn't work too.

i need to reboot to start another discovery.

I am using LMS 3.1

Can you help me on this


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Martin Ermel Thu, 02/04/2010 - 16:33
User Badges:
  • Blue, 1500 points or more

It seems you are seeing BugID CSCsv42110:


CSCsv42110 Bug Details

Discovery hangs sproadically


CSDiscovery does not finish and keeps hanging


CS 3.2




According to jclarke it is fixed in LMS 3.2 - and TAC should have a patch for LMS 3.1

Even if you cannot stop discovery from within the GUI, you should be able to stop it by executing

     pdterm CSDiscovery

form the command line (Dos - Box or solaris shell) without restarting LMS or  rebooting the server

desrochj1 Fri, 02/05/2010 - 08:10
User Badges:

In Common services, i see that i have Ciscoworks LMS 3.1

and Common Services is at 3.2.0

Do i need to upgrade to LMS 3.2, even if common services module  is at 3.2.0 ?

Martin Ermel Fri, 02/05/2010 - 08:58
User Badges:
  • Blue, 1500 points or more

Common Services (CS) 3.2 is not the same as LMS 3.2. Each application in LMS does have its own version number;

LMS 3.1 does have CS 3.2

LMS 3.2 does have CS 3.3

You have 2 options, open a Service Request with Cisco TAC to get the patch or update your LMS version from LMS 3.1 to 3.2. You can download LMS here:

then click on "Download Evaluation Software"

to get the DVD media, enter your service contract number here:

your current License does work for LMS 3.2

desrochj1 Tue, 02/09/2010 - 08:08
User Badges:


can i install lms 3.2 directly on top of lms 3.1 (execute


Martin Ermel Tue, 02/09/2010 - 09:34
User Badges:
  • Blue, 1500 points or more

yes you can ..
It is always a good practice to make a backup of the current installation before starting the update;
Depending on the size of the network and the customizations you have yet done you could also consider an uninstallation and starting from scratch (LMS 3.2 is a full version).

these are the typical steps to perform an upgrade:
- make a backup
- stop the processes (/etc/init.d/dmgtd stop)
- verify that there is no process running (ps -ef | grep -i CSCO)
- verif that all necessary solaris patches are installed on the system as mentioned here:

- execute the


This Discussion