If the connection limit on the WAE is exceeded it will enter the TFO overload status and all subsequent TCP sessions will be placed in Pass Through (e.g. not attempted to be optimized).
When the WAE exits this condition by TCP connections closing on the end client or server then new TCP connections will be flagged for optimization.
While the 1st WAE is in the TFO overload condition if you had an intermediate WAE that was not in TFO overload it would flag the SYN packet for optimization per the normal TFO auto discovery process and if the server side or 3rd WAE was not in overload then this traffic could be optimized between WAE 2 and 3.
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...