I understand once ACE determines which back-end load balanced server is getting tha packet based on the load balance algorithm, it then performs an implicit destination NAT that changes the dest address of the packet to that of the back-end server's. Does it also replace the client address with the VIP address?
By default, the original src.address is retained, when ACE forwards the packet to selected rserver.
You have the option of configuring client-nat on incoming client-requests, by which you're replacering the original src.ip with an ip, usually picked from the address-range of the outgoing ACE-interface. This can be done as either dynamic (PAT) or static NAT.
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...