You are correct. Although preempt may also play a role. If you do not specify a priority and peer priority, then the default value will be 10 for both. The first one up will be active. When the second ACE comes up, it will only become active for that context if it has a higher priority and preempt is enabled (which it is by default).
I would recommend manually configuring the priority and peer priority of each context within the respective FT group, so that your active an standby will be more predictable. If it does not matter to you which ACE is active, then you can make it even more predictable by disabling preempt with the no preempt command in the FT group. However, if you are going to use tracking (ie. interface, host, gateway), then you will need to leave preempt enabled.
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...