Discovery problems with DFM 3.0

Unanswered Question
Jan 7th, 2008
User Badges:

Hi friends.

I have DFM 3.0, and I'm having problems to discover devices, all of them (switchs, routers, AP, ETC) stay in "Learning" state. I don't have problems with the others modules. I've checked the devices credentials and It's OK.

This is an example:


IP Address = 10.101.0.11

DNS Name = 10.101.0.11

Device Status = Learning

Device Type = N/A

Aliases = N/A

Containments = N/A

DFM Processing = N/A

Time Last Discovered = N/A

Import Time Stamp = 26-Dec-2007 07:26:24


*** Data Collector Status Information ***

Discovery Progress = 10% completed

Error Code = N/A

Error Message = N/A







  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Joe Clarke Mon, 01/07/2008 - 09:57
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

On what platform is LMS installed?

Joe Clarke Mon, 01/07/2008 - 10:04
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I meant installed on Windows or Solaris.

Joe Clarke Mon, 01/07/2008 - 10:26
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Do you have .NET 2.0 SP1 installed on this server?

Joe Clarke Mon, 01/07/2008 - 11:03
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

A learning state of 10% implies a problem with the DfmServer processes. Please post the output of pdshow as well as the number of sm_server, sm_authority, and brstart processes running. Also, post the NMSROOT\objects\smarts\local\logs\brstart.log, DFM.log, and DFM1.log.

Joe Clarke Mon, 01/07/2008 - 11:31
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The pdshow.txt file is actually an IOS config snippet. Please repost the pdshow. Also, please provide the output of:


NMSROOT\bin\perl NMSROOT\bin\resolver.pl


Where is the fully-qualified domain name of this server as seen under My Computer > Properties > Computer Name > Full computer name

Pablo Martin Avalos Mon, 01/07/2008 - 11:50
User Badges:

OK, here is the output and the pdshow:


C:\Program Files\CSCOpx\bin>perl C:\PROGRA~1\CSCOpx\bin\resolver.pl arpalnet03

Original name: arpalnet03

Hostnames/IP Addresses:

arpalnet03/10.101.5.211





Attachment: 
Joe Clarke Mon, 01/07/2008 - 11:56
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Nothing problematic so far. Please post the contents of the NMSROOT\log\dfmLogs\TIS and cfi directories. You will need to compress these.

Joe Clarke Tue, 01/08/2008 - 11:11
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

I do not see any recent errors in these logs that would account for this problem. In fact, the only thing that troubles me so far is that the server is configured for a non-US English locale which is not supported.


There is some additional debugging that can be enabled, but it is not straight-forward, and it would be better for you to work with TAC to enable this in case something goes wrong.

chharris41 Mon, 01/07/2008 - 11:02
User Badges:

I am having this same issue, some devices are "known", others are "learning" and others are "unknown". I've tried deleting/re-adding, increasing SNMP timeout, etc. I opened a TAC case and so far not much help there. TAC did not mention anything about .NET 2.0 SP1 - is that a requirement for DFM?? I am running LMS 3.0 with Windows 2003 Server SP2.

Joe Clarke Mon, 01/07/2008 - 11:05
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

There is a known bug if .NET 2.0 SP1 is installed on the server (it will be found under the Add/Remove Programs control panel). If it is installed, newly added devices will hang at 10%, and DFM will not work. The workaround is to uninstall .Net 2.0 SP1 from the Add/Remove Programs control panel, and restart dmgtd.

chharris41 Tue, 01/08/2008 - 09:22
User Badges:

J,


I don't have .NET 2.0 SP1 installed on my server. I am stuck on this issue, I was able to delete/rediscover the devices and initially all devices were in known state. Since then (few days ago), 200 devices have gone back into "questioned" state while 93 remain known. Any idea of what could be happening here?

chharris41 Tue, 01/08/2008 - 14:52
User Badges:

J,


I looked at the server and I see hundreds of entries in the event view like this:


The description for Event ID ( 16640 ) in Source ( InCharge ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [08-Jan-2008 9:35:34 AM+704ms] [email protected] Discovery #8

ADTM-E-AD_EACCESSADDRESS-While discovering 'Willow_6504_2', Qualified access

address not found



I have this entry for every device that is questioned (approx 200 devices). Can you tell what this might relate to?


Joe Clarke Wed, 01/09/2008 - 11:37
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This error comes from the EMC side of DFM, so I do not know for certain, but it sounds like Willow_6504_2 is not a resolvable hostname. You should raise this with your TAC engineer, and have them follow up with developers to get an exact meaning.

mrguitar Wed, 01/30/2008 - 11:25
User Badges:

Did you ever find a resolution to this issue? If so, can you please let me know what it is? I'm having the same issue.

pieterddejong Mon, 06/01/2009 - 22:31
User Badges:

Hi,


I have the exact same issue. Let me know if you found a fix please?


Thanks

Actions

This Discussion