I recently upgraded from lms 2.2 to lms 2.5. The program is running on a windows 2000 server w/sp.4.
When I look at the following:
-->Campus Manager --> Administration --Current Status:
-->Operation: Device Discovery
-->Last Completion Time: Device Discovery Timestamp
Information is not available.
You have not performed Device Discovery.
Results: 0 Devices
Action: Start Device Discovery
If I attempt to start a Device Discovery, I get a Warning that Device is already in progress! I finished the upgrade 2 days ago and the Device Discovery has been running ever since. Does anybody have any ideas why this hasn't completed yet? TIA
Results of pdshow:
State = Transient terminated
Pid = 0
RC = 0
Signo = 0
Start = 10/04/2005 07:00:00 AM
Stop = 10/04/2005 07:00:57 AM
Core = Not applicable
Info = Server started by admin request
I start the process and after a minute or so, the ProcessState indicates the following:
Anyone have an idea what this means?
That is not good. You might be running into bug id CSCsb21408
Can you attach your CSCOpx\campus\etc\cwsi\DeviceDiscovery.properties file
This looks good. It says that it started a new Device Discovery on 05 Oct 2005 at 11:00:01
I wonder if your discovery is simply taking too long and thus shows up as Running all the time
Try going to the discovery schedule and setting it to run only once per day, let's say 11:00
Then wait a while and see if the discovery ever completes
Open a TAC case, it is a known cisco bug. I had the same problem. Cisco has a patch for it, but you have to open a TAC case to get it resolved.
An update on what has transpired:
I received and installed the patch to fix Device Discovery. Now it is in an "idle" state and does not run when it is scheduled. In fact, it has never run. Back to the drawing board!
ok, then :
- save your campus topology map(campus\etc\users)
- uninstall campus manager
- reinstall campus manager and after sp2
I dont suppose you have authentication on the CiscoWorks installation to use ACS do you? Weve been using LMS 2.5 with ACS 3.3.2 and have the same problem unless we just use local logins and remove ACS authentication from the ciscoworks box.
**Im aware these two releases dont officialy work together and am waiting on the next IDU.
Try removing authentication to ACS if you have it configured and try then.