Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Device Discovery

Our CW LMS 2.6 is integrated with ACS 4.0.

All devices in LMS have been imported from ACS by BlunkImport. But device discovery does not see any device.

DeviceDicovery.log

Unable to open debug file: D:\log\discovery.log

Instead Messages will be now logged to the file in the NMSROOT location: C:\PROGRA~1\CSCOpx\log\discovery.log

MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DeviceDiscovery.properties

messages will be logged to file: D:\log\discovery.log

discovery.log

2007/09/04 11:00:01 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties

2007/09/04 11:00:01 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties

2007/09/04 11:00:01 main MESSAGE DBConnection: Created new Database connection [hashCode = 3456720]

Common trust user is: admin

User name in Security context is: admin

log4j:ERROR No appenders could be found for category (CTM.common).

log4j:ERROR Please initialize the log4j system properly.

2007/09/04 11:00:02 main MESSAGE DCRDevWrapper: Fetching DCRDeviceIDs

com.cisco.nm.dcr.DCRException: Authorization Failed

at com.cisco.nm.dcr.LocalDCR.getDeviceIdentifiers(Unknown Source)

at com.cisco.nm.dcr.DCRProxy.getDeviceIdentifiers_DIRECT(Unknown Source)

at com.cisco.nm.dcr.DCRProxy.getDeviceIdentifiers(Unknown Source)

at com.cisco.nm.ani.server.devdiscovery.DCRDevWrapper.getDCRDeviceIDs(DCRDevWrapper.java:488)

at com.cisco.nm.ani.server.devdiscovery.DCRDevWrapper.getDevicesFrmDCR(DCRDevWrapper.java:584)

at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFCreateSeedDevice.apply(DevdiscoverySMFCreateSeedDevice.java:98)

at com.cisco.nm.ani.server.framework.EvalSMFApply.apply(EvalSMFApply.java:93)

at com.cisco.nm.ani.server.frontend.EvalGroup.executeMajorNode(EvalGroup.java:578)

at com.cisco.nm.ani.server.frontend.EvalGroup.apply(EvalGroup.java:655)

at com.cisco.nm.ani.server.frontend.EvalGroup.apply(EvalGroup.java:611)

at com.cisco.nm.ani.server.devdiscovery.DiscoveryMain.performScheduleFunction(DiscoveryMain.java:207)

at com.cisco.nm.ani.server.devdiscovery.DiscoveryMain.main(DiscoveryMain.java:51)

2007/09/04 11:00:07 main WARNING DCRDevWrapper: Got DCRException in getDeviceIDs() Authorization Failed

2007/09/04 11:00:07 main WARNING DCRDevWrapper: Zero Devices found in DCR

2007/09/04 11:00:26 EvalTask-Devdiscovery-15 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.20.177 will not remap SMFFactory

2007/09/04 11:01:31 DBConnecton-Reaper MESSAGE DBConnection: Closed Database connection [hashCode = 3456720]

2007/09/04 11:31:38 EvalTask-Devdiscovery-38 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.17.9 will not remap SMFFactory

2007/09/04 11:32:23 EvalTask-Devdiscovery-44 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.17.22 will not remap SMFFactory

2007/09/04 11:32:23 main ERROR DevdiscoverySMFEnd: Error in add Device: Authorization Failed

2007/09/04 11:32:23 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties

2007/09/04 11:32:23 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties

2007/09/04 11:32:23 main MESSAGE DCRDevWrapper: Closing DCRProxy

2007/09/04 11:32:23 main MESSAGE DBConnection: Created new Database connection [hashCode = 1581629]

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Device Discovery

You should not touch the CiscoWorks Windows services unless explicitly asked to do so by TAC. Under normal operation, those services will work without any user intervention.

5 REPLIES
Cisco Employee

Re: Device Discovery

Given the authorization error, it looks like your System Identity User, admin, is not properly configured in ACS. The System Identity User MUST have all rights to all components in LMS. So check admin's group configuration in ACS, and make sure that each CiscoWorks application is assigned a role with full access rights. This means you will need to createa custom role for each CiscoWorks application (e.g. call in Superuser).

New Member

Re: Device Discovery

It is possible to change the System Identity User on Services menu (Microsoft Windows)?

Can you send me a list of services for each CW component? Can you send me a list (web link) of services for each CW component?

Thanks

Cisco Employee

Re: Device Discovery

No, the System Identity User must be changed within LMS under Common Services > Server > Security > System Identity Setup.

I'm not sure I understand the second question. To which services do you refer?

New Member

Re: Device Discovery

I have thought that it is necessary to replace user under which CM services in Microsoft Windows are started.

Cisco Employee

Re: Device Discovery

You should not touch the CiscoWorks Windows services unless explicitly asked to do so by TAC. Under normal operation, those services will work without any user intervention.

268
Views
4
Helpful
5
Replies
CreatePlease login to create content