Can you explain how Cisco is determining the core fan out ratios and how they size a WAE for a particular environment based on DRE size?
Its my understanding that the DRE cache values in the DRE database for optimized chunks are unique to each peer. Meaning that the chunking is not shared across multiple peers. So if you have 10 sites optimizing the same file at each site, the main core site DRE cache would represent that file 10 times in its database as 10 different chunks differentiated by what peer it came from. Is that the case? If so, why wouldn't or couldn't you share that information in the main core site cache to reduce DRE disk space utilization?
Cache architectures are designed to accomplish one or both of the following:
1 Application Response time improvement
2. Bandwidth reduction
Cisco WAAS is designed to provide both but with an emphasis on application optimization. If bandwidth reduction is primary goal, then with a single file store serving multiple peers the potential is there to increase response times. Hence WAAS point-to-point peering.
In terms of fan out, the WAVEs are intended for branch deployment offering Windows core application offload.
They are recommended for for Central Manager function, 274 supports 125 devices, 474 250, and 574 500
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...