12-01-2016 04:25 AM - edited 03-11-2019 12:16 AM
Hello,
We have two ACS boxes running as a primary/secondary cluster which upon a minor access policy change which brought down a network access group authorization service.
Since then, we see that the either roles are presented with Primary Instance status wherein the supposedly Secondary node sees itself as Primary.
Any ideas why this could be and how to revert it back to Secondary role?
Thanks,
MSC
12-02-2016 02:38 AM
Hi,
A change made in primary will automatically replicate to secondary. Users authenticating against secondary will also be impacted by the same policy change.
As a case of showing both servers as primary. I would suggest to deregister secondary from deployment. Reload it and make it part of deployment.
Regards
Gagan
ps : rate if it helps!!!
12-02-2016 08:06 AM
Thank you Gagan.
I will try this on Monday and update
Regards,
Mariano
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide