transport of files from the CDM to CEs is an automated FTP process. CDM's calue add is that "content channels" can be created to allow an administrator manage which files get sent to which subset of remote CEs. Content delivery in this context is a proactive positioning of data anticipating requests for specific information. So SODA is a proactive push of relative content as close to anticipated users as possible providing greater quality/speed of acces/experience to content.
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...