Urgent -- LMS 3.1 discovery

Answered Question
Sep 11th, 2009

I have LMS 3.1 on win 2003 R2 standard edition with sp2. It is working in AAA mode. When I am trying to go to CS-> device & credential, next page is not opening ... As a result i am not able to run discovery.

Why it is happening and from where I can get log related to such problem.

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 7 years 2 months ago

Devices will appear unreachable to discovery if the SNMP credentials you configured in Discovery are wrong. Double-check that you have entered the correct SNMP credentials for those unreachable devices.

Yes, you need to start a new thread for IPM.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
pradip.saha Fri, 09/11/2009 - 10:13

after clicking on device discovery within device & credential option, discovery summary page is not comming. I waiting for an hour or more. then it is giving page cannot be displayed. so, i am not able to provide seed info and start discovery.

Joe Clarke Fri, 09/11/2009 - 15:49

Post screenshots of the Services control panel showing all of the CiscoWorks services.

Joe Clarke Fri, 09/11/2009 - 21:17

You've set all of the CiscoWorks services to be Automatic. This is wrong, and will break LMS. You need to set the following services back to Manual start, then reboot:

CiscoWorks ANI database engine

CiscoWorks RME NG database engine

CiscoWorks Tomcat Servlet Engine

CiscoWorks Web Server

CWAWFEngine database engine

CWCS Cmf database engine

DFM dfmEpm database engine

DFM dfmFh database engine

DFM dfmInv database engine

IPM NG database engine

You also need to disable Kiwi as it is interfering with the syslog daemon that is included with LMS.

pradip.saha Fri, 09/11/2009 - 23:22

Made specified services as manual start. Disabled Kiwi. Restarted daemon manager. Also rebooted the server. But the problem persists.

Joe Clarke Sat, 09/12/2009 - 08:43

Post the new pdshow output, the CSDiscovery.log, and the list of contents under NMSROOT/conf/csdiscovery.

Joe Clarke Sat, 09/12/2009 - 12:34

Delete the NMSROOT/conf/csdiscovery/DiscoveryStatusObj file, then try and launch the Discovery configuration page.

pradip.saha Sun, 09/13/2009 - 10:12

gr8.. Yes clarke.. I am able to get into the discovery config page and start discovery.

But after the discovery is complete, in summary page it is showing all the discovered devices as unreachable. Whereas I am able to ping all those discovered devices from server CLI. I want to know why this is happening. Also I am not able to get IPM reports. I dont have HUM. What are the reports can I get at max. Do I need to open another discussion for this or can we continue.

Actually I am taking control of the server via remote connection (RDP). hence I am late to reply. Currently I am not getting remote connectivity. I will be back soon.

Correct Answer
Joe Clarke Sun, 09/13/2009 - 10:45

Devices will appear unreachable to discovery if the SNMP credentials you configured in Discovery are wrong. Double-check that you have entered the correct SNMP credentials for those unreachable devices.

Yes, you need to start a new thread for IPM.

Actions

This Discussion