Ciscoworks DFM Devices Questioned

Answered Question

I've recently upgraded Ciscoworks LMS to version 3 from version 2.5. Since the upgrade, a majority of my DFM devices are categorized as "Questioned". I've tried rediscovering these devices and the problem remains. I've also tried deleting them by disabling the synchronization with the DCR and then deleting the devices without success. The deleted devices move to a pending state and then after many hours move back to being questioned. All of the devices in either a questioned or a pending state show an error message under "Data Collector Status Information" that reads "DataCollector request timeout(internal problem)". Any ideas / help?

Correct Answer by Joe Clarke about 9 years 7 months ago

Okay, looks like there are some DFM database problems. Let's reinitialize all of the DFM databases, and see if we get into a better place.


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmInv dmprefix=INV


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmFh dmprefix=FH


Then delete NMSROOT/objects/smarts/local/repos/icf/DFM.rps and DFM1.rps.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 11/15/2007 - 08:36
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Please post the output of pdshow.

Correct Answer
Joe Clarke Thu, 11/15/2007 - 09:07
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Okay, looks like there are some DFM database problems. Let's reinitialize all of the DFM databases, and see if we get into a better place.


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmInv dmprefix=INV


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmFh dmprefix=FH


Then delete NMSROOT/objects/smarts/local/repos/icf/DFM.rps and DFM1.rps.

gpellizzari Wed, 06/03/2009 - 02:11
User Badges:

I had the same problem with some newly added devices, the described process solved it in a few minutes (all devices are now known).

Many thanks from me as well.

Actions

This Discussion