cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
599
Views
0
Helpful
6
Replies

CW LMS 3.0: Device Discovery doesn't stop/work

rolf.fischer_2
Level 1
Level 1

Hi everybody,

we are using an 90-days evaluation version of LMS 3.0 as NMS in a temporary customer-network:

- 70 Switches

- cdp enable

- seed-devices are the core-switches

- ip-range is limited to the /24 mgmt-vlan

- "use default credentials" is enabled.

When I start Device Discovery in CS, the job runs eternally without finding new devices. Adding devices manually works.

Any ideas?

Thanks,

Rolf

6 Replies 6

Joe Clarke
Cisco Employee
Cisco Employee

What version of Campus Manager and Common Services do you have?

OS ist Windows 2003

Campus Manager: 5.0.4

Common Services: 3.1.1

Please post the CSDiscovery.log and NMSROOT/conf/csdiscovery/CSDiscovery-config.xml.

Here we go.

Strange: CSDiscovery.log has not been changed since 27.03.09.

Running Wireshark showed that nothing happens at all when I start Device Discovery.

After enabling debugging for Device Discovery the CSDiscovery.log contains now a lot of entries like the following:

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryUtil : getNMSROOT] : NMSROOT: d:\PROGRA~1\CSCOpx

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryJobUtil : processStatus] : [processStatus] Called!!

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryJobUtil : processStatus] : Executing jobCmd: d:\PROGRA~1\CSCOpx\bin\pdshow.cmd CSDiscovery

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryJobUtil : processStatus] : ErrorStream Line: ERROR: CSDiscovery is not a registered server name.Please enter a valid process/server name or check the case of the entered process/server name.

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryJobUtil : processStatus] : Job Command Response:

[ Sa Apr 18 09:01:53 GMT 2009 ] DEBUG [DiscoveryJobUtil : processStatus] : Exit

I don't understand the statement "CSDiscovery is not a registered server name" - what exactly do I have to do to "register CSDiscovery"?