Secondary Cluster instance is inaccessible via Admin UI a couple days after clustering. Clustering is still good. This is occurring on two different environments. we found a document that stated, break the cluster and recluster. we have performed this action, but after a few days the 3rd instance in a Secondary Cluster configuration is not accessible.
The CAPAM_3.1.1.09 hotfix resolves an issue when CA PAM is left idle for over two days, the cached session expires, resulting in secondary node becoming inaccessible.