The [tfo] warning is raised when the 'Asymmetric Client' or 'Asymmetric Server' counters in the 'sh stat tfo pass-through' command output are greater than zero. This is an indication that interception is not happening bi-directionally. You should verify that there are no network paths between the client and server with WCCP configured.
The [wafs] warning means that the WAFS Edge service is not able to connect to the WAFS Core service running on 10.104.192.3. You should verify that all of the WAFS services are started, and that there is nothing blocking communication between the devices on TCP port 4050 (the cisco-wafs port).
Regarding port 4050 for WAFS. Should I be able to telnet to each peer (edge-to-core and core-to-edge) on this port? If there is an issue on the WAE, how would I go about restarting or starting the dependant service?
I think the tfo warnings were leftover stats when we were configuring. Cleared up now.
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...