04-16-2012 07:21 AM
Hi,
Does anybody know why this same kind of bug/error/software fault exist in LMS 4.2 as it was in LMS 3.2 ? Why after a while after discovery of devices (state is "Known") DFM drops the state of devices to "Learning" and it stucks forever. Restarting of daemon manager helps for a short time. It looks like the processing of faults stops a while after discovery is complete.
LMS 4.2 is running on Solaris 10, connected to other LMS in DCR Slave configuration.