Forum Discussion
APM CRL checking
We have an active/passive cluster and run an automated script to update our CRL.
The short answer is that we found we needed to run the same script on both the active and the passive node separately.
A couple of points to note about this process: 1.) It is best to run the script on the passive node a few minutes after the active node rather than at the same time. We ran into issues with synching when we had the script running at the same time on each node if the passive ran a split second before the passive or vice versa.
2.) You will find that your nodes will show "Changes Pending" every time the script runs. I haven't found a way around that yet. As in I would like to be able to tell APM to ignore CRL file updates in the triggers to signify what a change is.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com