DFM Device umanaged vs. managed

Unanswered Question
Jan 19th, 2010

I have unmanaged several interfaces in Ciscoworks and applied changes to make sure we do not get alerted.

Every now and then its seems as these interfaces are becoming in a managed state, why is that?

The version of DFM i'm running is 3.2.0 on LMS 3.2


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Sat, 01/23/2010 - 09:26

They shouldn't.  A bug was filed against DFM 3.1 regarding this, but it was fixed in 3.2.  Be sure you have applied dfm3.2-sol-CSCta56151.tar from http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=3.2.0&mdfid=282640771&sftType=CiscoWorks+Device+Fault+Manager+Patches&optPlat=Solaris&nodecount=2&edesignator=null&modelName=CiscoWorks+Device+Fault+Manager+3.2&treeMdfId=268439477&treeName=Network+Management&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y and that should give you all of the available fixes on the EMC side.  Then, with a port unmanaged, run a device rediscovery in DFM, and confirm the port is still unmanaged.


This Discussion