What to do when a Primary ACS appliance fails within a Split ACS 5.6 deployment?

[3iron]

Hi All,

Could anyone offer advice on this scenario?

Environment: 2 x ACS 5.6 appliances
- Primary ACS Appliance (+Log collector)
- Secondary ACS Appliance 

Test process
1. Simulated network connection failure on Primary appliance
2. Test switch able to authenticate against Secondary appliance 
3. Able to login to Secondary - Read only, no administration function, unable to view logs as log collector also

If administration required what is the best option for the secondary appliance?
- Promote to primary?
- Request local mode?

Thanks

[3iron]

Over a year later i'm g00gle searching for the same thing and come across my post from last year haha!

Reading through the cisco doc it explains what the functionality does - but not when, i.e. scenario basis. If anyone is able to offer advice / previous experience on this scenario it would be very much appreciated!

Thanks

[3iron]

Ok after some searching I found cisco doc with a scenario reference:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/cisco_secure_access_control_system/5-6/user/guide/acsuserguide/admin_operations.html#75607

Scenario covered in failover section

"ACS 5.6 allows you to configure multiple ACS instances for a deployment scenario. Each deployment can have one primary and multiple secondary ACS servers.

Scenario: Primary ACS goes down in a Distributed deployment"

[vthaluru]

Hi Davies,

If primary goes down ,then we can promote any secondary server to primary .

Once promotion is completed ,then change the log collector to another server to see the logs .

Please let us know ,if you have any queries .

Thanks

VenkataKrishna

Please rate helpful posts and mark correct answers.