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
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.
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.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...