In the previous case, what we found was that the CSS was sending back the SYN/ACK, but it wasn't being received by the Client. From memory it was being dropped somewhere upstream, and we suspected the firewall, but never fully got to the root cause of it.
If you raise a TAC case during the Australian shift (10am - 4pm Sydney Time or 00:00 - 06:00 GMT), I'll be happy to take a look in more detail and try to replicate in the lab again.
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...