×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

LMS 3.0 and DFM

Unanswered Question
Feb 25th, 2008
User Badges:

Something is wrong with the DFM (again), all the devices (>600) but 5 went into Questionable state, however the DFM is still reporting the events / alarms as before. The attempts to rediscover the questionable devices did not make any difference. I guess I'm looking at another DB cleanup. Awhile ago tried a fix for CSCsi01966 (stop the LMS and delete the dfm.rps and dfm1.rps and start it again and do rediscovery), all the devices (even the ones that were knowingly down) went into the Known state, however all the events / alarms stopped. Had to reinitialize the DB

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Mon, 02/25/2008 - 18:15
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

We've been having all sorts of problems with DFM lately. There are some DLL conflict issues that arise with .NET 2.0 SP1 and higher as well as versions of msvcm80.dll, msvcp80.dll, and msvcr80.dll newer than 8.00.50727.42. If you have any of those on your system, you will need to remove them and reboot.


Something else that could cause all devices to become Questioned is if you unmanaged the interface or IP address by which the devices are managed. We had one customer do this using the new bulk manage scripts. The only solution to get things going again in this case was to reinit the three DFM Sybase databases as well as delete the .rps files.

dmitry Tue, 02/26/2008 - 06:26
User Badges:

Thanks for the follow-up, in fact I did the bulk unmanage of the IPs that are not reachable by the LMS server but I'm 100% sure did not touch the management IPs. Will do the DB init

markusspitzli Wed, 02/27/2008 - 00:10
User Badges:

Well, We have also the problem that DFM doesn't work properly and we have installed a newer version of those libraries (msvcm80.dll, msvcp80.dll, and msvcr80.dll) but we can't remove them.


which application needs those dlls? osagent.exe? is it possible to bypass the latest dll and use those we need?

-> http://blog.kalmbachnet.de/?postid=80

Joe Clarke Wed, 02/27/2008 - 10:06
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

We only install the .42 versions. If you cannot remove the software that installs the newer versions, then you will need to wait for the patch which will resolve the conflict. IT would be best to open a TAC service request at this point so you can be notified when the patch is available.

markusspitzli Wed, 02/27/2008 - 23:13
User Badges:

Isn't there a workaround for it until the patch is available? Usually it takes very long until a patch (or a device package) is released.

Joe Clarke Wed, 02/27/2008 - 23:47
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The only reliable workaround is to remove the software that installs the conflicting DLLs. We are hoping for a patch in the next week.

Actions

This Discussion