AnsweredAssumed Answered

Agents still trying to connect to old primary after promotion

Question asked by Ronald Beaulieu on Jul 10, 2018
Latest reply on Jul 11, 2018 by Jay Guillette

Our Primary SecurID Authentication Manager (8.2.1) died.

After promoting one of our replicas to Primary Status, many of our Unix/Linux based servers are still trying to connect only to the old Primary instance.


Even a Clear Node secret on the console does not work.


When we execute the acestatus on the agent, all we see in the list is the Primary. 


The only way to get it to work was to generate a new sdconf.rec file, delete all files on /var/ace use the new sdconf.rec and perform a clear node secret in the SC console.


Anyone have an idea on why we get this behaviour.


Thanks in advance.