Hi
I have had this on a 10.5.1.11001-49 cluster.
The work-around is great and a reload has cleared the issue, but are there any errors to look out for that clarify this as the bug and what are the fixed in versions?
Is there something in the Finesse log on process that forces the agent browser to accept the certificate of the 2nd server, despite the fact that it is not going to connect, unless there is a failure event?
Thanks.
