LMS 4.2 - DFM devices stuck in "Learning" state

[tomeq82]

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.

[Michel Hegeraat]

The connection between the ciscoworks GUI and the DFM repository is not 'optimal', or something like that. It's complicated.

What could cause the behavior you mention however, is either someone rediscovering devices that are still in learning state, or the presence of multiple active rediscovery schedules.

You may even delete all schedules excepts the default redisovery schedule which you can/should suspend. If the problem then stays away you know what caused it.

At this stage any device that really changes must be rediscoverd in DFM manually.

I think Admin -> Fault takes you to a page showing the schedule, if not lookup 'fault rediscovery schedule' in the help.

Cheers,

Michel