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

DCR discovery

Hi,

I had a bit of trouble getting the DCR discovery to work in LMS 3.0 with Dec update and wanted to share the findings. Originally I had the LMS pupulated with the devices from a CSV file where I also inculded the MCS Call Managers that are not supported by LMS 3.0. When I enabled the DCR discovery (the new feature in the Dec update), it would run for 2 sec without discovering anything. In the debug log file it was showing exception on reaching the CCM hosts (I had "Use DCR as seed"). As soon as these CCM hosts were removed from DCR the discovery started working with no issues

10 REPLIES
Cisco Employee

Re: DCR discovery

What exception were you seeing? An unknown device in DCR should not cause discovery to abort.

Community Member

Re: DCR discovery

There was not much details on this, just the fragment below that gave some clues (the entire CSDiscovery.log just for a single discovery attempt was 130K):

[ Fri Dec 28 21:36:44 EST 2007 ] ERROR [CSDiscoveryAdaptor : constructDeviceInfo] : Exception while constructing Seed Device Info

from DCR device. mrkmccccm02: mrkmccccm02

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : getSeed] : [getSeed()] called .

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : getGlobalSeedDevices] : [getGlobalSeedDevices] No Global Seed Devices

set from File/GUI.

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : [putStatus()] called. com.cisco.nm.discovery.framework.i

nfo.DiscoveryProgressInfo@14df764

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : [putStatus()] called. com.cisco.nm.discovery.framework.i

nfo.DiscoveryProgressInfo@14df764

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : NGDDiscoveryStatus start time : 0

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : NGDDiscoveryStatus start time : 0

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : CS DiscoveryStatus start time : 0

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : CS DiscoveryStatus start time : 0

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : CS UNManaged Devices: 0

[ Fri Dec 28 21:36:44 EST 2007 ] DEBUG [CSDiscoveryAdaptor : putStatus] : CS UNManaged Devices: 0

Cisco Employee

Re: DCR discovery

What does the entry look like for this device from your import CSV file? How do you have discovery configured. I've tried a few things locally, but I am unable to reproduce this problem.

Cisco Employee

Re: DCR discovery

And compressing and attaching the entire CSDiscovery.log will be helpful.

Community Member

Re: DCR discovery

Actually I entered the MCS servers manually via Add Device and specified only RO community. The ZIPed CSDiscovery.log is attached

Cisco Employee

Re: DCR discovery

I think I found the bug. I have a patch you can try. You will need to open a TAC service request, and have the engineer contact me directly to get it.

Community Member

Re: DCR discovery

Thanks, so far it has been ok, I guess as long as I'm careful with adding the devices (to make sure they are supported / recognized by CS), all should be good

Cisco Employee

Re: DCR discovery

That's not the problem. The problem is hostname resolution. Any device that does not have an IP address in DCR will trigger a hostname lookup on the hostname value in DCR. If that fails, then discovery will fail. But it's worse than that. The domain name component is not taken into consideration. Therefore, if the short hostname fails to resolve, then discovery will fail.

The workaround is to make sure every entry in DCR has an IP address configured.

Community Member

Re: DCR discovery

You are right, all the routers / switches are configured in subdomain net.otn.local which is in the search path of resolv.conf; the CCM boxes are in otn.local, this domain is configured only as the domain name of the CW host Sun box in resolv.conf and not in the search path, apparently solaris does not try to search with its own domain name unless it is also in the search path.

Cisco Employee

Re: DCR discovery

I filed CSCsl99637 to track this issue.

150
Views
0
Helpful
10
Replies
CreatePlease to create content