We have several version 3.5 Dude Agents deployed in a distributed system (one per POP). From time to time, they appear to disconnect from the main Dude server.
In each case, I have found that the Dude Agent configuration is lost. After a power failure for example. I once thought that a recycle of the router after setting the configuration would correct the problem. This is not the case.
When logging back into the Agent with Dude client, the initial discovery screen also appears as it does after a fresh install.
Is anyone else seeing this issue?
Thanks!
Marc