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.
This document covers the important troubleshooting data to be collected and data collection procedures when you experience an issue with ACI fabric. The collection of the relevant troubleshooting data is very critical to root cause the issue and...
There are certain situations in where an On-Demand Techsupport is not able to be performed. In such cases, a local techsupport can be collected instead for either the APIC or an ACI switch. This document outlines this...
Webcast: Evolution of Data Center: From Classic Ethernet to VXLAN
(Live Webcast Tuesday May 15, 2018 at 10 am Pacific/ 1 pm Eastern / 7 pm Paris)
Register today for this live Cisco Support Community webcast.