We are running the latest code of WAAS and what I want to do is have all edge locations act as core as well. We have 10 locations and each location has critical servers that need to communicate (ie. file replication) with each other. I understand this isn't the intended "design" of this product, but has anyone else deployed it this way? Currently, the CIFS optimization is only working from edge to core. I did add core services to the edge device but it still isn't working.
It's definitely capable of doing that. Even without the WAFS services, you should still see significant improvements with TFO, DRE and LZ.
If you are running core and edge services on a WAE, you need at least 2 GB of RAM on the box. Then you need to add connectivity statements between the new cores and respective edges that you want to optimize between.
I have the connectivity setup in both directions with the bandwidth and low round trip time configured, We have4 gb memory and its still not working from core to edge. Do I need to configure the core WAAS with edge services?
Strange, I have both edge and core configured as core/edge and the configs are basically identical (each is in its own device group), but still the file copy when initiated from the core side is not optimized. Any other thoughts? I have rebooted all devices as well.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
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
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...