After reading what GRE return is, and assuming I actually understook what it was talking about. We didnt plan on using that. We were going to just setup a subinterface on our routers to connect the WAAS hardware.
We have a total of 14 sites including the two data centers. We have DS3 45Mbps at the data centers, and currently 1.5Mbps at each branch location. Latency varies, but is normally around 35ms with spikes of 1200ms durring heavy traffic.
The major issue we would be trying to address is slow file access at the branches, and issues when deploying software(again file access), computer startup(more files being accessed while scripts, and GPO's are applied).
We also want to improve the application performance of our business software. Its just normal TCP traffic but I cannot go into details about what applications those are here.
Thanks for the follow up. I would consider one of the Data Center appliances (WAE-7341 or WAE-7471) for the head end. The subsystems on these devices are tuned for aggregating numerous remote sites, and will give you better long-term scalability potential.
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...