This is not quite what I am trying to achieve. Using the sticky option on the backup serverfarm will only ensure all existing (sticky) connections are load balanced to the backup serverfarm after the primary serverfarm is up again.
My requirement is that server(farm) A (which was originally the "primary" server) should not receive traffic until server(farm) B goes down. Not even new connections.
I.e: All traffic is sent to A until A fails. Then all traffic will be sent to B until B fails. Then all traffic will be sent to A until it fails, etc.
Note that I do not necessarily need to use a "primary/backup serverfarm" approach. Any configuration achieving the desired functionality will do :-)
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...